forked from phenom/healer-man
Update Healer Man server
This commit is contained in:
1 parent
6114a2295f
commit
69809f7228
593 files changed
+903643
-40774
No files matched your search
@@ -0,0 +1,11 @@
|
||||
# Chronomancer resource baseline
|
||||
|
||||
Chronomancer now initializes the expected 414 mana at level 1. The committed baseline initialized 369; both the earlier working-tree run and saved HEAD-source replay reproduced that mismatch, establishing that it predated the recent RoM changes.
|
||||
|
||||
The intended bonus is sourced by Chronomancer's automatic `Chrono Sorcery` passive in `src/game/generated/coaAbilities/chronomancer.json`: its Aura 132 modifier increases maximum `power` by 0.12. Source MiscValue 0 identifies Mana. The human level-1 derived pool is 123 mana before the global 3x pool multiplier, so the expected result is `round(123 × 1.12) × 3 = 414`. The generated description still contains `$s1%`, which the old description-only path could not resolve. The runtime now consumes the structured modifier directly.
|
||||
|
||||
`src/game/classPassiveResourceModifiers.ts` converts structured permanent passive Aura maximum-resource percentage effects into source- and rank-preserving `TalentModifier` entries. Aura 132 uses its source power identity; generic power without that source channel uses the class profile. Explicit resources stay scoped, and matching parsed duplicates are removed. Other-recipient, timed and hit/crit-gated effects stay excluded. This preserves Sun Cleric's Rage and Necromancer's Runic Power as separate resources instead of expanding their Mana.
|
||||
|
||||
The root runtime integration is complete. Nine helper checks and the original selected combat-store resource case pass, including Chronomancer's 414 pool and the unchanged other class/resource expectations. The original case and expectation were preserved. No all-class balance run was used.
|
||||
|
||||
See `docs/STOCKADE_ENEMY_MECHANICS_2026-10-05.md` for the coordinated build and validation totals.
|
||||
Reference in new issue
Block a user