docs: sanitize documentation and generalize upstream reference server citations

This commit is contained in:
CAtlas0784 committed 2026-10-31 23:27:27 +07:00
1 parent 7f106dbe46
commit d1f8beac6f
18 files changed
+87 -87

No files matched your search

+4 -4
View File
@@ -1,8 +1,8 @@
# Currency Wars generated route continuation
The route continuation uses the extracted FFGO `gfPendingAdvanceNode` ->
The route continuation uses the extracted reference `gfPendingAdvanceNode` ->
`gfFxHEnterNode` flow and `gfRouteCreateNode` configuration. Reference executable
and Excel-dump hashes are recorded in `CurrencyWarsReferenceNodes.json`; its 493
and Excel reference hashes are recorded in `CurrencyWarsReferenceNodes.json`; its 493
normalized templates are data, not snapshots of another player's run.
`cwAdvanceRouteNode` operates only on the caller's detached run. It finds the
@@ -37,7 +37,7 @@ the user's run reached 1-6, revision 545, without resetting the run. Boss start
was rejected by the new helper's `CW validated battle scalar parameters missing`.
That guard incorrectly required Level and HardLevelGroup to be nonzero. Decoding
the proven first-node BattleTemplates wire shows both are omitted/zero, while
formation is 5. Updated FFGO `gfBattleMonsterWave` (RVA 0xc62b00) initializes its
formation is 5. Updated reference protocol handler `gfBattleMonsterWave` (RVA 0xc62b00) initializes its
wave param with formation and elite only, independently confirming omission.
The helper now preserves those captured zero values and validates the required
@@ -53,7 +53,7 @@ and EliteBranch's selected penalty against the extracted penalty table. This
does not generate those layers or establish that the Client accepts the fight.
The reference `gfRouteCreateNode` uses a run-specific neutral camp for Monster
nodes. `gfRoutePlanForRun` reads that camp from an internal FFGO run field; it
nodes. `gfRoutePlanForRun` reads that camp from an internal reference run field; it
is not represented by the saved Client stage's boss camp list. The captured
first battle's monster IDs match more than one native season camp, so they do
not uniquely recover the saved run's neutral camp. As an explicit compatibility