Unit tests for t1111 (push column, attach at bottom, successive shots,
two launched blocks). A reproduction of the video column (repeated
launches under a flying cluster plus falling blocks). A randomized
soak of thousands of ticks across several seeds, asserting no overlap,
no illegal colour change and no vanish without a score. Falling-below-
a-gap and hanging-chain tests for the t1112 stackTop and
releaseUnsupported fixes. makeGame enables strictInvariants by default.
A flying cluster is one rigid body with a single anchorY/vy and integer
cell offsets, so members stay grid-aligned. A block shot into a cluster
pushes the hit column up by one cell and attaches at the bottom, and
the same rule applies to successive shots (t1111). Thrown blocks collide
with each other the same way. Collisions are swept between every pair
(launched vs cluster, launched vs launched, falling vs flying, cluster
vs cluster).
stackTop no longer ignores gaps, so falling blocks cannot teleport up
onto a hanging still. releaseUnsupported repeats until a hanging chain
is stable. An invariant checker (no overlap, no duplicate cells) runs
at the end of every tick in tests and under ?debug.
Adds the poisoned-pointer plus correct-touch regression that failed
before the t1106 fix, unit and Playwright coverage for under-flyer and
landed-cluster drags, thrown-falling merges, cell-corner grabs (mouse
and touch), mixed landing matches, and a 3x flame size check with a
screenshot.
Still stacks under a flying cluster are draggable; the flyer itself is
not. Landed clusters can be rearranged, and swapping in or out updates
membership (t1107). A thrown block collides with falling blocks the same
way two flying clusters do: they merge with velocity averaged by count
and cannot pass through each other (t1108). Grabbing uses the grid cell
under the pointer, with a half-tile fallback for mid-animation blocks
(t1109). Coloured cargo that lands into a mixed row with resting blocks
launches immediately; greys wait until they recolor (t1110).
On a real phone, PointerEvent coordinates can be wrong while TouchEvent
changedTouches stay correct, so a one-tile drag walked the whole column.
While a touchstart is live, Touch Events lead and pointer move/up/cancel
are ignored. Document-level non-passive touch listeners prevent scrolling,
setPointerCapture is gone, cancel ends without launching, and layout
freezes mid-drag. ?debug=drag shows an overlay.
Rocket flames are 3x as large in width and length, extending downward
under the block (t1110).
Record the cause of the drag bug (accumulated deltas with a 0.25-tile
threshold, plus a fragile canvas-pixel mapping), the new 1:1 target-row
rule, spontaneous rockets on flying clusters, and the display-only
Power invert (1 − miss / 0.60).
Displayed Power is 1 − missChance / 0.60, as a percentage, in both the
JS and PHP displayValues used by the planet picker, the HUD and the
lobby. 0% miss shows as 100% Power. Gameplay power() and missChance()
are unchanged (60% miss at 0, 5% at 1), so Cinder displays 92% and
Terra 44%. Tests and Playwright strings follow.
Unit tests cover a 1-tile drag down, a 1-tile drag up, a 2-tile drag
then stop, and a short move that stays in the same cell. Playwright
checks the same with the mouse and with real touch, including mobile
viewports and deviceScaleFactor 3.
New tests require a ground match after a fall, a match after grey
recolor, a flying match after cargo attaches, and a flying match after
two clusters merge, each to become a rocket.
moveDrag now targets the row under the pointer (floor of field y),
clamped to the still stack, and swaps step by step to that row only.
A short pull no longer jumps a full cell, and a stopped pointer moves
nothing else. Launch-by-pulling-above-the-top is unchanged.
Pointer coordinates are mapped through the CSS box and the 10×13 field,
not canvas.width / app.tile, so a high-DPR backing store cannot inflate
a small finger move into a full-column swipe.
Spontaneous lines of 3+ after a cargo attach, a cluster merge, a ground
landing or a settle/recolor become rockets, the same as a player-made
match. A match inside an already flying cluster re-launches the whole
cluster from its current position (same height as a player push).
Hanging cargo after recolor still falls from rest.
Spelen opens a grid of all 12 worlds with numeric g/d/F/Power and
color placeholders. Each lobby player picks their own field; the HUD
and sprites follow that planet. Selection is kept in localStorage.
Members store planet_id. Shots use the sender's planet, not a lobby
flat rate, so the client cannot cheat. Players can change planet only
while the lobby is waiting.