Alliance rules generator

Pick the rules you actually enforce, choose the tone that sounds like your alliance, and copy the notice. Nothing is stored anywhere but your own browser.

Your notice

Why the tone selector is the part that matters

Most alliance rules fail for one of two reasons, and neither is the content. Either they are written in a register nobody in that alliance uses, so they read as somebody else's rules pasted in — or they are so gentle that nothing in them is actually a rule, and the first time a leader tries to enforce one it looks arbitrary.

Each clause here is written three ways. Plain says the thing. Warm is for a social alliance where the rules are a floor rather than a filter. Firm is for a competitive one where a slot is worth something and everyone knows it. The same rule about going quiet reads as "a message keeps your slot" in one and "we will not chase you twice" in another. Pick the one you would actually say out loud.

Enforce fewer rules, better

Not every clause is switched on by default, and that is deliberate. A rules notice with sixteen items in it is a notice nobody reads to the end, and every rule you list but do not enforce teaches the alliance that the list is decoration. Turn on the ones you will act on, and leave the rest off until you need them.

The clauses about rally leads, solo attacks, planned breaks and accounts start off for exactly this reason: they matter enormously to some alliances and are noise in others.

No numbers, and the brackets are yours

You will not find an inactivity window, a power requirement or a point threshold written into any clause. Where one belongs there is a bracket — [your window], [names or ranks], [event] — for you to fill in.

Two reasons. The first is that these are your decisions, not ours, and an alliance that inherits somebody else's thresholds ends up enforcing rules it did not choose. The second is the rule this whole site runs on: a number reaches a page here only with its source and the date it was read attached, and a generated document cannot carry that. How we verify has the rest.

What to do with it once you have copied it

Put the short version in the pin and keep the full version where new members can find it. The pinned notice is what people read; the full document is what you point at when something happens. The message templates page has a shorter pinned version alongside the onboarding message that should go with it, and the two are meant to be used together — a new member who reads the welcome message and the pin in their first few minutes almost never needs the long document at all.