# Check Rust plugin message placeholders after an update

[Rust server guides](https://rustsc.com/learn/index.html.md) / [Configuration](https://rustsc.com/learn/configuration/index.html.md)

A language file can load successfully while a message shows a placeholder or puts values in the wrong order. Use a small action with known values in two supported languages and read what each tester actually sees.

## Choose a message whose values are easy to check

For example, a test shop message tells a player how many points remain after a purchase. Use a private world with test balances. Find the entry the current plugin version registers, then compare the same entry in the default language file and your translated file. Oxide stores its default language files under oxide/lang, with a folder for each language.

Keep every placeholder the new version expects. A token such as {0} is part of the plugin's formatting. Find what it stands for in the author's documentation or current example before moving it in a sentence. If the new defaults add or change a token, update the translated entry to match the new inputs.

## Observe two languages and two values

Have each tester select a locale as supported by the plugin or framework. Keep other permissions and actions the same.

| Try | Expected output |
| --- | --- |
| Default language with the known test balance | The right amount in the expected message, with no unfilled token. |
| Translated language with the same test values | The intended translation and the same correct amount. |
| One more action with a different value | The text changes only where the new amount belongs. A named placeholder still refers to the expected field. |
| Restart and repeat one translated action | The correct language and values appear again. |

## Keep the failing line usable

If you get the default language, check how the version chooses a language and whether it found your file and key. If a token appears literally, compare the entry against the current version. Send the maintainer the message key, the two results and the synthetic input values if you need help.

## Sources

- [Oxide data storage and language formatting examples](https://docs.oxidemod.com/guides/developers/data-storage)
- [JSON strings in RFC 8259](https://www.rfc-editor.org/rfc/rfc8259)

## Related resources

- [Change the messages players see from an Oxide plugin](https://rustsc.com/learn/configuration/change-player-facing-rust-plugin-messages/index.html.md)
- [Which Rust plugin settings should survive an update?](https://rustsc.com/learn/configuration/compare-rust-plugin-defaults-before-keeping-your-settings/index.html.md)

---

HTML version: https://rustsc.com/learn/configuration/test-rust-plugin-language-placeholders-in-game/
