fix: 重置松果重新部署后的S2攻击成长
This commit is contained in:
1 parent
1db8e51023
commit
8ebdcf5d17
5 files changed
+120
-3
No files matched your search
@@ -479,3 +479,16 @@ imports and typecheck pass. This round changes no production UI and does not rer
|
||||
the `roster`, `bonds`, `fields`, `matches`, `standins` families are unchanged.
|
||||
- **Contracts updated:** design/engine.md, SIM.md (cabin), design/client.md, design/network.md, META.md and PLAYING.md
|
||||
(local identity recovery and handshake).
|
||||
|
||||
|
||||
### 28.28 Pinecone S2 resets its ATK ramp on deployment — `kits/ops/chess_char_3_10-pinecn.js`
|
||||
|
||||
- Cause: the kit selected its ATK step from `SkillRuntime.activations`, which counts all activations in the battle;
|
||||
the first cast after automatic redeployment therefore used a later step.
|
||||
- Source: [PRTS 松果](https://prts.wiki/w/松果), S2 备注: the count starts from this deployment. Rank-4/rank-7 steps
|
||||
come from `data/chess.json` skill blackboards. The mode's redeployment/carry-state rules do not preserve this count.
|
||||
- A unit-local S2 counter is cleared in her existing deploy hook. Growth within one deployment and the fourth-step
|
||||
cap remain; S1, range, trigger, talent and the global cumulative activation sequence are unchanged. No new
|
||||
[ASSUMED] rule. This touches only Pinecone's kit, not 凛冬's separate deployment lifecycle (issue #315).
|
||||
- Regression: `test/content/kits_pinecn.test.js`, normal, elite without module and elite RPR-X; ramp/cap, later
|
||||
paid redeployment, natural enemy knock-out and two copies with independent counters. These are model tests.
|
||||
Reference in new issue
Block a user