walker naming convention in CLAUDE.md (first/secondNameIndex 0-31 via name_index.json); add Veteran Beast copy
This commit is contained in:
@@ -58,6 +58,13 @@ load: gunzip -> XOR decrypt -> Newtonsoft-BSON parse
|
|||||||
If a game update changes the key, recover it with no RE via `walker/recover_key.py`.
|
If a game update changes the key, recover it with no RE via `walker/recover_key.py`.
|
||||||
- `pymongo`'s `bson.encode` reproduces Newtonsoft.Bson byte-for-byte, so decode→encode is identity.
|
- `pymongo`'s `bson.encode` reproduces Newtonsoft.Bson byte-for-byte, so decode→encode is identity.
|
||||||
|
|
||||||
|
### Walker naming convention
|
||||||
|
A walker's display name is **two indices**, not a string: top-level `firstNameIndex` + `secondNameIndex`
|
||||||
|
(BSON int32, **0–31 each**). Resolve them via `name_index.json` → `first_name` / `second_name` tables
|
||||||
|
(e.g. `(16,5)` = "Veteran Veteran", second `6` = "…Beast"). The top-level `name` field is **null/unused**
|
||||||
|
— the shown name comes from the indices. "name1" = `firstNameIndex`, "name2" = `secondNameIndex`. Set
|
||||||
|
both with `build_wbt.py rename <wbt> <first> <second> -o out`, or edit the index directly when copying.
|
||||||
|
|
||||||
### The 5 hashes (a `.wbt` is a serialized `WalkerBlueprintDto`)
|
### The 5 hashes (a `.wbt` is a serialized `WalkerBlueprintDto`)
|
||||||
|
|
||||||
All = `MD5(UTF8(JsonConvert.SerializeObject(obj))).hexUPPER` — Newtonsoft compact JSON: no whitespace,
|
All = `MD5(UTF8(JsonConvert.SerializeObject(obj))).hexUPPER` — Newtonsoft compact JSON: no whitespace,
|
||||||
|
|||||||
Reference in New Issue
Block a user