Skip to main content

Diplomacy and NAPs

Diplomacy tracks non-aggression pacts (NAPs), pending treaty requests, and the archive of expired or cancelled relationships. Each NAP has a counterparty alliance, an optional expiry date (or 'never expires'), and notes for context. Cross-server treaty requests come in and out via a separate inbox so officers know what needs an answer.

// ON THIS PAGE

How it works

Open Diplomacy from the sidebar. Four tabs:Active (current NAPs, with countdowns to expiry), Inbox (treaty requests sent to your alliance), Outgoing (treaty requests you have out), and Archive (expired and cancelled NAPs, kept for record).

R5/R4 add NAPs from the “Add NAP” button or by accepting an incoming treaty request. Either way, the result shows up under Active with a status pill, a countdown, and (if you set notes) the context for why it exists.

Try it

// LIVE DEMO · SAMPLE DATA

IronGuard

[IGX]Server 481544d 23h left

Apr 4, 2026 → Jul 3, 2026

Mutual non-aggression. Refresh quarterly.

NorthlineSyndicate

[NLS]Server 4815Until cancelled

Jan 19, 2026 → until cancelled

Open-ended NAP, top-tier rivals.

The actual production view, running against four sample NAPs (two active, one expired, one cancelled), one inbound treaty request, and one outbound. Tabs work; officer-only actions are hidden in this read-only demo.

Treaty requests

Treaty requests are the cross-server (or same-server, if both alliances use Last Command) alternative to a one-sided NAP. When another alliance proposes peace with yours, the request lands in your Inbox with a 14-day deadline and the proposed terms. R5/R4 can accept, reject, or counter — accepting auto-creates a mirrored NAP on both sides so neither alliance has to retype anything.

// TIP

Use the Outgoing tab to see what's pending from your side. If a counterparty hasn't responded inside the 14-day window, the request expires automatically and you can re-send if it's still relevant.

Expiry reminders

Three days before any active NAP's expiry, the platform fires a NAP expiring soon reminder to your officer notification channels — so you have time to renegotiate or let the agreement lapse cleanly. When a NAP actually expires, a NAP expired notification confirms the status flip in case it was missed.

Reminder timing is platform-side; you don't configure it per NAP. Officers turn the channel on or off in My Hub → Notifications. Diplomacy as a whole is on the Free plan — no Pro upgrade required to track NAPs, send treaty requests, or receive expiry reminders.

// PREVAI screenshot scanning// NEXTServer directory