What's new
By:
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal

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

Rewards said:
Warrior CC 20% Phase

Priority sub 20% is to get executioner to 5 stacks(spamming execute) using MSs when you need to keep Slayer at 3 stacks and not falling off, then once ur at 5 stacks executioner, 3 stacks slayer, MS > CS(swap MS and CS if no 4pc t13) > Execute(50+ rage).
No heroic strike, no overpower or slam.

can you fix it?
Thanks for kbrebel04 to post this.
Click to expand...

Firstly; as a 7/8 H raiding arms warrior... just plain no.

Sub-20%, you replace Slam with Execute (execute moves to the top of the prio list if Executioner is going to fall off)

Otherwise, you keep the same rotation. Using overpower only if its going to result in more damage (less than 30 rage, use overpower, otherwise, use execute)

Keep CS up -> MS on CD -> Overpower if < 30 rage -> Execute.

The idea is to stay in berserker for the entirety of the execute phase. (That means popping Deadly Calm/Reck if you need to, as well as Inner Rage, etc)

Execute itself isn't a great DPS increase, its the haste buff that makes it worth it. (Replacing slam with Execute basically ensures you'll never lose the Executioner stacks) MS/CS are still higher prio during the burn.

You may still want to pop HS if you have Incite and CS up at once, but thats a big "if". (Personally, I never do, as Execute does more avg damage)

I rewrote the Arms rotation the other day to have better stance-dancing. Netted another 3k DPS over the old rotation. However, this is still 6k short of my manual play. Writing proper stance-dancing arms logic is quite difficult. (You only ever want to be in battle stance for rend, and *right* as you need to pop Overpower) Its also difficult to delay overpower for back-to-back Overpowers during a CS duration.
 
WL - Channeling to heal the Felguard always break outside Combat. In Combat my WL do this fine, but outside it starts and move and break.

the bear tree quest in hyjal in kickz profile doesnt work with WL and Singular. When the WL is in the Tree to use the QB it trys always to cast something on him self from Singular.
 
Last edited:
burgermund said:
That didnt fix the problem... and it use "dark Command" to. even when i try to start hb after i join the intance or heroic it still use DB and DC. And taunt is set to false.
Click to expand...

attach a log file please
 
I'm using this CC to level my now 65 warrior via questing and overall it's pretty good. However, there are couple of issues that some people already mentioned which I will mention again:
1. It does not cast hamstring even though the slow box is checked
2. It does not cast intercept even though the box is checked

I also use this on my now 84 druid and it will be nice to be able to cast healing spells on itself when out of combat instead of just moving on to next mob when it's <50% health.
Thanks again for this great CC.
 
What have you changed?! I used to put my bot on combat mode and then put 'DisableMovement' to False then go do a bunch of Heroics
Now when I do this he always tries to get behind the enemy, this causes me to sometimes run into AoE areas

I thought disablemovement false would stop all bot-combat movement?
is my bot just going crazy?
 
Is it me or blood Dk start to spam Blood Boil a lot which lead then to less death strike?
while doing raid or hc i used to heal myself more than healer or sometime little less but since I update singular self healing reduced a lot which lead me to shift back to old singular i was going to provide a log but i deleted all the logs by mistake. Is anyone else have the same problem like me using the new blood cc?
 
Mage and Paladin specs (except Holy) are completely reworked
 
Setting charge/heroic leap to false while prot warr doesn't disable it, it still tries to charge and heroic leap. Here's a log from madness of deathwing
 

Attachments

Current talent tree's up are only ones yous are gonna support? Kinda been the same old for awhile now, None of which I use.
 
Some things with the ret file:
Zealotry should not be blown during AoE phases because Divine Storm doesn't proc 3 HP.
AoE phases should be 4+ mobs. At 3 most spreadsheets still show single target better DPS.
Guardian should be be cast to build strength, then 10 second later Zealotry / AW.

I haven't tested it yet, but will do so when I get the chance. One thing I noticed with my Ret file is that Spell.Cast("Judgement") refuses to cast on Ultraxxion. Works fine everywhere else.
 
Please update the Arms CC. I have only moved the prio to MS > CS (I just replaced the rota from default rotation MS > CS) And is there anyone working with the Stance dance. Im willing to to test all CC?s. I have been raiding with this Arms CC long time now.. and it rocks. But i want to go abit better in DPS and there is just fix the rota and add working stance dance.
 
I've completely redone the Arms rotation, but am waiting for the new release from Raphus w/ better Instance/BG rotations before I change anything. He's flying through the updates though, so it shouldn't take long.
 
Why is singular the default CC? I've been trying to help G in the forums today due to Bossland and Tony not able to be around, and 90% of the 'won't fight' issues are singular. Either 'spec not supported' Or 'Spec supported in PvE, But not in PvP (Mixed mode)'
 
Anyone having problems with the paladain class not switchings auras and just chain casting blessings?
 
khurune said:
Why is singular the default CC? I've been trying to help G in the forums today due to Bossland and Tony not able to be around, and 90% of the 'won't fight' issues are singular. Either 'spec not supported' Or 'Spec supported in PvE, But not in PvP (Mixed mode)'
Click to expand...

Because overall, it handles all classes/specs the best. (Check the numbers) Its also the CC we use while testing HB internally, as we can ensure none of the CC code is doing anything beyond what its actually supposed to. (Like completely re-implementing targeting, or ignoring things HB has deemed as important)

Also; you should be redirecting those people to this thread. Singular will *always* fight. Period. If there is an error message, then people need to learn how to read the error message.

Currently, the only spec we don't support, is Sub Rogues. (Mostly because I'm too lazy to code the rotation for it)
 
Apoc said:
Because overall, it handles all classes/specs the best. (Check the numbers) Its also the CC we use while testing HB internally, as we can ensure none of the CC code is doing anything beyond what its actually supposed to. (Like completely re-implementing targeting, or ignoring things HB has deemed as important)

Also; you should be redirecting those people to this thread. Singular will *always* fight. Period. If there is an error message, then people need to learn how to read the error message.

Currently, the only spec we don't support, is Sub Rogues. (Mostly because I'm too lazy to code the rotation for it)
Click to expand...

Good answer, but as to the 'always fight' Holy priest has a check in it that stops it running in Battlegrounds. You also got to keep in mind, people don't put alot of effort in what they do, if atall. Maybe some better way of notifying the user that there current spec isn't supported instead of just a quick message in the window thats quickly spammed out of sight?
 
You must log in or register to reply here.
Back
Top