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

Well that’s not good or as designed,
@skiski

Are you using one of the two talent strings provided?

Taunt is not sequenced. I double checked everything in the sequence but didn’t see anything that would cause this :thinking:

… Unless there is some Guardian mechanic I’m missing? :eyes:

i am using the string provided maybe its an issue on my side then

‘New User Help Links’ at the top is the best help I can give you to make sure you’re configured properly :+1:

Hey Aerrek, gotta say that I’m really liking your combat systems. I’m still trying to understand the logic behind them as imho it is a masterpiece of macro code!

My question is in the Guardian macro, it imports 4 guardian and 4 feral macros, each with a nomod, shift, ctrl and alt version. I assumed we are supposed to just bind the 4 for Guardian as when I bind the Feral ones afterwards, GSE replaces the Guardian ones. Why are the Feral macros included? What is their purpose? Do we in fact only keybind the 4 Guardian macros?

Thanks for any clarification you can provide.

Hey @Logan_5,

Thanks for the complements,

You import 8 sequences total (4 each.)

When you are Feral, bind the Feral sequences.
When you are Guardian, bind the Guardian sequences.

It should be as easy as that. Sequence keybindings are spec specific.

Macros (not sequences) starting with !, @, #, or $ are used in the sequences.
Other macros are my recommendations to add to your action bars, ‘better’ spells.

:+1:

The Macro is awesome the only thing is missing is that the Ironfur is not stacking and its mandatory to be able to push tanks limits can you also see it through?

Hey @Rainskkull,

I went in and increased the likeliness of Ironfur to be used, the goal is 100% uptime.

I don’t want it on a modifier because it’s pressed so often, trust me I tried, very annoying / cumbersome lol


If it seems like I’m missing a mechanic of Ironfur, lmk :+1:

i will install it again and let you know ofc

Is it for Moonkin in your to do list? XD

1 Like

@Rainskkull it is but the highest on my to-da list is 1 spec per class, which I am getting close to. :+1:

Making the first spec of a class is 1/2 the work of each spec. I’m still trying to level too

So talking about ironfur the reason it doesnt go off as much as you would expect is because maul is in the nomod of the guardian rotation so it eats a lot of your rage. A way I’ve fixed this is by changing /cast maul to /cast ravage this is awesome because if your Elunes Chosen you don’t use maul anyways and if your druid of the claw you want to save all your maul buffs for ravage and this will ensure it only casts it when you get a ravage proc. hopes this helps!

1 Like

Good to know, I’m going to give Guard some love in the future. If there are any improvements I need to know, this is my main lol

Yes i agree, Druid tank is the S pushing Keys tank.

I blv @Aerrek that you should remove all hitting procs like ravge etc.
and the attack skills should be in the macro

Procs should be
Regeneration
Incarnation
Survival Instincts

the Attack rotation and stacks of Ironfur should be in the macro

I will fix it also as you mentioned

Also the Elunes Chosen is the meta spec.

A rotation to consider also

The issue with Ironfur being in a sequence by itself is that it will spend all of your rage away on Ironfur.

Ironfur is not on the GCD meaning if you click it, it will cast immediately. Click it twice, it will cast immediately twice.

That’s bad for us because we’re using auto click. So having it used ‘autonomously’ won’t work. Unless…

Unless I sequence Ironfur with another ability, and use its cooldown as Ironfur’s CD. Which is how it it currently configured.
/castsequence [combat,nochanneling,harm] Thrash, Ironfur


I don’t put all abilities in the sequences because they are not effecting in a ‘fire off CD’ priority list.


I want to keep Ironfur in the sequences because when it is not this setup feels too busy. I’ve tried many different configurations.


I could think of, this was the most user friendly and smoothest I found.

1 Like

@Rainskkull @Wilson,

I hear you load and clear and I made some big updates. I think it’s a big improvement


Guardian Update

  • CTRL: Ironfur
  • Increased the refresh rate of sequences Moonfire for Galactic Guardian proc consumption
  • @mouseover Wild Charge from CTRL → SHIFT
  • Bear Form in dungeons fixes.
  • Updated Descriptions and Notes

Both imports updated :+1:

Lmk of any issues, if any

Hey Aerrek,

Thanks for the tip on this. Excellent idea using the thrash, ironfur.

Well done, mate.

Not sure at what time exactly but I made a second improvement and updated to the GSE :+1:

1 Like

What did you change to remove maul. I see it in the sequence down in block 5.1.3. I actually disabled that block all together and it has definitely helped, however MAUL is still going off from time to time with the no mod keybind and I can’t figure out why. Also I feel like Moonfire should fire off on pulls. For me its not firing until GG procs or at least seems that way. I have keybound moonfire to circumvent the issue for now.

1 Like

so I don’t have the most up to date Aerrek’s as I’ve made a shit ton of my own alterations but just make sure u go through and make sure its all ravage then save and reload ui if that still doesnt work make sure its not tucked inside one of the macros somewhere lmk if it still doesnt work for you

2 Likes

Hey @Dissident,


What did you change to remove maul. I see it in the sequence down in block 5.1.3. I actually disabled that block all together and it has definitely helped, however MAUL is still going off from time to time with the no mod keybind and I can’t figure out why.

Maul

NOMOD: Regular DPS priority Maul.
SHIFT: Ravage and Tooth and Claw Procs.

image
NOMOD is Step 7, we don’t use Raze.


I feel like Moonfire should fire off on pulls. For me its not firing until GG procs or at least seems that way. I have keybound moonfire to circumvent the issue for now.

#DoTs /macro

Thrash: Start of COMBAT*
Maul: Start of COMBAT*
Moonfire: Every TARGET swap
*Improves DPS by quickly applying multiple Thrash DoTs when traveling from pack to pack, like in an instance. Nominal DPS loss on single target.

/cast [combat,noform:1]Bear Form
/castsequence [combat,nochanneling]reset=combat Thrash, null
/castsequence [combat,nochanneling]reset=combat Mangle, null
/castsequence [combat,nochanneling]reset=target Moonfire, null

‘Moonfire on target swap’ is the highest priority in the “Core DPS Priority Loop”.

Galactic Guardian procs are consumed naturally as you swap targets AND within the NOMOD sequence*
For when you are not swapping targets as often, i.e. raid boss, PvP, target dummy.


While I’m at it

Ironfur works similarly to Maul, it’s applied by the GSE and refreshed by the WA


Lmk :+1:

Hey @wilson,

If you want to make a modification, no problem, cool with me. Just know that you can’t update :thinking:

Also, since TWW relaced I’ve been doing nothing but making these systems, I’m up to abt 20/40(ish) specs now. Only mentioning this b/c in the past week I’ve been on my main Guardian (finally). Guard has gotten some big updates including Ironfur rework, stance logic updates, and many other things

Either way works, just wanted to mention :+1: