Moderators: In-Game Game Master, In-Game Head Admins
deedubya wrote:side suggestion in addendum to the above policy, for coders or config editing: Double the chance for midround antags to spawn every half hour, so that rounds don't drag on for too long.
Screemonster wrote:how the fuck are you supposed to RP with a grille
Malkraz wrote:if you don't want some guy calling the shuttle then stop him
From a admin intervention perspective I usually leave shuttle calls to the players in game to resolve. The Heads of Staff (or the guy with their ID) are accountable to the crew and if they truly go against the will of the majority there are in game avenues that can be taken usually leading to some interesting situations. That said, Ari is right that when you've got some kind of shuttle call abuse going on it can end up with admin recalls, BSA smites and centcom messages.
I wouldn't want to completely remove the ability for the crew to generally decide they've had enough and move on to the next round. I'd prefer they stayed engaged in the round for as long as possible but much of this is about having regular non-antag content that keeps most departments engaged even into the hours.
deedubya wrote:Malkraz wrote:if you don't want some guy calling the shuttle then stop him
"Robust anyone that does something you dislike" is a stupid argument that should never be used on any server that even has the mildest semblance of RP standards.
deedubya wrote:Malkraz wrote:if you don't want some guy calling the shuttle then stop him
"Robust anyone that does something you dislike" is a stupid argument that should never be used on any server that even has the mildest semblance of RP standards.
Yakumo_Chen wrote:Implement round end shuttles like they do on high RP servers. Force a time limit to the round so it can't drag on for eternity (that admins can override) and at the same time disallow stubbed toe calls because if there's nothing to do, the round will end on its own anyway.
Long rounds tend to spawn more side antags though, or meteors, so the amount of rounds that are getting past two whole hours are pretty rare unless you're on a nopop server.
Deedubya wrote:That leads to my big issue with IC/OOC separation issues. Sure, OOC you're bored, you have work in the morning, you didn't want to commit to a 2+ hour shift, you didn't roll antag and just want the round to end...any number of reasons OOC. None of that justifies an IC shuttle call. The station is running, power is getting everywhere, everyone's well fed, in good health, there's no looming emergency. There's no reason to evacuate. The common scenario where a Captain calls a vote to evacuate? Almost all the people voting "yes" are just bored stupid and want the round to end, rather than invested employees seeing a legitimate reason to evacuate their workplace. That shouldn't be any more acceptable than a head calling the shuttle because of boredom.
However, as others(and I to an extent) have stated, this is a problem that probably needs a combination of code and policy to solve. Either by giving the station more goals to work towards, or by making midrounds more common the longer the round drags on. The latter is probably an easier solution, and solves the issue of rounds dragging on too long. After all, we're all adults with responsibilities(I hope), so expecting someone to commit to 2+ hours of spessmen in a single sitting is a bit much. Code forcing disaster level events by the 1:30 mark would solve the issue, I think.
BeeSting12 wrote:We don't have enough content in most jobs to justify the round lasting much longer than an hour and a half in the absence of a fun gimmick by either admins or players. Instead of going "we need more content" then go make some or suggest some, preferably the former. That's why I don't do anything about "I'm bored" shuttle calls after an hour or so, and even then, the worse I'd do is a recall and smite.
This is when I usually spawn low impact side antags -- abductors, morphs, etc. -- to give the ghosts something to do and produce conflict in the round.
deedubya wrote:BeeSting12 wrote:We don't have enough content in most jobs to justify the round lasting much longer than an hour and a half in the absence of a fun gimmick by either admins or players. Instead of going "we need more content" then go make some or suggest some, preferably the former. That's why I don't do anything about "I'm bored" shuttle calls after an hour or so, and even then, the worse I'd do is a recall and smite.
These are all points that I've already mentioned, even in the post you're quoting. I even proposed a code solution that would be fairly effective at forcing rounds to end faster without putting a hard time limit on the amount of time you're allowed to remain on the station. If I wasn't so horribly inept at coding, I'd even propose the PR myself. Basically, double the rate at which midround antags and hostile events spawn every half hour, so by two hours in you have a 16x chance for nasty shit to pop up. (2x at 30, 4x at 60, 8x at 90, etc)
BeeSting12 wrote:deedubya wrote:BeeSting12 wrote:We don't have enough content in most jobs to justify the round lasting much longer than an hour and a half in the absence of a fun gimmick by either admins or players. Instead of going "we need more content" then go make some or suggest some, preferably the former. That's why I don't do anything about "I'm bored" shuttle calls after an hour or so, and even then, the worse I'd do is a recall and smite.
These are all points that I've already mentioned, even in the post you're quoting. I even proposed a code solution that would be fairly effective at forcing rounds to end faster without putting a hard time limit on the amount of time you're allowed to remain on the station. If I wasn't so horribly inept at coding, I'd even propose the PR myself. Basically, double the rate at which midround antags and hostile events spawn every half hour, so by two hours in you have a 16x chance for nasty shit to pop up. (2x at 30, 4x at 60, 8x at 90, etc)
That I'm saying is you're asking us to ban people who are calling the shuttle for a legitimate, albeit OOC, reason. It may ruin your immersions, but the game gets boring after an hour and a half for almost every job (usually earlier). It's ridiculous to ban people for that. Even in the OP you admit it: the situation is in character. It seems stupid in character, and thus should be dealt with in character.
deedubya wrote:BeeSting12 wrote:deedubya wrote:BeeSting12 wrote:We don't have enough content in most jobs to justify the round lasting much longer than an hour and a half in the absence of a fun gimmick by either admins or players. Instead of going "we need more content" then go make some or suggest some, preferably the former. That's why I don't do anything about "I'm bored" shuttle calls after an hour or so, and even then, the worse I'd do is a recall and smite.
These are all points that I've already mentioned, even in the post you're quoting. I even proposed a code solution that would be fairly effective at forcing rounds to end faster without putting a hard time limit on the amount of time you're allowed to remain on the station. If I wasn't so horribly inept at coding, I'd even propose the PR myself. Basically, double the rate at which midround antags and hostile events spawn every half hour, so by two hours in you have a 16x chance for nasty shit to pop up. (2x at 30, 4x at 60, 8x at 90, etc)
That I'm saying is you're asking us to ban people who are calling the shuttle for a legitimate, albeit OOC, reason. It may ruin your immersions, but the game gets boring after an hour and a half for almost every job (usually earlier). It's ridiculous to ban people for that. Even in the OP you admit it: the situation is in character. It seems stupid in character, and thus should be dealt with in character.
I wouldn't suggest a full on ban for stuff like that. Warning someone for a bored/stubbed toe call would be appropriate in my eyes, followed by potential rolebans from command if the warnings start stacking up.
Also, the issue almost never gets resolved in-character, because most of the people playing have a similar level of little-to-no IC/OOC separation. OOC they're bored, didn't roll antag, and haven't seen any valids for an hour - so that means IC they want to evacuate. So when someone with access(legit or tided) calls the shuttle, they won't form a lynchmob to go recall, since they OOC just want to move on to a more exciting round.
I will reiterate though that I think a code solution would be good alongside a policy solution. But if admins/coders want to see more IC actions rather than the culture of validhunting and tiding we currently have, you should implement policy to reflect that.
⠀technokek wrote:Cannot prove this so just belive me if when say this
Users browsing this forum: Google [Bot]