Running a clan

Ranks#

• Leader — one per clan. Can do everything.
• Officer — invite, accept join requests, kick members (not officers), manage the vault and the recruiting post, give guest passes.
• Member — sees the roster and map, drops pins, sees the vault locks their rank allows, and votes.

Size#

Joining#

Two doors, one result:

• Invite — an officer invites a linked player from the site. The player gets a DM and accepts on the site.
• Request — a linked player presses Request to join on a recruiting clan's page. Officers accept or decline.

Either way you are pending until the log sees you at the clan's base — anything the log records you doing within 50 m of the pole. Then you are a full member: Discord role, channel, map, vault. An invite or request that is not acted on expires after 7 days; a pending member who never shows up at the base drops off after 7 days too.

One clan per player. Joining another means leaving first.

Leaving and kicks#

Both put you on a 3-day cooldown before you can join any clan. Same length either way — "just kick me" should not be a faster exit. Disbanding exempts everyone. Leaving or being kicked gives up your share of the clan's base; after the cooldown you can declare a solo base again.

The Leader#

Transfer

The leader can hand leadership to any full member at any time, with a confirmation step.

If the leader goes quiet

If the leader has no in-game activity for 7 days, any officer — or any member, if there are no officers — can claim leadership on the site. The clan channel is told. The leader has 48 hours to show up in the game; if the log shows them doing anything in game, the claim is cancelled. Otherwise the claimant is leader.

If the leader is removed from the Discord

A leader who is banned, or who leaves the Discord, is gone from the clan at once. Leadership passes immediately to the longest-serving officer, or to the longest-serving member if there are no officers. No window, no vote — a clan is never left without a leader.

No-confidence vote

Any time, for any reason. Any full member nominates a replacement — themselves included — and that opens a vote.

• The vote runs 48 hours, in the clan channel and on the site. Every full member votes except the leader. The leader is told at once and can make their case.
• It passes on two-thirds of all full members — not just those who voted. With ten on the roster that is six of nine.
• The electorate is fixed when the vote opens. Members who leave mid-vote drop out of the count; nobody can be added to it.
• While a vote is open, the leader cannot kick anyone, hand over leadership, or disband the clan. Invites still work; arrivals do not vote in that one.
• On success the nominee leads and the ex-leader stays as an officer. Replacing is not expelling.
• A failed vote means 14 days before another. One open vote at a time.

Two consequences, stated so nobody is surprised: the founder can be voted out by the people they invited — the clan is the people, not the founder — and the base declaration does not move, because it is the clan's, not the leader's.

Rebrand#

Leader only, once per 30 days. Change the name, the tag, the flag, or any mix of them. The feed announces it. Your old name and tag are held for the rest of the season so nobody can impersonate you.

A new flag works like founding. Pick it on the site, and it is reserved for you at once. It arrives in your kit at the next restart, and it becomes your flag the moment a member raises it at your pole. Until then you still fly your old flag, and raising either one at home counts, so a raid in the meantime can still be defended. Nobody raises it within 24 hours? It goes back to the pool and you keep your old flag. Changed your mind? The leader can cancel a pending flag change on the settings page, or with /clan rebrand-cancel, and the flag goes back to the pool at once. A change of flag alone costs no cooldown if it lapses or is cancelled; a rebrand that also changed the name or tag started the cooldown when you saved it. The old flag is held for 3 days, then goes back to the pool.

Moving your base#

A member raises your clan's own flag at a pole nobody holds. The leader confirms the move on the site within 24 hours. Your base is now the new pole; supplies follow at the next restart. 7 days between moves. The new pole must be 200 m from any declared base.

The old base gets its 3-day grace before going public — nobody can teleport their loot, and publishing the old spot the instant you leave would make moving so dangerous that nobody would. The 7-day cooldown is deliberately longer than the 3-day grace, so nobody can bounce between two poles and keep both private.

Disband#

Leader only, with confirmation. The flag returns to the pool immediately; the channel is deleted; the base goes public after 3 days; nobody gets a cooldown. The name and tag are held for the rest of the season, same as after a rename, so nobody can wear a disbanded clan's colors the next day.

Recruiting post#

Officers set Recruiting: yes or no, a play window, a language, and a one-line pitch. It shows on the directory and turns on the Request to join button.

The Vault#

One per clan, on the site, members only. A list of locks: a name ("Front gate", "Loot room"), the current 4-digit code, an optional note, and a minimum rank to see it. You see only the locks your rank unlocks. Codes are hidden behind a tap so they are not on screen in a stream.

• Rotate any lock, or all of them. The site generates fresh random codes. Rotating a code on the site does not change the lock in the game — a member has to go do that. Until someone confirms they did, the lock shows changed in game?.
• History of who added, rotated, revealed or confirmed which lock, and when.
• When anyone leaves or is kicked, every lock they could see is badged known to an ex-member until it is rotated. Nothing rotates on its own.
• The bot never posts a code anywhere. It DMs codes rotated — see the vault, never the codes themselves. A code posted in Discord can be screenshotted and can never be taken back. A code on the site can.