Naming Policy Clarification

Ask and discuss policy about game conduct and rules.
Forum rules
Read these board rules before posting or you'll get reprimanded.
Threads without replies for 30 days will be automatically locked.
Post Reply
User avatar
RaveRadbury
In-Game Game Master
Joined: Fri Mar 08, 2019 3:41 am
Byond Username: RaveRadbury
Github Username: RaveRadbury
Location: BK ChatZone
Contact:

Naming Policy Clarification

Post by RaveRadbury » #780547

Sometime during the prolonged host garbage fire naming policy was adjusted on the fly without writing it down (outside of the moment it was decided) and notifying admins. The forums were down as well.

Now that the dust has settled this has come up again and while headmins have discussed it and do have takes on it the point remains that there was no community involvement in the discussion. Until now.

So, here are the two models we have for naming policy. (I will update this if I've misunderstood anything, please quote what is incorrect and provide the clarification.)

Classic Naming Policy (Pre-Garbage Fire)
  • Any admin can rule a name unacceptable and note that
  • Players appeal names that they think should be allowed
  • If headmins rule the name acceptable it's more or less granted a pass (New terms and naming policy changes could affect it in the future
  • Generally though having a successfully appealed naming policy note means at worst that the name is in the grey
  • Ruling a name permissible without a successful appeal lasts for the round it was given due to how we clarify overruling another admin. No note is made.
  • This means that if an admin has a problem with an unappealed, unnoted name that has been approved by others, they can wait for the next round to bwoink and note
  • DendyDoom, during her term, made an allowance for headmins to be consulted about a name in bus and if they were in agreement a headmin could provide an "allowed name" note
New Naming Policy (Post-Garbage Fire)
  • Admins can rule names acceptable and note the name as approved
  • If another admin takes issue with this they are to bring it up in bus and the two discuss it
  • I assume that if they can't come to an agreement that headmins are involved?
  • If headmins disagree with the approval they can take it away

(I will update this if I've misunderstood anything, please quote what is incorrect and provide the clarification.)

I think that the new system has less transparency and record which is ultimately a bad thing. I don't think that having to track down a conversation in discord to figure out why a name is okay is as good as our forums which can't be nuked like discord can.

It was also pointed out that an admin saying "this name is okay" is kind of making a promise that they can't control as headmins can overrule that as they please. People really do not enjoy having things taken away from them which is evident in the many naming policy appeals we've already had. A shift in culture towards "approval notes" would result in more names being taken away as a finality.

The way I see it:

Classic process: Admin rules against character name ➡️ Player appeals it ➡️ Headmins approve it = Redemption Arc
New process: Admin rules for a character name ➡️ Another admin takes issue and talks about it in bus ➡️ Headmins deny it = Shadow Ban Arc with a side of admins bickering with each other

To me the new process invites direct conflict between admins and the old process separated things out so that the player could advocate for themselves, the community could weigh in via peanut, and headmins made the decision without having to directly choose one admin over the other.
User avatar
dendydoom
Site Admin
Joined: Fri Dec 04, 2020 10:40 am
Byond Username: Dendydoom

Re: Naming Policy Clarification

Post by dendydoom » #780550

a large part of the ruling in our term is that we didn't want to see admins intentionally undermining each other and leveraging rules as written to "correct" something outside of the headmins' purview. we select admins to be a team and expect them to not engage in dishonest low level skulduggery to achieve their personal view of enforcement. my mandate during a particular incident was that any action that restricts a player in the long term (ie telling them they can't use a name) needs to be noted every time because otherwise the player has no basis to engage with the appeals process, and there is no record for headmins to figure out who was told what, and what the specifics of the ruling is.

for complete transparency, the inciting incident for me to push for this was, in my eyes, really shitty admin behaviour and it's my belief that players come first. if our processes put the player in a bind, then it's the headmins' role to circumvent policy to resolve it, and on the admin side we just have to cope and do what is right by the player. that will oftentimes be messy but i believe it's the right stance to take, precedence be damned.
MrStonedOne wrote:I always read dendy's walls of text
MatrixOne wrote:I always read dendy's walls of text
MothNyan wrote:Dendy's walls of text are always worth reading
User avatar
Timberpoes
Site Admin
Joined: Wed Feb 12, 2020 4:54 pm
Byond Username: Timberpoes

Re: Naming Policy Clarification

Post by Timberpoes » #780564

It's admin team internal policy about how to enforce the rules. I don't think the players will give a fuck beyond knowing that there's some way for admins to now formally approve nonstandard names. And I can't really see players disapproving of making it harder for admins to overrule eachother via yet more awho roulette.

Dendy's term's ruling/stance was reaffirmed or possibly extended by my last term - Dendy & co can correct me on that as necessary: admins could approve names at their discretion by placing notes as well as disapprove names at their discretion by placing notes, and that admin disagreements over approved/disapproved names might become headmin issues earlier than they became player issues. The headmins would then make the final call on if to overrule the admin on their naming policy note, and nobody else would make that call except the headmins.

Allowing other admins to place binding notes has more transparency and record-keeping. It allows admins to record that definitive ruling that they've investigated a name and ruled it okay, via note with transparent justification visible to the player and all admins alike. It also still allows admins going "meh, I don't take issue with your name but other admins might, so yolo enjoy it while you can" when they don't want to commit either way, so flexibility is retained for non-rulings. There doesn't really need to be huge transparency for admins giving non-rulings like that either. It's not just that if an admin places a note the name is protected, but ALSO if an admin doesn't place a note, the name isn't protected.

The reason for approving any name is invariably going to be in the note too.

That shift to backing via positive notes is there to protect players from non-headmins trying to overrule another admin's decision. It lets some us codify that the name was approved, who approved it and why. It's now harder to disapprove approved names, and involves more people to disapprove instead of just the Naming Stasi manifest in single admin form - and this is all a good thing for players compared to the old ways in my view.
/tg/station Codebase Maintainer
/tg/station Game Master/Discord Jannie/Forum Admin: Feed me back in my thread.
/tg/station Admin Trainer: Service guarantees citizenship. Would you like to know more?
Feb 2022-Sep 2022 Host Vote Headmin
Mar 2023-Sep 2023 Admin Vote Headmin
Sep 2024-April 2025 Player and Admin Vote Headmin
User avatar
Timberpoes
Site Admin
Joined: Wed Feb 12, 2020 4:54 pm
Byond Username: Timberpoes

Re: Naming Policy Clarification

Post by Timberpoes » #780567

Also doublepost to state the admins being able to formally approve names is necessary for this part of naming policy to be functional:
Species have naming conventions that are part of their in-universe culture. These may be subverted if they have a sufficient amount of in-character reasoning and effort explaining their non-standard name. Non-standard names are held to higher scrutiny and you may be questioned on why your name breaks these conventions.
/tg/station Codebase Maintainer
/tg/station Game Master/Discord Jannie/Forum Admin: Feed me back in my thread.
/tg/station Admin Trainer: Service guarantees citizenship. Would you like to know more?
Feb 2022-Sep 2022 Host Vote Headmin
Mar 2023-Sep 2023 Admin Vote Headmin
Sep 2024-April 2025 Player and Admin Vote Headmin
User avatar
RaveRadbury
In-Game Game Master
Joined: Fri Mar 08, 2019 3:41 am
Byond Username: RaveRadbury
Github Username: RaveRadbury
Location: BK ChatZone
Contact:

Re: Naming Policy Clarification

Post by RaveRadbury » #780571

Timberpoes wrote: Wed Jun 25, 2025 7:36 pm Also doublepost to state the admins being able to formally approve names is necessary for this part of naming policy to be functional:
Species have naming conventions that are part of their in-universe culture. These may be subverted if they have a sufficient amount of in-character reasoning and effort explaining their non-standard name. Non-standard names are held to higher scrutiny and you may be questioned on why your name breaks these conventions.
Disagree, this is carried out the same way naming policy has always been carried out: by explaining how it works and underlining the caveat.

"Yeah so naming policy can be subjective. I hear your reason and I think it's fine, but another admin might not. If that happens and you disagree you can always appeal it on the forums."
User avatar
TheRex9001
In-Game Head Admin
Joined: Tue Oct 18, 2022 7:41 am
Byond Username: Rex9001

Re: Naming Policy Clarification

Post by TheRex9001 » #780572

I believe this is a point my fellow headmins might disagree with me on but I like the new system, I think the burden of work should be on the admin and not the player, nobody will want to ever break naming policy in reality if you have to appeal to get your name approved. It also feels extremely shitty from a players pov to have your name approved but that approval only lasts for a round and then someone can just swoop in and note you for it. I think note approval for weird names is a better system that remedies these flaws.
User avatar
Timberpoes
Site Admin
Joined: Wed Feb 12, 2020 4:54 pm
Byond Username: Timberpoes

Re: Naming Policy Clarification

Post by Timberpoes » #780583

RaveRadbury wrote: Wed Jun 25, 2025 8:25 pm
Timberpoes wrote: Wed Jun 25, 2025 7:36 pm Also doublepost to state the admins being able to formally approve names is necessary for this part of naming policy to be functional:
Species have naming conventions that are part of their in-universe culture. These may be subverted if they have a sufficient amount of in-character reasoning and effort explaining their non-standard name. Non-standard names are held to higher scrutiny and you may be questioned on why your name breaks these conventions.
Disagree, this is carried out the same way naming policy has always been carried out: by explaining how it works and underlining the caveat.

"Yeah so naming policy can be subjective. I hear your reason and I think it's fine, but another admin might not. If that happens and you disagree you can always appeal it on the forums."
I considered that an undesirable outcome. To me, that's really player-hostile. It assumes the admin team doesn't have its shit together and admins can only be held accountable when the player drags their ass to the forums to sort out what is ostensibly one non-headmin overruling another non-headmin because those non-headmins disagree on a topic.

Last term when I spoke on the topic in the admin channels, I re-affirmed that admins could place notes allowing players to have names and those notes would prevent other admins from disallowing those names.

I did it because I trust that our admins aren't so utterly devoid of critical thinking skills that they'll start approving names that have no place falling under any exception or exemption. And I trust that all admins are on board with the mission statement that we serve the players and that every action we take should be in the best interests of those players, to improve the game, the community, how players percieve the admin team and everything else related. And I trust that our admins can respectfully disagree without drooling all over themselves and soiling their undergarments because papa headmin forgot to change babby admin's diaper this morning, in pursuit of that objective of taking the best interests of players into account.

That's how my thought processes go.

Normally when an admin tells a player something that is patently false/incorrect/honestly mistaken, the admin is responsible for any reasonable response or actions a player does in response to that. We get it all the time. Admin bwoinks player, player says some other admin said thing was okay to do, and we have a little ticket dive to verify what was said and do our internal due diligence processes without punishing the player if they were genuinely or honestly misled or reasonable mistaken as to what they were told. Because we serve the players and not ourselves.

What definitely does not matter to our players is how much wanky LARPy red tape or other impenetrable admin-favoured and bullshit-flavoured ginger bread houses we use to construct our Ivory Tower. What players care about is that they can trust admins, trust what admins say and that when admins step on eachothers' toes we're able to resolve it without requiring the player to waste their time fixing our problems for us.

And honestly, from where I stand, appeals and complaints are the final line of defense. They're not a LARPfest we force players to interact with to solve petty and pointless inter-admin disputes. Instead, they're the nuclear option, which when used mean a disgruntled player has no more recourse available to them. Appeal rulings are final. Complaint rulings are final.

By allowing admins to approve names and requiring admins that disagree to do what we do with every other disagreed ruling - talk it out or call headmins - we add a new player-favoured line of defense that sits between them being told they can use a name and them having to make an appeal or a complaint to solve what is ostensibly admins being fucking morons overruling eachother.

Honestly, I feel like I'm sat here in my "/tg/ admins are the best admins because we serve the players and not the other way around"-tier Ivory Tower. I'm laughing at those servers with the terrible admins that overrule eachother and do shit just to inconvenience players over themselves. Only I start to realise there are calls from inside the tower to be just like those terrible admins. To prioritise our experience over that of our players.

And this player-advocate stance is not even off-brand for me. As headmin I was always involved in appeals trying to guide them to resolutions that mutually satisfied all parties and didn't result in pointless headmin reviews. My second term I was involved in writing the ruling that prevented admins from modifying notes or ban reasons outside of appeals with a caveat that it was allowed if the modification was to the player's benefit.
https://wiki.tgstation13.org/Admin_Conduct wrote:Modifying Notes and Bans
Do not modify non-secret notes/bans outside of appeals unless it either benefits the player in question or you are correcting an error within a reasonable period of time of it being placed.
Why? Because making players jump through pointless hoops just for the sake of appeasing admin corpo red tape mandates is patently one of the dumbest stances imaginable when it comes to community management and player<->admin relations. If we can solve something internally to a player's benefit without having to rope the player into engaging with our LARPy admin corpo-plus bureaucracy-laden wankfest then we can and should do so, every time.

Admins being able to take ownership over this topic and positively allow names is of benefit to the players, even if the Naming Stasi might lose some of their powers to micromanage names.

That this may make other admins unable to change that player's name forcibly without invoking headmin involvement is of benefit to the players.

That there's a chance that admin disagreement over a player's name can be resolved to the player's benefit, without the player even having to do anything or perhaps never even realising at all there was a disagreement that got solved in their favour, is of benefit to the players.

That this new process activates without forcing the player to need to appeal means that an appeal against the decisions can continue to be the last line of defense rather than the default setting, which benefits us all by not turning admin team retardation into public spectacle unless absolutely necessary to ensure high quality fertiliser for our peanut farms.
/tg/station Codebase Maintainer
/tg/station Game Master/Discord Jannie/Forum Admin: Feed me back in my thread.
/tg/station Admin Trainer: Service guarantees citizenship. Would you like to know more?
Feb 2022-Sep 2022 Host Vote Headmin
Mar 2023-Sep 2023 Admin Vote Headmin
Sep 2024-April 2025 Player and Admin Vote Headmin
User avatar
RaveRadbury
In-Game Game Master
Joined: Fri Mar 08, 2019 3:41 am
Byond Username: RaveRadbury
Github Username: RaveRadbury
Location: BK ChatZone
Contact:

Re: Naming Policy Clarification

Post by RaveRadbury » #780584

Timberpoes wrote: Thu Jun 26, 2025 12:56 am
RaveRadbury wrote: Wed Jun 25, 2025 8:25 pm
Timberpoes wrote: Wed Jun 25, 2025 7:36 pm ...necessary for this part of naming policy to be functional...
Disagree...
I considered that an undesirable outcome...
You're calling it "necessary" but it's only structurally necessary if your goal is to bypass appeals through admin empowerment.

That's a valid goal, but it's not the only one, and it's not cost-free.

The classic model lets players know when they're in a grey zone and gives them tools to resolve it.
The new model gives admins the illusion of authority they can't actually guarantee, which creates whiplash when it's revoked.

If the goal is "player benefit," you can argue either direction.
If the goal is mechanical clarity, the classic model is more stable: player-initiated, trackable, and headmin-resolved.

Your version puts internal admin consensus at the center of fairness.
Mine leaves that to the appeals process.

So no, your version isn't functionally necessary. It's just more aligned with a trust-the-admins model.
And I trust the structure more than I trust the trust.
Post Reply

Who is online

Users browsing this forum: Bepis