Xenos cannot pylon working comms anymore

[ihatethisengine]

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:

[HeresKozmos]

Seems pretty cool.

[Drulikar]

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.

[ihatethisengine]

What about this?

[Drulikar]

This works, but means that this proc is now very spammable (e.g. toggling the power on and off at the apc). The timers should then be considered unique and allowed to override one another else you can create lots of timers that are redundant: