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

no, I was using demo - but im having a problem now that it targets between the two mobs, and dont cast anything, including health funnel. the log of that is in my other post, on this page.

 

I'm trying to recreate it on my lock atm to see what's going on.

 

if it helps, I was level 50 in ungruro creator - using the felguard - demo spec, if you think I might know somthing else to help you let me know.

 

This is what I'm getting if I try to start HB while in Utgaard Keep:

Code:

[4:39:37 PM:415] ReadLog: [skiWarlock] Starting skiWarlock v3.67
[4:39:37 PM:416] [skiWarlock] Starting skiWarlock v3.67
[4:39:37 PM:421] ReadLog: [skiWarlock] Loading Grind Settings Profile
[4:39:37 PM:422] [skiWarlock] Loading Grind Settings Profile
[4:39:37 PM:426] ReadLog: [skiWarlock] Initializing Settings Profile: Affliction
[4:39:37 PM:427] [skiWarlock] Initializing Settings Profile: Affliction
[4:39:38 PM:51] ReadLog: [skiWarlock] Initializing: Spec: Affliction
[4:39:38 PM:51] [skiWarlock] Initializing: Spec: Affliction
[4:39:38 PM:84] ReadLog: [skiWarlock] Initializing: Pet: Felhunter
[4:39:38 PM:85] [skiWarlock] Initializing: Pet: Felhunter
[4:39:38 PM:86] ReadLog: [skiWarlock] Initializing: Fight Adds: True, With AOE: False
[4:39:38 PM:87] [skiWarlock] Initializing: Fight Adds: True, With AOE: False
[4:39:38 PM:92] ReadLog: Object reference not set to an instance of an object.
[4:39:38 PM:92] Object reference not set to an instance of an object.

I normally keep it stopped during dungeon runs but I do use Mr. AutoFight to help with single boss battles/pulls, etc. The "object reference" error causes HB to immediately stop and sometimes even throw a crash error.

 

Problem:

Level: 18
MultiAdd = true
Maxadds = 2
minadds = 1

Default Settings except for no shadow bolt, I disabled it.

It just keeps targeting through both of them really quick not getting any spells off.

 

That's exactly the same thing that I'm noticing when I see it. Seems to do it with 2 adds and just cycles back and forth like that.

 

This is a internal HB problem when entering/exiting instances.

 

I've got a fix coming. I've been working on the Combat Adds.

 

ahhhhh sweet!

 

Right, but I normally shut down HB before I zone into the instance and then reload it once I'm in. So it's a fresh "run" once I'm inside.

Worked in the various vanilla and BC instances, only happens in this one dungeon so far (going to try and get into another one).

But, you're saying that's an HB error that has nothing to do with the .cc?

 

I recently started using eSafe for situations like this. Finally got a viable log to share. I've got eSafe set to log out of WoW after 5 minutes of being stuck. Looks like I finished a combat and it got stuck trying to apply a Spellstone to the weapon.

Code:

[6:35:44 PM:339] ReadLog: [skiWarlock] NeedRest: Need to apply Spellstone Enchant to weapon
[6:35:44 PM:355] [skiWarlock] NeedRest: Need to apply Spellstone Enchant to weapon
[6:35:44 PM:360] ReadLog: Activity: Resting
[6:35:44 PM:377] Activity: Resting
[6:35:44 PM:570] ReadLog: [skiWarlock] Rest: Applying Spellstone to weapon
[6:35:44 PM:589] [skiWarlock] Rest: Applying Spellstone to weapon
[6:35:45 PM:650] ReadLog: [skiWarlock] NeedRest: Need to apply Spellstone Enchant to weapon
[6:35:45 PM:671] [skiWarlock] NeedRest: Need to apply Spellstone Enchant to weapon
[6:35:45 PM:677] ReadLog: Activity: Resting
[6:35:45 PM:702] Activity: Resting
[6:35:45 PM:878] ReadLog: [skiWarlock] Rest: Applying Spellstone to weapon
[6:35:45 PM:890] [skiWarlock] Rest: Applying Spellstone to weapon
[6:35:46 PM:965] ReadLog: [skiWarlock] NeedRest: Need to apply Spellstone Enchant to weapon
[6:35:46 PM:991] [skiWarlock] NeedRest: Need to apply Spellstone Enchant to weapon
[6:35:47 PM:7] ReadLog: Activity: Resting
[6:35:47 PM:17] Activity: Resting
[6:39:23 PM:42] ReadLog: [skiWarlock] Rest: Applying Spellstone to weapon
[6:39:23 PM:68] [skiWarlock] Rest: Applying Spellstone to weapon
[6:39:24 PM:132] ReadLog: [skiWarlock] NeedRest: Need to apply Spellstone Enchant to weapon
[6:39:24 PM:143] [skiWarlock] NeedRest: Need to apply Spellstone Enchant to weapon
[6:39:24 PM:148] ReadLog: Activity: Resting
[6:39:24 PM:175] Activity: Resting
[6:39:24 PM:364] ReadLog: [skiWarlock] Rest: Applying Spellstone to weapon
[6:39:24 PM:378] [skiWarlock] Rest: Applying Spellstone to weapon
[6:39:25 PM:257] ReadLog: Exiting wow! Stuck for too long!
[6:39:25 PM:267] Exiting wow! Stuck for too long!
[6:39:31 PM:52] ReadLog: Wow exited, Honorbuddy stopped!
[6:39:31 PM:62] Wow exited, Honorbuddy stopped!

And that's when eSafe logged WoW out and halted HB.

EDIT: The log file is too long. But trust me, it is 5 minutes of the same thing. I just cut out most of the middle.

 

Correct.

I've been getting this error on my DK in SotA

 

Were you watching it do this? Was it trying to cast the Spellstone?

Can you please post the whole log as an attachment.

 

That cut and paste is straight from the log file. That's all there was.

If you want I can edit the log file and attach that as the log file is too large to upload without editing (as most of it is this error).

But no, I wasn't watching. So I don't know if it was trying to summon it.

 

What color is your weapon? HB bugs trying to enchant weapons that are white or grey.

 

It is a brand new Blue weapon (that's pretty damn awesome).

 

skiWarlock v3.68
Fixed: Combat Adds logic
When there are more than 2 mobs attacking, the caster will SoC if available. If unavailable or all mobs have SoC on them, it will fall back to dotting each mob.

Corruption, Curse of Agony and Immolate will be used. Order is determined by spec.

If any of these dots are disabled via the GUI, then they will not be used.

Rain of Fire support will not be added as SoC or dotting each mob is far safer and more effective.

Combat Adds is not used in PVP.

 

Thank you - will test this now - if it works like it should, I'll test all night - will post results and problems if any.

EDIT : works great man, excellent. No problems here.

 

Thats loads better thanks thedrunk

 

Testing it now. HB still states 3.67, so you may want to update the version #.