[PureRotation] Warlock - The Ultimate Level 90 PvE/PvP Routine

thanks. whitch specc do you mean? Do you can add a spec, to choose my demon?

 

All specs, and a demon choice setting already exists.

 

hey millz will you be optimizing this for pvp eventually? (destro)

 

Suddenly it won't cast Rain of Fire unless in AoE rotation?
I was under the impression RoF gains embers and is thus useful in even single target rotation - or has this been patched?
EDIT: It does seem to do it occasionally. However I did Galleon just before and it did not cast a single RoF until I hit AoE rotation.

 

I will be, but I'm not much of a PvPer so need lots of feedback to improve it.

 

It only casts RoF in single target when you have plenty of mana. I put a mana check in as i found it kept going oom and pausing briefly. Haste increases your mana regen. Make sure the setting is enabled to RoF in single target too.

 

Saaweet BETER GET MY LOCK GEARED !

 

Awesome! I've yet to try this out yet because I'm leveling a new lock, I stopped WoW a few months ago when this was in development I think, so looking forward to giving this a try once I hit a high enough level to make use of it (Level 25 at the moment)

 

Hmm, how i can switch routine from PvE to pvp? My warlock just pounding PvE spells and ignores pvp talents.

 

It supports the majority of the PvP talents ? Think there's only shadowfury that it's missing.

 

It's very strange, because in the header post stated "pvp": "The Ultimate Level 90 PvE/PvP Routine". But it does not use proper PvP talents such as "Howl of Terror", "Archimonde's Vengeance" or "Blood Horror". I dont know why but character just stand and nothing do, while still being killed by other players.

 

I can't help but feel that this post is a bit condescending. The code for 2 of the 3 abilities you've listed is already supported.

Code:

Spell.Cast("Blood Fear", ret => !Me.HasAura("Blood Fear") && TalentManager.HasTalent(10))
..
Spell.Cast("Howl of Terror", ret => TalentManager.HasTalent(4) && Me.HealthPercent <= WarlockSettings.HowlofTerrorPercent && Unit.CachedNearbyAttackableUnits(Me.Location, 10).Count() >= WarlockSettings.HowlofTerrorUnitCount),

It doesn't support Archimonde's Vengeance, because the routine can't predict when there's going to be a high burst of incoming damage. If you've any suggestions as to how you believe would be best for it to act, then feel free to leave your suggestions here. I.e. X number of people are targeting us, my HP drops below X value...

*Edit*

Oh, and the same goes for Sacrificial Pact, Harvest Life and Shadowfury. Answers on a post card.

 

Hello, Millz. Found 2 errors in affli pve rotation. 1) your CR use Haunt always then i have soulshards. Needed use Haunt only then active Dark Soul or then i already have 3 (4 with talent) soulshards. I can explain: u use "weak" haunt for "weak" dots. if i can keep 3-4 soulshard for my dark soul - i got more dps. 1 soulshard for instant refresh dots for more powerful ticks and 2+ (with procs) for "powerful" haunt. By the way, in this tier we have all rppm trinkets. You have an option to refresh dots then i have trinket procs or haste. But u don't have shards for this refresh and u waste 3 gcd instead of 1.
2) then CR try to instant refresh dots CR cast 1-2 dots manually with active buff Soulburn and after this use soul swap on same target with 1-2 already refreshed dots. We need update only 1-2 dots manually, then we have all 3 "weak" dots on target and we got proc/burst - we always refresh dots with SB+SS. instead it's waste of gcd and dps. many dps

https://www.dropbox.com/s/1zc4szsvmipejzj/6116 2013-06-28 12.29.rar

if u need some more help with theory - i can help you. Thanks for your work, sry for bad english

 

Your version is a couple of revisions behind, update from SVN often

As for Haunt, it's using the optimal setup according to simulationcraft, i've added comments so that it should be easier to read, but this is what it looks like..



As for the manual dotting before Soul Swap, think I've found the problem with that. Pushed fix to SVN.

 

Owh, how do u get the dotted lines connecting the braces millz?

 

Just out of curiosity what is the reason that so many CR does not include movement and targetting as a option? I can't see what it would hurt to have it as a option. Is it because it is really hard to code or?

I am aware of that it ofcourse wouldn't work as good as a pro human playing it , but just as a option

 

updated to last rev, but your fix didn't work. huge log from lfr https://www.dropbox.com/s/9o5hcvt35zg7txi/3680 2013-06-28 14.08.rar

also.. tested your refreshment dot system.. not bad, but too slow. i think what you need download AffDots from Curse. This addon gave me 5 top 10 ranking in t14, 25ppl full hm. and all bosses in top 75 ranking. i could more but my guild so slow with progress

also execute phase. rotation is: ~20.5% SB+SS, Haunt, DS 2-3 ticks, Haunt, DS 2-4 ticks, Haunt SB+SS, DS ..... not need to SB+SS after each DS, but Haunt uptime need around 100% for this phase
thx sry for this, i just trying to do this CR better with my experince playing warlock

 

because movement option make CR work slowly. Always.

 

Because those CR's without movement and targetting are made for raiding in mind, where you most likely want to take care of movement and targetting yourself.
If you want movement for these kind of CR's you can allways try out the plugin "I Want Movement", if you search.

 

Visual Studio plugin, think it's called Indent Guide or something?

As Amputations says, it's all excess code when this is designed to perform max dps. If you want movement and targeting, then you can use the plugin I wrote which allows PureRotation (and other non-movement CCs) to add movement/targeting etc. http://www.thebuddyforum.com/honorb...ovement-use-lazyraider-crs-afk-bot-bases.html

Yep that's definately a fault for <20% HP. I'll take a look now and post again soon.

*Edit*

Fixed Haunt for <20%. Also changed haunt refresh point to use the actual cast time of haunt rather than a fixed < 1.5s. Should help keep the uptime.

The DoT refresh system is still a work in progress. It's easy in theory, but via code it's harder than you'd expect.