Fix Ares' InitialPayload for teams spawned by trigger actions #1283
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.
Ares marked its initialpayload already created for units spawned by trigger actions because of the mutex.
I've been testing this on 336 missions for several months and so far no crash or perf drop related to this
For the record, this should not be documented. Ares didn't fix it because of some so-called "endless loop call". I wasn't able to find any and this worked just fine on my side. It should be tested on a wider scale to see if such a thing could exist.