florian.berthold
7b318475e8
The previous file augmented _G.RAID_CLASS_COLORS with hand-picked placeholder colors. On both the Voljin/CoA and Ascension classic+ clients the table is already populated by FrameXML (SharedXML/SharedConstants.lua) with all 32 class tokens, so the augmentation was dead code (only-set-if-nil never triggered) and the hand-picked palette diverged from what the realm itself ships. The path that DOES still need fixing is !ClassColors. When that addon is loaded it injects a separate _G.CUSTOM_CLASS_COLORS populated only with the vanilla 10, and Omen.lua:914-917 prefers CUSTOM_CLASS_COLORS over RAID_CLASS_COLORS. So on a !ClassColors-equipped client the 22 CoA tokens silently fall through and the bar reverts to dbBar.BarColor. Rewritten to: when CUSTOM_CLASS_COLORS exists, copy missing entries from RAID_CLASS_COLORS — same nil-only policy. RAID_CLASS_COLORS is left untouched (the client is authoritative). No more divergence between Omen and the realm palette.
Omen
Omen is a threat meter.
Basically, enemies in WoW decide who to attack by deciding who is the most threatening based on the abilities you use. What Omen does is provide accurate values of your group's relative threat level on individual enemies, so that you can see when you're in danger of pulling aggro (or, if you're next on the snack list if your tank bites it). This info is usually only critical in raids, where only tanks can survive aggro, but it's useful for any multi-player situation.