ShamWOW for HB2 - An Enhance/Elemental/Resto + PVP/RaF Healbot by Bobby53

[mrgalabama]

Shamanistic Rage will cast if your char is in a stressful fight and the target has 85% or more health left. Idea here is to cast early in the fight or not at all. It's possible if you are that geared you may be taking them below 85% too quickly for it to cast.

On the config items, I was going to add a few options. Let me know what you think of these:

Treat target #### levels higher as elite (default is 3)
Treat fight with #### mobs as stressful (default is 2)

That would allow you to indicate not to break out the Spirit Wolves unless the target is at least ##### higher so you could set to as many levels higher as you want. The last one would allow you to control the size of the group that represents a stressful situation.

that would be great. i think both would be excellent if you could do the code for both. after you add all those option and codes your CC is going to be the new platform for all new CCs.

A.) i also played with the emergency heal like you said. you said it would trigger the pots but its not. i set it to 85% just to see if it would drink a potion. all it did was cast lifebloom (thank you for adding this, herbalism heal), and cast healing wave but no healing potion was taking. do i need to add a list of the potion items somewhere??

B.) i notice this earlier but didn't say anything till i was sure. its casting magma totem on i guess mobs it consider to be elite instead of what i want it 2 cast. this is causing me to pull more mobs. which isn't a problem for my gear enhan shaman but for other this might cause a very quick death. magma totems is good but if am fighing for mana this its a mana hog totem. meaning if i using mana to stay alive for a single mob fight that is consider to b elite (3 or more lvls higher) this isn't a totem i want down. it cost more than a healing wave. but for a grp of mobs this would be great to use. considering you might die anyways so go out with a fire impression on the mobs, lmao

 

[laria]

I tried to use 4.04 with the new questing beta, but when i hit start, i only get

Spell book built
Could not compile CC from C:\Users\Sam\Downloads\hb2_BETA\CustomClasses\Shaman.cs!
File: Shaman.cs Line: 27 Error: Der Typ- oder Namespacename "Properties" konnte nicht gefunden werden. (Fehlt eine Using-Direktive oder ein Assemblyverweis?)
File: Shaman.cs Line: 135 Error: Der Typ- oder Namespacename "UI" konnte nicht gefunden werden. (Fehlt eine Using-Direktive oder ein Assemblyverweis?)

Could not compile CC from C:\Users\Sam\Downloads\hb2_BETA\CustomClasses\UI!
File: ConfigForm.cs Line: 21 Error: Der Zugriff auf "ShamWOW.Properties.Settings" ist aufgrund der Sicherheitsebene nicht m?glich.
File: ConfigForm.cs Line: 21 Error: "ShamWOW.Properties.Settings" enth?lt keine Definition f?r "Default".
File: ConfigForm.cs Line: 22 Error: Der Zugriff auf "ShamWOW.Properties.Settings" ist aufgrund der Sicherheitsebene nicht m?glich.
File: ConfigForm.cs Line: 22 Error: "ShamWOW.Properties.Settings" enth?lt keine Definition f?r "Default".
File: ConfigForm.cs Line: 23 Error: Der Zugriff auf "ShamWOW.Properties.Settings" ist aufgrund der Sicherheitsebene nicht m?glich.
File: ConfigForm.cs Line: 23 Error: "ShamWOW.Properties.Settings" enth?lt keine Definition f?r "Default".
File: ConfigForm.cs Line: 24 Error: Der Zugriff auf "ShamWOW.Properties.Settings" ist aufgrund der Sicherheitsebene nicht m?glich.
File: ConfigForm.cs Line: 24 Error: "ShamWOW.Properties.Settings" enth?lt keine Definition f?r "Default".
File: ConfigForm.cs Line: 25 Error: Der Zugriff auf "ShamWOW.Properties.Settings" ist aufgrund der Sicherheitsebene nicht m?glich.
File: ConfigForm.cs Line: 25 Error: "ShamWOW.Properties.Settings" enth?lt keine Definition f?r "Default".
File: ConfigForm.cs Line: 27 Error: Der Zugriff auf "ShamWOW.Properties.Settings" ist aufgrund der Sicherheitsebene nicht m?glich.
File: ConfigForm.cs Line: 27 Error: "ShamWOW.Properties.Settings" enth?lt keine Definition f?r "Default".
File: ConfigForm.cs Line: 43 Error: Der Zugriff auf "ShamWOW.Properties.Settings" ist aufgrund der Sicherheitsebene nicht m?glich.
File: ConfigForm.cs Line: 43 Error: "ShamWOW.Properties.Settings" enth?lt keine Definition f?r "Default".
File: ConfigForm.cs Line: 44 Error: Der Zugriff auf "ShamWOW.Properties.Settings" ist aufgrund der Sicherheitsebene nicht m?glich.
File: ConfigForm.cs Line: 44 Error: "ShamWOW.Properties.Settings" enth?lt keine Definition f?r "Default".
File: ConfigForm.cs Line: 45 Error: Der Zugriff auf "ShamWOW.Properties.Settings" ist aufgrund der Sicherheitsebene nicht m?glich.
File: ConfigForm.cs Line: 45 Error: "ShamWOW.Properties.Settings" enth?lt keine Definition f?r "Default".
File: ConfigForm.cs Line: 46 Error: Der Zugriff auf "ShamWOW.Properties.Settings" ist aufgrund der Sicherheitsebene nicht m?glich.
File: ConfigForm.cs Line: 46 Error: "ShamWOW.Properties.Settings" enth?lt keine Definition f?r "Default".
File: ConfigForm.cs Line: 48 Error: Der Zugriff auf "ShamWOW.Properties.Settings" ist aufgrund der Sicherheitsebene nicht m?glich.
File: ConfigForm.cs Line: 48 Error: "ShamWOW.Properties.Settings" enth?lt keine Definition f?r "Default".
File: ConfigForm.cs Line: 69 Error: Der Zugriff auf "ShamWOW.Properties.Settings" ist aufgrund der Sicherheitsebene nicht m?glich.
File: ConfigForm.cs Line: 69 Error: "ShamWOW.Properties.Settings" enth?lt keine Definition f?r "Default".
File: ConfigForm.cs Line: 74 Error: Der Zugriff auf "ShamWOW.Properties.Settings" ist aufgrund der Sicherheitsebene nicht m?glich.
File: ConfigForm.cs Line: 74 Error: "ShamWOW.Properties.Settings" enth?lt keine Definition f?r "Default".
File: ConfigForm.cs Line: 79 Error: Der Zugriff auf "ShamWOW.Properties.Settings" ist aufgrund der Sicherheitsebene nicht m?glich.
File: ConfigForm.cs Line: 79 Error: "ShamWOW.Properties.Settings" enth?lt keine Definition f?r "Default".
File: ConfigForm.cs Line: 84 Error: Der Zugriff auf "ShamWOW.Properties.Settings" ist aufgrund der Sicherheitsebene nicht m?glich.
File: ConfigForm.cs Line: 84 Error: "ShamWOW.Properties.Settings" enth?lt keine Definition f?r "Default".
File: ConfigForm.cs Line: 89 Error: Der Zugriff auf "ShamWOW.Properties.Settings" ist aufgrund der Sicherheitsebene nicht m?glich.
File: ConfigForm.cs Line: 89 Error: "ShamWOW.Properties.Settings" enth?lt keine Definition f?r "Default".
File: ConfigForm.cs Line: 107 Error: Der Zugriff auf "ShamWOW.Properties.Settings" ist aufgrund der Sicherheitsebene nicht m?glich.
File: ConfigForm.cs Line: 107 Error: "ShamWOW.Properties.Settings" enth?lt keine Definition f?r "Default".
File: ConfigForm.cs Line: 112 Error: Der Zugriff auf "ShamWOW.Properties.Settings" ist aufgrund der Sicherheitsebene nicht m?glich.
File: ConfigForm.cs Line: 112 Error: "ShamWOW.Properties.Settings" enth?lt keine Definition f?r "Default".
File: ConfigForm.cs Line: 117 Error: Der Zugriff auf "ShamWOW.Properties.Settings" ist aufgrund der Sicherheitsebene nicht m?glich.
File: ConfigForm.cs Line: 117 Error: "ShamWOW.Properties.Settings" enth?lt keine Definition f?r "Default".
File: ConfigForm.cs Line: 122 Error: Der Zugriff auf "ShamWOW.Properties.Settings" ist aufgrund der Sicherheitsebene nicht m?glich.
File: ConfigForm.cs Line: 122 Error: "ShamWOW.Properties.Settings" enth?lt keine Definition f?r "Default".
File: ConfigForm.cs Line: 127 Error: Der Zugriff auf "ShamWOW.Properties.Settings" ist aufgrund der Sicherheitsebene nicht m?glich.
File: ConfigForm.cs Line: 127 Error: "ShamWOW.Properties.Settings" enth?lt keine Definition f?r "Default".
File: ConfigForm.cs Line: 132 Error: Der Zugriff auf "ShamWOW.Properties.Settings" ist aufgrund der Sicherheitsebene nicht m?glich.
File: ConfigForm.cs Line: 132 Error: "ShamWOW.Properties.Settings" enth?lt keine Definition f?r "Default".
File: ConfigForm.cs Line: 137 Error: Der Zugriff auf "ShamWOW.Properties.Settings" ist aufgrund der Sicherheitsebene nicht m?glich.
File: ConfigForm.cs Line: 137 Error: "ShamWOW.Properties.Settings" enth?lt keine Definition f?r "Default".
File: ConfigForm.cs Line: 142 Error: Der Zugriff auf "ShamWOW.Properties.Settings" ist aufgrund der Sicherheitsebene nicht m?glich.
File: ConfigForm.cs Line: 142 Error: "ShamWOW.Properties.Settings" enth?lt keine Definition f?r "Default".
File: ConfigForm.cs Line: 147 Error: Der Zugriff auf "ShamWOW.Properties.Settings" ist aufgrund der Sicherheitsebene nicht m?glich.
File: ConfigForm.cs Line: 147 Error: "ShamWOW.Properties.Settings" enth?lt keine Definition f?r "Default".
File: ConfigForm.cs Line: 152 Error: Der Zugriff auf "ShamWOW.Properties.Settings" ist aufgrund der Sicherheitsebene nicht m?glich.
File: ConfigForm.cs Line: 152 Error: "ShamWOW.Properties.Settings" enth?lt keine Definition f?r "Default".
File: ConfigForm.cs Line: 157 Error: Der Zugriff auf "ShamWOW.Properties.Settings" ist aufgrund der Sicherheitsebene nicht m?glich.
File: ConfigForm.cs Line: 157 Error: "ShamWOW.Properties.Settings" enth?lt keine Definition f?r "Default".
File: ConfigForm.Designer.cs Line: 180 Error: Der Zugriff auf "ShamWOW.Properties.Settings" ist aufgrund der Sicherheitsebene nicht m?glich.
File: ConfigForm.Designer.cs Line: 180 Error: "ShamWOW.Properties.Settings" enth?lt keine Definition f?r "Default".
File: ConfigForm.Designer.cs Line: 181 Error: Der Zugriff auf "ShamWOW.Properties.Settings" ist aufgrund der Sicherheitsebene nicht m?glich.
File: ConfigForm.Designer.cs Line: 181 Error: "ShamWOW.Properties.Settings" enth?lt keine Definition f?r "Default".
File: ConfigForm.Designer.cs Line: 201 Error: Der Zugriff auf "ShamWOW.Properties.Settings" ist aufgrund der Sicherheitsebene nicht m?glich.
File: ConfigForm.Designer.cs Line: 201 Error: "ShamWOW.Properties.Settings" enth?lt keine Definition f?r "Default".
File: ConfigForm.Designer.cs Line: 207 Error: Der Zugriff auf "ShamWOW.Properties.Settings" ist aufgrund der Sicherheitsebene nicht m?glich.
File: ConfigForm.Designer.cs Line: 207 Error: "ShamWOW.Properties.Settings" enth?lt keine Definition f?r "Default".
File: ConfigForm.Designer.cs Line: 253 Error: Der Zugriff auf "ShamWOW.Properties.Settings" ist aufgrund der Sicherheitsebene nicht m?glich.
File: ConfigForm.Designer.cs Line: 253 Error: "ShamWOW.Properties.Settings" enth?lt keine Definition f?r "Default".
File: ConfigForm.Designer.cs Line: 259 Error: Der Zugriff auf "ShamWOW.Properties.Settings" ist aufgrund der Sicherheitsebene nicht m?glich.
File: ConfigForm.Designer.cs Line: 259 Error: "ShamWOW.Properties.Settings" enth?lt keine Definition f?r "Default".
File: ConfigForm.Designer.cs Line: 263 Error: Der Zugriff auf "ShamWOW.Properties.Settings" ist aufgrund der Sicherheitsebene nicht m?glich.
File: ConfigForm.Designer.cs Line: 263 Error: "ShamWOW.Properties.Settings" enth?lt keine Definition f?r "Default".
File: ConfigForm.Designer.cs Line: 269 Error: Der Zugriff auf "ShamWOW.Properties.Settings" ist aufgrund der Sicherheitsebene nicht m?glich.
File: ConfigForm.Designer.cs Line: 269 Error: "ShamWOW.Properties.Settings" enth?lt keine Definition f?r "Default".
File: ConfigForm.Designer.cs Line: 273 Error: Der Zugriff auf "ShamWOW.Properties.Settings" ist aufgrund der Sicherheitsebene nicht m?glich.
File: ConfigForm.Designer.cs Line: 273 Error: "ShamWOW.Properties.Settings" enth?lt keine Definition f?r "Default".
File: ConfigForm.Designer.cs Line: 279 Error: Der Zugriff auf "ShamWOW.Properties.Settings" ist aufgrund der Sicherheitsebene nicht m?glich.
File: ConfigForm.Designer.cs Line: 279 Error: "ShamWOW.Properties.Settings" enth?lt keine Definition f?r "Default".
File: ConfigForm.Designer.cs Line: 294 Error: Der Zugriff auf "ShamWOW.Properties.Settings" ist aufgrund der Sicherheitsebene nicht m?glich.
File: ConfigForm.Designer.cs Line: 294 Error: "ShamWOW.Properties.Settings" enth?lt keine Definition f?r "Default".
File: ConfigForm.Designer.cs Line: 295 Error: Der Zugriff auf "ShamWOW.Properties.Settings" ist aufgrund der Sicherheitsebene nicht m?glich.
File: ConfigForm.Designer.cs Line: 295 Error: "ShamWOW.Properties.Settings" enth?lt keine Definition f?r "Default".
File: ConfigForm.Designer.cs Line: 319 Error: Der Zugriff auf "ShamWOW.Properties.Settings" ist aufgrund der Sicherheitsebene nicht m?glich.
File: ConfigForm.Designer.cs Line: 319 Error: "ShamWOW.Properties.Settings" enth?lt keine Definition f?r "Default".
File: ConfigForm.Designer.cs Line: 320 Error: Der Zugriff auf "ShamWOW.Properties.Settings" ist aufgrund der Sicherheitsebene nicht m?glich.
File: ConfigForm.Designer.cs Line: 320 Error: "ShamWOW.Properties.Settings" enth?lt keine Definition f?r "Default".
File: ConfigForm.Designer.cs Line: 345 Error: Der Zugriff auf "ShamWOW.Properties.Settings" ist aufgrund der Sicherheitsebene nicht m?glich.
File: ConfigForm.Designer.cs Line: 345 Error: "ShamWOW.Properties.Settings" enth?lt keine Definition f?r "Default".
File: ConfigForm.Designer.cs Line: 351 Error: Der Zugriff auf "ShamWOW.Properties.Settings" ist aufgrund der Sicherheitsebene nicht m?glich.
File: ConfigForm.Designer.cs Line: 351 Error: "ShamWOW.Properties.Settings" enth?lt keine Definition f?r "Default".
File: ConfigForm.Designer.cs Line: 368 Error: Der Zugriff auf "ShamWOW.Properties.Settings" ist aufgrund der Sicherheitsebene nicht m?glich.
File: ConfigForm.Designer.cs Line: 368 Error: "ShamWOW.Properties.Settings" enth?lt keine Definition f?r "Default".
File: ConfigForm.Designer.cs Line: 374 Error: Der Zugriff auf "ShamWOW.Properties.Settings" ist aufgrund der Sicherheitsebene nicht m?glich.
File: ConfigForm.Designer.cs Line: 374 Error: "ShamWOW.Properties.Settings" enth?lt keine Definition f?r "Default".
File: ConfigForm.Designer.cs Line: 378 Error: Der Zugriff auf "ShamWOW.Properties.Settings" ist aufgrund der Sicherheitsebene nicht m?glich.
File: ConfigForm.Designer.cs Line: 378 Error: "ShamWOW.Properties.Settings" enth?lt keine Definition f?r "Default".
File: ConfigForm.Designer.cs Line: 384 Error: Der Zugriff auf "ShamWOW.Properties.Settings" ist aufgrund der Sicherheitsebene nicht m?glich.
File: ConfigForm.Designer.cs Line: 384 Error: "ShamWOW.Properties.Settings" enth?lt keine Definition f?r "Default".
File: ConfigForm.Designer.cs Line: 446 Error: Der Zugriff auf "ShamWOW.Properties.Settings" ist aufgrund der Sicherheitsebene nicht m?glich.
File: ConfigForm.Designer.cs Line: 446 Error: "ShamWOW.Properties.Settings" enth?lt keine Definition f?r "Default".
File: ConfigForm.Designer.cs Line: 452 Error: Der Zugriff auf "ShamWOW.Properties.Settings" ist aufgrund der Sicherheitsebene nicht m?glich.
File: ConfigForm.Designer.cs Line: 452 Error: "ShamWOW.Properties.Settings" enth?lt keine Definition f?r "Default".
File: ConfigForm.Designer.cs Line: 456 Error: Der Zugriff auf "ShamWOW.Properties.Settings" ist aufgrund der Sicherheitsebene nicht m?glich.
File: ConfigForm.Designer.cs Line: 456 Error: "ShamWOW.Properties.Settings" enth?lt keine Definition f?r "Default".
File: ConfigForm.Designer.cs Line: 462 Error: Der Zugriff auf "ShamWOW.Properties.Settings" ist aufgrund der Sicherheitsebene nicht m?glich.
File: ConfigForm.Designer.cs Line: 462 Error: "ShamWOW.Properties.Settings" enth?lt keine Definition f?r "Default".
File: ConfigForm.Designer.cs Line: 638 Error: Der Zugriff auf "ShamWOW.Properties.Settings" ist aufgrund der Sicherheitsebene nicht m?glich.
File: ConfigForm.Designer.cs Line: 638 Error: "ShamWOW.Properties.Settings" enth?lt keine Definition f?r "Default".
File: ConfigForm.Designer.cs Line: 644 Error: Der Zugriff auf "ShamWOW.Properties.Settings" ist aufgrund der Sicherheitsebene nicht m?glich.
File: ConfigForm.Designer.cs Line: 644 Error: "ShamWOW.Properties.Settings" enth?lt keine Definition f?r "Default".
File: ConfigForm.Designer.cs Line: 697 Error: Der Zugriff auf "ShamWOW.Properties.Settings" ist aufgrund der Sicherheitsebene nicht m?glich.
File: ConfigForm.Designer.cs Line: 697 Error: "ShamWOW.Properties.Settings" enth?lt keine Definition f?r "Default".
File: ConfigForm.Designer.cs Line: 698 Error: Der Zugriff auf "ShamWOW.Properties.Settings" ist aufgrund der Sicherheitsebene nicht m?glich.
File: ConfigForm.Designer.cs Line: 698 Error: "ShamWOW.Properties.Settings" enth?lt keine Definition f?r "Default".
File: ConfigForm.Designer.cs Line: 859 Error: Der Zugriff auf "ShamWOW.Properties.Settings" ist aufgrund der Sicherheitsebene nicht m?glich.
File: ConfigForm.Designer.cs Line: 859 Error: "ShamWOW.Properties.Settings" enth?lt keine Definition f?r "Default".
File: ConfigForm.Designer.cs Line: 860 Error: Der Zugriff auf "ShamWOW.Properties.Settings" ist aufgrund der Sicherheitsebene nicht m?glich.
File: ConfigForm.Designer.cs Line: 860 Error: "ShamWOW.Properties.Settings" enth?lt keine Definition f?r "Default".

Can't start - No combat class is loaded!

When i get back to the nonquesting version i often see
missing reagents needed to cast spell: Strength of Earth Totem
im doing a classquest currently which will get me new stuff.

 

[blacklisted]

i get the same error as laria when i use it with questing beta 3

 

[cawpet]

Using currently and all works fine and well, has gotten me to 20 so far . Ty!

 

[anders!]

works like a charm for me so far, thank you

 

[dottzor]

Using a lvl80 resto shaman.
Still attacking and using Flametongue on MH.
Anything I missed?

Edit: When using "auto" as setting.

 

[bobby53]

A.) i also played with the emergency heal like you said. you said it would trigger the pots but its not. i set it to 85% just to see if it would drink a potion. all it did was cast lifebloom (thank you for adding this, herbalism heal), and cast healing wave but no healing potion was taking. do i need to add a list of the potion items somewhere??

No user change is needed. I'll look into this further and get back to you.

B.) i notice this earlier but didn't say anything till i was sure. its casting magma totem on i guess mobs it consider to be elite instead of what i want it 2 cast. this is causing me to pull more mobs. which isn't a problem for my gear enhan shaman but for other this might cause a very quick death. magma totems is good but if am fighing for mana this its a mana hog totem. meaning if i using mana to stay alive for a single mob fight that is consider to b elite (3 or more lvls higher) this isn't a totem i want down. it cost more than a healing wave. but for a grp of mobs this would be great to use. considering you might die anyways so go out with a fire impression on the mobs, lmao

Agreed. It is dropping magma if fighting > 1 melee or a char 3+ levels or more higher. It should only be for 2 or more melee however so I'll fix that.

 

[bobby53]

Using a lvl80 resto shaman.
Still attacking and using Flametongue on MH.
Anything I missed?

Edit: When using "auto" as setting.

It will attack if nobody needs heals. However, a resto with the Auto setting should get Earthliving applied. Please attach a log so I can look into this one further for you.

 

[LiquidAtoR]

Not at the moment. I have only seen this occur with the Stags in Ashenvale. Watching the WoW screen while this happens shows the mob is Visually in front being faced, but the red message displayed repeatedly is its not. I'll have this resolved in the next version. What mobs did you see this occur with?

I've seen this happen on occasion with the rhino's in Sholazar as well. Fortunate I watch when I grind (and a movie on the other screen).
Moving it "past" the mob manually seems to "reset" the non visual facing error, and he continues as intended.

Also there's the occasional "There is no Initialize() in this cc." message (which doesn't seem to clip the cc's behaviour).
If you want logs from that let me know.

 

[bobby53]

I've seen this happen on occasion with the rhino's in Sholazar as well. Fortunate I watch when I grind (and a movie on the other screen).
Moving it "past" the mob manually seems to "reset" the non visual facing error, and he continues as intended.

Also there's the occasional "There is no Initialize() in this cc." message (which doesn't seem to clip the cc's behaviour).
If you want logs from that let me know.

Thanks for the post Liquid and no logs needed for these. It appears to self-resolve if any movement causing a position change occurs, so I am likely going to just have him jump or slight strafe and then reface if the last red error seen is about facing.

"There is no Initialize() in this CC" is a benign message. It doesn't affect it but I'll make it go away for the next release.

 

[bobby53]

I tried to use 4.04 with the new questing beta, but when i hit start, i only get

Spell book built
Could not compile CC from C:\Users\Sam\Downloads\hb2_BETA\CustomClasses\Shaman.cs!
File: Shaman.cs Line: 27 Error: Der Typ- oder Namespacename "Properties" konnte nicht gefunden werden. (Fehlt eine Using-Direktive oder ein Assemblyverweis?)
File: Shaman.cs Line: 135 Error: Der Typ- oder Namespacename "UI" konnte nicht gefunden werden. (Fehlt eine Using-Direktive oder ein Assemblyverweis?)

Could not compile CC from C:\Users\Sam\Downloads\hb2_BETA\CustomClasses\UI!
File: ConfigForm.cs Line: 21 Error: Der Zugriff auf "ShamWOW.Properties.Settings" ist aufgrund der Sicherheitsebene nicht m?glich.
File: ConfigForm.cs Line: 21 Error: "ShamWOW.Properties.Settings" enth?lt keine Definition f?r "Default".
...
Can't start - No combat class is loaded!

Laria,

Just need to confirm my understanding. You are saying you receive the above errors only when using HonorBuddy 1.9.3.1 and not when using HonorBuddy 1.9.2.3 ?

Thanks, Bobby53

 

[laria]

if i use the beta 3 with questing it breaks with the error mentioned above, if i use the nonquesting release it kills all mobs fine.

 

[Hagoroth]

Doesn't seem to work with the latest stable version 1.9.2.3.

My guy lightning bolt pulls then lets the monster kill him without swinging or using any abilities(level 7 shammy)


View attachment 6-1-2010 Log.txt

 

[Joker76]

Doesn't seem to work with the latest stable version 1.9.2.3.

My guy lightning bolt pulls then lets the monster kill him without swinging or using any abilities(level 7 shammy)


View attachment 4870

I'm still having a similar issue at lvl 77 with 1.9.2.3, where he will pull and then wait 4-6 seconds before entering melee combat. I posted a couple logs already with debugging information. If you want, I can try to take a video as well...

Initially, I thought changing to Survival mode fixed it but he is now doing it randomly in Survival mode as well. Noticed in the Debug log that it was spamming this during the pauses;

[9:47:01 PM:375] % Range pull Target is standing still or moving away
[9:47:01 PM:392] % At2 9879ms dist from Mangal Crocolisk: 5.01 valtrg: True tagged: True tagbme: True tgt-me: True
[9:47:01 PM:515] % Range pull Target is standing still or moving away
[9:47:01 PM:534] % At2 10020ms dist from Mangal Crocolisk: 5.01 valtrg: True tagged: True tagbme: True tgt-me: True
[9:47:01 PM:653] % Range pull Target is standing still or moving away
[9:47:01 PM:675] % At2 10161ms dist from Mangal Crocolisk: 5.01 valtrg: True tagged: True tagbme: True tgt-me: True
[9:47:01 PM:799] % Range pull Target is standing still or moving away
[9:47:01 PM:817] % At2 10304ms dist from Mangal Crocolisk: 5.01 valtrg: True tagged: True tagbme: True tgt-me: True
[9:47:01 PM:936] % Range pull Target is standing still or moving away
[9:47:01 PM:950] % At2 10437ms dist from Mangal Crocolisk: 5.01 valtrg: True tagged: True tagbme: True tgt-me: True
[9:47:02 PM:68] % Range pull Target is standing still or moving away
[9:47:02 PM:85] % At2 10572ms dist from Mangal Crocolisk: 5.01 valtrg: True tagged: True tagbme: True tgt-me: True
[9:47:02 PM:202] % Range pull Target is standing still or moving away
[9:47:02 PM:217] % At2 10703ms dist from Mangal Crocolisk: 5.01 valtrg: True tagged: True tagbme: True tgt-me: True
[9:47:02 PM:332] % Range pull Target is standing still or moving away
[9:47:02 PM:352] % At2 10839ms dist from Mangal Crocolisk: 5.01 valtrg: True tagged: True tagbme: True tgt-me: True
[9:47:02 PM:473] % Range pull Target is standing still or moving away
[9:47:02 PM:488] % At2 10975ms dist from Mangal Crocolisk: 5.01 valtrg: True tagged: True tagbme: True tgt-me: True
[9:47:02 PM:611] % Range pull Target is standing still or moving away
[9:47:02 PM:629] % At2 11116ms dist from Mangal Crocolisk: 5.01 valtrg: True tagged: True tagbme: True tgt-me: True
[9:47:02 PM:754] % Range pull Target is standing still or moving away
[9:47:02 PM:773] % At2 11259ms dist from Mangal Crocolisk: 5.01 valtrg: True tagged: True tagbme: True tgt-me: True

Then after a few seconds, it goes to this;

[9:47:06 PM:585] % At2 15071ms dist from Mangal Crocolisk: 5.01 valtrg: True tagged: True tagbme: True tgt-me: True
[9:47:06 PM:599] % At3 15085ms dist from Mangal Crocolisk: 5.01 valtrg: True tagged: True tagbme: True tgt-me: True
[9:47:06 PM:612] % ** Auto-Attack started in Pull
[9:47:06 PM:634] % distance after pull: 5.01
[9:47:06 PM:646] % Exited Pull
[9:47:06 PM:865] % Entered Combat

I'm assuming that this means the mob is outside of melee range? If that's the case then the CC is mistaken because the mob is sitting there wailing on me and if I attack it manually I can hit it with melee abilities.

 

[bobby53]

Doesn't seem to work with the latest stable version 1.9.2.3.

My guy lightning bolt pulls then lets the monster kill him without swinging or using any abilities(level 7 shammy)

View attachment 4870

Hagoroth,

Sorry for your troubles. Please look at the FAQ in this thread on how to create a LOG with debugging info and please attach that so I have a little more detail to go on.

Thanks

 

[Joker76]

Sorry to make another post so soon but I think I found the answer to my issues.

I am using a Tauren Male Shaman. If you Google "Tauren Hitbox" or "Tauren Melee Range", you will see quite a few results indicating that Taruens have the largest melee range/hitbox in the game at 9 yards.

Is there any way to edit the melee range that the CC is calculating? I think this will resolve the delay I'm seeing (and some others as well).

 

[bobby53]

Sorry to make another post so soon but I think I found the answer to my issues.

I am using a Tauren Male Shaman. If you Google "Tauren Hitbox" or "Tauren Melee Range", you will see quite a few results indicating that Taruens have the largest melee range/hitbox in the game at 9 yards.

Is there any way to edit the melee range that the CC is calculating? I think this will resolve the delay I'm seeing (and some others as well).

No worries on posting frequently. I am looking into your issues, but I am going to hold off on a modifiable melee range. That isn't related to a delay in the initial fight sequence, there are some other factors at work because some instants with range greater than melee (the shocks) are available and not fired in your case. You are having two problems and I don't believe at this time either would be solved by a modifiable melee range. The example of a mob being 5.01 yards away may be, but that was situational and wouldn't be solved regardless if the mob was melee+0.01 yds away. The real issue is moving to the target after it has been in melee range. Increasing the melee range in that case would just increase the range that the target would stand still and not pursue a mob.

I will have a new version posted later today that fixes some of the issues people are experiencing. I believe the two issues you cited will be addressed by the following release which I hope to have by Friday. It will involve a lot of changes to the movement system which will require a lot of testing.

 

[Joker76]

No worries on posting frequently. I am looking into your issues, but I am going to hold off on a modifiable melee range. That isn't related to a delay in the initial fight sequence, there are some other factors at work because some instants with range greater than melee (the shocks) are available and not fired in your case. You are having two problems and I don't believe at this time either would be solved by a modifiable melee range. The example of a mob being 5.01 yards away may be, but that was situational and wouldn't be solved regardless if the mob was melee+0.01 yds away. The real issue is moving to the target after it has been in melee range. Increasing the melee range in that case would just increase the range that the target would stand still and not pursue a mob.

I will have a new version posted later today that fixes some of the issues people are experiencing. I believe the two issues you cited will be addressed by the following release which I hope to have by Friday. It will involve a lot of changes to the movement system which will require a lot of testing.

Sounds good, thanks for looking into it. I will certainly help test when you get the changes in.

Keep up the good work!

edit: Do you think it would help if I changed the pull type from Auto to Fast or Body?

 

[bobby53]

Should help with the delay problem to change it to Fast. The only difference between that and body pull is Fast will cast a Shock spell while on the run towards the mob, while Body waits to attack when in melee range.

 

[LiquidAtoR]

[SIZE=1]Activity: Resting[/SIZE]
[SIZE=1]HB EXCEPTION in ShamanBuffs(): System.Threading.ThreadAbortException: De thread is afgebroken.[/SIZE]
[SIZE=1]bij System.Threading.Thread.SleepInternal(Int32 millisecondsTimeout)[/SIZE]
[SIZE=1]bij System.Threading.Thread.Sleep(Int32 millisecondsTimeout)[/SIZE]
[SIZE=1]bij ShamWOW.ShamWOW.ShamanBuffs(Boolean atRest) in d:\HonorBuddy 2.0\HonorBuddy Shammy\CustomClasses\Shaman.cs:regel 1078[/SIZE]

This appeared a few times in the logs, particularly when HB goes into "Activity: Resting" state
Then after manually applying weapon and shield buff, it mounts up and continues.
The resting loop (if it is a loop) seem to appear more frequent lately (even though nothing has changed in setup, spec or food/drinks. All that has changed atm is location as I'm doing my mining skills on the Vanilla and currently Outlands continent).

If you would like full logs, or logs with "debug enabled" on, let me know.
Regards, Liquid.

Edit: It's spamming in the logs that GCD is active (while it's not). I've had this issue before. By removing all references to GCD I had no problems anymore.
Edit2: Already made debug log and uploaded it. Maybe makes it easier. It's alot of the same in error reporting, all related to the GCD detection.