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

Fix Ares' InitialPayload for teams spawned by trigger actions #1283

Closed

Conversation

chaserli
Copy link
Contributor

@chaserli chaserli commented Jun 22, 2024

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.

@chaserli chaserli added the Minor Documentation is not required label Jun 22, 2024
@chaserli chaserli requested a review from Starkku June 22, 2024 11:34
Copy link

github-actions bot commented Jun 22, 2024

Nightly build for this pull request:

This comment is automatic and is meant to allow guests to get latest nightly builds for this pull request without registering. It is updated on every successful build.

@chaserli chaserli marked this pull request as draft July 10, 2024 10:51
@chaserli chaserli closed this Jul 10, 2024
@chaserli chaserli added the Demo only Only for demo purpose, no need for merging label Jul 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Demo only Only for demo purpose, no need for merging Minor Documentation is not required
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant