Disable riot damage in city (without removing code support) #79594
+1
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
None
Purpose of change
This is an alternative to #79580 which effectively reverts the #79535 changes as far as user experience goes, but leaves the code support in so that it can be further worked on behind the curtains until it's in better shape (see #79584 and #79575)
tagging #79565, although this does not technically fix the core issue
Describe the solution
JSON-only change. With this PR no overmap has
PP_GENERATE_RIOT_DAMAGE
flag so the riot damage generator never runs.But it can still be enabled locally for testing very easily.
Describe alternatives you've considered
Completely revert the code as #79580 does. That would be preferable if this feature is fundamentally unfixable (since the current PR effectively creates dead code, and having dead code is not ideal)
Testing
Additional context