BOARDRAID
中文 Find Player

Rules

BoardRaid Rules

Last updated: September 16, 2026

These rules apply to public matches in Ranked, Casual and Custom Rooms.

Rules cannot list every situation: behavior this page does not spell out can still be ruled a violation. The management team decides the final ruling and the size of the penalty.

If you are unsure about a rule (especially whether some mod or some action is a violation), ask first, through the communities listed in the footer. Until you get an answer, do not assume that anything not banned may be used.

1. Overview

These rules are built on the Minecraft speedrunning community (speedrun.com/mc) v7 rules for 1.16.1 Any% Glitchless: except where this page states a difference, that rule set applies as written.

A match starts when matchmaking succeeds and the match can no longer be cancelled; from that point these rules are in force.

One player uses one Minecraft account, and one account is used by one player. If you need to change accounts, contact the management team first.

This applies to public matches in Custom Rooms too: the host may agree on their own way of playing, but nothing agreed inside a room excuses cheating, boosting or personal attacks.

Inside a match you must not edit options.txt to reach settings the in-game sliders cannot set, and gamma stays inside the 0-5.0 range the speedrun rules allow; only officially approved launchers may be used to play; modifying game code or resource files to gain a match advantage is forbidden, with non-transparent skin and cape appearance changes excluded.

2. Match Rules

The board is the only objective: both sides complete tasks on the same board (or on their own board), and the first side to reach the win condition wins. The board settings are fixed before the match starts:

  • Board Size: 3x3 to 7x7, the larger the size the more tasks;
  • Board Difficulty: Ranked mode (the same difficulty mix as Ranked) or Casual mode (difficulty drops sharply);
  • Board Assignment: random assignment, drafting the board together, or custom board content;
  • Win Condition: complete 15 advancements (Ranked mode), complete one line (BINGO line mode), or complete every advancement (Challenge mode);
  • Seed: the ranked seed library, generated at random, or specified by hand.

Once a match has started, do not leave the world, quit the game or crash the game to escape the match; the exception is a case where leaving really is necessary (for example the game is frozen and cannot be recovered).

After a disconnect you can reconnect and continue; staying offline for a long time is treated as a forfeit. A voluntary surrender counts as a loss.

Inside a match Open to LAN is forbidden; running game commands is forbidden unless the BoardRaid system runs them by itself; changing the system time to trigger time-limited game content is forbidden; unnecessary Save and quit to title is forbidden; only the very few accident and bug-recovery cases that v7 allows are permitted, and it must never be used to gain a match advantage.

3. Client and Mods

You must use an official BoardRaid release; modified versions and versions of unknown origin are not allowed.

Before a match the client checks the loaded mods and does not let you in if anything is outside the whitelist. This check must not be bypassed, and a whitelisted component must not be replaced by a modified component carrying the same name.

The whitelist is built from the mods shipped with the modpack plus the mods the speedrunning community accepts as legal in v7; the two sources are listed on the Download page and the OSS Licenses page. A mod that is not on the list needs a question first, even if it looks harmless.

Key registration depends on key-binding-api, provided by Speedrun API or Fabric API; when both are missing, the mod crashes outright during key registration (see the "Just the jar" section on the Download page).

Resource packs and texture packs: aligned strictly with v7 rule A.4 Resource Pack Rules. Only vanilla, programmer art, high-contrast color-blind packs and the accessibility packs on the official speedrun whitelist are allowed; the limited appearance changes that are allowed stay strictly within the items v7 lists. Anything that brings an information advantage is not allowed (highlighted ores, see-through effects, simplified far rendering, changed block collision hints). Non-default shaders (Super Secret Settings) are forbidden.

DLL injection follows the speedrunning community v7 rules unchanged (which is why ToolScreen can be injected). To inject a DLL outside the whitelist, contact the management team and ask for permission; third-party recording and overlay DLLs are allowed by default under the speedrun rules.

Reset mods (Atum, SeedQueue and the like) may not be interacted with after the match has formally started. For the log and state files a mod writes, only the legal read scenarios listed by v7 apply inside a match; reading them to work out this match's board, resources or mob spawning is forbidden.

4. Keys and Rebinding

Rebinding follows speedrun.com/mc v7 rule A.10 Macros and Key Rebinding. BoardRaid keeps its rebinding rules in sync with the speedrun rules and changes nothing in them; players are encouraged to read rebinding the same way the speedrunning community does.

Under the speedrun rules: each game input may bind to only one physical key, and each key may trigger only one game input; binding an F3 combo shortcut (Shift+F3 and the like) directly to a single key is forbidden. The input source must be a button, and binding to the mouse wheel is forbidden. Apart from a few exceptions, all in-game control settings may be used. For example, using the in-game settings to bind one key to several controls is allowed; binding "Attack / Destroy" or "Use Item / Place Block" to a keyboard key in order to exploit repeated input is not.

No macros, auto-clickers or button-mashing tools, and no input performed on your behalf by any external program.

Only window-resize macros and toggle sprint macros are allowed, and the bounds on window-resize macros follow the speedrun rules. A reset macro must be triggered by the player by hand; it must not read game files or the screen to reset automatically on its own.

Do not resize the game window to a resolution outside your display (the single window resize the speedrun rules allow is the exception).

5. External Tools and Information

This section follows speedrun v7 rule A.11 External Resources: you must not read the game's statistics or advancement files during a match. The calculator, printed paper reference sheets and named whitelisted external tools that the speedrun rules allow are all disabled in BoardRaid matches; that is a difference specific to this project.

The difference on this page: NinjabrainBot may be used (its version ceiling follows the version on the speedrun whitelist); other tools of the same kind are still not allowed.

No external program or tool may read or infer this match's board state. A tool that takes a few tasks from your board as input and works out a route for you, for example, may not be used in a match.

Looking up public material by hand is allowed (the crafting recipe of an item on the Minecraft Wiki, for example), but what you look up has to be public knowledge about the game and must not touch this match's specific board, seed, mobs or spawning information.

Do not get information about the match you are playing through any external channel, including watching your opponent stream (stream sniping).

In Ranked the calls have to be your own: someone else deciding for you, or calling the route for you over voice (reading the board to you), is not allowed. When someone breaks a rule for you or makes things easier for you, both you and they can be found in violation.

External programs that read your screen or listen to your audio to get game information out of a match are forbidden; screenshot, OCR and audio analysis are all disallowed.

6. Seeds and Glitches

Do not try to obtain, work out or use the world seed during a match, whether the match uses a ranked seed or a random seed.

Glitches follow the speedrun.com/mc v7 D.1 Glitchless glitch list: only the glitches that rule D.1.1 explicitly allows may be used, everything else is forbidden; for cases this page does not cover, ask before using them.

Currently allowed:

  • Breaking bedrock; the exact conditions and how it is done are in the D.1.1 allowed glitch list of the Minecraft speedrun v7 rules.

Currently explicitly not allowed (examples, not limited to these; the full list is the v7 document):

  • See-through: X-Ray and its variants, including peeping through blocks while crawling, the camera clipping through blocks, chunk reloads (F3+A) and the like;
  • Walking through walls, or wedging into walls to reach areas that should be unreachable;
  • Duplicating items;
  • Using ghost blocks, or a mismatch between a texture and the real collision, to gain an advantage;
  • Every glitch v7 D.1.2 lists as denied (zero-tick farms, the various teleport glitches, duplication glitches, ghost-block jumping and so on).

7. Cheating

Matches in Ranked mode and Casual mode must follow the speedrun.com Minecraft Any% Glitchless v7 leaderboard rules (within the scope where they apply).

Do not abuse Minecraft glitches. Allowed and denied known glitches follow clauses D.1.1 and D.1.2 of the speedrun.com rules (BoardRaid's own differences are in section 6). Penalty: a queue ban from Ranked and Casual matchmaking, 7 days to permanent.

Do not abuse problems in the BoardRaid mod itself. Penalty: access to BoardRaid blocked, 30 days to permanent.

Do not inject cheats into BoardRaid. Penalty: permanent ban from accessing BoardRaid.

8. Code of Conduct

The basic requirement is to respect your opponent and make sure they get to play the whole match. Do that and this section does not concern you.

No insults, discrimination, harassment, spam, or unsuitable content in in-game chat. Depending on how serious it is: a Ranked queue ban of 7 days to permanent. Serious incidents outside the game are handled case by case; the most serious lead to being hidden from matches and from the leaderboard.

Smurfing: consistently not playing seriously so that your score stays far below your real level and you match weaker opponents. Sustained score suppression triggers an automatic queue timeout; doing it on purpose (deliberately not ending a match you have already won, for example) is a Ranked queue ban of 3 to 14 days.

Match fixing: deliberately throwing a match, or colluding with someone else to produce a preset result, so that one side's score benefits. All participants are penalized together, a Ranked queue ban of 7 days to permanent; the matches involved may be voided.

Boosting and account sharing: playing a match for someone else, or handing your account to someone else to play. Penalty: a Ranked queue ban of 30 days to permanent.

Alting: repeatedly switching between several accounts while queueing. The main account gets 30 days to permanent, the other accounts permanent bans; replacing an account completely because you lost access to it is not a violation, but you must tell the management team in advance.

AFK: not playing the match after matchmaking succeeds. Repeated AFK is penalized with 1 to 7 days.

9. Enforcement and Appeals

Penalties escalate with severity: warning → Ranked queue ban (a few days to permanent); the most serious cases also get access restricted and are removed from the leaderboard.

Rulings use the match records, logs and mod-reported data kept on the server as their main evidence, and screenshots or a spoken account are never the only proof. The management team may ask a player to supply extra evidence such as a match recording; refusing to cooperate can make the penalty heavier.

Reporting: inside the client you can use the report entry on any player you have already been matched with; you can also reach us through the communities listed in the footer.

Appeals also go through those communities, and must state the account, the matches involved and the reason you think the penalty is wrong. A successful appeal shortens or revokes the penalty. Filing an appeal does not mean the penalty will be revoked; it means the case gets reviewed again.

This page updates as versions and gameplay change; changes are announced in the official community. If you disagree with a penalty, contact us first; do not handle it yourself by breaking the rules.