Term No.22

Below are the results of the No NAP Proposal vote conducted on August 31, 2026.

Alliance Vote Results

Total: 11 alliances

OPTION 1 — YES: No NAP

During non-SVS weeks: No NAP. All alliances and all HQ levels can be looted. Farming days: Monday, Wednesday, and Friday

During SVS weeks: NAP 10 alliances (top 10) are protected from being farmed, including all HQ levels within those alliances.

OPTION 2 — NO

Based on the vote, Option 2 received the majority of votes: 6 NO vs. 4 YES, with 1 alliance not voting.

As we wrap up the season, migration has become the main focus. With very few events going on, I thought it would be a good time to try some simple mud games — something different to keep the state active and give people a reason to log in.

Unfortunately, even something this simple has been difficult for some alliance leaders to organize or motivate participation in. And how will the state manage SVS?

If an alliance is unable to motivate or coordinate its members for something as simple as a mud game, why should that alliance automatically be entitled to NAP protection?

The No-NAP proposal did not pass and I respect the result. But voting NO doesn't make the underlying issue disappear.

By the authority of the Office of the President, it is hereby ordered:

Section 1. Every server-wide vote runs for up to three (3) days from announcement.

Section 2. If an alliance fails to vote in two (2) consecutive server-wide votes, it forfeits its tie-breaking privilege in the next vote that ends in a tie.

Section 3. If an alliance's R5 has not voted when the window closes, one R4 may vote in their place. That vote stands as the alliance's position.

Section 4. If two R4s of the same alliance cast the same vote against their R5 before the window closes, their vote overrides the R5. No more than two R4s may vote on behalf of an alliance in any single vote.

Section 5. If the two R4s do not agree with each other, the R5's vote stands.

Section 6. Only active R4s on file with 395 Leaders count. No exceptions.

Section 7. This applies going forward only. No past vote is reopened.

Silence no longer speaks for an alliance.

— Imwrong President of the United States

We're opening the PLSH Discord server to everyone in the cluster.

Come hang out, talk strategy, share information, ask questions, or just chat with other players.

We've also opened the #migration chat room specifically for migration discussions — potential migrants, recommendations, questions, planning, and anything else related to migration.

Discord: https://discord.gg/9DVvaSau

The Discord invite link is also available on both: 395migration.com 395rules.com

Everyone in the cluster is welcome. Just be respectful and don't make me regret this 😂

— Imwrong President, Server 395

During Non-SvS Weeks

Wednesday is Purge Day. NAP 10 will be temporarily suspended, and all alliances may be farmed.

Monday and Friday remain regular farming days. Only alliances ranked 11 and below may be farmed.

During SvS Weeks

NAP 10 protections remain in effect. Only alliances ranked 11 and below may be farmed on Monday, Wednesday, and Friday.

Farming Schedule

Aside from the two monthly Purge Days:

• HQs belonging to alliances ranked 11 and below may be farmed.
• Alliances with 70 members or fewer may be farmed every day.

Hive Farming Limit

A maximum of five (5) members from the same alliance may farm a single hive at one time.

Event Restrictions

No farming is permitted during Tyrant or Dino Egg Defense events.

If a player teleports into an alliance before an event begins, they must wait until the event has concluded before farming. Farming may resume once the event has ended.

Defending Farming Members

Alliances may defend members who are farming by:

• Reinforcing the farming member.
• Initiating TVT.
• Attacking the farmer's HQ.
• Zeroing the farmer to force them to leave the hive.

Counter Defense

Members may reinforce a farming member who is under attack.

Players who were not farming themselves may not attack in defense.

Protected Farm Alliances

The following farm alliances are protected and may neither be farmed nor participate in farming:

0nly · 0n2y · boaf · lgfm · ata2

Rule Violations

If you believe a farming rule has been violated, please notify your R4 or R5.

Alliance leadership should work directly with each other to resolve the issue.

By the authority vested in me as President of the United States, it is hereby ordered as follows:

Section 1. Purpose. The existing Server 395 rule provides that alliances with 70 or fewer members may be farmed daily. This order clarifies that, for purposes of that rule, membership shall be determined by active membership rather than total roster size.

Sec. 2. Active Membership. An active member is a player whose alliance roster shows the player as Online, 1 day offline, or 2 days offline.

Sec. 3. Inactive Members. Any player whose roster status shows 3 days or more offline shall not be included when determining whether an alliance exceeds the 70-member threshold.

Sec. 4. Application. An alliance's total roster size shall not, by itself, qualify the alliance for protection from daily farming. Only active members, as defined in section 2 of this order, shall count toward the 70-member threshold.

Sec. 5. Verification. Where an alliance's active membership is disputed, current alliance roster information may be used to establish the applicable active-member count.

Sec. 6. Effective Date. This order is effective immediately and shall apply uniformly to all alliances subject to the Server 395 farming rules.

IMWRONG President of the United States