fix: 避免恢复默认被尚未完成的旧调配同步覆盖
This commit is contained in:
1 parent
bc50cac01f
commit
19c854c1f7
5 files changed
+204
-3
No files matched your search
@@ -768,6 +768,11 @@ leaker's own capsule / row (`ui/hud.js uniteRemaining`) and the leakers' team ro
|
||||
|
||||
## 5. Views (DESIGN §8.2 / §8.3) and deviations
|
||||
|
||||
The client's stored loadout and `m.private.loadout` / `ops` must agree after a successful sync. In
|
||||
`public/js/ui/loadoutSync.js`, edits and `welcome` invalidate preparation still awaiting game data, so an older
|
||||
payload cannot overwrite a newer reset on the session/seat or enter the next match (§16, §29.15). Request reply
|
||||
ordering, debounce, close flush and retry/lock handling remain unchanged.
|
||||
|
||||
`m.public` (throttled ≤ 10/s, only sent when it changed) carries the DESIGN fields plus: `drawnDisabledBonds` (the 3+4
|
||||
drawn set; `disabledBonds` = drawn ∪ the mode's static list), `hiddenBossId`, `bossRound`, `hiddenRound`, `spRound`,
|
||||
`combatMode` (`'client'` | `'server'`), `fields[].progress { killed, total, done }` (teammates' progress UI), `paused`
|
||||
|
||||
Reference in new issue
Block a user