feat: remove overwrite of vanilla skill container events #459
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.
wasUpdatingfix. However, upon reflection I have realized that that fix is only necessary for thebuildPropertiesForXYZfunctions. Because it is these functions which have a chance of being called from within other skill container events. The other events e.g.onTurnEndetc. are very well secluded and are only ever called independently, so never run into an issue of settingIsUpdatingto false too early. So we keep thewasUpdatingcheck manually for thebuildPropertiestype functions, but for the others we remove the overwrites.Eventually with the combination of the other fix in #447 this might as well fix some hidden/unknown bugs being caused by MSU.