Handle trigger attachments that still use deprecated isSuicide #6970
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.
This adds
getIsSuicide
back so that the trigger attachments in TWW will still work.I've also wrapped the exception inside a new exception that has the name of the trigger, the property, and what type of attachment it is on. This should help in finding and fixing similar issues.
Fixes #6961
Functional Changes
[] New map or map update
[] New Feature
[] Feature update or enhancement
[] Feature Removal
[] Code Cleanup or refactor
[] Configuration Change
[x] Problem fix
[] Other:
Testing
Loaded a TWW save that triggered it, verified that the unit attachment had suicide turned off before non-combat and then had it turned back on after non-combat. And then I let the UI play for several more rounds to see if anything else might happen.
Screens Shots
Additional Notes to Reviewer
Release Note
FIX|TWW will no longer crash before Germany's non-combat phase.