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
Trinity ignores fire when transferred #4026
Comments
Please upload the replay. |
http://zero-k.info/replays/20200728_000618_Comet%20Catcher%20Redux%20v3_104.0.1-1544-ge1f249f%20maintenance.sdfz (added a comment to battle so it doesnt get purged) |
Ah, thanks! |
status -> semi-resolved in branch commshare-maintenance I've resolved this partially locally with remerge feature. I'm working on logic to prevent it totally. |
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
A followup to issue #4025, once my squadmate resigned, it resigned me. I had a trinity, and I already scouted the enemy and selected a part of their base that was not protected. However, after the bug when the game made me resign, the trinity did not fire even after completing stockpile. The order was still in queue, but the nuke simply did not fire.
http://zero-k.info/Battles/Detail/931472
The text was updated successfully, but these errors were encountered: