Update 12.0.0+ Compatibility and Roadmap

[bozoweed]

In update 12.0.0+, WoW introduced SecretValues and applied major breaking changes that broke many addons. WoW's objective is to prevent users from using powerful addons that provide a significant advantage in combat.

Because of these changes, many addons are now archived or broken; major ones like WeakAuras and Decursive have been hit as well.

What we are not allowed to do now:

• Check Debuff type to display cooldowns for spells used, or track failed/successful dispel casts.
• Use Debuff name/type/applications (and all related data) to prioritize targets or trigger warnings (e.g., isHarmful or isFatal).
• Perform any logical operations directly linked to SecretValues.

What we can still do:

• Display Debuff data exactly as provided, without any modifications.
• Use Left/Right click to cast spells.
• Display MUFs/Live lists with Blue/Red coloring.

To reach a stable release, we have to:

• Update Live List to only display Debuff Data
• Update to use UNIT_AURA instead of COMBAT_LOG_EVENT_UNFILTERED
• Update MUFs
• Find a way to bypass LibQTip limitations in MUFs ( Currently migrate from LibQTip to Native GameToolTip )
• Update the Priority system to ensure we never perform operations on SecretValues
• Ensure changes are still backward compatible

I created this issue to describe the current project state and to prevent users from opening new issues asking for an ETA or updates.

Note: This to-do list is not final, and the owner may have other tasks that I haven't listed.

[bozoweed]

also i'm thinking about the cooldwon issue, should we provide a way to user to say what is the defaut type that he want to track ? for exempl if my magic dispell got 10 secondes cooldown but my seconde one has 60 seconde i want track the 60 secondes cooldown , i know thit is possible cause in my original code base i have succefull track it so maybe we can introduce that option to let user choice wich one he want track.

just an idea ^^

[2072]

Thanks for creating this issue.

Actually as it is now, it tracks the cooldown of the first spell (the one at top priority).

I'm currently working on replacing LIbQTip with Blizzard's default GameToolTip, I was able to restore the full tooltip, I just have a problem with the application number which is always displayed even if it is 0...

For the priority system we could use a trick: set one texture per type and set their strata according to the configured priority (there will be a performance impact as we will have multiple texture to set each time but it's worth it)

[2072]

actually we can use https://warcraft.wiki.gg/wiki/API_C_UnitAuras.GetAuraApplicationDisplayCount

[bozoweed]

actually we can use https://warcraft.wiki.gg/wiki/API_C_UnitAuras.GetAuraApplicationDisplayCount

that is not secret value ? :o

Edit: yes i confirme i already have explore that way ( without implement it because that made lot of CPU ops for just get back Application OPs and can be really havy on slow computer )

[bozoweed]

i think that all new havy methode must have an option to enable or disble them because some player have low spec computer

[2072]

as long as it's not done repetitively in a loop it's ok, they are not that heavy and I haven't checked but they are probably not implemented in Lua or if they are Blizzard will optimize them later if it's an issue.

[bozoweed]

look like good in fact ^^