Files
ark-stronghold-protocol/docs/history/0.2.1.md
T
sganggs cfd3c67281 feedback6 R21A: a 突袭 member may land on a teammate's half when both halves of the field are taken — the two-helper 联防 field and the Final Assault / Hidden Core pair field (the owner's decision of 2026-10-07): Battle.onFieldBoard (onOwnBoard of any player of the battle) read by raidTile only; a lone 联防 helper's empty half, a solo boss field's other half and the hand / 临时整备区 rows stay closed, every other landing rule kept, 乌尔比安's S3 【移动】 keeps onOwnBoard; golden: 8 moved, each parting from the parent at a member's first landing on its teammate's half (checked tick by tick with the parent instrumented) — fields boss-boss_2 / 3 / 4 / 5 / 6-pair and hidden-boss_8 / 10-pair (the right player's 缄默德克萨斯 / 伊内丝 / 仇白 / 耀骑士临光 on the left player's half, 1–7 landings per battle, the first 0.3–39.8 s in), matches coop4-ABYSS-7 (round 6's two-helper 联防: ai_2's 斯卡蒂 on ai_1's half at 52 s; only ai_1 / ai_2 dmgDealt move, 8263 between them); unite-2 unchanged (its two landings stay on their own half)
Tests: test/sim/feedback5-raid-own-board.test.js — the pair field (the right player's member onto the left telin's board tile (2,3), the left player's onto the mirrored right (2,17), the hand rows closed) and the two-helper 联防 (each helper onto the other's half; 乌尔比安 beside a teammate stays on his own) fail on the parent; the solo boss field's hand rows and the lone helper unchanged.
Docs: docs/history/0.2.1.md (new, §26; §26.1 cites the owner's decision and PRTS 卫戍协议/帮助 §联防阶段), the DESIGN index row and versions line, a pointer from §25.18.1, docs/SIM.md (onFieldBoard; onOwnBoard now 乌尔比安's only).
2026-10-07 17:09:39 +08:00

4.4 KiB
Raw Blame History

DESIGN §26 — 0.2.1

Part of DESIGN.md (the index; section numbers are global).

26. 0.2.1 — after the 0.2.0 release

0.2.1 is built on feedback6, branched from the 0.2.0 release (tag v0.2.0) and marked 0.2.1-dev until it ships. Its workstreams branch off it as fb6-*, each merged after review with its golden scenarios named. Each rule was checked against the official data and PRTS; anything no source backs is marked [ASSUMED]. Where each is handled: the 突袭 landing on a teammate's half of a shared field → §26.1.

Decisions of the owner: 2026-10-07 — a 突袭 member may land on a teammate's half when both halves of the field are taken (the two-helper 联防 field, the Final Assault / Hidden Core pair field), replacing part of §25.18.1; 乌尔比安's S3 【移动】 keeps his own board (§26.1).

26.1 突袭 may land on a teammate's half when both halves are taken (the owner's decision of 2026-10-07) — sim/battle/players.js onFieldBoard, content/bonds/addon/battle.js raidTile

  • Seen: 0.2.0 (§25.18.1) let a member land only on its own board, on every field. Where both halves belong to players — the two-helper 联防 field and a Final Assault / Hidden Core pair field — a member whose target stood on the teammate's half stayed home or took a farther tile of its own half (reproduced: the right player's member with an enemy on the left telin (1,3) of 战场#01 stayed home; on the two-helper 联防 map the left helper's member with an enemy at (10,15) stayed home). After the release the owner decided that such a member may land on the teammate's half.
  • Official: the bond text 「保留技力立即再部署至一名地面敌人周围」 names no board, and where the official landing falls among the legal tiles is not in the data (§22.2). PRTS 卫戍协议/帮助 §联防阶段: with two helpers 「两处阵地将前后拼接为一处 阵地,玩家在同一阵地作战」; a pair field is one boss map holding both players' boards (research 09 §1.2, ConvertChessPositionInfoToBossMap). A lone helper's other half and a solo boss field's other half hold no player.
  • Now: Battle.onFieldBoard(r, c) — the tile lies on the board of a player of this field (onOwnBoard of any of players, the players whose units the battle holds; the 联防 right-hand helper's +8 columns and the mirrored right half of a pair are mapped as before) — and raidTile takes only those tiles: both halves on the two-helper 联防 field and on a pair field; the own half for a lone 联防 helper (escaped_single) and on a solo boss field (nobody stands on the other half; a teammate eliminated before the battle or playing another field opens nothing); never a boss field's hand row 0 or 临时整备区 row 1 (no board covers them). Every other landing rule is kept: ground / ranged tiles (grid.canStand), free tiles (isReservedTile), a blockable tile first for a melee member (§25.11.3), a target only reachable from a forbidden tile skipped (the next candidate is tried, else the member stays); the candidates are still the player's own enemies first (raidTargets). 乌尔比安's S3 【移动】 keeps onOwnBoard (§25.17.2, a separate community report): his landing never takes the teammate's half. This replaces the own-half rule of §25.18.1 on those two fields.
  • [ASSUMED]: none beyond §22.2's landing rule (which legal tile the official landing takes); with both halves open the nearest covering tile wins, on whichever half it lies.
  • Golden: 8 scenarios, each parting from the parent at the first landing on a teammate's half (checked tick by tick with the parent instrumented: identical up to that landing): boss-boss_2 / 3 / 4 / 5 / 6-pair, hidden-boss_8 / 10-pair (the right player's 缄默德克萨斯, 伊内丝, 仇白 or 耀骑士临光 landing on the left player's half, 1–7 times per battle, the first 0.3–39.8 s in) and the bot match coop4-ABYSS-7 (its round-6 two-helper 联防: at 52 s ai_2's 斯卡蒂 lands on ai_1's half; of the match digest only the two players' damage totals move, 8263 from ai_1 to ai_2). unite-2 is unchanged (its two landings stay on their own half). Tests: test/sim/feedback5-raid-own-board.test.js (4 cases; the pair and the two-helper cases fail on the parent; the solo boss field's hand rows, the lone helper and 乌尔比安 beside a teammate are unchanged). Docs: docs/SIM.md (onFieldBoard; onOwnBoard is now 乌尔比安's only).