updated WA and the GSE then popped a reload.
i too have a WA problem. i get the shift popping, but CTRL is nowhere to be seen. i tried to get into WA > primarly display > execute Mt ( and ST) then under text 1 type in %c to get the custom box to open, nothing happend⦠something im doing wrong?
Original Message
Is the issue that the WeakAura isnāt prompting you to press Ctrl, or that your configuration isnāt actually sending Ctrl + Activation Button?
If your system canāt register Ctrl + Activation Button, then adding %c is the workaround. That forces the text to fall back to just your action bar execute keyāit just uses the action bar key directly.
But if the problem is that the WeakAuras never prompts you to use Execute, thatās a different situation. That would relate to how I set up the triggersāExecute usage is pretty selective by design, and itās not triggered often as a heads up.
If you can confirm which of those two issues youāre seeing, thatād be super helpful. Iāll review the triggers again either way, but I also left an explanation a few comments up about how the trigger logic works in case that helps clarify.
EDIT: Found a potential issue with Multi Target expecute please update weakaura
EDIT to the EDIT: Somethings not right Iām looking into it.
After checking it out Iāve updated both the WeakAura and GSE.
I do wonder though. Wouldnāt doing something like the get you banned since using an auto-clicker is against Blizzards TOS?
Hey @Noblex,
First off ā do your own research and make your own call. This is just my personal view and experience.
Yes, Blizzardās ToS prohibits automation ā systems that play the game for you. AutoSpec doesnāt do that. It requires you to be fully present: holding modifiers, reacting to mechanics, making decisions. Thereās no scripting, memory reading, API manipulation, or injected .exe behavior ā just clean, real-time inputs.
AutoSpec follows the āone action per key pressā rule that GSE is built on. GSEās been public for years with millions of downloads and a massive, visible community. If that crossed a hard line, it wouldāve been addressed by now.
Using repeat input is a grey area, but Iāve personally never had an issue. I only use a hold-to-click setup ā no toggles, no AFK play. Iām always at the keyboard, actively playing, reacting, and contributing. From what Iāve seen, players whoāve reported bans were often also botting or had long histories of being disruptive ā which I suspect factors into Blizzardās decisions. They can see behavior patterns and chat logs, not just inputs.
TLDR: I remember being hesitant when I first started using it, but Iāve never had an issue.

The choice is yours.
Your macros consistantly perform well. with meta talents etc.. lol please make a rogue assasination one Im using yours for all the classes you have made some for so ty..
Glad to hear itāRogue is up next on my list. Iāve been stuck on Balance Druid for a few days; itās been a real headache with all the moving parts.
Assassination will be nextāif I remember right, itās a lot more straightforward, melee builds usually are.