A shared reference for community order, player safety, NAP agreements, and appeals.
Version 2026.09.29
Last updated: 29.09.2026
01
Rule file
Respectful Communication and Conduct
Communication must remain respectful and measured in every community area. Insults, threats, harassment, discrimination, targeted abuse, and personal attacks are forbidden. Ideas and actions may be criticized, but people must not be humiliated. Provocation, spam, and deliberately escalating arguments are also violations. Depending on severity and repetition, staff may issue a warning, mute, or disciplinary sanction.
Open rule
02
Rule file
Player Identity and ID Records
The permanent player ID is the primary reference for identifying a player. Name and alliance changes are stored in the player's history and do not erase earlier violations or sanctions. Attempts to hide identity or provide misleading information to evade records are reviewed as an additional violation. Reports should include the correct player ID whenever possible.
Open rule
03
Rule file
Alliance Security and Server Order
Conduct that intentionally disrupts alliance order or server peace, repeated violations, coordinated harassment, and provocation are recorded. Disputes between alliances should first be handled through leaders or R4 members, and retaliation must not begin before the review is complete. Intent, repetition, and the harm caused are considered together when a case is assessed.
Open rule
04
Rule file
Evidence and Accurate Reporting
Reports should use original and relevant screenshots showing the date, time, player name, and ID whenever possible. Altered, misleading, out-of-context evidence and knowingly false reports are forbidden. Staff considers the complete evidence, available records, and statements from both sides before making a decision. Unrelated personal information must be hidden before evidence is shared.
Open rule
05
Rule file
Event Times and Coordination
All event times are displayed in server time, and countdowns use the same clock. Schedules may change, so players should check the current event page shortly before an event begins. Authorized staff may update the time or cancel an event when necessary. Event-specific alliance, server, and NAP instructions must be followed.
Open rule
06
Rule file
Violation Reports and Appeals
Violations should be reported privately to a leader, R4 member, or authorized staff member with the player ID, incident time, a clear summary, and any available evidence. Public accusations, threats, and retaliation in world chat must not be started. Both sides have the right to explain their position during review. A decision may be appealed once when evidence was missing or new evidence becomes available; unsupported repetition does not reopen a case.
Open rule
07
Rule file
Privacy and Personal Information
A person's real name, phone number, address, social media account, login details, or private correspondence must not be shared without permission. Evidence should hide private information unrelated to the incident. Doxxing, threats to expose personal information, and account takeover attempts are serious violations. Staff will never ask for your game or website password.
Open rule
NAP rules
NAP framework
The basic framework of the server peace agreement.
1 Non-Aggression Within NAP
NAP alliances and their academies are protected. Scouting or attacking any NAP member is forbidden. Accidental attacks may be resolved between the two alliances involved.
Violation penalties:
1st violation: Warning
2nd violation: Compensation
3rd violation: Removal from NAP
2 Farming and Attack Rules
To protect server growth and active players, attacks are limited until the KE event. Active players in non-NAP alliances must not be targeted. Only inactive players without a shield may be attacked. The goal is to farm resources without driving active players away from the server.
3 Major Violations and Tower Attacks
Attacking the towers of NAP alliances is strictly forbidden. Mass attacks or unfair attempts to destroy an alliance are considered major violations. In such cases, all NAP alliances may make a joint decision.
4 NAP Decisions
All important NAP decisions are made by vote. Our main goal is to keep the server active, balanced, and alive.
5 Member Transfers and Recruitment
Poaching members within NAP is strictly forbidden. Private recruitment messages such as “join our alliance” are not allowed. Alliances may advertise in world chat. Players are free to change alliances by their own choice.
6 Iron Castle / Expedition Development Center
Iron Castle registration priority is determined by power ranking. If the leader or an R4 member cannot be reached during the day, the turn passes to the next alliance. Expedition Development Centers are open attack points; anyone sharing a border may attack.
7 New NAP Members
If a new alliance wants to join NAP, the current alliances are reviewed by power ranking. If necessary, the lowest-power alliance leaves NAP and the new alliance joins. This rule applies equally to all alliances.
8 Communication and Dispute Resolution
All NAP issues must first be reported to alliance leaders or R4 members. Players must not start public arguments in world chat. Each alliance is responsible for reviewing the issue and sharing evidence when needed. Disputes should be resolved calmly between leaders before any action is taken.
9 Observation Stations and passage routes
Observation Stations must be positioned diagonally whenever possible so that other alliances can pass through; they must not form a straight, uninterrupted line. Destroying another alliance’s Observation Station violates the NAP rules and is prohibited. An obstructing station may be removed only when passage is completely blocked, the route remains closed despite warnings, and the NAP alliances make a joint decision.
