Posts: 190
Threads: 41
Joined: Mar 2019
BYOND Username: TheMaskedMan2
I just saw another round earlier today which is prompting me to say something else. It was 17 minutes again, and a blob spawned, it killed two people, and within seconds they called shuttle.
"Blob is going to win at this point."
The player pop was 50+.
I mean, maybe it would win, but it feels so lame to just do that. I'll just be repeating myself at this point, but it does legitimately happen. Maybe completely disabling shuttles isn't the best decision, but I feel like something should be adjusted at least, or at least thought about.
Posts: 108
Threads: 12
Joined: Jan 2024
BYOND Username: JORJ949
Character Name: George/Etienne Khouri, Rene Lent, G3-0R
I played a bit on an ss14 server where blob would completely prevent shuttle if the shuttle wasn't already at the station by recalling it immediately whenever it was called or if it was enroute, this provided a really terrible experience where a lateround blob would spawn when evac should really be coming and the blob couldnt win as the remnants put up enough of a fight but the crew couldnt call because the blob put up enough of a fight to not die. Crew calling over antags is IMO an admin issue and not something that should be enforced via game mechanics unless the round is 100% guaranteed to end, for example nukies only mess with shuttle after the nuke is armed so theres 13m maximum of the round left, flock messes with it when relay is built and even then only delays by the amount of time to detonate the relay, meaning if you stop the relay theres only a little extra time, revs starts killing everyone at 50m by centcom gibbing crew at random but also gives pinpointers to the people to kill to end the round way before then.
If you get the shuttle called as a major antagonist you did win, but if this is happening just from your mere existence rather than the threat caused by your skill then you should ahelp it.
If crew are causing shuttle without a good reason just because there is X antag thats an ahelp issue.
Posts: 95
Threads: 11
Joined: Mar 2021
BYOND Username: AmazingDragons
Character Name: Ben Wyatt, Honky the Syndicate Agent, Friend Computer
Imo the compromise is to just set a minimum time before the shuttle can be called. In general I think you shouldn't be calling it before 30 minutes, so maybe before 25 minutes the shuttle won't come? I feel like we also need a bit of a culture shift where we're not trying to end rounds as non-antags quickly, because that just sucks for the antags. A bomb hitting a hallway or an ion storm is not cause for calling the shuttle, make an effort to work with the station whenever possible as it deteriorates.
Posts: 5,792
Threads: 304
Joined: May 2014
04-28-2025, 04:43 PM
(This post was last modified: 04-28-2025, 04:47 PM by Frank_Stein. Edited 1 time in total.)
(04-26-2025, 11:00 PM)AmazingDragons Wrote: Imo the compromise is to just set a minimum time before the shuttle can be called. In general I think you shouldn't be calling it before 30 minutes, so maybe before 25 minutes the shuttle won't come? I feel like we also need a bit of a culture shift where we're not trying to end rounds as non-antags quickly, because that just sucks for the antags. A bomb hitting a hallway or an ion storm is not cause for calling the shuttle, make an effort to work with the station whenever possible as it deteriorates.
One way to go about this would be to allow shuttle calls early on, but changing arrival times based on how much time has already elapsed. A shuttle call 5 minutes into a round might take 15 minutes to arrive, a shuttle called 10 minutes in might take 10 minutes to arrive, etc
In canon explanation, ship is still being fueled up, can't arrive until certain point.