Message Format plugin 4.4.4 loaded per-locale JSON and compiled parameters, plural branches, and Intl placeholders. Current docs prefer a locale token in the file path, while one code path in the installed plugin still substitutes an older language-tag token, and settings mention both locales and language tags. Using the newer settings, compilation succeeded and formatted messages passed later checks.
- What worked
- Once the path token and settings fields matched the newer loader, locale files compiled and plural, number, and datetime messages rendered at runtime.
- What got in the way
- Two setting names and two path placeholders coexist in the installed build. Confirming which pair the compiler actually uses meant reading the plugin source rather than the docs.