Ahh man 12 percent that is crazy!!!!
It sucks, but I can understand their reasoning. I was seeing consistently 3rd dps on my lock in Beta, by a good margin. Just barely below mages and rogues, but above all pallies/shaman/wars/dk's/(whatever else I can't think of).
12% to warlocks alone though? What about mages, shaman, hunters, DKs, and the rest that still top the dps meters in the 5-digit range of dps? I remember when hunters got a dps nerf way back, and now they're back again topping the meters. Beast Mastery got a dps buff in one of the last couple of patches. I don't have a lock yet, but there are a few in my guild that are extremely pissed about the damage cut across the board. They liked topping charts at #1. Our top guild lock was hitting 16-17k DPS, and our top DK (owned by the same person) also hits 15k with frost DW. I just think it's a bit harsh to hit the locks like that. If Blizz is about normalizing the classes, then thoroughly test each class, see where they're overe powered, and normalize them all, THEN test again before release to ensure everything's working right. Y'know?
Its for Cat, not for Wrath. In Cat, I was pulling 25-26k dps, with mages and rogues around 26-27k. All the other dps were in the 22-23k range in similar gear/skill. I'm sure mages will get a nerf soon too, rogues will probably stay up there.
Working with latest build?
[23:29:06:17] Cleared POI
[23:29:06:187] Activity: Combat
[23:29:14:352] Spell_C::CastSpell(1120, 0, 0x60000000348E83C, 0)
[23:29:14:834] Activity: Combat
[23:29:16:31] System.NullReferenceException: Object reference not set to an instance of an object.
at Styx.Bot.CustomClasses.skiWarlock.PetAttack(String logPrefix, WoWUnit mob, Boolean WaitForTargetMatch) in g:\Bots\Honorbuddy\CustomClasses\skiWarlock\skiWarlock.cs:line 2917
at Styx.Bot.CustomClasses.skiWarlock.Combat() in g:\Bots\Honorbuddy\CustomClasses\skiWarlock\skiWarlock.cs:line 922
at Bots.Grind.LevelBot.cj(Object A_0)
at TreeSharp.Action.RunAction(Object context)
at TreeSharp.Action.a.a()
at TreeSharp.Composite.Tick(Object context)
at TreeSharp.Sequence.a.b()
at TreeSharp.Composite.Tick(Object context)
at TreeSharp.PrioritySelector.a.b()
at TreeSharp.Composite.Tick(Object context)
at TreeSharp.PrioritySelector.a.b()
at TreeSharp.Composite.Tick(Object context)
at TreeSharp.Decorator.a.a()
at TreeSharp.Composite.Tick(Object context)
at TreeSharp.PrioritySelector.a.b()
at TreeSharp.Composite.Tick(Object context)
at TreeSharp.PrioritySelector.a.b()
at TreeSharp.Composite.Tick(Object context)
at TreeSharp.PrioritySelector.a.b()
at TreeSharp.Composite.Tick(Object context)
at TreeSharp.Decorator.a.a()
at TreeSharp.Composite.Tick(Object context)
at TreeSharp.PrioritySelector.a.b()
at TreeSharp.Composite.Tick(Object context)
at TreeSharp.PrioritySelector.a.b()
at TreeSharp.Composite.Tick(Object context)
at Styx.Logic.BehaviorTree.TreeRoot.b()
It sucks, but I can understand their reasoning. I was seeing consistently 3rd dps on my lock in Beta, by a good margin. Just barely below mages and rogues, but above all pallies/shaman/wars/dk's/(whatever else I can't think of).
The nurf does only affect level 1-79 - you will do the same damage in cata release![]()
So it is certainly something between Mr. AutoFight and this CC (as well as the one bot they have that's just for testing against the Dummies) where it will get stuck in a loop trying to summon a pet. CodenameG swears it isn't anything with Mr. AutoFight so you may want to fire him off a PM and see if you two can brainstorm it out as it would be *really* good if these two could learn to play well together again.
I'll dl it and look at code for both to see if I can see what's up. It'll be at least a few days though, lots of work going on with my house, lots of regular work, and cataclysm powerleveling![]()
How do i set my config to pull max 2 mobs at a time?
But still go as mass pul.. i Want to pull more than one, but 3 might be to many
Set Mass Pull Max Adds and Min Adds to 2 in the config. Of course set Mass Pull to true.
If you want to AE them set Min Adds to AoE and Mind Adds to SoC/RoF to 1 (there's a bug in this version where you have to set it to 1 less then the value you want it to start doing AoE stuff).
Ty for the help, but im still only pulling 1 at the time :S