[11.1.7] šŸ’  AutoSpec: FURY // Maximum DPS Output, Sophisticated GSE Sequences, Single-Target & Multi-Target Detection, Advanced Cooldown & Defensive Usage — Delivered Through a Custom-Built, Precision-Tuned Combat UI

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.

:brain::balance_scale: The choice is yours.

1 Like

Your macros consistantly perform well. with meta talents etc.. lol please make a rogue assasination one :slight_smile: Im using yours for all the classes you have made some for so ty..

1 Like

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.