Term No.17

PURGE DAY DATE: JUNE 18,2026

OPTION 1 YES
OPTION 2 NO

PROPOSAL Purge Day

If it was a yes, leaders would have discussed in more details on timeframe and rules.

To quote the wise words of one of the leaders who suggested "Man needs war, not farming. It can be done very smart and help people solve differences"

He also suggested purge day during weeks without capital clash and afterwards, alliances must help each other for 2 glory wars if its between 2 alliances purging.

RESULTS But results were a no on purge day

Hit 396 trucks we will be invading

Attention State 395,

The following statement appeared in a State 396 President message regarding our server:

“There’s also a good chance that the strongest player on 395 won’t participate.”

Whether true or not, this is a reminder that information shared outside of 395 can quickly find its way to our opponents.

Please be mindful when discussing participation, battle plans, and other sensitive matters. Protect our state. Protect our advantage.

TRADE HUB RULES DATE: JUNE 22,2026

OPTION 1 YES
OPTION 2 NO

PROPOSAL - Each alliance can own one Trading Hub of each level.
- Alliance rank does not determine Trading Hub eligibility. Ownership is determined on a first-capture basis; the alliance that successfully captures the hub first, wins.
- No HQ burning or tvt (tank vs tank) on the same server during this event.
* If a player initiates a tvt attack on purpose or burns another player's HQ within same server, there is possibility of retaliation

Captured City Rules DATE June 24 ,2026

OPTION 1 Captured cities cannot be attacked without permission from the owning alliance, or the offending alliance may face daily farming attacks for 1 week Main alliances have priority over farm alliances, and alliances ranked 1–3 will be assigned City 6. Cities will be distributed among the NAP 10 alliances based on server rankings. For example: City Level 3, there are 10 available cities, and each NAP 10 alliance will be allocated one city. Alliances can trade or drop cities per agreements

OPTION 2 Alliances will take cities how they each deem fit. No assignments. Alliances are free to claim or negotiate cities through their own agreements.

OPTION 3 Cities will be assigned to Nap 10 alliances. Leaders will discuss specific assignments later if this option wins

RESULTS Option 3

395,

As we prepare for our upcoming SvS against State 396, the following alliance assignments have been decided:

Positions will be as follows:

• PLSH – Turret 2 side and Capital support. • LGD & ATAA – Turret 3 sector. • BOAR, MELT & NLT – Turret 1 sector. • SHLD, DABO & UPEX – The corridor between Turret 2 and Turret 3.

All alliances should ensure their members understand their primary responsibilities before battle begins.

Please set your alarms now.

Save your troop speedups for SvS. Avoid unnecessary expenditures beforehand so that we enter the capital battle with every possible advantage.

Reach out to your R5 for coordination and objective assignments. Pay attention to any group chats that you may be invited to, as battle instructions and updates will be communicated there.

Avoid unnecessary engagements and preserve troops for objectives that matter.

• PLSH – Position between Turret 2 and Turret 3 to engage LEND and take pressure off LGD and ATAA as they deal with SHX. • IWLL, FLOT – Turret 2 sector. • LGD & ATAA – Turret 3 sector. • BOAR, MELT & NLT – Turret 1 sector. • SHLD, DABO & UPEX – Flexible support and reinforcement as needed.

Your HQ should be in 396. At minimum, get on grass, bubble, and reinforce as directed. Coordinate.

We need more coverage on turret 2 side @R5s

NAP 10

The following alliances were locked in as the NAP 10 based on Holistic Day at 9:30 PM:

PLSH LGD1 AATA BOAR MeLT NLTs IWLL SHLD FLOt UPEX Farming Rules NAP 10 alliances are protected from farming. This protection applies to all Headquarters (HQs). Alliances ranked 11th and below may be farmed on Monday, Wednesday, and Friday. Alliances with fewer than 70 members may be farmed every day, regardless of rank. Defending Against Farmers

Alliances defending members who are being farmed may:

Reinforce the targeted member. TVT the attacking farmer. Attack the farmer's Headquarters (HQ). Zero the farmer if necessary to force them to leave the hive. Counter-Defense Members of the farmer's alliance may reinforce their farming member if that member is attacked. They may not attack the defending alliance unless they were actively participating in the farming operation. Limitation Clause A maximum of 5 alliance members may farm a single hive at one time.

Send 1 Yellow Rose to activate a 2-hour +20% Building Speed buff

Our first Season 3 Glory Wars starts tomorrow!

The following alliances have requested server support:

09:00 • BOAR vs ZNAT • NLT vs JPFE • DABO vs SATU • UVT vs JP Take It Easy

18:00 • IWLL vs UWES

22:30 • MELT vs VTTV

If your alliance needs additional support, please post your coordinates in world chat, and the server will assist where possible.

Good luck to everyone, and let's represent the server well!

Date: June 29, 2026

Vote Summary

Result: Motion Passed

Approved City 6 Rules The Top 4 alliances will hold City 6. The Top 4 alliances will be determined based on the rankings from the last Holistic Day before City 5 becomes available. Capital ownership will rotate between the participating alliances. The alliance currently holding the Capital will transfer City 6 to the alliance that is rotated out of Capital ownership.

My Fellow Citizens,

As my time as President comes to an end, I want to leave with optimism and confidence in the future of our state. When I accepted this role, my goal was to ensure that every major alliance had a voice, that decisions were transparent, and that the future of our server belonged to all of us.

Together, we built the 395 Leaders process, published votes openly, preserved our farming rules, established Holistic Day as the method for determining NAP status, set clear guidelines, and created a culture where it might be possible to settle our disagreements.

I was never a perfect President. I made mistakes, and at times I am wrong. But everything I did was driven by a sincere belief that 395 deserved openness and a future that every player could help shape.

To those worried about migration, I ask you not to be. Migration is still a long way off, and 395 remains one of the strongest, most resilient, and most respected states in our cluster. We can overcome any setbacks. The strength of 395 belongs to its people. But after losing the SvS against 396, many believed our best days were behind us. But we continue to stand, compete, and grow together.

To every alliance: continue participating, continue building. The systems we created only work when people remain engaged and committed to a shared future. Long after any of us have moved on, 395 will continue to stand as one of the finest states in this cluster.

And while my term may end as President, I have learned that one should never assume a leader has exhausted every tool at his disposal. History has a way of surprising us. And if history teaches anything, it is that a President should never reveal his final executive order before its proper time.

Until then — keep building, keep fighting, keep believing in 395.

Thank you for allowing me to serve, and a special thanks to @Sun for managing the vote process — without her, none of it would have been possible.

— Imwrong President of the United States

EXECUTIVE ORDER 2 IAPU State Security Directive By the authority vested in me as President of Server 395, and in order to ensure the continued stability, security, and continuity of the state during periods of transition and uncertainty, it is hereby ordered as follows: WHEREAS the stability of Server 395 depends on clear and recognized lines of authority during moments of capital assignment, leadership transition, SvS preparation, migration uncertainty, and other periods of instability; and WHEREAS the interests of the state must be safeguarded through a designated body empowered to act decisively when such instability arises; NOW, THEREFORE, it is hereby ordered: Section 1. Establishment of Authority. The IAPU Representatives are hereby recognized as the official State Security and Continuity Authority of Server 395. Section 2. Purpose. This authority exists for one purpose: to protect the future of 395. Section 3. Scope of Authority. During periods of capital assignments, leadership transition, SvS preparation, migration uncertainty, or other state instability, the IAPU Representative is authorized to review the situation and determine what action is necessary to preserve the interests of the state. Section 4. Suspension of Conflicting Rules. Where existing rules are found to threaten state continuity, they may be temporarily suspended for the purpose of securing the server's future. Section 5. General Provisions. This order shall take effect immediately. — Imwrong President of the United States Issued this 1st day of July, in accordance with the powers of the Presidency of 395.