docs: sanitize documentation and generalize upstream reference server citations
This commit is contained in:
1 parent
7f106dbe46
commit
d1f8beac6f
18 files changed
+87
-87
No files matched your search
@@ -31,14 +31,14 @@ save migration was justified by the old partial catalog alone.
|
||||
|
||||
## Reference-backed correction prepared
|
||||
|
||||
The FFGO update inspected on 2026-10-26 contains an explicit
|
||||
The reference protocol specification inspected on 2026-10-26 contains an explicit
|
||||
`challenge_peak_extra_data` JSON object at binary file offset `0x114c212`,
|
||||
decoded length 9101 bytes, binary SHA-256
|
||||
`235f5c3567f281cc99613ed84694ef23f492c15298dc868a8e78e6529f0cda86`.
|
||||
Its Peak 204 mapping is NPC **4015010**, entrance **3013701**, maze group
|
||||
**10**. These values come from the reference object, not ID arithmetic.
|
||||
The full reference extraction is retained in
|
||||
`battle_diagnostics/ffgo-20261026/challenge_peak_extra_data.json`.
|
||||
`battle_diagnostics/reference-20261026/challenge_peak_extra_data.json`.
|
||||
|
||||
`resources/ChallengePeakSceneOverrides.json` retains all 44 explicit mappings
|
||||
and their provenance. `peak_scene_overrides.go` applies only the scene NPC,
|
||||
|
||||
Reference in new issue
Block a user