[Warlock CC] skiWarlock 3.0 for HB2 - ALL TREES -

skiWarlock 3.66

 

Working well so far,

I have pet attack on... yet pulling with shadowbolt it still will not engage until it has casted.

 

hmmmmm

Ok, I switched to your newest verson and this is the problem im getting. It already had a health and soulstone in my inventory.

EDIT: Disabling the soul stone in the configuration fixed my problem, not sure what was going on.

EDIT 2: One more thing, is there a way (im sure there is I just missed it) for me to get it to mass pull then use rain of fire to AOE them down?

 

Applies CoA and Corr fine, really often double casts Immolate. Just seems not to wait a split second to check whether its up or not. Also neglects to Drain Life when it has adds. Maybe by design due to the pushback but it would keep the character alive better.

 

It's faster and safer to SoC them to death then trying to heal with Drain Life. Adjust your Healthstone and Deathcoil use if you are having health problems during a mass pull. Also, lower your Mass Pull Max Adds.

What level are you?

Those having problems need to provide more details.

 

In PvP it only uses Incinerate ... with the older releases it had more logic is this a bug or supposed to be?

 

For the record, I have no problems like the people above (except the double immolate, tends to happen more often on lower level mobs) but I think it's probably more of a HB issue than the CC because your code looks right.
I did notice odd behavior with the spell stone, but never to the point where it breaks, so I never worried about it. It's rocking with saving Metamorph for adds, I've increased this number to 4 now, it's awesome

 

Need more details. Need a log as well as your Settings Profile.

 

Is there a PVP function that will also cause an enemy to be a priority on the targets list?

I noticed walking into Un'Goro craters neutral town i kept dismounting and trying to attack the other faction..... Is there a way to only PVE?

Also my pet still will not attack until i have finished casting shadowbolt...

 

skiWarlock v3.67
Fixed: Item cooldown LUA check - Soulstone problem
Fixed: Pet pull before shadow bolt pull - yell at hiddenlol if you die while having your Imp out
Fixed: Double Immolate - hopefully
Re-added: Global cooldown check to WaitWhileCasting(). This was previously removed due to a broken HB implementation.

 

All i can say is my pet now holds agro without me taking damage.

The way it should be (add to gui if its an issue for others)

 

When it mass pulls and aoe's, does it simply dot them all and just target back and forth between them and wait for them to die? is there any way to make it use rain of fire? is there something im missing?

 

Here to report a bug - it looks like at the bottom of the log, from what I watched, the warlock just switched targets and didn't dot them, or anything, also didn't use health funnel to heal the felguard.

the problem starts about...

[8:35:03 AM:927]

 

Yay I'm back. Looks like thedrunk held down the fort while I was gone, I'll update the first post with 3.67.

 

Welcome backkk! enjoy yourself?

 

I'm assuming that you're a dotlock from what you're saying... Until you hit 70 and get Seed of Corruption there's no real good way for it to use Rain of Fire well due to aggro issues cutting it's ticks down that it just isn't worth the mana/time to use it versus dotting everything.

 

On latest release add dotting isnt working for me. Very rarely double immolates tho!

 

Is it doing anything to the adds at all?

 

Is there an option to use fear only on a second mob appearing? And what about the abilities of the voidwalker? Are they used / how to configure the CC that he uses them?

 

It is acting like a few sub versions ago. If you're a dotlock that's pre-70 it just cycles back and forth between the adds targeting each one over and over again once every second or so. But not casting.

Only when things trigger like the health of your pet going lower or the number of adds drops (due to your pet having killed one) does it seem to drop out of this behavior.

It really seems to like doing it when you have exactly 2 targets that you're dealing with.