Review follow-up to the D5 fix. Two changes in grid.js _buildField:
- The road-over-floor preference smoothing is 0.1.0's again: its line of sight
may cover non-blockable tiles (Bresenham footprint, diagonal-step corners
included) only on the tile's own raw chain, and the jump stops at the first
ancestor it cannot see so. Exact crossings (a corner touch is not a crossing)
are used only to choose between the official and the preference pointer.
The previous version let the preference brush the corner of off-chain floor,
so on 战场#02's Final Assault the right-half exit route (2,10) -> (3,11)
slipped past an operator on (2,11) while the left half was still blocked on
(2,9). Both halves now mirror each other again ((2,10) -> (2,11) -> (4,11)).
- On an equal floor count the official pointer stays; the preference pointer
wins only when it merely skips a collinear official waypoint (same walk).
The old "farther waypoint" tie-break could bend an official route without
saving any floor, e.g. a crate on (10,6) of 战场#04 brought back the L via
(9,8) for the lower gate.
Still 140 of 154 stage routes official; data/stages.json groundPaths
regenerated (战场#02 boss right exit back to 0.1.0's, device-less helper paths
of #03 / #04 / #06 follow the same rule). New tests: 战场#02 boss exits mirror
and are blocked beside the exit; a single crate on any tile of an active stage
never leaves a gate route non-official without crossing strictly less floor.
The cross-check reference port follows both rules.
Community report: on 战场#04 活性源石 the lower-gate enemies walked two tiles left
of the red gate and then straight up instead of crossing diagonally from row 9
into row 10 as in the official game. The playtest #2 road-over-floor smoothing
counted the corner tiles of a diagonal step as crossed, so it bent the official
(9,10) -> (10,7) into (9,10) -> (9,8) -> (10,8) although that line only brushes
the corner of the floor tile (10,9).
grid.js now keeps the official flow field (research 08 §3.1) and replaces a
tile's pointer by the road-over-floor preference one only where its route
crosses strictly fewer non-blockable tiles (or as few with a farther waypoint);
a segment crosses the tiles whose interior it passes through (segmentTiles,
exact geometry). 140 of the 154 stage x gate x field routes are now official
(was 109); the 14 left avoid floor the official route walks over (战场#01's
col-8 road of playtest #2, boss exits of 战场#01 / #02, two 联防 partner gates).
data/stages.json groundPaths regenerated.
Player reports #3 and #9 after the 0.1.0 release.
#3 On 战场#08(下半) 涨潮控制 (act2autochess_m04) operators could be placed in the
pool and 突袭 members jumped into it. The 深水区 (tile_deepsea) has buildableType
ALL in the level file, but it refuses deployment (PRTS 地形 深水区 "地形机制：拒绝
部署"; the season-1 战场#05 puts a 特制水上平台 - "在水上建立可以部署任意单位的
平台" - on every one of its water tiles).
- grid.js DEPLOY_REFUSED_TILES: the legend's effective build is NONE, so
canStand (突袭 landing tile, tactical points, summon tiles) never picks the
water; a hard-blocked 射击台 / mound tile takes no melee unit either.
- build-data: stages.json legend `buildable` is the effective type (the level's
value kept in `buildableType`), deployTiles exclude the water, a 特制水上平台
makes its tile deployable (act1 m05, inactive). board.js / gameLogic.js
deploy maps follow (water platforms included); bots plan on the same map.
- Gate routes are unchanged; the water now counts as non-blockable ground in
the path tie-break (audit lists updated).
#9 伺夜's 狼群 and 缪尔赛思's 流形 ("只能部署在召唤者攻击范围内", tokens.json
`ownerRange`) could be placed anywhere.
- PlayerState._legal / summonRange: a range-bound summon only on a tile of its
owner's attack range (loadout grid rotated by the owner's facing); swaps with
the owner are checked from the owner's new tile; re-orienting (or promoting)
the owner sends a summon left outside back onto its stack with a toast.
- The client lights and accepts the same tiles (gameLogic.summonRange), the bot
plans inside them, the invariants check it, the 伺夜 kit re-uses the piece's
tile only inside her range.
Tests: test/match/feedback1-placement, test/sim/feedback1-water, the opt-in
headless-Chrome test/ui/feedback1-placement.e2e (fastServer hook SP_STAGE);
existing summon / deploy / pathing tests moved off the water tiles.
sganggs