From 693cd9c221deea8c0a451798c284967175d47c40 Mon Sep 17 00:00:00 2001 From: prosolis <5590409+prosolis@users.noreply.github.com> Date: Sat, 9 May 2026 08:04:25 -0700 Subject: [PATCH] Adv 2.0 Phase L2 step 4b: clarify Misty repair comment MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 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) --- internal/plugin/adventure_arena.go | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/internal/plugin/adventure_arena.go b/internal/plugin/adventure_arena.go index 9afe74f..16fdb27 100644 --- a/internal/plugin/adventure_arena.go +++ b/internal/plugin/adventure_arena.go @@ -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) }