Skip to content
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

Convert variation in carriers and turrets to new format #2165

Merged
merged 3 commits into from
Sep 17, 2024

Conversation

aBlueShadow
Copy link
Contributor

Converted the old scenario variation to a difficulty setting in the new format, so the update locale script can generate translation entries for it.

@aBlueShadow
Copy link
Contributor Author

aBlueShadow commented Sep 16, 2024

i just realised, that the new settings cannot get recognised, as I would also need to change getScenarioVariation() to getScenarioSetting("Difficulty"). And then I realised that the old setting probably never did anything in the first place, as while there is a setVariations() function that would take care of it, it never gets called.
The new commit fixes both issues.

Successor of the "none" variation, so no additional checks in setVariations()  are needed
@aBlueShadow aBlueShadow deleted the patch-4 branch September 17, 2024 08:53
@aBlueShadow aBlueShadow restored the patch-4 branch September 17, 2024 08:53
@aBlueShadow aBlueShadow reopened this Sep 17, 2024
@daid daid merged commit 1fa7098 into daid:master Sep 17, 2024
13 of 14 checks passed
Piglit pushed a commit to Piglit/EmptyEpsilon that referenced this pull request Oct 8, 2024
* Convert variation in carriers and turrets to new format

so it is translatable

* recognise the difficulty settings

* add default "normal" option

Successor of the "none" variation, so no additional checks in setVariations()  are needed
Tsht pushed a commit to Tsht/EmptyEpsilon that referenced this pull request Oct 12, 2024
* Convert variation in carriers and turrets to new format

so it is translatable

* recognise the difficulty settings

* add default "normal" option

Successor of the "none" variation, so no additional checks in setVariations()  are needed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants