Punishments

Consent

A screenshare only happens once the player has agreed to it.

• •

  Informed consent: A screenshare (inspection) is only conducted after the player has consented to it. That includes agreeing to manual inspection, automated screenshare tools, and approved screenshare utilities.

• •

  Implied consent: Allowing a connection for the inspection, running the automated scanners, or discussing the conduct with the screensharer is enough to validate the screenshare.

Purpose & Scope

• •

  The charter is the procedural framework for screensharing in Ranked Bedwars, to keep conduct fair and honest. It applies to all staff, players and associated parties involved in screensharing, to protect competitors in organised events.

• •

  It is only valid on this community, for as long as the screenshare team has autonomy over the matter. Any change or addition only takes effect after a changelog announcement.

Definitions

• •

  Screensharers: Non-staff team members, kept separate from staff duties, whose sole purpose is identifying cheats on a reported suspect’s device. Also called inspectors.

• •

  Screensharing: The whole procedure. It begins when a screensharer receives a report — verbal (text or voice), formal (the freezing system) or personal (DMs, staff chats, requests from higher-ups; public chat does not count) — followed by review of the evidence and the player being frozen. Any screenshare conducted on a basis other than a permitted one is invalid.

• •

  Players: Every member of the community regardless of role, permissions or status — including ownership, administration, moderation and partners involved in ELO games. A player cannot be screenshared, inspected or penalised under the charter until they become a suspect.

• •

  Suspects: Frozen players undergoing a screenshare. The status lasts until the screenshare ends.

• •

  Authorized personnel: Screenshare management, senior mods, admins, owners, developers, and the individual suspect.

Authority

• •

  The charter is the only binding document regulating screensharing. Any ticket, appeal, application or request must follow it unless the special part says otherwise.

• •

  Only screenshare managers have the authority to enact the charter. No one else on the team, ownership included, may interfere with its regulations.

• •

  Anything not explicitly disallowed by the charter is permitted.

Records, Data & Tools

• •

  Standard protocol: Screensharers follow a standard protocol for starting and running sessions, including obtaining consent and staying transparent throughout.

• •

  Records: Every screenshare is documented. Records are kept for audit and review for no longer than the ongoing season.

• •

  Data access: Screenshare data is visible only to screensharers, screenshare managers, admins and ownership. Measures prevent unauthorised access, and disclosure is only allowed at the player’s request.

• •

  Required tools: Players cannot refuse the Echo or Detect screenshare tools.

• •

  Ocean: Players may refuse the Ocean tool if they do not want to temporarily pause their anti-virus to avoid the packed file being deleted — unless the screenshare is “scan only”, in which case they cannot.

• •

  Who can screenshare: Players and non-screenshare staff cannot screenshare other players, manually or with tools. They may only open reports.

Guiding Principles

• •

  No rule may be made that violates these principles: evidence and appeals are evaluated collectively rather than arbitrarily; where evidence is lacking or disputed, the decision favours the suspect (left in a pending state); suspects are never permanently cleared after the fact in a way that lets them break the charter; and force is never used to screenshare a suspect who refuses.

• •

  Impossible attempts: Nobody can be punished for an impossible attempt. There are two kinds:

  • Factually impossible — e.g. running a discontinued cheat sample that cannot run on the system in its current build.
  • Codified impossible — e.g. trying a bypass that the charter already makes impossible, such as cheating on a different server.

Reporting a Suspect

• •

  A report can only be made by a player who warned, fought and/or personally witnessed the suspect in an ongoing game.

• •

  A request from the administration bypasses the standard reporting procedure.

• •

  If the reporting player is muted, other participants — in-game spectators, Discord stream viewers, AFK bystanders or third-party stream watchers — may not report on their behalf.

• •

  When: Report from the second half of the game up to 7 minutes after it ends, by opening a ticket. If reporting during the game, screensharers must be notified when the game ends before they proceed.

• •

  A suspect may tell the screensharer through the ticket that they are in an ongoing ranked match. Queues do not count.

• •

  Evidence: Reports should include full screenshots of the ongoing game with both of the following clearly visible:

  • The entire chat open (“T” key), including the “Don’t Log” warning that names the specific player being reported.
  • The scoreboard with the date clearly displayed.
• •

  If that is not followed, the request may be denied, or the screensharer may ask for a formal screenshot.

• •

  Untraditional reports: Screensharers can deny reports made untraditionally (Discord DMs, ongoing-game tickets, public chat @-mentions). However, if a player warns the suspect in-game and then additionally warns them through every possible way, screensharers lose the ability to deny the request.

• •

  Late or unclear tickets: Tickets opened after the game ends, after the last final kill, or in hard-to-tell scenarios can be denied.

• •

  Individual screensharers cannot open tickets against players; that is covered by the internal screenshare regulations.

• •

  Anyone interfering with screensharer duties does not hold a screensharer’s authority, so suspects may deny them without penalty.

• •

  Players who find a flaw in the regulations that suggests they should be freed from a punishment may notify the screenshare managers.

Suspect Rules

• •

  Having Discord DMs or notifications closed does not free a suspect from penalties.

• •

  Suspects may refuse repeated screenshare requests from the same individual throughout the day (the next 12 hours).

• •

  Suspects may not choose which screensharers screenshare them in hosted events. Doing so counts as refusal.

• •

  Asking for a different screensharer: Allowed, but if no other screensharer arrives within 10 minutes and the suspect still denies the original one, it counts as refusal. A suspect also cannot request a swap if no other screensharer is online — it counts as refusal if nobody else takes the report within 10 minutes of the initial refusal.

• •

  Asking for a different manager: Allowed. Other managers are notified immediately, but if none arrives within 3 minutes it counts as refusal.

• •

  Suspects can refuse a screenshare from unauthorised screensharers who are not part of the team.

• •

  Not knowing the rules does not free a suspect from the consequences.

• •

  During scans, bans are issued for instant detections.

• •

  A suspect who is aware they are being screenshared and shows their presence loses the ability to appeal on the grounds of being unaware, an invalid report, or any other privilege in the charter.

• •

  A suspect who claims they could not see the report filed against them must show evidence in their appeal. The decision is at the screenshare managers’ discretion.

Time Limits & Cooldowns

• •

  Reports after a game must be made within 7 minutes (valid if issued in under 8).

• •

  The “after game” countdown starts when the game channel closes for any reason other than inactivity; otherwise it starts the minute after the game ends.

• •

  Cooldown on reporting a suspect after an expired ticket: 30 minutes.

• •

  No cooldown after a ticket that was immediately denied without the screensharer even replying.

• •

  If a screensharer concludes a report was made out of personal impulse or bias after losing a match, the reporter cannot issue reports for the next 24 hours, and screenshare misuse rules apply.

• •

  More than 3 baseless warnings not to log off leads to a suspension from screenshare tickets for up to the rest of the ongoing season. The count carries over between seasons and only resets once a penalty has been applied and expired.

• •

  Maximum length of a screenshare: 1 hour 30 minutes (2 hours for special events).

• •

  Average length of a screenshare: 25 minutes (40 minutes for special events).

• •

  A screensharer may be AFK for at most 10 minutes before connecting; after that the request is void and cannot be continued.

• •

  If a screensharer has to leave entirely, the suspect is free to leave if no replacement arrives within 15 minutes.

• •

  The “after frozen” countdown starts when the screensharer first talks.

• •

  A suspect may re-queue for one game before the screenshare is claimed. Queueing another counts as stalling.

• •

  A suspect faces no penalty for logging off 7 minutes after the ticket opens, or closing Minecraft 10 minutes after it opens.

• •

  Stalling is 7 minutes of no response to the ticket. Suspects must show presence in the ticket to avoid a penalty — typing in it or updating consent preferences counts. The ban is then issued for 15 minutes of inactivity after the report ticket opened.

• •

  A player can request only 1 screenshare on the same suspect per day (expired or mistaken requests don’t count). The player base as a whole can request at most 4 screenshares on the same player per day.

• •

  “Before screenshare”: Counted from the suspect’s first ranked match of the day. For clearing files, it is counted from the moment the suspect is warned not to log off.

Light Offenses

• •

  Inability to SS: Split into three types:

  • Type (i): extremely low-end PC or internet, no admin permissions, or issues with remote connection applications, where it is evident none of it was intentionally caused, set up or falsified. The same inability, if intentionally caused or falsified, is punished far more heavily.
  • Type (ii): a customised OS where the screensharer chooses to act with leniency, a suspect who clearly had to leave from the start of the game while avoiding screenshares, or any other form that makes a screenshare impossible.
  • Both types during international holidays get a reduced penalty that escalates on repeat instances but never leads to a permanent ban.
  • Type (iii): if the suspect agrees to tool scans and can run the scanners, the inability is pardoned and the screenshare is considered concluded.
• •

  1+ mouse plugged in: Applies whenever a suspect has two mice connected — even with mouse software pre-installed, even if one is broken, and regardless of any other reason.

• •

  Possession of anti-forensic material: Any software, script or utility designed to obscure, delete or modify digital evidence on a player’s system — generally known as MITRE attacks or digital anti-forensics. Includes Direct Memory Access cards used to evade screensharing.

• •

  Stalling: Going AFK while frozen, or deliberately or unintentionally failing to reply within the given interval. Also applies when suspects re-queue matches to avoid being screenshared.

• •

  Players who were frozen but not added to the screenshare ticket are advised to check their DMs and message requests, in case a screensharer or higher-up could not add them to a general ticket.

• •

  SS misuse: Warning a suspect “as a joke” (regardless of changed intentions), baiting newcomers or other players into breaking screenshare rules, and sabotaging. Covers both baseless and troll screenshares.

• •

  Also applies to suspects who fabricate evidence, or tamper with falsified or context-less evidence, after being banned in order to reduce or remove the punishment.

• •

  Revenge screensharing is disallowed.

• •

  Sabotaging is waiting for a specific team to report with the intent of slowing down the scoring system, wasting time, or bypassing the limitations in this charter.

• •

  Reusing a screenshot from an expired report to get around limitation rules is also SS misuse.

Medium Offenses

• •

  Disabled services: Ranked Bedwars bans for these being disabled: Sysmain (Superfetch), CDPUserSvc_{…}, PcaSvc, DPS, EventLog, Scheduler, SearchIndexer, BAM/DAM, Dusmsvc, Appinfo. Players may open a ticket to verify the services are not disabled — but if the ticket is pending and nobody has replied, they can still be banned if caught. Using optimising software is at your own risk; if you think you are at risk, open a ticket so screensharers can try to fix it for you.

  • Also counts: terminating BAM inheritance, disabled Activitiescache, disabled JumpLists, and terminated threads in services.
  • When a player opens a ticket only to verify service state, staff are not obliged to help toggle them on. Keeping services on is the player’s responsibility, and carelessly leaving them disabled without research or effort to enable them is not subject to leniency.
• •

  Closing MC / AnyDesk: A suspect may not close their game after being warned not to log, nor close AnyDesk mid-session. This applies even if the game crashes. Logging off alone is not bannable unless the suspect simultaneously broke other rules.

• •

  Refusing / Admitting: Same ban length. Refusing is refusing to comply with the screensharer, before or after accepting AnyDesk. Admitting is admitting to the advantages the screensharer asks about.

• •

  Tampering: Same offense as stalling; applies when a suspect deliberately makes it harder for the screensharer to search. Suspects with specific confidential items must tell the screensharer before agreeing to share their desktop. Images, documents, text files and script files are not considered confidential — screensharers only check them if there is reasonable suspicion.

• •

  Cheating: Cheating with hacked clients, cheat applications or unfair advantages, when all of these are true:

  • The cheats did not self-destruct or have alerting self-destruction modules.
  • No bypass methods or anti-forensic techniques were used.
  • The player made an effort to hide the cheat but its form was not altered.
  • No combination of Bypass Attempt offenses applies.

Severe Offenses

• •

  Bypass attempt: Only applies in guaranteed violations of the medium-offense rules. Four types, from least to most severe:

  • Type I — restarting services, clearing the journal, registry entries, event logs or prefetch, string-clearing applications, file shredders, clearing shell:recent, NvAPPTimestamps tampering, and lying to screensharers.
  • Type II — any interaction with PsExec, scripting applications (VS Code, Node.js etc.), overwriting or replacing files on FAT32, using FAT16/32/exFAT drives when the user has a history of mass bans and executions from a FAT drive that is atypical of its common use, re-connecting mass storage devices, and virtual mounts.
  • Type III — scheduled PowerShell / PowerShell ISE / scripting applications / CMD or .bat files, accessing regedit or scripting environments, accessing or running ProcessHacker / SystemInformer / ProcMon, cleaners or optimisers near or during screenshares, WMIC bypass methods, unicode characters on cheats, and a modified default Downloads path.
  • Type IV — switching PCs, public anti-forensics, modifying file data, and combined degrees of offenses. Suspects cannot verbally appeal these; they must purchase an unban.
• •

  Lying to screensharers about your condition, or knowingly selecting a lesser offense to evade proper punishment, gets you re-banned under this rule.

• •

  Illegal modifications: Includes proxy clients (e.g. Lilith), mouse macros, external macros, clients that enable HitDelayFix or Freelook, and applications or launchers banned by Hypixel itself. Cloudflare / Cloudflare WARP is allowed.

  • In force majeure scenarios, screensharers can choose not to ban and instead whitelist the suspect for next time.
  • Any other force majeure, upon appeal, can be pardoned by screenshare management.
  • Launchers used for performance or visuals with no built-in advantage (Lunar, Feather, etc.) are allowed. Lunar QT must not be renamed to confuse screensharers.
  • Any form of ping manipulation (e.g. hotspots) falls under ping spoofing, whether intentional or not, when the player could have opened a rules-inquiry ticket first.
  • Applications or mods that modify mouse input, sensitivity or acceleration are allowed as long as they do not include CPS, hit-delay or other settings banned by this charter or Hypixel.
• •

  Modified OS: Customised operating systems (e.g. Atlas OS) that are impossible to screenshare because most services are off or cannot be re-enabled. Screensharers must try everything to still screenshare the suspect before giving a verdict.

  • If the system disables or limits more than 3 of the settings listed under Disabled Services, the first offense is treated as Inability to SS.
  • Boot Camp Assistant (macOS Tahoe 26 or earlier; Intel-based Mac) is allowed.
  • Having used Swills or other partnered system optimisers that trim the system is not subject to leniency or unbans.
• •

  Ban evasion: Banning alts is the responsibility of non-screenshare staff, but screensharers may still ban alts of users who evade their previous punishments by creating them.

Force Majeure

• •

  An irresistible force or unforeseen event beyond anyone’s control. No player or suspect is penalised if the cause of an offense is an unforeseen event.

• •

  Force majeure events do not stack penalties. They are calculated separately and are not subject to amnesty or pardon by screenshare management.

• •

  If an Inability and/or Trimmed OS offense is judged to be force majeure by the screensharer or manager, the alternative is either a very short ranked ban with the game voided (or not), or no ranked ban at all but a game void or an ELO sanction.

• •

  Using force majeure in bad faith results in Bypass Attempt penalties and moves penalty stacking onto the main penalties.

Alternative Penalties

Suspects banned for light offenses may be sanctioned without a ranked ban instead.

• •

  ELO reduction: Sets the suspect’s ELO down to 400–200, or to one third or one quarter of their current ELO. This is not a deduction.

• •

  ELO transfer: Transfers up to two thirds (or two quarters) of the suspect’s current ELO onto all 4 members of the opposing team. Only permitted if it does not significantly affect the leaderboards.

• •

  Warning of a severed penalty: A conditional penalty: the suspect is let go on the condition they do not repeat the offense. If they do, they are penalised for up to triple the usual length.

ELO Restitution & Compensation

• •

  Restitution: Recovery of 10–20 ELO per game lost to a cheater, if any of these apply:

  • You reported the cheater within the 7-day period of their screenshare penalty and the report was never claimed, or was claimed but took under 25 minutes to finalise, or the suspect was only scanned with tools.
  • You reported within that period but the suspect was released on a technicality (force majeure, procedural error, etc.).
  • Your report within that period was deemed invalid on a technicality.
  • You reported, but the screensharer was bypassed, had to leave, or otherwise caused an unwanted result.
  • You queued against the cheater within the season and management believes they cheated periodically across those queues.
  • The screensharer mishandled a report against the suspect, whether or not they were banned.
• •

  Compensation: ELO you can claim back:

  • 2 ELO per false light offense penalty.
  • 5 ELO per false medium offense penalty.
  • 10 ELO per false severe offense penalty.
  • 5 ELO per falsely denied first-instance appeal.
  • 10 ELO per falsely denied second-instance appeal.
  • 20 ELO per falsely denied appeal to screenshare management.
  • 50 ELO per falsely purchased unban in an unappealable category.
  • 1 ELO per hugely wasted screenshare (30 minutes minimum) throughout the season.

Appeals

• •

  How appeals are handled is set by screenshare management only, based on the charter.

• •

  First instance: Handled by an individual senior screensharer who did not screenshare the person. Nobody may override, influence or disregard their decision, and they face no penalty for incorrectly handled first-instance appeals. Screenshare management is bound by these restrictions.

  • They can handle cases from the reporting, prevention, offense and limitation sections, except Type III–IV severe offenses, unappealable offenses, ELO restitution or compensation, and penalties imposed by ownership or non-screenshare staff.
• •

  Second instance: If the first appeal is denied, a minimum of three senior screensharers plus the original screensharer handle it. The decision is finalised by majority vote.

• •

  Slow appeals: If an appeal takes more than 24 hours, the person is eligible for 1 ELO of compensation per 6 hours wasted, with the initial 24 hours counting.

• •

  Missed warnings: Suspects who miss warnings from players but ask to be screenshared overdue can still verbally appeal — they just won’t be screenshared.

• •

  Medium offenses: Suspects banned for medium offenses who also misbehaved toward screensharers lose the ability to verbally appeal for the whole span of the penalty.

• •

  Replay bans cannot be appealed through screensharing.

• •

  Any offense where the suspect recorded the session using the screenshare appeals system cannot be appealed.

• •

  Suspects lose the ability to appeal a penalty if they do not appeal within the ongoing season.

• •

  New players: New members get a short, reduced penalty for their first light-to-medium offense so they can properly read the regulations; their offenses don’t stack from that penalty. Players whose medium-to-severe bans were caused by force majeure may receive a single-day penalty if they can prove it was out of their control.

• •

  Procedural errors: Players banned through an incorrectly handled screenshare are unbanned regardless of offense stage, or re-banned for a reasonably lesser penalty. Players banned because of misinformation from staff or screenshare managers in a rules-inquiry ticket are unbanned if the ban was issued on that clarification. Scoring management decides whether the games are voided, to keep things fair for the suspect, the reporter and the community.

Unappealable Offenses

• •

  Continuous cheating and bypassing: Leads to a blacklist from the screenshare team. Continuous cheating alone does not get a suspect blacklisted, but possessing, creating, selling or distributing (even for free) bypasses to players makes them accountable.

• •

  Bribing screensharers: Managers can’t control their screensharers’ greed, but a suspect who bribes one is permanently banned with no verbal appeal, and the screensharer is demoted. The same applies to screenshare managers.

• •

  Organised alting: Organising a group of players to alt on one shared account to avoid or complicate screensharing, to confuse, mislead or manipulate staff, or to have a clean device screenshared in place of the real one. Everyone involved is covered, by role:

  • The instigator (original account owner) — permanent ranked ban or server ban; unappealable verbally and by purchase. May remain on the server as long as they cause no complications in appeal tickets.
  • The accomplice (participants in the plan) — permanent ranked ban or server ban; unappealable verbally and/or by purchase.
  • The assistant (those who deliberately confuse staff or hide information before exposure) — permanent ranked ban, unappealable verbally; may purchase an unban (which does not count as a screenshare unban).
  • Ownership or event organisers have full authority over this section and may overrule, change or ignore it, since event funds are at risk.
• •

  Popularising bypasses: Suspects caught using popular bypasses (sold for above $20), or bypasses above $15 specifically aimed at Ranked Bedwars, skip all steps and begin with a permanent, unappealable ranked or server ban. They can only be unbanned by buying an unban from the store.

  • Ranked ban: they have not bypassed more than one individual screensharer, have not gone “too far” up the leaderboard (top 10, above 1200 ELO), and were not caught too late (after 1/3 of screenshare requests or 2/3 of the season).
  • Server ban: they bypassed more than one screensharer or at least one screenshare manager, went “too far” up the leaderboard, or were caught too late.

Legal, Data & Guarantees

• •

  Data: Players’ data is subject to the terms of the allowed autonomous scanner (Echo). Manual inspections are subject to data protection laws, and every screenshare document, ticket and consent form comes with informative clauses in plain English. Screensharers explain any complication or misunderstanding without rushing or being rushed.

• •

  Data during inspection is governed by the EU Charter of Fundamental Rights (Article 8), GDPR, the UK Data Protection Act, US data privacy laws and the European Convention on Cybercrime.

• •

  Inspections are done by an experienced screensharer following established protocols. The assumed age is 16 until told otherwise; if a suspect is revealed to be under the age of consent, the screenshare can be abandoned and their access restricted. Management may ask a suspect’s country of residence in appeals to apply the right laws.

• •

  Legitimacy: No personal data is collected or required. Inspection starts under informed consent with the legitimate purpose of detecting cheats or banned utilities (autoclickers, disallowed modifications, hacked clients, cheat injectors) and anti-forensic practices. Suspects may admit to cheating or refuse the inspection before it begins.

• •

  Remote control: Inspections run over remote connection (TeamViewer or AnyDesk). Players keep control of their device, may move their mouse, and may refute any action by the screensharer. Penalties for that are only issued when:

  • The screensharer is about to detect a cheat file or bypass and the player prevents it.
  • The screensharer reasonably believes, from experience and insider information, that the player is using an anti-forensic technique based on objectively unusual evidence.
  • The player is purposefully mocking the inspection to run out the time limit.
  • The player has cheated and been banned before.
  • Other scenarios defined in the special part of the charter.
• •

  Guarantees: Screenshare administration guarantees no clause is breached by inspectors or management.

  • Every player may review the evidence collected against them, unless they are on the verge of a blacklist or a second permanent screenshare ban and the evidence is beyond doubt. It can still be requested and provided to them under a parent’s supervision if they are under 18.
  • Undisclosed evidence can be handed to the banned player after two months of the penalty, or sooner if the bypass, cheat or technique they were banned for has leaked publicly.