-
Notifications
You must be signed in to change notification settings - Fork 35
Translations
Quests has a language file which is located at /plugins/Quests/lang/en.yml by default. This YAML document can be edited at your discretion, whether it remain English-language or translated to something of your choice. However, it is recommended that you copy/paste a new file if you plan on editing the entire file. You can then rename the file (e.g. from "en.yml" to "fr.yml") and change the 'language' setting in config.yml to the name of your new language file.
As of Quests 2.2.2, new language strings will sometimes be added to a new file in the same folder as your language file when you update Quests. This file will be named similarly to your current file, but with "_new" appended at the end of the name (for example, "en_new.yml" or "fr_new.yml"). Simply copy the strings from this new file into your current one.
If you are using the default "en.yml" language file, you may also simply delete the file and allow Quests to create a new one with the updated strings next time the server is started.
Here are some tips to follow when editing the language file:
- Keep the double quotation marks on the ends of each translation
- Do not use double quotation marks in any of your translations or you will likely break them. You can use single quotes however.
- Do not change anything in < >'s. This is special data that later gets replaced by something else when the translation is accessed. You are welcome to move it around, but do not modify it in any way. Example: " has forcibly started the Quest ." You could modify this to something like: "The Quest has been given to player " but do not remove/change the things in the < >'s. Regular brackets and parentheses are okay though [ ] ( ), those are just for show.
- All of the Quests command translations are prefixed with COMMAND_ and are in all caps. You can change the specific Quests commands like list, take and quit, but you cannot change the /quests, /quest and /questadmin commands to anything else. Make sure to change the help displays for each of them if you change them.
- If you change the 'cmdCancel', 'cmdClear' etc. translations, make sure to change the translations that have things like "or enter 'cancel' to return" to match your new cancel command.
- Things that are lowercase are meant to be that way for formatting purposes. You can change it to uppercase if you want but it won't look pretty afterwards.
You may put any of the following formatting tokens into your language files.
- %br% - Line break
- %tab% - Tab character
- %rtr% - Return carriage character
- %bold% - Bold chat color
- %italic% - Italic chat color
- %underline% - Underline chat color
- %strikethrough% - Strike-through chat color
- %magic% - Magic (end text) chat color
- %reset% - Reset formatting
- %white% - White chat color
- %black% - Black chat color
- %aqua% - Aqua chat color
- %darkaqua% - Dark aqua chat color
- %blue% - Blue chat color
- %darkblue% - Dark blue chat color
- %gold% - Gold chat color
- %gray% - Gray chat color
- %darkgray% - Dark gray chat color
- %pink% - Pink (light purple) chat color
- %purple% - Purple (dark purple) chat color
- %green% - Green chat color
- %darkgreen% - Dark green chat color
- %red% - Red chat color
- %darkred% - Dark red chat color
- %yellow% - Yellow chat color
If you are ever unsure about whether or not your edits are correct, or you receive errors on startup, try using an online YAML parser to check your language file. One such parser can be found here.