mirror of
https://github.com/prosolis/gogobee.git
synced 2026-07-15 00:32:40 +00:00
Adv 2.0 Phase L2 step 4b: clarify Misty repair comment
runZoneCombat already calls npcRepairMostDamaged internally when the Misty buff is active and the 20% chance hits — boss flow inherits that behavior automatically. The comment in resolveArenaRound previously implied the boss flow skipped Misty repairs, which was wrong. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
@@ -250,8 +250,9 @@ func (p *AdventurePlugin) resolveArenaRound(ctx MessageContext, run *ArenaRun, c
|
||||
return p.resolveArenaDeath(ctx, run, char, tier, monster, result, bossNarr)
|
||||
}
|
||||
|
||||
// Misty condition repair (post-combat). Boss-flow path runs through
|
||||
// runZoneCombat which doesn't surface condRepair; skip it there.
|
||||
// Misty condition repair (post-combat) for the legacy path. Boss flow
|
||||
// runs through runZoneCombat, which calls npcRepairMostDamaged
|
||||
// internally — no surfaced return value needed.
|
||||
if condRepair > 0 {
|
||||
npcRepairMostDamaged(ctx.Sender, equip, condRepair)
|
||||
}
|
||||
|
||||
Reference in New Issue
Block a user