|
|
| Line 1: |
Line 1: |
| 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.
| | == Discord Moderator-Specific Conduct (WIP) == |
|
| |
|
| 1: You are our most trusted players. Act like it: | | * Don't jump straight to banning. You are expected to use the ?warn command for most offences, and delete the offending message(s). |
| | * Mutes are handled automatically whenever a user gains three warning points. The default points value per ?warn is 1. While you can specify different point values using the command, do not do this unless the offence is very minor (give a 0 point warning) or very major, such as using exploits to distribute viruses. |
| | * Ask the admin team before handing out a discord ban. They should only be used for repeat offenders, ban evaders, alt accounts or other severe offenders such as accounts distributing illegal content. |
| | * Do not leak the contents of #moderators or #mod-log. |
| | * You are expected to handle discord mute/ban appeals created by people you muted, caused to be automatically muted or banned. You are expected to follow the same guidelines as admins handling ban appeals. |
| | * Do not abuse your ability to lock, unlock, retitle and recategorise threads, or your ability to instantly hide posts. Use them when appropriate (locking ban appeal, moving a thread to the correct category, etc.) |
|
| |
|
| 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.
| | === Demotion Procedure === |
|
| |
|
| 2: Do not be toxic to other players:
| | * A report may be opened against you on the forums, or you may be internally investigated by the admin team. |
| | | * If you are found guilty of a conduct breach you will be demoted immediately or warned, depending on severity. |
| 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 within your role.
| |
| 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.
| |
| 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.
| |
| | |
| Discord Moderator-Specific Conduct (WIP)
| |
| | |
| Don't jump straight to banning. You are expected to use the ?warn command for most offences, and delete the offending message(s).
| |
| | |
| Mutes are handled automatically whenever a user gains three warning points. The default points value per ?warn is 1. While you can specify different point values using the command, do not do this unless the offence is very minor (give a 0 point warning) or very major, such as using exploits to distribute viruses.
| |
| | |
| Ask the admin team before handing out a discord ban. They should only be used for repeat offenders, ban evaders, alt accounts or other severe offenders such as accounts distributing illegal content.
| |
| | |
| Do not leak the contents of #moderators or #mod-log.
| |
| | |
| You are expected to handle discord mute/ban appeals created by people you muted, caused to be automatically muted or banned. You are expected to follow the same guidelines as admins handling ban appeals.
| |
| | |
| Do not abuse your ability to lock, unlock, retitle and recategorise threads, or your ability to instantly hide posts. Use them when appropriate (locking ban appeal, moving a thread to the correct category, etc.)
| |
| | |
| Demotion Procedure
| |
| | |
| A report may be opened against you on the forums, or you may be internally investigated by the admin team.
| |
| | |
| If you are found guilty of a conduct breach you will be demoted immediately or warned, depending on severity. | |
| | |
| 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.
| |
| If you are not a full maintainer, do not merge pull requests with changes you do not have authority over. Maptainers and asset maintainers should not be merging PRs with code changes, for example.
| |
| Do not merge any pull request with config changes. Review and approve it then request a review from Crossed. Make sure the author edited both the Golden and Sage config files.
| |
| Do not self-merge a pull request.
| |
| Do not unilaterally merge balance changes.
| |
| Follow and enforce the code contribution guidelines.
| |
| If you break everything or otherwise act maliciously, please refer to the Demotion Procedure section.
| |
| PR Vote Procedure
| |
| Any PRs other than pure fixes/code improvements should typically receive a vote.
| |
| 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
| |