Conversation
reiserFSs
left a comment
There was a problem hiding this comment.
Changes requested: keep robot and enhance-skill data on the same client version.
P2 — Mixed-version premade deployment (AscNet.GameServer/Handlers/FightModule.cs:890–899). Study stage 30100081 resolves frozen 4.6 robot 2273, but the added lookup reads 4.7 enhance groups. The frozen removal list lacks 102628–102630, so the actual PreFightResponse grants all three at level 1 to base Pyroath. Version-matched original EN Lua generation produces an empty enhance list; the current robot row explicitly removes these skills. The legitimate leap control on stage 30100099 still produces its three level-18 skills.
Use version-matched robot/enhance/removal inputs throughout the legacy Study path and correct the Pyroath regression expectation to an empty list. Preserve legitimate leap deployments.
Evidence: registered-handler packets plus the unmodified original Lua generation method with authoritative table adapters. No rendered/native-combat claim.
f0b8c8c to
8ef92fc
Compare
In response to review
Additions
Changes
Table-driven throughout - no character or stage-specific cases in runtime code. Verification
Known unrelated failures, also present on |
Summary
Premade robot deployments ignored
Robot.tsv.EnhanceSkillLevel, leavingtheir
Character.EnhanceSkillListempty. This prevented leap/enhancemechanics from activating in Leap Trial stages.
Changes
EnhanceSkillLevel.RemoveSkillIdfor base-form robot variants.robot-based fights.
The runtime change is table-driven and contains no character- or stage-specific
special cases.
Verification
and Bianca Theatre compatibility selectors pass.
Known unrelated compatibility failures remain in existing Pain Cage,
Theatre6/activity-version, and character-unlock tests.