Skip to main content

Title 12 — Opt-Outs & Expulsions

This Title governs how alliances voluntarily withdraw from NAP 9, how they may be expelled, and the conditions for potential reinstatement.

Departing alliances immediately lose all protections and procedural rights under NAP 9.

⚖️ Definitions​

TermDefinition
Opt-OutA voluntary withdrawal declared publicly by an alliance, resulting in immediate loss of NAP protections and rights.
ExpulsionA forced removal from NAP 9 enacted by a Supermajority Council vote.
CooldownA mandatory waiting period before an alliance may petition for reinstatement.
ReinstatementA formal process for rejoining NAP 9 after Opt-Out or Expulsion, requiring Council approval.
Associate RemovalA Simple Majority action removing an Associate Member from NAP 9 due to specific violations.

Article I — Voluntary Opt-Out​

Section I — Procedure​

An alliance voluntarily opts out by making a public declaration in:

NAP Discord → #nap-announcements

Section II — Immediate Consequences​

Upon Opt-Out:

  • All NAP protections end immediately
  • The alliance loses access to all evidence, case, and appeals procedures
  • Previous NAP rulings no longer apply to the departing alliance
  • The Council ceases all jurisdiction over land disputes involving the alliance unless explicitly reopened

Section III — Cooldown​

A 7-day cooldown is required before an alliance may petition for reinstatement.

Article II — Expulsion​

Section I — Grounds​

Expulsion may be considered for:

  • Harboring blacklisted players
  • Repeated refusal to enforce penalties
  • Repeated non-responsiveness to governance communication
  • Interference with governance operations
  • Coordinated misconduct
  • Cross-server collusion
  • Actions indicating the alliance cannot operate in good faith within NAP 9

Section II — Voting Requirement​

Expulsion requires a Supermajority (≥7 YES) vote of the Council.

Section III — Consequences​

Expelled alliances:

  • Lose all NAP protections immediately
  • Lose all procedural rights
  • May not petition for reinstatement for 30 days unless otherwise specified by Council ruling

Article III — Reinstatement​

Section I — Filing a Petition​

After completing the applicable cooldown:

  • The R5 must file a reinstatement petition in #nap-announcements
  • Petition must confirm full compliance with outstanding rulings or penalties

Section II — Voting Requirement​

Reinstatement requires a Simple Majority (≥5 YES) vote of the Council.

Section III — Conditions​

Council may:

  • Deny reinstatement
  • Grant reinstatement with conditions
  • Require verification or restitution before reseating

Article IV — Associate Removal​

Section I — Grounds​

Associate Members may be removed for:

  • Repeated non-response to governance communication
  • Interference with Clerk or Council operations
  • Refusing to honor penalties or rulings
  • Harboring blacklisted players

Section II — Voting Requirement​

Associate Removal requires a Simple Majority (≥5 YES) vote.

Section III — Aftermath​

Vacancies created by removal:

  • Are filled automatically from the waiting queue (if any)
  • Do not bypass eligibility or ranking rules established in Title 1

Article V — Practical Notes​

Section I — Immediate Termination of Protections​

NAP protections end instantly upon Opt-Out, Expulsion, or Associate Removal.

Section II — Post-Departure Disputes​

Land disputes involving departed alliances are:

  • Outside NAP jurisdiction, and
  • Resolved solely by the involved parties unless the Council explicitly votes to open a case

Last amended by Council vote [not amended].