WARZONE #1727 CODE OF ORDINANCES

Preamble

We, the collective leadership of Warzone #1727, in order to form a more competitive server, ensure domestic tranquility, provide for the common defense, promote the general welfare, and secure the benefits of coordinated growth in preparation for Season 1 and beyond, do ordain and establish this Code of Ordinances for Warzone #1727.

Table of Contents

TITLE I: GOVERNANCE AND COMMUNICATION

Chapter 1: General Provisions

§ 1.1 Official Communication Platform.

  • (A) The official platform for server governance, diplomatic relations, and official announcements is the Warzone #1727 Discord Server.
  • (B) Access to the Discord Server shall be maintained via 1727.io.

§ 1.2 Representation.

Representation on the Discord Server is mandatory for alliances seeking protection under Title II or participation in the mutual defense pact under Title IV, as detailed in the relevant sections.

TITLE II: NON-AGGRESSION PACT (NAP)

Chapter 1: General Provisions and Objectives

§ 2.1 Strategic Objective

The objective of the revised Non-Aggression Pact (NAP) structure is the strategic consolidation of active commanders into centralized, high-activity alliances. This policy is essential to maximize collective server strength, resource utilization, and competitive readiness for Season 1.

§ 2.2 Structure

The server-wide NAP is hereby rescinded and replaced by a phased, merit-based system implemented in two phases: NAP20 and NAP10.

Chapter 2: Implementation Timeline and Phases

§ 2.3 Implementation Synchronization

The implementation timeline is synchronized with the conclusion of the VS Alliance Duel week. This allows commanders to complete their events, receive rewards, and relocate with minimal disruption before the subsequent round begins.

§ 2.4 Phase 1: NAP20 Implementation

  • (A) Phase 1 establishes protection for the Top 20 alliances by Total Power that satisfy the criteria set forth in Chapter 3.
  • (B) Effective Date: Phase 1 (NAP20) shall commence on:
    • Loading Timezone... (Your local time)
    • Monday, October 27, 2025 12:00 AM UTC (Server time)
    • Sunday, October 26, 2025 7:00 PM PDT
    • Sunday, October 26, 2025 10:00 PM EDT
    • Monday, October 27, 2025 11:00 AM KST

§ 2.5 Phase 2: NAP10 Implementation

  • (A) Phase 2 establishes protection for the Top 10 alliances by Total Power that satisfy the criteria set forth in Chapter 3.
  • (B) Effective Date: Phase 2 (NAP10) shall commence on:
    • Loading Timezone... (Your local time)
    • Monday, November 3, 2025 12:00 AM UTC (Server time)
    • Sunday, November 2, 2025 6:00 PM PST
    • Sunday, November 2, 2025 9:00 PM EST
    • Monday, November 3, 2025 11:00 AM KST

Chapter 3: Criteria for NAP Protection

§ 2.6 Requirements

To qualify for NAP protection during any phase, an alliance MUST concurrently satisfy all criteria listed in this Chapter. Failure to maintain these standards may result in the revocation of protection.

  • (A) Power Ranking. The alliance must rank within the current NAP threshold (Top 20 during Phase 1; Top 10 during Phase 2), subject to the assessment provisions detailed in Chapter 5.
  • (B) Strategic Hive Location. The alliance hive must be established in the central strategic area. This is strictly defined as surrounding the Contaminated Land (Mud) or situated within the boundaries of the Level 6 cities.
  • (C) Discord Representation and Communication.
    • (i) The R5 (Leader) MUST be present and active in the Server R5 Chat.
    • (ii) At least one (1) R4 Officer MUST be present and active in the Server Leadership Chat.
  • (D) Minimum Membership Threshold. The alliance must maintain a minimum of Fifty (50) members. This requirement ensures organizational viability and prevents the exploitation of NAP rules by individuals or shell alliances.

Chapter 4: Academy and Sister Alliances

§ 2.7 Designation

Alliances protected under the final NAP10 structure (Phase 2) may designate a maximum of one (1) official Academy or Sister alliance.

§ 2.8 Criteria for Academy Protection

  • (A) Academy alliances are exempt only from the Power Ranking requirement (§ 2.6(A)).
  • (B) Academy alliances MUST satisfy all other criteria: Strategic Hive Location (§ 2.6(B)), Discord Representation (§ 2.6(C)), and Minimum Membership Threshold (§ 2.6(D)).

§ 2.9 Identification Requirements

  • (A) The Academy alliance must utilize a clearly identifiable, related tag (e.g., ABC2) and alliance name.
  • (B) BOTH the primary alliance and the Academy alliance MUST explicitly state the relationship in their respective alliance biographies.

Chapter 5: NAP List Management and Power Assessment

§ 2.10 Official List Maintenance

The list of all protected alliances (Primary and Academy) shall be maintained and updated in a dedicated channel on the Server Discord.

§ 2.11 Power Fluctuation and Snapshot Protocol

To ensure that alliances actively participating in major events are not penalized for temporary reductions in power due to troop losses, the following assessment protocol is implemented:

  • (A) Snapshot Timing: An official snapshot of Alliance Power Rankings shall be taken immediately preceding the commencement of the following destructive events:
    1. SvS Warzone Duel (Capitol Invasion Phase)
    2. Sky Predator (Battle Phase)
    3. Meteorite Iron War
    4. VS Alliance Duel (Buster Day)
  • (B) Calculation Method: The active NAP protected list shall be defined as the UNION (addition) of the most recent pre-event snapshot AND the current live rankings. This ensures that alliances previously qualified maintain protection through the event cycle, while also allowing emerging alliances immediate inclusion upon reaching the threshold.

Chapter 6: Temporal Ceasefires

§ 2.12 Rationale

To maximize server-wide participation and performance in critical events, temporal ceasefires may be enacted. This allows all commanders, regardless of NAP status, to contribute to the server's success without fear of domestic attack during these periods.

§ 2.13 Automatic Ceasefires

A full server-wide ceasefire (temporary restoration of server-wide NAP) shall automatically be in effect for the duration of the following events:

  • (A) SvS Warzone Duel (Capitol Invasion phase, regardless of invader or defender status).
  • (B) Sky Predator (Battle phase).
  • (C) Meteorite Iron War.

§ 2.14 Declared Ceasefires

A temporal ceasefire may be declared by the President upon receiving a majority vote from the collective leadership (R5s of currently NAP-protected alliances).

TITLE III: RULES OF ENGAGEMENT (RoE) AND CONDUCT

Chapter 1: General Rules of Engagement

§ 3.1 Plundering Restrictions

  • (A) The plundering of resources for Secret Tasks, Trucks, and Trains MUST be conducted exclusively using targets from external servers (outer-Warzones).
  • (B) Domestic plundering of these assets within Warzone #1727 is strictly prohibited, regardless of the target's NAP status.

Chapter 2: Conduct and Communication

§ 3.2 Engagement with Unprotected Alliances

Attacks on alliances not covered by the current NAP are permitted as a mechanism to encourage strategic consolidation. Standard farming activities from unprotected alliances serve the dual purpose of resource acquisition and incentivizing migration to protected alliances.

§ 3.3 Prohibited Conduct

  • (A) While farming unprotected alliances is permitted, excessive harassment that would cause active players to quit the game rather than seek protection is strongly discouraged.
  • (B) Examples of discouraged conduct include, but are not limited to:
    • (i) Systematic destruction of all members within a single alliance
    • (ii) Repeated ashing (zeroing) of bases without strategic purpose
    • (iii) Persistent targeting designed to force game abandonment
  • (C) Incidental ashing during normal farming operations is understandable and not subject to penalty.
  • (D) While specific penalties are not yet defined herein, violations of these standards will be addressed by the collective leadership. Formal enforcement mechanisms and penalties will be incorporated into this Code of Ordinances in the near future.

§ 3.4 Recruitment Opportunities (Advisory)

When commanders identify players with growth potential in unprotected alliances, it is encouraged (though not required) to:

  • (A) Reach out with recruitment offers before or after initiating attacks
  • (B) Explain the benefits of consolidation and stronger alliance membership
  • (C) Welcome them to join protected alliances or their academies

§ 3.5 Standardized Message Template

For commanders who choose to communicate with targets showing potential, the following message template is provided:

ATTENTION: Your alliance currently does not meet NAP protection criteria. The server is consolidating for Season 1 preparation. You're welcome to join [Alliance Name] or another protected alliance for safety and organized growth. Protected alliance list available on server Discord (1727.io).

TITLE IV: MUTUAL ALLIANCE PROTECTION (MAP)

Chapter 1: Declaration of Mutual Defense

§ 4.1 Declaration (MAP10)

A pact of Mutual Alliance Protection (MAP10) is hereby recognized among the leading alliances of Warzone #1727.

§ 4.2 Scope and Commitment

  • (A) The MAP10 constitutes a commitment to the mutual defense of the server against external threats and invasions during SvS and other cross-server events.
  • (B) Member alliances pledge coordinated defense strategies and strategic support when Warzone #1727 faces outside threats.

§ 4.3 Membership

Membership in MAP10 shall encompass all alliances protected under the NAP10 structure (Title II, Phase 2), including both primary alliances and their designated Academy or Sister alliances as defined in Chapter 4.

§ 4.4 Effective Date

This pact has been in effect since Loading Timezone....