One player, one honest session
Use an account you are authorized to control. Do not impersonate another player, obtain access to another person’s account, share authentication credentials, or attempt to bypass the game’s active-session controls. Crownlands may invalidate sessions or actions that fail server authentication, integrity, or abuse checks.
Do not automate gameplay through bots, macros, scripted browsers, packet replay, modified clients, or other tools that perform actions without normal player input. Do not exploit race conditions, duplicate requests, stale interfaces, or network retries to obtain resources, duplicate rewards, or send orders that the interface would not normally permit.
Server results are authoritative
The shared server decides city ownership, troop availability, marches, combat, rewards, purchases, clan changes, and other multiplayer outcomes. Information on screen is a view of that state and may briefly lag during a reconnect. If a displayed estimate conflicts with a validated server result, the server result controls.
Do not attempt to write directly to protected game data, alter another player’s records, forge identity fields, or interfere with live functions. Report a reproducible issue instead of repeatedly testing it against other players.
Combat and expansion
Attacks, scouting, captures, protection periods, daily limits, and experience rewards are part of normal play. Successful scout intelligence expires ten minutes after the scout arrives and is replaced only by a newer successful report against the same target; its Reports entry disappears when that intelligence expires. Attack and defense reports expire 24 hours after combat. Each troop starts at 1.25 attack power; maximum Swordmastery raises that to 2, and an army’s value is fixed when it launches. Each defending soldier starts at 1.30 defense power; Shieldwall Discipline adds up to 60%, while personal and shared clan objective percentages add against that same base. City level never increases soldier defense. City and objective combat has two phases: attack power first damages the holding’s one physical wall, and only power remaining after a breach fights the garrison. Capturing requires both a breach and enough remaining power to exceed garrison defense. Stoneworks is the only wall-strength bonus. Reinforcements add their sender’s live soldier defense package but do not create extra walls. Every level uses the same linear wall formula, 200 + 28,858 × (level − 1), so each additional city level adds the same base wall power. The full-breach repair window is 15 minutes plus 0.3 minutes per city level, rounded to the nearest minute with no gameplay cap. A hit that removes at least 5% of full wall power persists and adds the same damage share of that full-breach window to the running deadline. Wall integrity and defense recover continuously as that countdown falls, reaching 100% at the deadline. Later meaningful hits use the recovered wall strength, preserve elapsed repair progress, and add only their own proportional time. Combat captures, relinquishment, inactivity releases, neutralization, neutral claims, ownership changes, and capture level drops carry the existing integrity and deadline unchanged. When an intact wall holds, defender troop losses are capped at 10%. Protected raids do not persist wall damage. Every neutral reward camp instead starts with 20,000 troops, has no level or wall, and receives exactly 1.00 defense power from each stationed troop.
A forecast uses the scout report’s current wall integrity, wall and garrison power, known bonuses, and reinforcements. The attacker’s per-troop attack power is fixed at launch, while defender troop production, reinforcement arrivals, wall repairs, bonuses, ownership, and protections remain live until arrival. A displayed likely capture therefore describes the scouted moment, not a guarantee against later defensive changes. The server calculates online march routes and arrival times from the current world layout. Scout Nearby and Regroup charge their displayed cost atomically: the confirmed batch either launches in full or does not charge. A city changing owners can reduce its level and redirect relevant troops according to the current rules.
The Citadel Legion attacks up to 20 randomly selected player-owned regular, non-main cities in the Crown Citadel region at 10:00 AM and 6:30 PM Eastern Time. Selected defenders receive 15 minutes of warning, beginning at 9:45 AM and 6:15 PM Eastern. These attacks ignore 100% of city-wall defense without damaging the wall. If every stationed and reinforcing troop is defeated, the city loses five levels; a city at Level 5 or lower becomes a Level 1 neutral city with 10 troops. Peace Shields do not block these server events, successful defenses preserve the city level, and no defense experience is awarded.
An account may manually relinquish one holding per UTC day. Regular cities, Strongholds, and the Crown Citadel share this allowance, which resets at 00:00 UTC. Combat losses, inactivity releases, and other server-driven ownership changes do not use it.
Each non-Citadel Stronghold has a Stronghold Legacy ledger that ranks rulers by their cumulative control time for that specific Stronghold. Completed tenures remain in the ledger, repeat tenures are added together, and the current holder’s time rises until capture, relinquishment, or inactivity changes control. The Crown Citadel keeps its separate Reign Ledger.
Weaker-kingdom protection and other safety rules are designed to limit extreme mismatches, not to guarantee that every holding is safe. Do not use alternate accounts, coordinated surrender, repeated throwaway captures, or other arrangements to manufacture experience, rankings, resources, or protected states.
Multiple accounts are permitted, but hostile attacks are blocked between accounts recently used in the same game installation. Crownlands also allows two successful captures of cities freshly claimed from neutral between the same two accounts in a rolling seven-day period; a third qualifying attempt blocks hostile attacks between that pair for seven days. Ordinary wars over established cities, scouts, shared networks, and friendly troop actions are not restricted by this rule.
Inactive kingdoms
A kingdom with no successful server login or heartbeat for 15 consecutive days automatically surrenders every holding except its protected main city. Troops owned by that ruler in surrendered holdings, marches, camps, and allied reinforcements are consolidated at the main city. Territory surrendered for inactivity is not restored.
After 20 consecutive inactive days, the remaining main city is released and that ruler’s current-world slot is reset. The sign-in account and public identity remain available, but returning to the realm starts a fresh kingdom. Returning between days 15 and 20 cancels the pending world-slot reset.
Hero skills and presets
Hero levels award skill points. Skills are organized as Attack (Swordmastery, March Orders, and Field Medics), Defense (Shieldwall Discipline and Stoneworks), and Utility (Tax Stewardship, Royal Granaries, and Guild Charters); the groups do not restrict mixed builds. Four private preset slots unlock at Hero Levels 25, 50, 75, and 100. Selecting, inspecting, saving, renaming, or overwriting an unlocked preset is free. Every confirmed Apply costs 1,000,000 gold, including an active preset or an identical saved allocation, and moves the active marker to that tab. Existing Shieldwall rollout credits are reserved for Reset Skills and are never consumed by preset applications. A preset stores only the exact allocation saved in it, so later-earned points remain unspent when an older preset is applied. Spending points or using Reset Skills clears the active marker but never overwrites a preset automatically.
Clans and communication
Clan leaders and officers may review applications, manage roles, and remove members according to the permissions shown in the interface. Allied reinforcements remain attributable to their contributor. In city and objective sieges, they add their troops and applicable troop-defense bonuses to the garrison behind the holding’s single wall; they do not duplicate the wall or Stoneworks bonus. At reward camps, every reinforcement contributes exactly 1.00 defense power per troop and receives no skill, level, wall, or objective bonus. Each ruler may maintain two assignments with each clanmate, limited to one contribution per holding. Ordinary cities reserve at most five contributors; allied Strongholds and reward camps are uncapped.
Recalled or dismissed reinforcements return to their original source holding while the sender still owns it. If that holding has been captured before departure or before the return march arrives, surviving troops are redirected to the sender’s current Main City. Assignment capacity remains occupied until the return arrives, unless no troops survive.
Clan rallies are server-authoritative coordinated attacks against eligible objectives. Only clan leaders and officers may form them. Forming rally targets are visible only to current clan members, although assembly marches remain visible on the shared map. Committing troops removes the contributor’s active Peace Shield. The rally leader controls launch and cancellation, allies may withdraw only before launch, and only the rally leader may spend a Recall Horn on the launched combined army.
The Clan War Room is the clan’s rally coordination area. Every member may view current rally details and use the rally controls permitted by their participant or leader status. The same rally state also appears under Kingdom Activity. All rally commitments and launches remain subject to current ownership, diplomacy, protection, route, and anti-farming rules.
Clan names, descriptions, flags, and messages must not contain threats, harassment, hateful content, sexual content, personal information, scams, malicious links, or attempts to evade moderation. Competitive disagreement is allowed; abuse directed at a person is not.
Gold, items, and optional rewards
Gold, troops, items, cities, ranks, and other game resources have no cash value and cannot be redeemed for money. Purchase limits, cooldowns, inventory capacity, and eligibility checks apply even when a client displays an older state.
Daily login rewards follow the current UTC calendar month. Missing a day pauses progress instead of skipping a reward. No more than two earned rewards can wait for collection, and anything still unclaimed expires when the next UTC month starts. Every calendar length distributes the same total production-hour and item budget.
Daily Missions reset at 00:00 UTC and are generated, progressed, rerolled, and claimed by the server. Three distinct mission families and their capacity-scaled targets and rewards are locked for each UTC day. Each ruler receives one reroll for an unfinished mission; replacement discards that mission’s progress. PvP and Stronghold attack missions count only valid hostile actions that commit at least 5% of the ruler’s snapshotted deployable troops. Camp missions count server-confirmed successful captures regardless of that PvP threshold. Client-submitted progress, duplicate reward claims, and replayed mission events do not grant credit.
Optional rewarded advertising, when available, requires a deliberate choice and a completed reward signal from the advertising provider. Closing, blocking, skipping, or failing to load an advertisement does not grant a reward. Attempting to simulate completion events or replay a claimed intent is prohibited.
Responsible security research
If you discover a vulnerability, stop before accessing private data, changing another player’s state, degrading service, or extracting credentials. Preserve only the minimum details needed to explain the issue and report it through the public support channel. Do not publish active exploit instructions while the issue remains unresolved.
Updates and enforcement
Crownlands is actively developed. Balance values, limits, world layouts, protection rules, and feature behavior may change. Significant updates can require a restart, reset, migration, or refreshed client. Continuing to play after a published update means the current rules and server configuration apply.
Actions that threaten accounts, the shared world, or fair competition may be rejected, reversed where practical, rate-limited, or associated accounts may lose access. Enforcement decisions consider server records and the severity or repetition of the conduct.