Skip to content

Fix: Mistweaver Monk shows wrong power bar color after zoning - #2052

Open
svart2521 wants to merge 1 commit into
EllesmereGaming:mainfrom
svart2521:wrong-power-colour
Open

Fix: Mistweaver Monk shows wrong power bar color after zoning#2052
svart2521 wants to merge 1 commit into
EllesmereGaming:mainfrom
svart2521:wrong-power-colour

Conversation

@svart2521

@svart2521 svart2521 commented Sep 10, 2026

Copy link
Copy Markdown
Contributor

Bug: https://discord.com/channels/585577383847788554/1544377339981594805

Issue: PLAYER_POWER_DEFAULT in EllesmereUIUnitFrames.lua overrides which power type a player-frame power bar defaults to for specs whose class has multiple power types, so it doesn't rely on a raw UnitPowerType() read that can transiently report the wrong type right after a zone transition, before spec-power resync settles. Priest (Shadow), Druid, and Shaman already had this override; Monk was missing it, so Mistweaver could briefly show the wrong power bar color (e.g. Energy) after zoning through an instance, delve, or portal.
Fix: added MONK = { [2] = 0 } (Mistweaver -> Mana) to PLAYER_POWER_DEFAULT, matching the existing entries for the other affected classes.

Bug:

Issue: PLAYER_POWER_DEFAULT in EllesmereUIUnitFrames.lua overrides which power type a player-frame power bar defaults to for specs whose class has multiple power types, so it doesn't rely on a raw UnitPowerType() read that can transiently report the wrong type right after a zone transition, before spec-power resync settles. Priest (Shadow), Druid, and Shaman already had this override; Monk was missing it, so Mistweaver could briefly show the wrong power bar color (e.g. Energy) after zoning through an instance, delve, or portal.
Fix: added MONK = { [2] = 0 } (Mistweaver -> Mana) to PLAYER_POWER_DEFAULT, matching the existing entries for the other affected classes.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant