Singular - A community driven All-In-One CC - It Just Plain Works - (Pt. 2)

SMF Fury and TG Fury needs some major fixes.
Below is how SMF Fury needs to be implemented. This CC has a lot of potential, but it's outdated in terms of 4.2 priorities.

Ultimately you want to use your highest DPR abilities every time they're off cool down. When dealing with TG, RB is actually your highest DPR ability and as such is a button you want to use on cool down. This is not the case for SMF.

Damage per rage:
BT: 1450
RB: 1000
HS: 850
Execute: 1200


Rage > 85 and you're not in execute phase.
Colossus smash and rage > 50
Incite proc (Save for Colossus smash if possible.)
Battle trance proc

It should be noted, that even though heroic strike is our least rage efficient attack, you will still be using it a lot. It generally ends up being 8-12% of my overall damage on most encounters.

General rotation:

BT_BT_BT

Fill in blanks with CS > Slam > RB > Battle shout

Rage management is incredibly important here. I would highly recommend grabbing some sort of add-on that places a rage bar close to the middle of your screen. I use enraged at the moment, and I would recommend it as it’s highly customizable. You’re going to be pooling rage, which will lead to moments where you think you need to use heroic strike.. but you’re going to have to hold off using it for colossus smash.

Why do we pool rage? Colossus smash. When Colossus Smash occurs, you're going to want to shove as many abilities as possible in that 6 second window, and if possible you want to save an incite proc as well for this. If you have timers, I would HIGHLY suggest that you place Colossus Smash as one of your timers so that you know when it’s about to come up so you’re not like “Oh %***, I have no rage.”

So when Colossus Smash happens, in a perfect world it would like this:

CS-Bt-Slam-Bt
With 2 heroic strikes thrown in.

If for some reason you do not have a slam proc, it is fine to throw in a raging blow instead.

If you’re rage starved (<50 rage), do not use heroic strike unless you have an incite proc.

The reason you want to pool rage as much as possible is that to do the entire rotation in 6 seconds it will require 120 rage without raging blow, 140 with it. That means that if you pool 80 rage for CS, you'll need to have a rage income of 40-60 over the next 6 seconds to make this work effectively. Generally you will have enough rage, as with most gear setups you probably have an average Rage Generation per Second of anywhere between 12-14, which means that in 6 seconds on average you gain 72-84 rage. Of course anyone who has actually played fury will tell you that our rage generation is not very reliable as hit-cap is not feasible nor is it even recommended even trying to hit, and a string of misses could lead to you being rage starved over this 6 second period, which is why we want to pool as much rage as possible to counteract RNG.

Effective colossus smash usage is THE most important part of this rotation.

Execute phase:

Execute is no longer our hardest hitting ability as blizzard buffed everything else and to make this easy… you’re basically only going to use execute to maintain the 25% haste buff and as an extreme rage dump.

When it’s ok to execute:

Getting stacks of executioner up to 5, or when executioner is going to expire in 2 seconds.
Rage is above 50, or the boss is going to die in the next 3 seconds and you need to empty out your rage bar.
As a filler during colossus smash, if you don’t have a slam proc, you can do BT_Execute_BT instead. (Due to rage capping you will actually do this a lot.)

You will no longer use raging blow during execute phase unless you have more than 13 mastery which after the 4.1 patch is just incredibly unlikely. Execute is more rage-efficient due to the "Adjustment" mastery/raging blow took recently, if you have more than 13 mastery go ahead and use raging blow as normal.

Keeping executioner up is your highest priority. It doesn't matter what you're doing, if it's about to run out... execute.

Generally during execute phase your rage income is high enough that your rotation will end up being BT-Exe-Bt-(slam proc?)-Bt-Exe, with very very few free GCDs.


PRO-TIPS AND STUFF:
Go ahead and macro berserker rage into bloodthirst, it's better to use it on cooldown than saving it to activate raging blow so that you can get the additional 5-8 rage per use. SMF has a higher uptime on enrage due to more autoattacks so it will be very rare that you cannot use raging blow when you want to, even without timing berserker rage.

actions+=/auto_attack
actions+=/recklessness
actions+=/death_wish
actions+=/heroic_strike,if=((rage>85&target.health_pct>=20)|buff.battle_trance.up|((buff.incite.up|buff.colossus_smash.up)&((rage>=50&target.health_pct>=20)|(rage>=75&target.health_pct<20))))
actions+=/execute,if=buff.executioner_talent.remains<1.5
actions+=/colossus_smash
actions+=/execute,if=buff.executioner_talent.stack<5
actions+=/bloodthirst
actions+=/slam,if=buff.bloodsurge.react
actions+=/execute,if=rage>=50
actions+=/berserker_rage
actions+=/raging_blow,if=target.health_pct>=20
actions+=/battle_shout,if=rage<70

 

Also, the fury CC actually CASTS Slam....

It's only supposed to use instant cast slams.
Please line it up so that it rage builds up to 75 before colossus smash is off CD, then uses that with everything it can quickly while CS is up.

Thanks

 

Why doesn't the SVN Update work anymore?

 

hasn't been updated in a month I don't think anyway. Use the one that came with 5104.

 

Im working on a new singular routine where it's required that i do alot of target switching (dotting) is it possible to do something like this:

PHP:

Me.CurrentTarget = Player;

Nevermind found a solution!

PHP:

TargetUnit(unit);

 

can we get an update on the front page as to what class/spec combinations work?

 

my hunter hit lvl 69 and just won't target neutral mobs, or even send in the pet to attack 1st which would set of the attack, he just targets and follows the mob

 

What Class are you?:

Druid

What Spec are you?:

Feral

What 'context' is the bot in? (Instance, BG, Normal):

Questing, Grinding and GB2

What level are you?:

85 and 43

What revision of Singular are you using?:

the one bundled with 5104

Have you made any modifications to Singular?:

Nope

Are you using a branched build, or the trunk build? (Only viable for developers):

N/A

What version of Honorbuddy are you using?:

5014


Bot doesnt use Mark of the Wild ever.

 

This isnt a CC probleme.

 

Hi,

I cannot get singular to buff my druid with Mark of the Wild. Every other part is working fine resting, combat, etc. I have my keybindings set to default and am using the latest version of HB. Is there a fix for this?

 

Can you please throw out some updates for this?

Also, please change so interrupts happen at the end of casts - not the beginning.

 

I read somewhere that this was supposed to be community driven is why it isn't being updated. Not sure how much of the community knows how to write cc's. I sure can't make any sense of it.

 

Can some1 please add some adds handling to MM hunter ?

 

Is it a general singular bug or shadow priest bug where the CC will start dotting but continue to run to the next waypoint rather than stop moving?

 

3rd post says MM isn't implimented. How current that is I can't confirm tho.

Sent from my Xperia_X8 using Tapatalk

 

can you guys add to resto druid small check, if not in party or raid and get attacked use something to kill attacker, becouse atm bot does nothing, just heal self

 

Link is dead.

Hehe - now it works

 

svn link down?

 

Seems to be. :/

[EDIT]: Nevermind, the server just seems to be a little unstable. It came up after a while. Keep checking, it seems to go up and down.

Also, just updated mine from a old revision #256 to the current #358 and holy moly it's amazing now. Way better than it use to be!

Thanks to everyone who has been developing this CC. I only wish I thought of updating it when I first started my new character!!

 

Fury; Execute needs a talent check to see if we have Executioner, else you'll pull better DPS without using execute and sticking to the standard rotation.