We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the bug Analysis Visor main tech and the upgrades all have the same name, making it difficult especially for screen readers.
To Reproduce Steps to reproduce the behavior:
Expected behavior Upgrades should be named "Scanner Module" (UP_SCANNER1_NAME_L) for additional clarity.
Screenshots
Logs No logs required.
Please complete the following information:
Additional context Class indication in text form would be nice, but hard to localise since the game doesn't use the classes in the name either.
The text was updated successfully, but these errors were encountered:
technically applies to all upgrades, not just analysis visor
Sorry, something went wrong.
Would be solved by #264
No branches or pull requests
Describe the bug
Analysis Visor main tech and the upgrades all have the same name, making it difficult especially for screen readers.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Upgrades should be named "Scanner Module" (UP_SCANNER1_NAME_L) for additional clarity.
Screenshots
Logs
No logs required.
Please complete the following information:
Additional context
Class indication in text form would be nice, but hard to localise since the game doesn't use the classes in the name either.
The text was updated successfully, but these errors were encountered: