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

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

I respect your decision Millz, I know you and I have talked about it a lot and the community benefits either way you go with it. You will not stop making great contributions to Pure, or anything else you work on as you are here to help us all. Keep up the good work!
 
Nothing wrong with making a little cash to support your hobby.
 
An update on Demonic; I've decided to take the path I've been trying to avoid, and release Demonic as 2 seperate versions, i.e. a paid and free version. This isn't a decision I've taken lightly, given that I was one of the last few devs that wasn't profiting from plugins/routines. I have the utmost respect for the remaining devs who are keeping their work free, however due to a recent change in personal finances I've decided to turn to the dark side. I intend to release the free version in the coming weeks (months?) with reduced features, the paid version is in a full complete working state, and I'm now working through adding more features. That being said, if you're interested in the paid version, shoot me a PM.
Good choice millz, :)
 
j2r.png


Something like this I'm thinking....

Yes that would work :P
But, you dont want to hinder the speed of the CC.

The only spell you wouldn't want to cancel is Chaos Bolt though if you're at like 90% in to it. All the other spells dont matter.

PvP is all about speed.
 
It tries to use chaos bolt if 3 stacks of havoc, and shadowburn if 2 or less (i.e. if it messes up and casts too fast). Think I'll add an option to cancel cast and shadowburn if target <20% HP and have enough embers. Could be the make or break of some fights.

You can't have 3 stacks of Havoc?

You can only apply it to one target, cast your chaos bolt or shadow burn and boom.
 
Yes that would work :P
But, you dont want to hinder the speed of the CC.

The only spell you wouldn't want to cancel is Chaos Bolt though if you're at like 90% in to it. All the other spells dont matter.

PvP is all about speed.

It wouldn't have any noticable affect on speed. You wouldn't want to cancel any spell that only has 0.3s or something left on it, but anything longer than that and you're probably better off canceling to get the shadowburn in.

You can't have 3 stacks of Havoc?

You can only apply it to one target, cast your chaos bolt or shadow burn and boom.

Cast havoc on a target dummy then look at your own aura, it's 3 stacks. CB uses all 3 stacks, shadowburn or other spells only consume 1.
 
lvl 70 in bgs. using bgbuddy. when it gets to enemies it does not dismount, and if it does dismount it doesnt attack anyone.
i keep geting this error in log

[04:04:34.675 D] Cleared POI - Reason Exception in Root.Tick()
[04:04:34.675 D] Cleared POI
[04:04:34.752 D] Changed POI to:Type: Kill, Name: Stalksyou
[04:04:34.848 D] System.AccessViolationException: Could not read bytes from 000007E8 [299]!
at Styx.MemoryManagement.ExternalProcessReader.ReadBytes(IntPtr address, Int32 count, Boolean isRelative)
at Styx.MemoryManagement.ExternalProcessReader.Read[T](IntPtr address, Boolean isRelative)
at Styx.WoWInternals.WoWMovementInfo.()
at Styx.WoWInternals.WoWMovementInfo.get_Position()
at Styx.WoWInternals.WoWObjects.WoWUnit.get_RelativeLocation()
at Styx.WoWInternals.WoWObjects.WoWUnit.get_Location()
at Styx.WoWInternals.WoWObjects.WoWObject.get_DistanceSqr()
at o.a.j(Object A_0)
at k.l.f(Object A_0)
at Styx.TreeSharp.Decorator.CanRun(Object context)
at Styx.TreeSharp.Decorator..()
at Styx.TreeSharp.Composite.Tick(Object context)
at Styx.TreeSharp.PrioritySelector..()
at Styx.TreeSharp.Composite.Tick(Object context)
at Styx.TreeSharp.Decorator..()
at Styx.TreeSharp.Composite.Tick(Object context)
at Styx.TreeSharp.PrioritySelector..()
at Styx.TreeSharp.Composite.Tick(Object context)
at Styx.TreeSharp.Decorator..()
at Styx.TreeSharp.Composite.Tick(Object context)
at Styx.TreeSharp.PrioritySelector..()
at Styx.TreeSharp.Composite.Tick(Object context)
at Styx.TreeSharp.PrioritySelector..()
at Styx.TreeSharp.Composite.Tick(Object context)
at Styx.TreeSharp.PrioritySelector..()
at Styx.TreeSharp.Composite.Tick(Object context)
at Styx.TreeSharp.Decorator..()
at Styx.TreeSharp.Composite.Tick(Object context)
at Styx.TreeSharp.PrioritySelector..()
at Styx.TreeSharp.Composite.Tick(Object context)
at Styx.TreeSharp.Decorator..()
at Styx.TreeSharp.Composite.Tick(Object context)
at Styx.TreeSharp.PrioritySelector..()
at Styx.TreeSharp.Composite.Tick(Object context)
at Styx.TreeSharp.Decorator..()
at Styx.TreeSharp.Composite.Tick(Object context)
at Styx.TreeSharp.PrioritySelector..()
at Styx.TreeSharp.Composite.Tick(Object context)
at Styx.TreeSharp.PrioritySelector..()
at Styx.TreeSharp.Composite.Tick(Object context)
at Styx.TreeSharp.PrioritySelector..()
at Styx.TreeSharp.Composite.Tick(Object context)
at Styx.TreeSharp.Decorator..()
at Styx.TreeSharp.Composite.Tick(Object context)
at Styx.TreeSharp.PrioritySelector..()
at Styx.TreeSharp.Composite.Tick(Object context)
at Styx.CommonBot.TreeRoot.()
 
Thanks for all of the bug reports. Think I've fixed everything now. Update will be coming soon.
 
I've requested that this thread be archived due to my new routine, Demonic. I've enough threads to monitor and keep up to date, this one is not required.
 
Back
Top