Fair play

Everything else in this guide is enforced by the server log. This chapter is enforced by people.

Break a rule in this chapter and you are removed from the Discord — which removes you from your clan, your link and the site at once. Staff never touch clan state directly. They remove a person, and the log does the rest.

Conduct#

Don't be a dick. No hate speech, slurs, threats or harassment — in game, in voice, in Discord, in DMs.
No doxxing. No real-life pictures of people. Nobody's family.
One account. Playing on two gamertags, or two Discord accounts, is a ban on all of them. Unlinking and linking a new gamertag is fine — that is one account changing, not two.
No stream sniping.
Don't post base locations in Discord. The map exists so you never have to.

Exploits — permanent ban#

No duping.
No glitching: through walls, under the map, into bases, into locked rooms.
No sky-walking, floating structures, or boosting that only works because the game is broken. Legal boosting: a two-player boost, vehicles, and up to two stacked watchtowers, both grounded. Not legal, permanent ban: stacked backpacks, car parts, or anything else used to climb. Stacked fireplaces and garden plots are not on this list any more — see Bases, below, for how those are sentenced now.
No whitewalling or restart abuse — using a loading screen or a server restart to see through walls or find players.
No cheating of any kind — aim assistance, ESP, mods. Clear proof means a permanent ban with no appeal.

Bases#

Every gate must be raidable. No unraidable bases.
No floating structures. Two watchtowers high at most; one if placed on top of another structure.
No building inside buildings that spawn medical or hunting loot. No building on roads.
Never log out inside someone else's base. If you disconnect during a raid, rejoin immediately.
No takeovers of a declared base. You raid it; you do not move in. Undeclared poles that have already gone public are fair game — see Bases.
Build nothing inside a watch zone that isn't yours. A watchtower, a fence, a wall, anything — if you didn't declare that base, you don't build there. The bot catches it from the log the same way it catches a dismantle, and it is sentenced the same way: a breach, on the base's owner pressing charges.
Pitch no tent inside a watch zone that isn't yours. A tent is tall enough to climb a wall on its own, so one tent is the offence — no stack needed. The bot treats it exactly like building there: the base's owner is told, whoever pitched it is warned, and it is sentenced as a breach if the owner presses charges. Your own clan's tents in your own zone are fine.
No boosting with stacked fireplaces or garden plots inside a watch zone that isn't yours. The bot spots the stack from how tight together and how high up the placements go, and warns whoever placed them. If the base's owner presses charges, it's sentenced the same way as a dismantle — a base term, more for breaching the wall, doubled on a repeat offence, permanent on the third. It is not on the exploits permanent-ban list any more: it scales with what actually happened.

Boost raids outside the window#

Base damage is on only from Friday 00:00 UTC to Monday 00:00 UTC. Outside that, you may boost in and lower the flag — that is legal and it scores. You may not dismantle any part of a base that is not yours, and you may not build anything there — a fence, a watchtower, a tent, turning a fence into a gate, none of it. That is true in the window and out of it. There is no carve-out any more: touching someone else's base is never part of raiding, window or no window.

The log records every dismantle and every build, with a name attached, and your watch zone tells the bot which base it happened at. The bot records the incident and warns whoever it caught. From there it is on the base's owner: an officer of the owning clan, or a solo declarant, can press charges from /base within 7 days of the incident going quiet. Press charges and the ban is automatic, scaled to the damage the log shows, against whichever of the people it names you choose to charge. This is the one fair-play rule that skips the ticket queue — every other rule in this chapter still needs a ticket; see Enforcement, below.

A warning DM is not an accusation. There is no helper-permit system, so someone your clan invited to help build gets the exact same warning a raider would — the bot cannot tell the two apart from the log. Nothing happens to them unless an officer presses charges naming them specifically, and an owner who invited the helper simply won't.

If you can boost in, make damn sure you can boost out.

Griefing#

Griefing is destruction with no purpose: dismantling walls you are not raiding through, destroying storage instead of looting it, dumping loot to despawn it, blocking doorways with junk, trapping players.

A raid with intent to loot is not griefing. Tactical destruction to get in during the window is not griefing. Lowering a flag is never griefing — it is the game.

Combat logging#

Don't log out within 10 minutes of combat — shots fired or received, voice contact, or being inside a base while it is raided. An accidental disconnect: rejoin as fast as you can and open a ticket.

No combat at the Hub#

The Fast Travel Hub is a no-combat zone. Hit someone, kill someone, or place a trap or explosive there, and you are banned for 1 hour. It is automatic: no ticket, no staff. The bot reads it straight from the log.

Self-defence is allowed. If someone hits you, you may hit them back for 2 minutes. Whoever lands the first hit is the one banned.
The Hub is everything within 100 m of the arrival point, up in the sky. The ground directly below it is ordinary map, and a fight there is fine.
A kill at the Hub counts for nothing: not on the boards, not your K/D, not a streak, not an achievement. Kills made there before the rule came in still count — nobody broke a rule that did not exist yet.
Every offence is its own 1 hour ban, never longer. More hits while that ban is on its way don't add to it.

Bounties#

Staff can put a bounty on a player as a punishment. It is announced in the server events channel, and until it ends, that player's position shows on everyone's map while they are online — logging off takes them off the map.

It ends when another player kills them, or once they have played 72 hours online (staff can set up to 7 days). Only time on the server counts: logging off does not run the clock. After 30 days it ends anyway.
Friendly fire does not collect a bounty, and neither does a kill at the Hub. Neither does a fall, a zombie or a suicide — unless another player's hit caused it, in which case it's a credited kill and it counts.
Whoever collects it is credited in the channel and on the Most bounty kills board.

Enforcement#

Report through a ticket, with video. Staff cannot act on "trust me". Dismantling, building, pitching tents and boost-stacking inside a watch zone are the exception: the bot catches them from the log, and the base's owner presses charges from /base — no ticket, no staff. Combat at the Hub is the other exception: the bot bans it on its own.
Warning, then temporary ban, then permanent, at staff discretion. Exploits and cheating skip straight to permanent.
Staff never create, edit or delete a clan, a flag, a base or a raid. If it looks like they did, they didn't — a person was removed and the system followed.