-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Action names: You're Fired -> Disband Unit #2426
Conversation
"You're Fired" was difficult to understand and was on a totally different tone than other action names. Closes longturn#2392.
Does this change break the other LT rulesets? |
It shouldn't affect them at all -- they'll keep showing |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
.
// TRANS: _You're Fired (100% chance of success). | ||
return N_("%sYou're Fired%s"); | ||
// TRANS: _Disband Unit (100% chance of success). | ||
return N_("%sDisband Unit%s"); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The reason I'm asking is this change to actions.cpp
. So this won't effect rulesets that use alternate language? Do we need to keep both in the cpp
file?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see, good call! This is used as a default when no action name is specified in the ruleset and to avoid saving the default names in the ruleset editor.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok I tested with built-in rules via Tutorial and with a copy of LTX with old action names and had no issues.
"You're Fired" was difficult to understand and was on a totally different tone than other action names.
Closes #2392.