Kingdom Governance & Server Constitution Guide

A strong kingdom needs more than powerful armies. Clear agreements help alliances grow during peace, settle disputes fairly, and prepare together for cross-server competition in Last Asylum: Plague.

This kingdom governance and server constitution guide provides a practical framework for Non-Aggression Pacts (NAP), Rules of Engagement (RoE), gathering etiquette, and minister requests.

Use your kingdom's current announcement: These are suggested community rules, not universal game restrictions. Alliance coverage, event exceptions, penalties, and title queues must be agreed and published by your kingdom's leadership.

1. Non-Aggression Pact (NAP) Framework

A NAP is an agreement between participating alliances to limit internal attacks. Its purpose is to preserve troops and resources so the kingdom is better prepared for events such as Kingdom War.

• Publish the protected alliance list. A kingdom may choose a Top 10 or Top 20 agreement, but rank alone does not establish protection. Check the current list, participating alliance tags, and effective dates.
• Define protected targets. A clear peace agreement should cover Sanctuaries, encampments, and gathering marches. Specify whether scouting is also prohibited.
• Register farm alliances. Farm accounts receive protection only when the kingdom agreement includes them. Leadership should publish the approved farm tags alongside their main alliances.
• Resolve incidents before retaliation. Report accidental tile hits, scouting, or other disputes to R4/R5 leadership. Leaders should contact the other alliance directly and review evidence before authorizing any response.

A player reporting a violation should include the battle report, player and alliance names, coordinates, server time, and a brief description. An accusation by itself should not trigger a kingdom-wide conflict.

2. Gathering Tile Rules

Gathering disputes are easier to avoid when everyone follows the same claim rule. The following policy is a useful starting point for a kingdom agreement.

• First arrival claims the tile. Under this policy, the march that reaches an unoccupied resource tile first has priority, even if another player sent a march earlier.
• Recall when another march arrives first. Check the tile before arrival and redirect if it is already occupied.
• No attacks on protected gatherers. Do not clear a NAP member from an occupied tile unless an explicitly announced event rule permits it.
• Finish what you start. Send enough troop load to empty the tile when practical. Avoid leaving small leftovers for other players to clean up.

If two marches collide, save the report and let alliance leaders resolve the incident. Do not turn a single tile dispute into repeated attacks.

3. Rules of Engagement During Events

An event appearing on the calendar does not automatically cancel the NAP. Leadership should announce permitted targets, locations, and the exact start and end times before any exception begins.

For event preparation, see the Kingdom War (KvK) Guide. When an announcement is unclear, ask an R4/R5 officer before attacking.

4. Minister Titles and Buffs

Kingdom leadership can coordinate access to available court titles so players can use their bonuses efficiently. A title applies according to its in-game description; it should not be confused with a kingdom-wide decree.

• Development or construction titles: Check the available research and building speed bonuses, then request the title that fits your next upgrade.
• War or training titles: Check the training speed and capacity benefits shown on the title screen. Do not assume a training title also grants combat attributes.

Verify the numbers in game. Title names, bonus percentages, availability, and assignment rules should be checked on your current kingdom's title screen. This guide does not assume a universal +10% bonus.

How to Request a Minister Buff

1. Prepare first. Gather the resources, meet the prerequisites, and free the relevant queue. Be ready to begin the upgrade, research, or training batch.
2. Use the designated channel. Follow the kingdom's request queue, whether it uses Kingdom Chat, City Chat, or another leadership-approved channel.
3. Make a clear request. For example: Development title please — research ready. Player: [name], alliance: [tag].
4. Wait for confirmation. Confirm that the correct title and bonus are active before starting the eligible action. Follow the title description for when its effect applies.
5. Release the queue promptly. Tell the minister when you are finished so the next player can be assigned. Follow any minimum holding time or reassignment restriction shown in game.

Use speedups according to your upgrade plan and event goals. Spending speedups immediately is not a general requirement for receiving a title.

5. Server Constitution Checklist for Leaders

Keep the kingdom agreement short enough to read and specific enough to enforce. Publish these details in one place:

• Protected main alliances and registered farm alliance tags.
• Rules for bases, encampments, scouting, gathering tiles, and other contested targets.
• Event exceptions, permitted zones, and start/end times using server time.
• R4/R5 contacts, required evidence, and a reasonable dispute response process.
• Agreed remedies and penalties, who may approve them, and how decisions can be reviewed.
• The title request channel, queue etiquette, and handover procedure.
• A revision date and the process for announcing rule changes.

Before you act: Check the protected list, read the current event notice, and ask leadership when the rule is uncertain. Consistent communication helps the whole kingdom prepare for its next major battle.

Back to Items & Strategy Guides · Alliance System Guide