Pylons now count only groundside marines, xenos get major boost to evo speed for 3 minutes after hijack

[ihatethisengine]

About the pull request

Pylons give larva only up to 50% of groundside (weighted) marines, instead of 40% of all humans.
Xenos get major boost to evo speed for 3 minutes after hijack, also hijacking removes ovi cd.

Explain why it's good for the game

Larva surge works this way (but for shipside), and pylons were kinda meant to work this way too. Current implementation encourages xenos to delay hijack as long as possible to get the maximum larva, get evo etc. which is not good. It shouldn't break balance too much, you should be able to defeat marines if you have 40% of their force.

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: Pylons give larva only up to 50% of groundside (weighted) marines, instead of 40% of all humans.
balance: Xenos get major boost to evo speed for 3 minutes after hijack. Hijacking resets ovi cooldown.
/:cl:

[Birdtalon]

I'd say this needs balance approval since xeno endgame relies largely on pylon larva at the moment to siege and then execute a successful hijack. Based on my gut feeling this PR could reduce the larva gain by anything from 20-50% some rounds which I would say is not insignificant.

Edit: Feel free to correct me as I haven't looked into the job weightings impact yet, just back of a napkin guestimate.

[ihatethisengine]

We can up the number to 50%. Theoretically all groundside marines (except doctors) should have weight of 1, so it shouldn't be an issue. Realistically if you have 20 xenos vs 40 marines it's xeno major, especially since you get new xenos when old xenos die.

[GoldenDarkness55]

less numbers = you're even more encouraged to wait for evo.
Just add some kinda check for queen ovi on DS that speeds evo up tenfold for a minute or smth

[cm13-github]

This pull request has conflicts, please resolve those before we can evaluate the pull request.

[cm13-github]

Conflicts have been resolved. A maintainer will review the pull request shortly.

[github-actions]

This PR has been inactive for long enough to be automatically marked as stale. This means it is at risk of being auto closed in ~ 7 days, please address any outstanding review items and ensure your PR is finished, if these are all true and you are auto-staled anyway, you need to actively ask maintainers if your PR will be merged. Once you have done any of the previous actions then you should request a maintainer remove the stale label on your PR, to reset the stale timer. If you feel no maintainer will respond in that time, you may wish to close this PR youself, while you seek maintainer comment, as you will then be able to reopen the PR yourself

[cm13-github]

This pull request has conflicts, please resolve those before we can evaluate the pull request.

[Drulikar]

Code changes look fine.

Resolved