Draft v1.0 — July 14, 2026. Gameplay and moderation policy has been confirmed by the owner. Remove this notice and add the working Discord support link before publication.
1. Event and participation
1.1. Event format
Chaos Event is a fifteen-day event in one shared survival world on a Paper 1.21.10 server. The Nether and the End are dimensions of that same world, not separate servers or resource worlds.
1.2. Who may participate
Players apply to participate. After approval, their Minecraft account is added to the server whitelist; submitting an application alone does not grant access. Streaming is not required: the same rules apply to streamers and players who do not broadcast. The server accepts connections while at least one streamer connected to the event is live.
1.3. Where the rules apply
These rules apply in Minecraft, in chats and voice channels connected to the event, and while using Chaos Event voting or other project mechanics. The baseline conduct rules remain in force during every dynamic event.
1.4. Account responsibility
Participants are responsible for actions performed through their accounts. Giving another person access does not remove the account owner's responsibility. Lost or compromised access must be reported to the organizers immediately.
2. Accounts and voting
2.1. Separate voting systems
Twitch viewers and Minecraft players vote through two independent systems. Each system is counted separately unless the interface for a specific vote explicitly states otherwise.
2.2. One ID, one vote
One Twitch ID may cast one vote in each active Twitch poll. One Minecraft UUID may cast one vote in each active Minecraft poll. Reconnecting or changing a display name does not create another vote.
2.3. Circumventing voting limits
Using additional accounts, sharing accounts, automating votes, or otherwise bypassing the “one ID, one vote” rule is prohibited. Organizers may remove related votes and restrict access to later polls.
2.4. Official results
Only the result recorded by the system and confirmed by the server is valid. A screenshot of an interim result, a chat message, or a third-party poll does not replace the official voting state.
3. Communication and conduct
3.1. Respectful communication
Harassment, threats, humiliation, discriminatory speech, sexual harassment, deliberate conflict baiting, spam, and flooding are prohibited. Players may criticize game decisions, but criticism must not become harassment of participants or the project team.
3.2. Personal data and safety
Searching for, publishing, or distributing another person's personal or confidential information without their explicit consent is prohibited. Real-world threats, phishing, malicious links, and attempts to access another person's account are prohibited.
3.3. Advertising and impersonation
Unapproved advertising of third-party projects, selling in-game resources for real money, and deliberately impersonating another player, moderator, or Dimension Science representative are prohibited.
3.4. Viewers and external actions
A viewer vote, donation, or other action may trigger a system-supported effect, but it does not grant a player or viewer permission to violate conduct, fair-play, property, or safety rules.
3.5. Streams and recordings
The event may appear on live broadcasts and in project recordings. Participants must not disclose another person's private information in-game or in connected chats. Personal matters should be handled through the official support channel rather than in a public broadcast.
4. Fair play and client modifications
4.1. Allowlist rule
Chaos Event uses the same set of permissions and prohibitions as the PepeLand modification list captured on 14 July 2026, while expressing the rules independently for Chaos Event. Only the modifications in rule 4.2 may be used. Any unlisted mod, fork, or client must be approved through a support ticket before use. Later changes to PepeLand rules do not automatically modify Chaos Event rules.
4.2. Allowed modifications
Allowed modifications are: AppleSkin, Autoclicker Legacy, Badlion Client, BetterF3, Blur+, Bobby, Chat Heads, CraftPresence, Distant Horizons, Essential, Fabric API, Flashback, Freecam (Fair Play), Held Item Info, ImagineBook, Iris Shaders, Item Scroller, JourneyMap, Just Enough Items (JEI), LambDynamicLights, Light Level Overlay, Litematica, Lithium, Logical Zoom, MiniHUD, ModMenu, Not Enough Crashes, OffersHUD, OptiFabric, OptiFine, Pochatok, Presence Footsteps, Replay Mod, Shulker Box Tooltip, Simple Voice Chat, Sodium, Sodium Extra, Stendhal, Twitch Chat Bridge, VoxelMap, Voxy, Xaero's Minimap, and Xaero's World Map.
The PepeLand list includes extra limits for several entries: Autofish is lobby-only; Autoclicker Legacy must use a constant delay and may not auto-aim or change the position of the mouse, player, or entities; Item Scroller must be used carefully; Litematica Easy Place Mode is permitted but schemes may not be used for unfair travel or resource gathering; Sodium Extra may not disable lava fog. If Chaos Event has no separate lobby, Autofish may not be used during the event.
4.3. Allowed resource packs
Resource packs are allowed except cheat packs, X-ray packs, and other packs that expose hidden resources or information.
4.4. Prohibited modifications
Auto-totem tools, cheats and X-ray of every kind, changes to standard underwater or lava visibility, and mods, AI, printers, macros, or programs that perform gameplay actions for a person are prohibited.
The following are also prohibited: Accessible Step, Accurate Block Placement, AFKPeace, Aristois, Attack Through Grass, Auto Shulker Inventory Loader, AutoSwitch, Baritone, Bedrock Miner, Better PVP, BetterClicker, BetterHurtCam, Bridging Mod, ClientCommands, CMDCam, Double Hotbar, EasyPlaceFix, Elytra Swapper, Elytra Utilities, Fake Weather, FindMe, FlightAssistant, FreeCam, Impact, Inertia, Inventory Plus, Inventory Tabs, InvMove, ItemSwapper, Jello, LavaClearView, Librarian Trade Finder, LookAtPlayer, MidnightControlsExtra, MultiConnect, No Mining Cooldown, NoFog, NoHurtCam, Peek, SeedCracker, Sigma, Squake, Stack to Nearby Chests, Trajectory Preview, Tweakeroo, Wall-Jump, Wurst, and any copies, forks, or equivalents with the same functions.
4.5. Duplication and bugs
Intentionally duplicating items, currency, or entities is prohibited. Exploiting server, plugin, voting, or dynamic-rule bugs for gain or to harm others is also prohibited. A critical bug must no longer be used and must be reported to the organizers.
4.6. Automation
Macros, bots, and autoclickers are prohibited when they continue gameplay without a person, bypass restrictions, or provide an advantage in combat, gathering, movement, or voting. Ordinary accessibility features are reviewed separately when requested by a participant.
4.7. Consequences of exploitation
Items and progress obtained through a prohibited modification or exploit may be removed. Organizers may roll back an affected area or event state when required to restore fair play.
5. Survival, property, and PvP
5.1. Other players' property
Griefing, theft, deliberate damage to builds, killing another player's pets, and taking items that clearly belong to someone else without consent are prohibited. Direct damage caused by a normal server effect is not automatically a player action, but deliberately directing or amplifying an effect against a specific participant is prohibited.
5.2. Land claims
Land may be marked with any available blocks as long as its boundary is visible and unambiguous. A claim may not overlap another player's land, and markers do not grant the right to hold an unreasonably large area without building. Absence alone never releases a claim: it remains valid until the event ends unless its owner removes the markers or agrees to transfer the land. Moderators intervene only for overlapping boundaries, clearly excessive claims, or disputes, using the visible boundary, actual construction, and action history.
5.3. PvP
PvP is allowed only after every participant gives explicit consent in an in-game or project text chat. Consent applies only to the named participants and the current fight, and ends after a death, disconnection, or withdrawal by any participant unless the parties agreed otherwise in advance. Silence, proximity, and a defensive counterattack are not consent. The exception is a system-announced PvP event whose announcement defines its participants, boundaries, and duration. Pursuit and continued combat are prohibited after the event ends, and prohibited modifications may never be used.
5.4. Traps and hazardous builds
Hidden traps designed to kill other players or make them lose items without consent are prohibited. Public paths, pits, and hazardous mechanisms must be visibly marked and safe during ordinary use.
5.5. Trading
Voluntary in-game trading is allowed. Organizers do not restore items after an ordinary trade dispute, so players should record the terms of a significant trade in an in-game or project chat. Selling in-game valuables for real money is prohibited.
6. Dynamic rules and Chaos effects
6.1. Duration
An activated dynamic rule remains in effect until the system or organizers explicitly replace, disable, or reset it. The end of a poll does not by itself end the selected rule.
6.2. Source of current state
The state displayed by the server and the official project interface is authoritative. If stream text, a chat message, or an older announcement conflicts with the current server state, the server state applies.
6.3. Boundary of permitted chaos
A dynamic rule may change survival mechanics, available actions, or event conditions. It does not remove the prohibitions on harassment, cheats, voting circumvention, theft, manual griefing, or deliberate technical disruption unless the rule explicitly defines a controlled gameplay exception.
6.4. Conflicting rules
A specific dynamic rule takes priority only for the mechanic and duration stated in its description. All other baseline server rules remain in effect. When uncertain, a participant must choose the safe action and ask the organizers.
6.5. Emergency shutdown
Organizers may pause, replace, or roll back an effect when it behaves differently from its description, threatens server stability, or makes the event impossible to continue. This is a technical safeguard, not a result change in favor of a particular participant.
7. Server performance and farms
7.1. Shared responsibility
Intentionally causing lag, overloading chunks, generating excessive items or entities, or building a mechanism whose primary purpose is to reduce TPS or server availability is prohibited.
7.2. Heavy mechanisms
Large portal farms, massive storage and sorting systems, large populations of villagers or other entities, chunk loaders, and permanently active redstone mechanisms may be built or activated only after moderator approval through a Discord ticket. There are no global numeric limits; moderators make the final classification and decision based on the design, location, and expected server load. If a player is unsure whether approval is required, the ticket must be created before construction starts.
7.3. Farm safety
A farm must have an off switch when its design allows one. It must not accumulate items or mobs without control or keep unnecessary areas loaded. Its owner must stop it when requested by moderators.
7.4. AFK and simultaneous operation
Being AFK is not prohibited by itself, but it may not be used for prohibited automation or to keep a heavy farm loaded for a long period without supervision. Running several mechanisms at the same time may be restricted when performance drops.
7.5. Technical intervention
Organizers may temporarily disable a mechanism, remove an emergency accumulation of entities or items, and require a build to be simplified. When possible, the owner will be told why the intervention occurred and how the mechanism may be operated safely.
8. Dimension schedule and the finale
8.1. Overworld
The event starts on 20 June 2027 at 18:00 Moscow time in the Overworld of the shared survival world. There is no separate resource world: resources are gathered in the dimensions available on the current day, subject to the general rules.
8.2. Nether
The Nether opens when day 7 begins, on 26 June 2027 at 18:00 Moscow time. Attempting to enter before the official opening or retaining access through a bug is prohibited.
8.3. End
The End opens on day 15, on 4 July 2027 at 19:00 Moscow time. Entering early or bypassing the closed portal is considered exploit abuse.
8.4. Main dragon
Defeating the main dragon after the End opens starts the ninety-minute Chaos Event finale. The official interface and organizer announcements show the start and remaining finale time.
8.5. Donation dragon
A dragon spawned by a donation event is a separate Chaos effect. Its appearance or defeat does not start, stop, or complete the ninety-minute finale.
9. Failures, deaths, and item restoration
9.1. Ordinary death
Items lost through an ordinary death, another player's rule-compliant actions, a dynamic effect operating according to its official description, or the participant's own mistake are not restored. A malfunctioning effect is reviewed as a possible technical failure under rule 9.2.
9.2. Confirmed technical failure
Restoration is considered only when a confirmed server or project failure directly caused the loss. Decisions are based on server logs and other available evidence; a statement or screenshot alone is not sufficient.
9.3. Review request
A request must be submitted within 24 hours of the technical failure and include the Minecraft name, approximate time, location, circumstances, and a list of lost items. A late request may be denied if logs or other evidence can no longer be checked reliably. The player must not duplicate items or attempt to compensate for the loss through an exploit while the request is reviewed.
9.4. Widespread failure
After a widespread failure, organizers may choose a general rollback, targeted data restoration, or continuation from a corrected state. The decision is published through an official project channel.
10. Moderation and rule updates
10.1. Moderation measures
Depending on severity and repetition, measures may include a warning, removal of unlawfully obtained progress, restrictions on chat or voting, temporary suspension, or a permanent ban. This sequence is not mandatory: a dangerous, deliberate, or severe violation may receive an immediate temporary or permanent ban without a prior warning.
10.2. Evidence
Moderators may use server logs, voting history, recordings, messages, and other verifiable data. Public harassment of an accused participant does not replace a support report and may itself violate these rules.
10.3. Unlisted situations
No ruleset can list every method of harming the event or bypassing its mechanics. In an unlisted situation, organizers assess intent, advantage gained, damage caused, and impact on other participants using the principles of these rules.
10.4. Appeals
Appeals and other requests are submitted through the Create ticket button in the official Discord support channel. A working link is added to the project page before applications open. A ticket must identify the decision, time, and reason for review. Public pressure and duplicate tickets do not accelerate review.
10.5. Updates
Material rule changes are published with a new version and date. A new revision applies from the stated time and is not enforced retroactively, except to correct an obvious wording error or to apply measures required for server safety.
10.6. Acceptance
By connecting to Chaos Event, participating in its votes, or continuing to play after a published update, a participant confirms that they have read the current rules and agree to follow them.