Skip to content

A mount with a rider on it is a creature on the board: a blast or a laid area catches it apart from its rider, it threatens, an aura it holds has squares, and the GM's board text gives it a line - #1066

Open
Smoebo wants to merge 7 commits into
Lebbitheplow:mainfrom
Smoebo:fix/ridden-mount-standings

Conversation

@Smoebo

@Smoebo Smoebo commented Nov 21, 2026

Copy link
Copy Markdown
Contributor

Follows the falls piece of #1055 (#1065). Ruling 6 says "an area that catches both creatures resolves each one separately". The engine could not do that, and this is why.

This branch is stacked on #1065. It is cut from that branch, so until #1065 merges the diff here shows both. The commit of this piece is the last one. Part of #1055; it does not close it.

What was wrong

A pair stands on one token, the rider's (ruling 1 of #1036 and of #1055). So the list of pieces on the board, listTokens, has no entry for a mount with a rider on it. getTokenByRef already finds such a mount on its rider's token. Every rule that reads the list instead passed the mount over:

  • A Fireball laid over a goblin on a wolf burned the goblin and never asked the wolf. Entangle, Grease and a wall caught the rider alone. Earthquake shook the rider alone.
  • A mount named for an area it stood nowhere near was accepted, because the check dropped a creature it could not find.
  • An aura held by a ridden mount covered no squares.
  • A mount whose rider was stunned threatened nobody.
  • The board text the GM's model reads had no line for the mount: no id, no conditions, no ranges. Only the rider's note said it was there.
  • A mount under a rider the GM keeps hidden was named to the table, because the hidden flag is on the rider's token and was asked by the mount's own id.

I counted 107 calls of listTokens in 70 files and classed every one. About half draw, count, place or move the pieces themselves and are right as they are. The rest ask a rules question and are wrong for a ridden mount.

What this does

One new function, listStandings in src/lib/db/battle-maps.ts: the pieces on the board, plus one entry for each ridden mount. That entry is the rider's token under the mount's own id, name and kind. It covers an enemy's mount (#1055) and a character's independent mount (#1036) alike. Rules code that asks who stands where reads it. Code that moves or draws pieces keeps listTokens, because the two entries of a pair are one row and a write made for each would be made twice.

listHiddenRefIds now holds the mount of a hidden rider too.

The doors switched, and what ran:

Door Where Evidence
A blast laid on the board creaturesInBlast, standingIn in aoe-shape.ts Test: Fireball, enemy pair and character pair
A creature named for an area areaProblem in aoe-shape.ts Test: Shatter 40 feet off is refused
An area that catches who stands on it as laid creaturesInLaidZone in aoe-shape.ts Test: Entangle
The ground shaking groundedIn in zone-quake.ts Test: Earthquake
An aura's squares liveZones in zone-store.ts Test: aura held by a mount
A turn starting or ending in an area momentFor in zone-triggers.ts The falls suite's standing Gust of Wind tests
Who threatens threatSpots in attack-spatial.ts Test: stunned rider, mount still threatens
Who a confused creature may strike lashOut in confusion.ts Test
The foes an attack does reach, and the names on the board checkPcAttackRange, unknownCombatant in map-tools.ts Test
The board text for the GM's model serializeMapForPrompt, called from turn.ts Test of the text; the one-line change of caller was read, not run
Whose figure is lit, and target lines buildPlayerMapView in view.ts Test: a steed's turn lights the pair
Who is hidden listHiddenRefIds Test of the list; its nine readers were read, not run

Switched the same way, read and type-checked but not run: where a cast area is centred and the foe a sphere is sent beside (zone-cast.ts), a drifting cloud's caster and a character's mount pushed by a standing area (zone-triggers.ts), the two swarm doors (genre-cc-a-spends.ts, genre-cc-a-turns.ts), a thrown area's named target (genre-b-zones.ts), the ally beside a Sneak Attack target and the Hand's walls check (map-tools.ts, attack-spatial.ts), Rakish Audacity's duel (authored-hooks.ts), a strike on a projected body (spirit-projection.ts), a summon's anchor (summon-store.ts), Cauterizing Flames (cauterizing-flames.ts), Naturally Stealthy's screen (hide-traits.ts) and a walking heal's target (authored-heal-area.ts).

Choices that are yours to overrule

  1. The mount comes before its rider. A rule that takes each creature in turn reaches the mount first. So a push laid over both moves the pair as one and the rider saves once, which is your "if both are pushed together". This settles choice 1 of the falls piece for an area the engine reads from the board. A call that lists the rider first by hand still takes the rider out alone.
  2. A caster's own cone leaves out the creature it shares a token with. A rider's cone or line starts at the edge of the pair's space, so it holds neither the rider nor the mount under them. A burst centred on a point still catches both.
  3. A mount counts as "another creature within 5 feet". By the letter, a swashbuckler duelling a goblin on a wolf has two creatures beside them, and one riding their own independent mount always has one. Rakish Audacity is refused in both. Say if a mount should not count.

What is not in it

Each of these is wrong for a ridden mount today and needs more than the new list. They are steps of the same plan, not surprises.

  • A rider carried into an area. When the mount walks the pair into Web or a Wall of Fire, only the mount is asked. This wants your ruling first: does the rider meet every area the mount enters, or only those not on the ground?
  • Dragging a grappled mount. The drag doors move a token by its id, so a grappled mount would drag its rider unasked. This is the same gap the falls piece names, and it needs the player's move undo taught about pairs.
  • A flying pair. Whether the token stays aloft is judged by the rider alone. A mount knocked prone stays up, and a rider with no flying speed of their own on a flying mount is grounded. This needs a rule for the pair.
  • Passing through a pair's space. The size that decides it is the rider's. It needs "blocked wins" for the two.
  • The rider named when the mount was meant. A handful of result lines and refusals take their name from the token, which is the rider's.
  • The facts the players' board holds for each foe (range, sight, edges, intents), which are keyed for ruling 5's two-name choice and belong with it.
  • The GM's measured template and Fling.

Settings, options and controls

  • This adds no new setting, toggle, option or other control. No tool gains a field and no description grows.

Tests

  • test-enforce-ridden-mount-standings (new, 12 tests). With listStandings stubbed to return the plain list and every other change removed, all 12 fail. The first of them tests the list itself, so it fails by construction.
  • The neighbours still pass: test-enforce-enemy-rider-falls 31, test-enforce-enemy-riders 22, test-enforce-independent-mounts 16, test-enforce-zones 65, test-enforce-last-spells 18, test-enforce-area-shapes 14, test-enforce-area-attacker 3, test-enforce-srd-combat 44.
  • npx tsc --noEmit: clean. npx eslint on every changed file: clean.
  • npm test: 1268 of 1270 files passed. The two that fail, test-backup-in-app and test-backup-restore, fail on my Windows machine on main as well. npm run build: passes.
  • Not checked: the browser harness and the app shell. The new board text against a live model (score-cards); I have no local model.

Checks

  • npm run build passes and lint is clean on every changed file; npm test as stated above.
  • No screenshots: this changes no screen.
  • No hostnames, IP addresses, logs, keys, .env files or players' names in the code, the tests or this description.

🤖 Generated with Claude Code

Smoebo and others added 7 commits November 21, 2026 09:06
…t saves to stay on, a push at the rider takes it alone out of the saddle, and a mount that goes down drops it

A rider knocked prone, or whose mount is pushed, pulled or force-moved, makes the DC 10 Dexterity save from its own stat block once as the call finishes, and a failure leaves it prone beside its mount (issue 1055). A push, pull or forced move that names the rider moves the rider alone, prone where the push ends, with no save, and the mount stays (ruling 6). A mount knocked prone or dropped to 0 costs its rider its reaction to land standing, and a rider with none falls prone.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
…h of one call

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
… and a pull at the mount draws the pair

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
… its own name, and tests hold the cast push, the thrown foe and the psionic push for a pair

A mount carrying a rider has no token of its own, and three places in
the area code looked for one. A mount whose turn started in Gust of
Wind was never asked its save, a mount caught by Web walked on to the
square it was making for, and an area that pushes had no token to move.
Each now finds the pair's token, and the push moves the mount as the
pair, so its rider saves once to stay on.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
…aid area catches it apart from its rider, it threatens, an aura it holds has squares, and the GM's board text gives it a line

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant