CLU (Codified Likeness Utility) - (Pt. 2)

Can you guys please update your first post, so we know what is supported for 5.1 and what still needs testing thnx

 

they havent really been updating anything unless its totally broke from what i can tell they have a new project called purerotation they are trying to have out before christmas

 

The Affliction lock CR sometimes does not always keep up Unstable afflication while using Malefic Grasp as filler.

 

oh thats interesting, sounds awesome

 

i like the rouge assiss i was in the 10raid on the second place

 

warrior prot is verry good

 

I tryed almost everything to fix lagging issue but nothing helped any advice or help ?

 

Affliction Warlock - Some problems I experienced in the rotation during LFR.

-at 20% he wasnt keeping haunt up - he would sometimes just sit there drain souling instead of keeping haunt up.
-drain souling mid fight when 0 soul shards - this doesn't need to happen, just wait for soul shard procs.
-not keeping up unstable affliction - at times it drops for 3-4 seconds before it refreshes it
-doesnt refresh dots after casting Dark Soul: Misery mid fight - needs to update dots after casting it, so the dots gain the effect.
-on new target it opens with haunt - it should dot first then haunt into malefic grasp, as the 2 global cooldowns wasted by casting dots is a dps loss on the haunt
-it doesnt stop casting malefic grasp to refresh dots before they run out - huge dps loss when 10 stack agony drops
-if talented into kil'jaeden's cunning, should continue normal rotation even when casting - it seems to just spam corruption and agony whilst moving.

hope this helps.

 

Just wondering if there's any resto shamans using CLU at the moment? I used CLU for different characters a long while back and loved it, trying to decide between this and KingWOW for resto sham.

 

Anyone having issues with blood dk? Just made a blood dk and this is crashing my dk saying that it can't find a rotation

 

This isn't intended as a leveling rotation. The reason it's not finding a rotation for you is because you don't have the signature spell it's looking for yet. I believe the spell it's looking for is Rune Tap and you get it at 64.

 

Thanks ksu, I used this on my warrior from 80-90 and the rotation was perfect so I figured I'd give this a try, I'll try it again at a later level. thanks!!

 

Bot says I do not have 2pc tier set bonus... I have two LFR pieces. Is there a way to force CLU to recognize? Using ret paladin

 

Good news/bad news situation.
Bad news, there's no good way to "force" it to see you have you 2/4 piece bonus.
Good news, you don't have to. It doesn't appear to care beyond a single line in the initialization text.

As an aside, the 2/4 piece tier detection algorithm CLU is using is broken and will not work if you are mix/matching between LFR, Normal, and Heroic pieces. It needs to add up the number of pieces you have from each of the three item sets to determine if you have your set bonuses.

 

Survival. This has been an ongoing issue with CLU.

 

So, why does it not recognize that I have 2 piece of the LFR White Tiger set?

 

long story short, it's still looking for the 397 set =\

as a quick fix, you can go into the retribution.cs file and change the item set at the top of the file to whatever one you want it to detect.

 

Tried this for tanking on my DK (Leveling thrugh dungeons) and it says it doesnt support my level. At what level does CLU start working for Blood DKs then?

EDIT: When I go frost it seems to be semi-working atleast.. This is at lvl 62.

 

Since I've seen a lot of affliction warlock discussion lately and many wrong informations I decided to write a bit on that.Bare in mind that I will be refering to a "target" as a Raid boss not ordinary mob you kill doing daily's.
Let's start with initial pull.

1. CoE
2. Dark Soul:Misery
2. Haunt
3. SB:SS
4. MG spam
5. rest of the rotation based on priorities

This is how initial pull should be done. Before anyone starts with "your dot's should be applie before haunt bla..bla..bla.." , Haunt has a TRAVEL TIME. If you are more than 20yards away from boss then your SB:SS will land BEFORE the Haunt. I hope this makes it clear. If by any chance you get trinket/lightweawe/weapon enchant proc on first MG, then it's beneficial to refresh your dot's with SB:SS if your new dots are atleast 30% stronger than old ones(how will you know this it's up to you)
Now for the "rest of the rotation" after initial pull there are some things you have to watch over.
Haunt should be casted only if you have INT/SP proc up to maximize it's damage, but if any of your dot's on target has remaining time less than 9 seconds refresh dot's first to get full uptime of dot's during Haunt. Also Haunt is ALWAYS casted if you have 4 shards so you don't loose NF proc.
Regarding dot's, all dots are refreshed on pandemic benefit if their new damage is equal or stronger than last one or earlyer than pandemic threshold if they are atleast 30% stronger than old ones. If you have strong dot's on target then you don't refresh them on pandemic but you squeeze some more MG's in and refresh them before they drop, especially Agony. If your corruption or UA drop by less than 1 second it's no big deal since last tick did more damage anyway than your new first one will do.
Regarding shards. If you are refreshing your dot's properly and Haunt on INT procs then you don't hoard your shards and save 2-3 for DS/BL. you save only 1 shard so that you can SB:SS on empowered dot's or switch target and apply fresh dot's quickly.
Execute phase. DS till you got 2 shards, then Haunt than SB:SS, then DS again and repeat. Doomguard is used either on BL or on execute. if your BL is not on execute phase than you use int pot and pop Doomguard on BL it will have more benefit.
And last thing KJC is great but bare in mind that you might get into trouble on fights like Windlord if by any chance you get 2 bombs in a row on you

Just my 2 cents

 

This error "ERROR: Could not add combat log event filter! - Performance may be horrible, and things may not work properly!

Occurs every time I start HB (521) with CLU (3.3.9)..

How do I get rid of this message? It's warning me that "the performance may be horrible".