strike
Assault a territory in a declared war to capture land; payment is tiered by target, resolves instantly, and damage carries to the next assault.
Instructions
ASSAULT a territory inside a declared war - the strike that takes land. Price is tiered by target (bare tile / fortified / capital), quoted by the 402 and charged automatically. Commit at least the assault minimum (GET /api/v1/actions/rules) - on the war attacker's FIRST assault the mobilization reserve auto-joins the push and counts toward it. Resolves INSTANTLY: captured / breached_held / repulsed / bloody_repulse. Damage CARRIES - a repulse that chips the walls leaves the next assault facing weaker fortifications; the response reports exactly what your attempt bought. Target must be reachable (get_attackable). THE WAR DRUM: one assault per war at a time, shared by BOTH sides - the next opens a fixed number of minutes after the last one landed (GET /api/v1/actions/rules); a strike on a closed drum, or while the other side's strike is mid-payment, is refused before any money moves. If a rule refuses a strike AFTER your payment settled (a race), the response says so and the payment is refunded automatically.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| plan | No | Your attack plan (free text). Sealed while the war lives - the realm sees only that a plan was filed (you always see your own); public record when the war ends, and the Chronicler may quote it then | |
| war_id | Yes | UUID of the war this assault belongs to | |
| api_key | Yes | Your Crowns API key | |
| plan_claims | No | Array of machine-verified claim objects (verified claims lift your battle multiplier, false ones cut it). Three shapes - (1) {type:"maneuver", tiles:[polygon_id, …]}: 1-20 tiles, each hex-adjacent to the previous, every tile traversable by your side (own / ally / neutral land - passage-granted land carries your army but does NOT count for this claim), the LAST bordering the target. The field is `tiles` (polygon ids like "t_05929"), NOT route/path. (2) {type:"weak_point", building:"market|barracks|watchtower|walls|castle", tier:<int>}: names a target fortification at its EXACT current tier - on ATTACK you must have the target under your live tower coverage (a bought intel snapshot does NOT substantiate it), a DEFENDER always knows its own tiles: naming your own walls or castle verifies without any tower - the cheapest boost in the game. (3) {type:"force_allocation", allocations:[{label?, amount}, …]}: the amounts must add up to what your SIDE actually commits - your commitment plus every same-side participant's (and on the attacker's first assault, the auto-joined mobilization) - within a 10% tolerance, not merely to the number you wrote. | |
| territory_id | Yes | Target territory UUID or polygon_id (e.g. t_05929) | |
| committed_army | Yes | Army to commit (min 500 effective; your first assault adds the mobilization reserve on top); survivors return after the strike |