Punishments

A screenshare is how staff check that a player is competing fairly. It exists to protect the people who play honestly, and it is only ever started from a valid report and with the player's consent.

• It applies to every player, whatever their role, once they are reported and frozen
• It covers Minecraft tier tests, ranked-style matches and events run by Kyriadon
• It does not cover anything outside the community, and nobody is inspected "just because"
• Anything this charter does not forbid is allowed

Nothing on your PC is looked at until you agree. Agreement can be spoken, typed in the ticket or shown by your actions, and you can withdraw it at any time. Withdrawing counts as a refusal, see the offense in the cheating category.

• Explicit consent: you say yes to the manual check, to the scanners and to the remote connection
• Implied consent: accepting the remote connection or running a required scanner counts as agreeing to that part
• Optional tools: a tool that is not marked required can be declined without penalty, the screensharer then checks that part by hand
• No force: nobody can make you share your screen, and nobody will try

The charter is the only document that governs screenshares. A ticket, an appeal or a request must follow it, and nobody can overrule it for one player.

• Only @Screenshare Manager can change the charter; changes take effect after an announcement in #Announcements
• @Staff who are not on the screenshare team cannot inspect players or their PCs, they can only pass reports on
• A person who is not part of the team has no authority here, and a suspect may refuse them without penalty
• Where the evidence is thin or disputed, the decision favors the suspect and the case stays pending

A report starts everything. Reports that skip these steps can be denied, so it pays to do them properly.

Reporting out of spite after a loss is screenshare misuse. A reporter judged to have done it cannot report for the next 24 hours.

You are frozen when a screensharer tells you in the ticket (or in your DMs). From that moment the clock starts, and a few things are asked of you.

• Show up in the ticket within 5 minutes: typing a message there is enough
• Do not close Minecraft, shut down or restart the PC, or leave the Discord server
• Do not delete, move or rename files, and do not run cleaners or optimizers
• Keep your DMs open and your notifications on, closed DMs do not excuse a missed message
• You may finish the match you are in. You may queue for one more match before the screenshare is claimed, a second counts as stalling

Every screenshare follows the same order. The screensharer explains each step before doing it, and you can ask what any step does.

Screensharers use well-known, publicly available tools. None of them changes your PC: they read, they list and they compare. Tools marked required cannot be declined, everything else is optional.

These are the commands a screensharer may run during a screenshare. Every command in this list only reads information, none of them deletes, changes or installs anything. Each one is explained so you know what is on your screen and why.

Run them yourself in a normal Command Prompt or PowerShell window to see exactly what staff see. A command marked "Needs admin" only works from an elevated window.

The screensharer reads the output with you watching. Output that contains personal information (account names, paths with your real name) is not copied into the ticket.

These rights apply from the moment you are frozen until the ticket is closed. A screensharer who ignores one can be reported to a @Screenshare Manager in #Appeals.

The "after match" countdown starts when the match channel closes for any reason other than inactivity, and otherwise one minute after the match ends.

A verdict always comes with a written reason. The more serious the punishment, the clearer the evidence has to be.

• A scanner result alone never decides a verdict, a person always reviews it
• Evidence is kept as screenshots, hashes and the exact command output
• A player who knowingly picks a lighter offense to dodge a heavier one is punished for the heavier one

For minor offenses a screensharer can choose an alternative to a ban, especially for new players and when something outside your control played a part.

You can appeal any punishment from a screenshare except the unappealable ones. An appeal is judged on the charter and on the evidence, not on who is asking.

• If a decision takes longer than 24 hours, staff will tell you why
• A suspect who recorded the session through a tool that is not allowed loses the appeal for that case
• A suspect who was rude or abusive to a screensharer cannot appeal verbally for the length of a medium or heavier penalty
• Unappealable offenses are marked on their own embed, for example bribing a screensharer

A screenshare looks at a PC, so how that data is handled matters as much as the check itself.

• Purpose: the data is only used to decide the case in front of the screensharer
• Access: only the screensharers, @Screenshare Manager and @Owner can see a screenshare record
• Retention: records are deleted 90 days after the ticket closes, unless an appeal is open
• No collection: no passwords, no personal files and no private messages are copied
• Your copy: you can ask for the evidence in your own case, it is shared in the ticket or in your DMs
• Reuse: screenshare evidence is never posted publicly and never used for anything else

Future versions are announced in #Announcements. The date and version at the top of this panel always match the newest entry here.

Filling a channel with noise so other people cannot read it. This is the most common offense and the lightest one.

• The same message, emoji or sticker sent again and again
• Walls of capital letters or a long run of symbols
• Several messages in a row that could have been one
• Using bot commands outside the bot channels to flood a chat

A burst of spam inside a single minute counts as one offense, not one per message.

Pinging people or roles without a reason, or pinging again before anyone had a chance to answer.

• Pinging @Staff or a whole role for something that is not urgent
• Repeated pings to the same person within a short time
• Mass mentions, including @everyone and @here where they are not allowed

Posting where the post does not belong. Every channel has a description, and reading it is part of using it.

• Off-topic conversations in a topic channel
• Questions that the guides on the website already answer
• Bot commands outside the bot channels

Treating a member or a staff member without respect. Disagreeing is fine, attacking the person is not.

• Insults, name calling and mocking someone for how they play or what tier they have
• Arguing with a staff decision in public instead of in a ticket
• Baiting people into an argument
• Continuing after someone has asked you to stop

Targeting a person over time, in public channels or in direct messages. One heated message is disrespect, a pattern is harassment.

• Following someone from channel to channel or into their messages
• Piling on with other people
• Repeated unwanted direct messages after being told to stop
• Using an alternate account to keep contacting someone who blocked you

Slurs, hateful jokes and discrimination about race, gender, religion, sexuality, disability or nationality. Intent does not matter, a joke that uses a slur is still a slur.

• In messages, nicknames, statuses, avatars and voice chat
• Quoting a slur "to make a point" is treated the same way
• Symbols or code words that stand for hate

The offenses staff never take lightly. They are removed on sight, the ladder does not apply and there is no warning.

• Threats of violence, even as a joke
• Posting or threatening to post personal information, such as addresses, photos or accounts
• Telling someone to hurt themselves

If you are in danger or someone else is, contact your local emergency number first, then tell staff.

Sexual, graphic or shocking content anywhere on the server. The server includes avatars, nicknames, statuses and bios, not only messages.

• Images, videos, links and emojis
• Profile pictures, banners and display names
• Describing graphic content in text

Links and files that can hurt someone else: malware, IP grabbers, token stealers, fake giveaways and fake login pages.

• Sending them in channels or in direct messages
• Sending them "by accident" from a hacked account, until it is secured

Promoting servers, products or social accounts nobody asked about.

• Invite links in channels, and invites sent in direct messages to members
• Promoting your own channel or stream outside the channels made for it
• Selling services, accounts or ranks

Pretending to be a staff member, an owner or another member.

• Copying a name or avatar to look like someone else
• Claiming a role you do not have
• Claiming to speak for Kyriadon or its staff

Sharing something that belongs to another person without their permission. Doxxing with a threat is covered by its own offense above.

• Private messages and screenshots of private chats
• Real names, locations, photos or account details
• Posting screenshare or punishment evidence in public

Anything that makes a voice channel hard to use for the people in it.

• Shouting, soundboards, voice changers and music without everyone agreeing
• Joining and leaving repeatedly
• Recording people without telling them

The Discord respect rules apply in game too, in chat, on signs, in books, in player names and on skins.

• Insults, slurs and spam in chat
• Signs and books with the same content
• Names and skins that would be removed on Discord

Destroying, stealing from or ruining what belongs to another player or to a match. This applies in normal gamemodes. In an SMP-based gamemode griefing is allowed and is never punished.

• Breaking builds and taking items that are not yours
• Ruining a match on purpose, for example by trapping or blocking
• Helping someone else do it

Repeatedly killing players while they respawn or enter a match. This applies in normal gamemodes. In an SMP-based gamemode spawn camping is allowed and is never punished.

• Standing at a spawn only to kill
• Following a player back to their spawn on purpose

Working with opponents to inflate kills, wins or points, or teaming in a mode that does not allow it.

• Agreeing not to fight each other
• Trading wins or taking turns losing
• Farming a friend or an alternate account

Using a glitch, a duplication method or an unintended mechanic to get ahead.

• Duplicating items or currency
• Using a bug to avoid damage, escape a match or reach places you should not
• Teaching the method to other players

Anything that slows the server down or crashes it for other players.

• Lag machines and redstone clocks built to overload the server
• Items or entities spawned to crash clients
• Tools or commands that do the same from outside the game

Buying, selling or trading accounts, items, ranks or tiers for real money or any outside currency.

• Selling a tier, a test result or an account
• Buying carries, boosts or results
• Offering to do it in direct messages

Testers give their time for free. Be polite and accept the result.

• Insulting or arguing with a tester during or after a match
• Spamming testers in direct messages
• Begging for a different result or tier

A tester accepts you, so you must be online and ready. The queue in #Testing has a limited number of slots.

• Not answering after your slot was accepted
• Queueing and leaving again and again
• Spamming testers to skip the line

Leaving, crashing or stalling a match to avoid losing. In a tier test, dodging counts as a loss.

• Closing the game or disconnecting during a test
• Waiting for the timer instead of playing
• Blaming lag without proof

Picking the wrong region, gamemode or version in the testing form, or giving false information about your setup.

• A region that is not yours, to get a better ping
• A gamemode or version you do not actually play
• Wrong details given to staff in a ticket

Results have to be genuine, and a test only counts if you took it yourself on your own account.

• Arranging a result, trading wins or playing with friends to get a better tier
• Testing on someone else's account, or letting someone test on yours
• Getting a friend to play your match for you

After a test you have to wait for the cooldown before testing again.

• Testing again on an alternate account
• Asking another tester to ignore the cooldown
• Changing your name or details to look like a new player

During matches and events, staff, referees and hosts have the last word.

• Ignoring an instruction from a host or referee
• Joining a different server or mode than the one you were assigned
• Leaving an event match without telling anyone

Any advantage that normal gameplay does not give you. What counts as a modification is decided by the screensharer, with the evidence shown to you.

• Hacked clients and cheat injectors
• Autoclickers, macros and anything that automates input
• Reach, velocity, aim assist, triggerbots and similar
• Disallowed mods, such as ones that remove the hit delay

Things that give an edge without being a cheat client. The allowed list is the reference, and asking before you join costs nothing.

• Mods that are not on the allowed list
• Key bindings or scripts that run several actions at once
• Resource packs and settings that change hitboxes, remove blocks or show more than vanilla

Only one mouse may be plugged in while you play or test, because a second one can hide a macro device.

• Two mice at the same time, even if one is broken
• A mouse with its software closed or not installed

Some Windows services write the records a screenshare reads. Turning them off leaves a gap that nobody can look into.

• The services are SysMain, PcaSvc, DPS, EventLog, Schedule, WSearch, Appinfo and DusmSvc
• System optimizers and "tweak" tools that switch them off
• Customised Windows builds that cannot turn them back on

Keeping the services on is your responsibility. Leaving them off without checking is not treated with leniency.

Telling the screensharer, or showing them, that you are using an advantage. It is treated like a detection.

• Saying you use a client, a macro or an autoclicker
• Showing the software when asked
• Telling the screensharer you cheated in the match that was reported

Saying you will not take the screenshare, or ending it before it is over. It applies to the required steps only, an optional tool can always be declined.

• Saying no to the remote connection or to the required scanner
• Withdrawing consent once the session has started
• Naming a screensharer you want to be checked by, in a hosted event

Slowing the screenshare down or going quiet after you were frozen.

• Not showing up in the ticket within 5 minutes of the freeze
• Not complying with the screensharer within 10 minutes of the claim
• Queueing a second match before the screenshare is claimed
• Going AFK while frozen, or reconnecting over and over

Closing the game, shutting the PC down, rebooting it or leaving the Discord server after you were frozen, whatever the reason.

• Closing Minecraft or the remote tool mid-session, even if the game crashes
• Shutting down or rebooting the PC
• Leaving the Discord server while frozen, or before the request exists

A screenshare that cannot happen for a reason that is not your fault. This is the lightest offense in the category and the only one with five steps.

• A very slow PC or connection, or no admin rights
• Problems with the remote tool that you did not cause
• A customised system where staff cannot do their checks

Removing, moving or renaming files after you were warned not to log off or after you were frozen.

• Deleting a client, a mod or a folder
• Emptying the recycle bin, the Recent items or the Minecraft logs
• Running cleaners or optimizers close to the screenshare

Owning or running software that hides, deletes or changes evidence on a device, including anything built to beat screenshare tools.

• Log, journal and trace cleaners
• File shredders and string cleaners
• Hardware that gets around a screenshare, such as direct memory access cards

Anything done to hide a rule break from a screenshare. A bypass attempt is worse than the offense it hides.

• Clearing the event log (event 104 in the System log is the sign), the journal, the registry or the Prefetch folder
• Restarting or stopping services right before a screenshare
• Replacing or overwriting files, running scheduled scripts or using virtual drives
• Switching PCs, or showing a clean device in place of the real one
• Lying to the screensharer about your setup, or picking a lighter offense on purpose

Using a bypass that is sold to players, or making, selling or sharing one, even for free.

• Software sold to get around screenshares
• Passing it on in direct messages or in public
• Recommending it to other players

Offering or giving anything of value to a screensharer in exchange for a good result.

• Money, items, ranks or favors
• Offering it before, during or after a screenshare
• Doing it through another person

There is no verbal appeal for this offense.

Abusing the report system. Reports exist to protect fair players, not to get back at someone.

• Revenge reports, or reporting someone to stop them from queueing
• Reports that are false, as a joke or from a loss
• Bribing or tricking someone into breaking the screenshare rules
• Reusing a screenshot from an expired report to get around a limit

Every ladder in this schedule is built from the same few punishments. Each one is shown with a text label and, where it applies, its exact length.

A ladder is the list of steps an offense follows. Every time you repeat the same offense inside its counting period, you move one step up. The last step stays the last step.

• Staff choose a punishment from the severity, the intent and your history, and serious offenses can skip steps
• Two offenses at the same time do not add up, the longer punishment applies
• A ban always counts from the moment it is issued
• Offenses that have no ladder start at the step shown, for example a permanent ban

The period starts on the day of the last offense of the same kind. Staff never raise a punishment because of an offense that has expired.

Joining on another account to get around a ban, a mute, a cooldown or a tier decision.

• Making a new Discord or Minecraft account while you are banned
• Using an alternate account to take a test again
• Helping someone else do it, or lending your account for it

Your account is yours alone. Tiers, roles and perks belong to the person who earned them and cannot be transferred or traded.

• Giving your login or session to someone else
• Logging in for someone else
• Selling, buying or lending a tier, a role or an account

Everything you give staff, in forms and in tickets, has to be accurate. This is the first thing you do with #Register, so it is also the first thing that can go wrong.

• Linking Minecraft or Discord accounts that belong to someone else
• Wrong details in the registration or in a ticket
• Lying to staff or to testers when asked directly

Staff make the final call in the moment. Comply first and open a ticket afterwards.

• Continuing after staff told you to stop
• Arguing with a decision instead of using a ticket
• Pretending not to see a message from staff

Evidence, accusations and arguments belong in tickets and appeals, not in public channels.

• Posting punishment evidence or accusations in public
• Dragging a personal conflict from another server into Kyriadon
• Calling someone out instead of reporting them

Roles are earned through registration and testing. Boosting and supporting follow the same rules as everyone else and are never a way to get out of a punishment.

• Asking staff for a role, a permission or a tier change
• Asking again after being told no
• Offering something in return

You can appeal any punishment in this schedule except the ones marked not appealable. An appeal is judged on the rules and on the evidence, never on who is asking.

Do not post your appeal or its evidence in public. It makes no difference to the result and it is a callout.