drwily/gogobee
1
0
Fork 0
mirror of https://github.com/prosolis/gogobee.git synced 2026-07-15 08:32:41 +00:00
Code Issues Packages Projects Releases Wiki Activity

Adv 2.0 Phase L2 step 4b: clarify Misty repair comment

Browse Source 
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:
prosolis
2026-05-09 08:04:25 -07:00
parent 6862a94c8f
commit 693cd9c221
1 changed files with 3 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
internal/plugin/adventure_arena.go
View File

@@ -250,8 +250,9 @@ func (p *AdventurePlugin) resolveArenaRound(ctx MessageContext, run *ArenaRun, c
return p.resolveArenaDeath(ctx, run, char, tier, monster, result, bossNarr) return p.resolveArenaDeath(ctx, run, char, tier, monster, result, bossNarr)
} }
// Misty condition repair (post-combat). Boss-flow path runs through // Misty condition repair (post-combat) for the legacy path. Boss flow
// runZoneCombat which doesn't surface condRepair; skip it there. // runs through runZoneCombat, which calls npcRepairMostDamaged
// internally — no surfaced return value needed.
if condRepair > 0 { if condRepair > 0 {
npcRepairMostDamaged(ctx.Sender, equip, condRepair) npcRepairMostDamaged(ctx.Sender, equip, condRepair)
} }