-
Notifications
You must be signed in to change notification settings - Fork 566
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
Xenos cannot pylon working comms anymore #6241
Conversation
Seems pretty cool. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I could be wrong, but this is not a repeating call to handle_xeno_acquisition
(except if those timers are used below). This is the proc called for the signal COMSIG_WEEDNODE_GROWTH
or a re-call using one of the addtimers a little further down. You likely need to in this situation either add a signal for the tower going inoperable, or for you to add a timer to recheck again later.
Co-authored-by: Drathek <[email protected]>
What about this? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
About the pull request
First of all, it looks like a simple oversight. You cannot turn on pyloned comms tower, but for some reason it works the other way around — you can pylon working tower. Don't think this was intended.
Secondly, I think it's a little too boring that you can get both pylon and working comms if you have corrupted xenos. It would be more interesting if you needed to choose between these options.
Explain why it's good for the game
Consistency, balance, important choices.
Testing Photographs and Procedure
Screenshots & Videos
Put screenshots and videos here with an empty line between the screenshots and the
<details>
tags.Changelog
🆑 ihatethisengine
balance: only disabled comms can be pyloned
/:cl: