search

tgstation / TerraGov-Marine-Corps

TGMC: TerraGov Marine Corps, a SS13 mod
GNU Affero General Public License v3.0
164 stars 822 forks source link

Rebalances Crash #16717

Open blackdav123 opened 3 weeks ago

blackdav123 commented 3 weeks ago

About The Pull Request

Various changes to make crash more fair.

How many xenos for a t3 slot? xenopopsheet

Why It's Good For The Game

  1. Wraith is the bane of this mode and can very easily cheese the Canterbury, this is not fun gameplay and lowpop suffers from having wraith in this mode. Hivemind is completely unkillable on crash and very annoying when it endlessly spams sticky weeds and walls, and hivelord is in a similar position with its large bulk allowing it to spam endless resin and sticky weeds, while also having the healbeam which can give a queen or other large xeno nearly 100% uptime, which is a bit too strong when marines are so short on staff.
  2. Marines are not well equipped to deal with t3s on crash and at 7 marines you can already be dealing with two ravagers. This causes very quick wipes and very little back and forth gameplay. Pushing the extra t3 slots to higher pop should help marines survive lowpop easier.

Discuss below what else you think needs tuned, im still not completely sure whether hivelord should stay or go.

Changelog

:cl: balance: Removes hivemind, hivelord, and wraith from crash. balance: Xenos get extra t3 slots one xeno later on crash.

/:cl:

Barnet2 commented 3 weeks ago

Have you decided by Queen, or do you think the rest of the changes will make up for it? Of course, by that point you should be playing Nuclear War, but to preserve the round

blackdav123 commented 3 weeks ago

Have you decided by Queen, or do you think the rest of the changes will make up for it? Of course, by that point you should be playing Nuclear War, but to preserve the round

Queen will probably still be a bit too strong but I couldnt figure out how to do what I wanted, ideally xenos wouldnt gain larva points until the ratio has accounted for the floor of 2 xenos so you'd get your 3rd xeno at 7 marines instead of 4 which would push the queen to be at higher pop than it currently is.

Hopefully removing the hivelord + queen combo will put a decent dent in the issue, along with the third t3 slot coming at 9 xenos instead of with the queen at 8.

Runian commented 3 weeks ago

For Wraith, can't you just create an area flag kind of like MARINE_BASE that prevents blinking into and then apply it to Canterbury? That should solve Wraiths blinking into and slashing the APC. As for sentries on Canterbury, there is certain distance to place them while on radical mode that prevents cheesing with portals.

Runian commented 3 weeks ago

Revert of #10567. The About Section and Changelog also doesn't mention how dead & pregnant marines are now excluded from the autobal / periodic larva spawning check.

blackdav123 commented 3 weeks ago

Revert of #10567. The About Section and Changelog also doesn't mention how dead & pregnant marines are now excluded from the autobal / periodic larva spawning check.

Fixed, pregnant marines are now counted (we dont live in distress world anymore) and the check for dead marines now works properly excluding DNR marines instead of excluding robots and people without brains/hearts.

Naaanii commented 3 weeks ago

Holy based.

Aporhtonoma commented 3 weeks ago

Removes hivemind, hivelord, and wraith from crash.

HOLY BASED

Lumipharon commented 2 weeks ago

I'm watching crash games where it is 6 xenos vs 9 marines. This is uh, extremely fucking terrible.

Edit: yeah taking this off TM, it genuinely makes crash unplayable.

Runian commented 2 weeks ago

Is it possible to hide the castes from the hive status menu? It seems a bit odd that the castes appear in there as if there could be an xeno with that caste at some point in the gamemode when obviously there won't be since it is impossible to evolve to.

WoodenTucker commented 1 week ago

abyssmal dogshit PR

github-actions[bot] commented 3 days ago

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 ~ 3 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