The goal is to migrate all strings (command responses, match configuration questions and etc) to the en-US locale (which is the default).
Some strings are already in the locale but are still hardcoded and are not getting from the main locale (en-US), they also need to be changed in the code to the i18next format.
Exemple:
t("commands:bio:noBio")
Exemple JSON:
// commands.json
"bio": {
"commandDescription": "Change your profile bio.",
"changedBio": "Your profile bio has been updated.",
"noBio": "It looks like you didn't specify your new bio/about, fix it and use the command again!"
}
All commands must have a value called commandDescription, this will be used in the help command.
If you want to contribute and have any questions, feel free to ask on the support server in the #dev-talk text channel.https://discord.gg/gBd6hTMDmq
This issue is good for contributors.
The goal is to migrate all strings (command responses, match configuration questions and etc) to the en-US locale (which is the default).
Some strings are already in the locale but are still hardcoded and are not getting from the main locale (en-US), they also need to be changed in the code to the i18next format.
Exemple:
t("commands:bio:noBio")
Exemple JSON:
All commands must have a value called
commandDescription
, this will be used in the help command.If you want to contribute and have any questions, feel free to ask on the support server in the
#dev-talk
text channel. https://discord.gg/gBd6hTMDmqPending strings
Commands
File: https://github.com/RitsuProject/ritsu-v3/blob/main/src/locales/en-US/commands.json
t("commands:...")
Match Settings
File: https://github.com/RitsuProject/ritsu-v3/blob/main/src/locales/en-US/gameQuestions.json
t("gameQuestions:...")
Strings that are already in the locale but still hardcoded.
Match Settings