Update AA synchronization, CW progression and diagnostics
This commit is contained in:
1 parent
67a819a4d3
commit
30bee81fe9
30 files changed
+1143
-55
No files matched your search
@@ -56,8 +56,12 @@ The reference `gfRouteCreateNode` uses a run-specific neutral camp for Monster
|
||||
nodes. `gfRoutePlanForRun` reads that camp from an internal FFGO 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. The reference uses one wave
|
||||
of three monsters for the first Monster node and five thereafter, filtering by
|
||||
the captured maximum tier; determining the run camp is still required before
|
||||
constructing that layer. EliteBranch generation additionally needs its option,
|
||||
difficulty and reward contract. No player save was modified by this audit.
|
||||
not uniquely recover the saved run's neutral camp. As an explicit compatibility
|
||||
policy, the new Monster factory picks an eligible, random-enabled captured
|
||||
season camp deterministically from the run ID. This retains one camp for the
|
||||
same run but does not claim to recover the reference's original choice. The
|
||||
reference wave counts, tier limit and chapter star weights come from the
|
||||
revision-bound resource. A focused unit test checks stable camp selection and
|
||||
valid monster membership; the generated node is not yet verified in Client.
|
||||
EliteBranch generation additionally needs its option, difficulty and reward
|
||||
contract. No player save was modified by this implementation.
|
||||
Reference in new issue
Block a user