Non-Admin Staff Conduct

This document is intended to set out a clear set of rules and guidelines for our mentors and other non-admin specific roles (TBA)

Universal Conduct

All types of non-admin staff must follow these guidelines. Admins who break these rules are liable for punishment as if they had broken admin conduct.

1: You are our most trusted players. Act like it:

You’ve been granted access to either sensitive policy or round info. As such, you are held to a higher standard than regular players. You should not accumulate large numbers of notes or bans as a mentor or maintainer. Some leeway is permitted, as nobody is perfect and we don’t expect you to be, but you should keep a generally clean record. The ballpark estimate for how many notes you can get away with is 0.033 per hour at the most, or one note per 30 hours of play. This does not apply retroactively, so do not panic if you have a pile of notes, so long as you improve and show a willingness to at least try to be a good player, you will not be removed from your position.

2: Do not be toxic to other players:

Likewise, you should act as an example to others during your interactions in OOC, the forums and discord. While you are not expected to coddle other players and never criticise anyone, you should not go out of your way to provoke fights or arguments for little to no reason. Do not harass other players, and do not constantly mock new players for being new. If someone is trying to provoke you and you end up in a massive fight with them, this is understandable, but try to avoid it regardless.

3: You are part of the staff team and as such represent us:

Do not raid or grief other servers. Do not advertise us on servers where this is not allowed. Use common sense and don’t do stuff that’d get other servers massively mad at us. Depending on the severity of your actions, you may be liable for offences within other server communities as if you had committed them within our community.

4: Follow forum/discord conduct:

Don’t peanut post in ban appeals. Do not spam threads with random images. Meming is allowed, but don’t do it in serious topics (Feedback threads, ban appeals, admin/player reports).

Mentor-Specific Conduct

1: Mentorhelp conduct:

• Your job is to provide assistance for players with gameplay issues.
• Do not leak the contents of mentorhelps outside of mhelp, msay or #mentors.
• Do not mock or insult players for any reason in an mhelp, do not give meme answers unless the mhelp is an obvious meme mhelp (use common sense).
• Do not give false or misleading information to a player during an mhelp, and if you are not sure if the information you are providing is accurate, make this clear in the message.
• For rules/grief related mhelps, refer them to adminhelp, but you may provide your own explanation if you are certain that it is correct. If you are unsure, don’t say anything.
• Do not act upon any information you receive in mhelps about the current round.

2: Msay/IC OOC conduct:

• By the nature of your position, you have access to means of private OOC communication. As you are supposed to be trustworthy, the IC OOC rules for these channels are somewhat loosened to allow you to function properly.
• You may freely discuss the contents of mhelps in both #mentors and msay.
• You may give IC information that is relevant to an mhelp freely in both channels.
• You may IC OOC in these channels for the purposes of expanding your collective knowledge of new features during a testmerge as well as to test for bugs.
• Do not act upon any information you receive from either channel about the current round.
• Do not release these private discussions outside of mhelp, msay and #mentors until the current round is over.

3: Mentor Application conduct:

• When asking questions on mentor applications, you should not be asking more than 4 questions per person per mentor application.

Demotion Procedure

• A report may be opened against you on the forums, or you may be internally investigated by the admin team.
• The facts are verified and it is decided if you are guilty or not of a conduct breach.
• If you are found guilty, you will be either officially warned or immediately dementored.
• Breaking a part of the conduct that is underlined is grounds for immediate removal.
• The results of the investigation will be published in a public channel similar to #admin-strikes, with the reasoning being given.
• If you are inactive for a significant period of time you may be dementored due to your knowledge of the game being out of date. You may reapply when ready to regain your mentor status.

Maintainer-Specific Conduct

• Do not disclose any information from the ops channels (#server-ops and #downstream-ops) without permission from the persons who posted it.
• Do not merge any pull request with config changes. Review and approve it then request a review from Crossed.
• Do not self-merge a pull request.
• Do not unilaterally merge balance changes.
• Follow and enforce the code contribution guidelines.
• Generally, closing a PR should require the consensus of at least two maintainers. This is done by the first maintainer leaving the 'key close' label.
• If you break everything or otherwise act maliciously, please refer to the Demotion Procedure section.
• Maintainers specific to a single area of the code (Maptainer, Spritetainer) should only testmerge/merge PRs in their area.
• Do not abuse in-game privellages.
• Changes that affect balance or add features should be given time and discussed with other maintainers and contributors for opinions. If there are no strong opinions, then the PR can be put to vote (See below).
• Non-critical PRs that have been open for less than 24h should generally not be merged unless they have approval from another maintainer

Maintainer Recruiting

Maintainers have a lot of trust placed upon them, and as such it is difficult to appoint maintainers. New maintainers are selected by the current development team and there is no formal application process.

Below are some important qualities that we look out for when trying to abduct recruit new maintainers.

• At least a few large scale projects which implement a new, original and well-designed feature into the game.
• High standard of coding and enough contributions in order to prove this.
• Performed reviews on other contributor's code, highlighting potential issues with code and design.
• Good communication skills, feedback given is easy to understand.
• Some level of involvement in the community. The maintainer role is quite a highly trusted role and as such, some level of 'clout' is required.
• Being a nice person to work around and communicate with.
• Survived long enough to not get burnt out already, if you made it this far.

PR Vote Procedure

• When subjecting a PR to a vote, apply the Voting label. Post a link to the PR in #pr-player-input. If the title does not provide all of the relevant info, include a short summary. If it's a sprite PR, include screenshots.
• After 2-3 days check the status of the vote, remove the Voting label, and apply the relevant outcome label to the PR. If the vote is roughly split with no significant majority, use your discretion.
• PR votes are non-binding, but you should typically have another maintainer or the headcoder sign off on ignoring the outcome. The PR is liable to stir the hornet's nest and we want consensus that it's actually a good change.
• The Headcoder reserves the right to ignore the voting procedures entirely.

Demotion Procedure

• The Headcoder will 'fire' you.