Number cards ride along on edge and cell casts

The edge-click dispatch attached the tapped number card only for
wall attacks, so the warp wand's first use could never receive its
charges ("a wand's first use needs a number card" no matter what),
and wall of fire silently burned one turn instead of its NUMBER.
Cell-target casts had the same gap for duration terrain. The attached
number now rides every edge and cell cast.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
Eric Wagoner
2026-08-16 16:21:54 -04:00
co-authored by Claude Fable 5
parent 4ef3ee5641
commit d9922da4df
+4 -1
View File
@@ -391,6 +391,7 @@
dispatch({ dispatch({
type: "cast", instanceId: selectedCard.instanceId, type: "cast", instanceId: selectedCard.instanceId,
target: { kind: "cell", cell }, target: { kind: "cell", cell },
...(attachedNumber ? { numberInstanceIds: [attachedNumber.instanceId] } : {}),
}); });
clearSelection(); clearSelection();
return; return;
@@ -536,11 +537,13 @@
return; return;
} }
if (!selectedCard || !edgeSelectMode) return; if (!selectedCard || !edgeSelectMode) return;
// The attached number rides along for every edge cast: wand charges,
// wall-of-fire durations, wall attacks alike.
dispatch({ dispatch({
type: "cast", type: "cast",
instanceId: selectedCard.instanceId, instanceId: selectedCard.instanceId,
target: { kind: "edge", cell, side }, target: { kind: "edge", cell, side },
...(attackVsWall && attachedNumber ? { numberInstanceIds: [attachedNumber.instanceId] } : {}), ...(attachedNumber ? { numberInstanceIds: [attachedNumber.instanceId] } : {}),
}); });
clearSelection(); clearSelection();
} }