2 Commits

Include renames

Author	SHA1	Message	Date
sganggs	806a047717	feedback6 R21P: every operator fights at full potential (潜能 6) — the owner's decision of 2026-10-07 (GitHub #252, PR #255; no host slider): tools/build-data.mjs OPERATOR_POTENTIAL adds every character_table potentialRanks attribute step (部署费用 / 再部署时间 / ATK / HP / DEF / RES / ASPD, all ADDITION, before rounding) to every chess (normal and elite), 补位 and 自选 unit form and picks talent / trait / module-talent candidates up to requiredPotentialRank 5 (「天赋效果增强」); a summon picks its talent candidates at its owner's potential (their requiredPotentialRank mirrors the owner's — PRTS 凯尔希: Mon3tr 3.5 s / 1400) and takes none of the owner's attribute steps; the 原型干员 stand-ins have no potential ranks (unchanged). 刺玫 413 / 17 → 435 / 15 as in the tournament video, 砾 18 → 16 s, 至简 80 → 70 s. data/chess.json (256 records), backups.json (the 71 owned picks, 8 summons), tokens.json (5 summons) and the data translations en / ja / ko / zh-TW rebuilt — only potential-driven fields (JSON-compared); the 干员调配 局内数值 and detail cards read the records. op-wang.js reads her stock cap 「最多拥有8（+1）枚」 through the potential step (the pattern fell back to 7: she sat at the cap from the start). Docs: DATA §2 / §18 / tokens, PLAYING (detail card), research 03, kits README, shared/diy.js / standIn.js, the 71 自选 kit headers and the kit comments that quoted potential-0 numbers. Tests: test/full-potential.test.js (new, fails on the parent); data.test.js re-derivation adds the potential steps (+ respawnTime); every test that hard-coded a potential-0 number carries the full-potential one (from the data and the test's own formula; no check loosened); golden: moves almost everywhere — roster 49/49, bonds 46/46, fields 22/22, matches 18/18, diy 133/138 (each battle parts on a stat: roster-001 / roster-020 at tick 1 on 角峰's HP (生命上限+250), bond-arcaneShip-high at 4.73 s and diy-001 at 3.70 s on an enemy's HP from a higher ATK; diy-110 / 111 also by 望's cap; the matches through those battles); unchanged: standins 10/10 and diy-135…138 (no potential ranks), diy-012 (twelve 夜莺 never hit, never redeployed)	2026-10-07 18:35:39 +08:00
sganggs	ee74401901	feedback5 WH: the first 自选 operator kit, 推进之王 (kits/ops/op-siege.js, registered in OPERATOR_KIT_FILES) — S1 冲锋号令·γ型 +12 DP at full SP, S2 跃空锤 next attack 250 / 280 % ATK on every ground enemy of her x-5 + 3 DP (2 / 3 charges), S3 碎颅击 interval +1.0 s with 290 / 320 % ATK and 40 % stun 0.8 / 1.1 s; T1 万兽之王 field 【先锋】 ATK / DEF +8 % (SOL-X stage 3: her own +8 % more), T2 粉碎 +1 SP per enemy falling on her x-5 (flyers, under 阻回; SOL-Y stage 3: +3 and +1 to another 先锋); SOL-X trait ATK / DEF +8 % while blocking; SOL-Y's 首次部署 −4 has no battle effect; tests in test/content/op_siege.test.js over every form (tiers 5 / 6, normal / elite × none / SOL-X / SOL-Y) ... No golden scenario moved (none fields a 自选 piece).	2026-10-05 19:54:32 +08:00