Missions

Before contracts, the Expeditions tab can send an Explorer into a sector with a guaranteed lead. The trip reveals one personal landmark on arrival, then the Explorer returns normally to the bastion. The journal keeps that landmark and a direct link to its tile.

After reconnaissance, preparation announces the exact result, minimum force, Cart requirement, calculated losses, full travel time, cooldown and seasonal right. Any change to those data invalidates confirmation and requires a fresh preparation.

The expedition departs with the troops actually committed, resolves on the server at arrival and returns with survivors. Recruited auxiliaries join the origin bastion on return; cancelling during outbound travel starts a normal return without consuming the contract right or cooldown.

Raids, spying when enabled by setting, outpost attacks, tower attacks and camp attacks are rejected against a protected player. A protected player who attacks another player loses protection.

A raid sends units toward a hostile bastion or structure. Travel, power and losses are recalculated server-side. Power gaps change Infamy and sometimes loot; after two victorious looting raids against the same player within 24 hours, later raids yield no resources. If no attacker survives and no loot is carried, the mission ends without a returning convoy.

Scouts report information according to the reached intel level and the target detection defenses. By default, the Ravenry grants +1 every two levels after the first, while Occultism grants +1 every two levels. Exact resources, the wall and the garrison have their own thresholds; at intel level 5, the report also reveals every constructed building and its level. Heroes present are revealed when the origin Ravenry is at least 2 levels above the target Watchtower by default, independently of scout numbers and Occultism. This threshold is configurable through intelligence.spy_report_heroes_level_advantage. Heroes on missions elsewhere stay hidden; active positions at the bastion and reinforcement Heroes on its tile are included. The report preserves the observation and shows up to 100 Heroes, indicating when it is incomplete. The Sovereign is public through the player profile and does not depend on spying. During raid preparation, indicative risk combines compositions and tactical advantages, the selected offensive Hero, defensive Heroes from the last spy report revealing the garrison, and public Sovereign bonuses. Bonuses add together and respect the shared cap; each defensive Hero only strengthens their owner’s units at their position. Older reports are never filled in with hidden current Heroes. Unknown bonuses are indicated. This estimate does not simulate walls, research or every combat modifier; the situation may have changed since the report.

With no available unit for an action, the NPC keeps its defensive reserve and waits for a later cycle. Its economic progression and recruitment continue under the usual rules.

NPCs automatically recruit with the same costs, requirements and training times as players. Each region contains local forces, established factions and major powers. The npc.army.tiers setting ties their army targets to the 25th, 50th and 85th player power percentiles in the region, with a separate minimum and maximum for each tier.

Local forces remain accessible to newer players, while major powers follow the top of the regional ranking without exceeding 75,000 power by default. Each tier also defines its recruitment batch, defensive reserve and the Granary level required for mobilization. Compositions remain faction-specific through npc.army.compositions.

A military attack only departs when the NPC can assemble at least 75% of its planned offensive power. Structure attacks scale with their defense; bastion raids also account for the targeted player’s power. Per-unit-type safety caps therefore no longer determine the ordinary size of an offensive.

Player towers and outposts are targeted before bastions: NPCs destroy towers and can capture outposts. By default, the same player receives six hours of respite between two NPC attacks and no more than three within a 24-hour period. The same structure receives eight hours of respite.

Each seasonal instance keeps its NPC faction doctrine and additionally receives the people it represents in its region. npc.offense.max_actions_per_region_per_tick caps pressure originating from one region, while a player already under active NPC pressure cannot receive a second one.

Units may join an allied bastion, a partner tower, or a partner outpost. An alliance automatically grants military support between members; a non-aggression pact may also grant it explicitly.

Each contingent keeps the name of its player and origin bastion, takes part in the shared defense, and can only be recalled by its player. Inside an allied bastion, these troops are added to local units when a raid arrives and take their share of losses. After combat, every player who supplied troops receives a personal report showing the committed units, losses, and survivors from their contingent. The stationed garrison and all detachments in transit are visible to the owner and every partner authorized to contribute.

Several players may simultaneously send a detachment to the same position without preventing its owner from sending their own troops; each player may nevertheless have only one active garrison movement toward that position at a time.

Recall remains available after an agreement ends, while a reinforcement still in transit returns home if permission is no longer valid on arrival. The report then explicitly distinguishes an ownership change from expired military support. A position owner may launch a reinforcement call that remains visible to authorized partners for an admin-managed duration.

Transfer convoys move resources and units only between the same player’s bastions, according to their capacity and travel time.

The Trade page lets a player propose an “I provide X for Y” contract to an authorized diplomatic partner. A contract may expire or be cancelled before acceptance. The form only asks for resources: both sides exclusively use Carts and automatically mobilize the minimum number required for the load.

One Cart carries 120 resources with the active definition. The sender must already own their Carts; the recipient’s Carts are checked only when they accept. The live summary displays each convoy’s load, maximum transportable amount, remaining capacity, and required Carts; a game synchronization does not clear a form being edited.

On acceptance, the server checks both bastions’ stocks, Carts, permissions, and routes together: both linked convoys depart, or neither does. Each convoy carries exactly the accepted basket, without a diplomatic delivery modifier or delivery bonus.

Between members of the same alliance, Convoy charters only reduces travel time according to its level and never changes either basket. Carts remain their player’s property and become available again after delivery. Commercial reports remind players of both baskets and open the corresponding contract in history. History links to a convoy while it is travelling and hides that shortcut once it is complete; it remains readable and can recreate an old offer.

A foundation convoy may travel to any reachable neutral tile, even beyond territorial influence, then start the construction of a new bastion. The target must respect the admin-managed minimum hex distance from the player’s other bastions and foundation sites, plus an admin-managed three-tile distance from every regional passage by default. A distance of three is allowed; only closer tiles are forbidden. When cancelled, the convoy makes a real return trip and keeps its resources and units committed until arrival. Claims, control towers and outposts remain limited by their own territorial range.