Messages Language Mapping
File:mods/Zuxaw_RPGLeveling/MessagesLanguageMapping.json
This file contains all translatable text strings for the plugin. It was renamed from messages.json in version 0.2.0.
Overview
The file supports full localization and includes messages for:- Stat names and descriptions - Health, Stamina, Damage, Defense, etc.
- HUD messages - Level, XP progress, zone names
- GUI labels and buttons - Stat allocation, navigation, confirmations
- Error messages - Invalid commands, permission errors
- Notification messages - Level up, stat allocation, system messages
- Command descriptions and responses - Help text, feedback messages
Translation Support
The plugin uses this file to support multiple languages. You can create a full translation by editing all text strings in this file.Supported Languages
Any language can be supported by editing the text strings. Common translations include:- English (default)
- French
- Spanish
- German
- Portuguese
- Russian
- Japanese
- Chinese
- And more…
File Structure
The file is organized into logical sections:Common Message Keys
Stat Names
Stat Descriptions
HUD Messages
GUI Labels
Notifications
Command Messages
Example Translation (French)
Here’s an example of a partial French translation:Placeholders
Many messages support placeholders that are replaced with dynamic values:| Placeholder | Description | Example |
|---|---|---|
{level} | Player level | ”You are now level 50” |
{points} | Stat points | ”Available: 15 points” |
{stat} | Stat name | ”Allocated to Damage” |
{current} | Current XP | ”1250 / 2000” |
{required} | Required XP | ”1250 / 2000” |
{min} | Min level | ”Zone 2 (Lvl 25–50)“ |
{max} | Max level | ”Zone 2 (Lvl 25–50)“ |
{id} | Zone/instance ID | ”Zone 3” |
Creating a Translation
To create a full translation:- Copy the default
MessagesLanguageMapping.jsonfile - Translate all text strings to your target language
- Keep the JSON structure intact (don’t change keys, only values)
- Test in-game to ensure all messages display correctly
- Share your translation with the community!
Formatting Tips
- Keep placeholders intact -
{level},{points}, etc. must remain as-is - Maintain similar length - Very long translations may not fit in UI elements
- Use consistent terminology - Use the same word for “level”, “stat”, etc. throughout
- Test thoroughly - Check HUD, GUI, commands, and notifications
See Also
- Configuration Overview - All config files
- Translation Guide - Detailed translation instructions
- Features - List of all stats and features to translate
