3.) In GSE, under the Keybindings section, created a “New Keybind”. Set Key to Bind “4” and Sequence set to “Aerrek_Beastmaster_NOMOD”, and Talent Loadout (test) as the 11.0.2 RAID talent from the Aerrek_Beastmaster_NOMOD Talent tab from set 2 above.
I’m having the same problems as the other guy, does not fire anything and i bound as you said. Other macros don’t have any issues. I use the mouse button 4. All it does is cast a hunter’s mark! Also if it works why would you need camouflage to go off? I would love to try this.
Hey Aerrek, this is amazing. So first of all, thank you. I have spent some time reading all of your instructions and appreciate how much care you have clearly put into this.
In one post about 12 days ago you mention Black Arrow isnt in the approved talents, then the next day you comment with this stating the top talents from WH are in the talents tab in NOMOD. I found those and imported them into my toon and they are pack leader hero talents. Which is totally cool, just curious if there will be builds that work with Dark Ranger as its been reworked and looks fun?
Can you post a screen shot of your Talents? I can’t get ALT + Actionbutton to work, and I am thinking it might be because I don’t have the correct Talent Tree.
This build follows top guide recommendations by disabling Kill Shot by default, while allowing manual toggling in the NOMOD GSE sequence. AoE is handled intelligently through Multi-Shot with real-time nameplate detection and Beast Cleave checks. Includes automated Hunter’s Mark logic for solo and PvP, and auto-Flare at cursor to counter stealth in PvP. Built for consistent output with minimal input and a streamlined HUD.
i can’t even import it i have all the latest versions when i paste the import code it all shows there to import but never actually goes into my sequences no errors in chat log just nothing happens.
I use your build for the Paladin, it works wonderfully.
However, I have a problem with this one, after a while I get the error “the addon has generated too many errors, please deactivate it”.
I don’t understand why.
Also, I thought I read elsewhere that you should no longer use “reset =” in macros, could that be the cause?
Back when the TWW prepatch dropped, Blizzard made a change that temporarily broke lines like: /castsequence reset=X Ability 1, Ability 2
That caused a lot of discussion online, and many people recommended avoiding it altogether. But that issue has since been fixed, and reset= is safe to use again. So if you stumbled on a forum post or thread warning against it, it was likely from around that time when it was a hot topic.
As for the error—if you can send me the actual copy-and-paste error text here or PM, I’ll take a look. I just hopped on my Hunter (Beast Mastery), and I’m not seeing any issues on my end. I’m happy to troubleshoot it with you, but I’ll need the exact error message.
EDIT: if it has anything to do with keybind, /reload your UI to see if it goes away. Sometimes if you move abilities or swap specs things get funky.
Hey, thanks for the quick reply, that’s really appreciated!
I’ll dig a bit deeper on my side — it might be something misconfigured. Since I play with the game in French, I sometimes have to rename abilities for things to work correctly (like Dire Beast, for example).
Good to hear that reset= is safe to use again! That’s definitely useful, so thanks for the clarification — I probably read outdated advice somewhere.
If I keep running into the error, I’ll try to capture the exact message and send it your way for troubleshooting. Thanks again for your time and amazing work!
Thinking about it more, I’ve had others tell me they avoid using reset= for a different reason. Some say you can’t use it with GSE, but I’ve found plenty of ways to make it work. Their argument is that because we’re clicking macros so frequently, the reset never actually resets. And technically, that’s true—but I think that behavior can actually be a benefit of GSE.
Take reset=1 for example. It resets after one second of not attempting the macro. That might sound useless at first—but what it really means is that you can trigger something once when the key is initially held, and it won’t happen again unless the user fully releases for a moment.
That opens up practical options. For example, make Concussive Shot fire the first time you press and hold the NOMOD sequence, and it won’t trigger again unless you release for a second—perfect for utility weaving. That would look like:
Or for modifier-bound abilities with multiple charges that are off the GCD (which users might accidentally double-tap), you can safely throttle it like this:
/castsequence reset=1 Off GCD Ability, null
This ensures the ability only fires once per keypress cycle, even if the button is spammed. It takes a little getting used to, but it’s a powerful tool when applied intentionally.