There are some weird interactions and bugs when you try to edit the spelllists. Adding spellID in a list doesn't work, as it keeps adding a different spellID that the one I'm trying to add. If I'm adding '#' before it, then the entire section is disappearing and I can't edit spelllists anymore.

It also doesn't work by adding spells one by one in the filter spell section.

For short, the entire filtering feature doesn't seem to work anymore

Sure !

On a fresh new Spell List and profile (because when it's bugged, the whole filter module is bugged)

• I try to add : 344179 (maelstorm weapon from shaman)
• It then freezes the entire UI for 2 sec and give me another unrelated icon
• If I'm trying to add the hashtag before it it just simply makes the whole module disappear and can't interact with it anymore, I have to create another profile to make it show again

Hope it helps, let me know if I can provide more infos

Could you fill in some details? Which spellIDs are you trying to add that get replaced? What are their replacements?

Hellll yes it's working again ! I tried adding stuff into spell lists, creating new ones, adding spellids directly to the filter section the buffs tabs of my bar group, and it's all working fine ! Thank you so much for fixing it !!

Is it possible that the addon is also lighter on the cpu thanks to your recent version ? It feels like the little lags I had entering combat are gone and overall more fps. Dunno if I'm hallucinating or not but it seems smoother and I didn't touch anything else

The bug with IconIDs has also been resolved.

Can you test r684 and see if all the problems you ran into have been resolved? Thanks!

Sooo...

A few things:

• r683 should fix the spell list becoming inaccessible. That seems the most important problem to resolve right now.
• 237584 is the IconID for Maelstrom Weapon. That's where it comes from, but I have to spend some time figuring out where that goes wrong.
• When I add #344179 (so with hashtag) on my Shaman I get what seems like the correct icon:

It shouldn't be crashing there. Can you install BugGrabber and see what it throws out after installing r683?