This is both a response to what @TsjipTsjip posted in #admin-questions on discord at Discord and to the things brought up in this thread.
Also I didn’t read over this after writing it out because I’m kind of time crunched for stuff this weekend. Sorry if anything is written confusingly or repetitive or something.
TLDR
This is essentially what the rules said prior and it’s the least bad option I can think of. I don’t know how to improve it but specific suggestions are welcome.
History of the rule
In the past version of the rules, this appeared as something along the lines of “rounds exist independently of one another”. In some cases when people have been bringing up feedback about this rewrite, they’re giving feedback about rules that have existed for a long time on Wizard’s Den, but they sometimes do it in a way that I’m unsure if they realize that the rule has always existed. One of the goals of the rewrite was to make the rules a lot clearer, and from what I’ve heard so far overall it has done that. As a side effect I think people think certain things are new, when in reality the rules just didn’t used to communicate it well enough.
It’s hard for players to tell what is actually new and what is just communicated better, because some things did actually change and there’s not a list of intentional changes anywhere. Too much happened to be able to make one, including clarifying massive grey areas.
I don’t know for sure that this is being mistaken for a new rule rather than a rewriting of an existing one, and it doesn’t matter at all for the argument of whether or not it is a good rule to have. I just want to point this out for people who are concerned about any immediate changes to enforcement around this.
“The rule” is maybe plural
I’m referring to this as “the rule” a lot. I don’t know if that’s the best way to refer to it because it’s a combination of various shields that try to come together to form a very clear definition. I don’t know if people consider each shield a rule or the metashield itself as one rule, it all technically only has one rule number.
The rule’s goals
This is about the goals of this specific rule, not the rule overall.
To my knowledge, the rule has three primary goals, and a closely connected fourth goal which is arguably just an expansion of the other two. I don’t think these goals are the issue that anyone has with the rule, I’m just putting them out here because it’s important to understand them when deciding on the rules.
Protect immersion
This is pretty simple, you don’t want someone saying “ya I died last shift when the station exploded” or things like that. Even if they don’t use any OOC terms or anything like that, it can still break immersion. “I can’t believe all of us died last shift.”
There are some lore ways to work around this, but you’d kind of have to be jumping through hoops with lore to get it to make sense. I’m sure some people would be entirely ok with it, but there are probably at least just as many who don’t want that.
Prevent metafriending
Metafriending is when you give someone an advantage in-game because of who they are OOC. It doesn’t matter what that advantage is, it could be addition access or items, or it could be just being less suspicious of them. Some player shouldn’t have an easy time doing whatever they want because they happen to have a friend, or multiple, in a command/sec/whatever position that round.
Prevent metagruding
Metagruding is the opposite of metafriending, a disadvantage in-game because of who someone is OOC. The fact that someone doesn’t personally like the person who is playing the character shouldn’t negatively affected them, in a lot of cases that happening could be described as bullying. Urist McClown shouldn’t have to worry about avoiding negative interactions with SecMain2000 just because SecMain2000 happens to play captain or security most of the time that Urist McClown is playing and could cause them issues without technically breaking something like escalation rules.
Avoid clique formation
In a situation where people can freely discriminate against or favor another player for OOC reasons, it’s possible for cliques to form. This can take many shapes, but some examples would be:
- A group of close friends play security at the same time. They prioritize each other over anyone else in security and shun or are rude IC to anyone who is not a member of their group in the department. This would likely have the effect of making security an incredibly unwelcoming department for new players.
- A subcommunity forms on a sever, or across multiple servers. They regularly choose members from their own subcommunity for promotions, and they trust them more when people have to be picked to be given things like weapons or important items. This would obviously give members of that subcommunity an advantage over other players, but it could also starve the wider community if the exclusion is severe enough to keep out and eventually drive away too many new players.
This is an issue that Salamander had for quite a while, though I’m not entirely sure if it manifested as metagrudging/metafriending. To my knowledge, it significantly improved a while ago.
Things that aren’t the rules goals
There are certain things which break the rule as written, but are almost entirely, if not entirely non-harmful to player experiences.
Saying “I once set the PA too high. It almost destroyed the station so the CE had me demoted, and that’s why I’m a bartender now.” is technically against the rule if that happened in a prior round, despite the fact that it’s not hurting anyone. In fact, it’s arguably doing the opposite, it’s a backstory and is arguably increasing the level of RP.
Acting as if you’ve worked with everyone in your department before is potentially against the rule. If you haven’t ever worked with them, and you’re just acting like you have then that’s good RP and not against the rules, but if you have with even a single one of then you are arguably remembering a past round and that’d be against the rules. This obviously doesn’t make sense to enforce like this. I hope no one enforces this rule like this, but this is arguably what the rules say right now.
I can’t imagine a single way that either of these things could be harmful, they’re in fact both better roleplay in my opinion than the alternative. I can however imagine adjacent things that are potentially problematic.
Grey areas
These aren’t grey in terms of if they’re allowed or not, at least not by the current version of the rules. The current rules don’t allow you to do any of this. These are grey in terms of it being arguable whether or not being able to do these things is desirable or harmful to the overall game and community.
- You know someone has been disruptively tiding for the last 4 rounds, so this round, only when legal under Space Law, you give them the harshest sentences allowed.
- You have to promote someone to chief engineer. You have two options, one is a person who you know just unlocked the station engineer role, the other is a person who regularly plays chief engineer extremely well so you promote them.
I don’t know what the opinions of the admin team or community are as to whether these two examples, and countless others, are desirable or not. At first glance, personally I want to say that these things should be fine, but I feel like small details can make the difference. What if the tider was actually, unknown to you, an antag the last 4 rounds, now they’re being punished for playing their role. Doesn’t automatically favoring the experienced player impede the other’s ability to get experience to some degree? At the same time, if it does, is it enough that it matters?
The rules don’t have to be free of grey areas, but we should try to minimize them where reasonable and at a minimum we should be aware that they exist.
So why have the rule as is?
The only easy to communicate options that I see for this rule are to either not have it at all or to have it in a form very close to what it is. Both are bad options.
I personally think that having it rather than not is a less bad option because we can choose to enforce it more reasonably than it is written, whereas I don’t think it’s reasonable to do the reverse. I prefer this approach with most rules, erring on the stricter side because I think it leads to a better experience for players when they can follow the rules as written without getting in trouble. The alternative is to have essentially unwritten rules.
The problem is that I only think it’s a well written rule when what is written is very close to what is enforced. In this case, it’s not as close as I’d like, but I don’t know how to get it closer without causing issues. Maybe it’d be a good balance to remove the “events from past rounds” shield while keeping the metagruding/friending restrictions, but that’d muddy the rules a bit and still wouldn’t technically allow stuff like going beyond saying another character is your friend IC and actually treating them like it because that would be metafriending.
I can’t guarantee that they’d be made, but I’d welcome any suggested changes to this part of the rules.