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

[quel]

Hey I just want to say thanks for making this custom cc it's fantastic. I just have one question: After observing my shaman grinding it seems he enjoys taking ~15 second breaks after ever kill before heading to the next one. I was just wondering whether or not this is normal for honorbuddy users, perhaps I've just configured it wrong. As you can probably tell I'm new to honorbuddy so go easy

Nope thats not normal

Do you mind posting a log?

 

[rsync]

Nope thats not normal

Do you mind posting a log?

Ok how's this. This is the log of killing a sunscale lasher, i stopped it when he began moving to the next mob.

[7:47:58 p.m.:190] [AutoEquip]: I'm not equipping anything into ChestSlot as I can't replace heirloom items!
[7:47:58 p.m.:190] [AutoEquip]: I'm not equipping item Lionfur Armor of inventory type Chest as there are no slots to equip it into
[7:48:14 p.m.:636] Activity: Moving towards Sunscale Lashtail
[7:48:22 p.m.:78] Changed POI to: Type: Kill, Name: Sunscale Lashtail
[7:48:25 p.m.:555] Activity: Combat
[7:48:25 p.m.:555] %   Entered Combat
[7:48:25 p.m.:575] %   - status COMBAT [me]:  h/m:96.7%/100.0%, combat:True, melee:1, range:0, rooted:False, immobile:False, silenced:False
[7:48:25 p.m.:635] %   CheckForAdds():  PVE list built has 1 entries within 30.0 yds
[7:48:25 p.m.:635] %   CheckForAdds() can see:
[7:48:25 p.m.:636] %     *MOB: Warrior - Sunscale Lashtail[13]  dist: 3.67
[7:48:25 p.m.:637] %      ## Total  1/0 melee/ranged in Combat - CheckForAdds took 19 ms
[7:48:25 p.m.:657] %   ** Auto-Attack started in Combat
[7:48:25 p.m.:847] %   SetTotemsAsNeeded:  earth: False  fire: False  water: False  air: False
[7:48:26 p.m.:20] Spell_C::CastSpell(8075, 0, 0xF1300CB60014E894, 0)
[7:48:27 p.m.:49] %   ShamanBuffs:  AllowNonHealSpells:True, atrest:False
[7:48:27 p.m.:49] %   Exiting Combat
[7:48:31 p.m.:266] Activity: Combat
[7:48:31 p.m.:266] %   Entered Combat
[7:48:31 p.m.:285] %   - status COMBAT [me]:  h/m:86.9%/100.0%, combat:True, melee:1, range:0, rooted:False, immobile:False, silenced:False
[7:48:31 p.m.:438] %   CheckForAdds():  PVE list built has 1 entries within 30.0 yds
[7:48:31 p.m.:438] %   CheckForAdds() can see:
[7:48:31 p.m.:439] %     *MOB: Warrior - Sunscale Lashtail[13]  dist: 3.67
[7:48:31 p.m.:439] %      ## Total  1/0 melee/ranged in Combat - CheckForAdds took 1 ms
[7:48:31 p.m.:613] %   SetTotemsAsNeeded:  earth: True  fire: False  water: False  air: False
[7:48:31 p.m.:802] Spell_C::CastSpell(3599, 0, 0xF1300CB60014E894, 0)
[7:48:32 p.m.:869] Spell_C::CastSpell(324, 0, 0xF1300CB60014E894, 0)
[7:48:33 p.m.:484] %   ShamanBuffs:  AllowNonHealSpells:True, atrest:False
[7:48:33 p.m.:484] %   Exiting Combat
[7:48:39 p.m.:702] Cleared POI
[7:48:45 p.m.:117] %   Totem Recall CheckForSafeDistance(30.0): saw Warrior - Greater Plainstrider[11] around 5 yds away
[7:48:48 p.m.:823] Changed POI to: Type: Loot, Name: Sunscale Lashtail
[7:48:52 p.m.:319] %   Totem Recall CheckForSafeDistance(30.0): saw Warrior - Greater Plainstrider[11] around 10 yds away
[7:48:52 p.m.:950] interact: 0x194C8398
[7:48:52 p.m.:976] interact done: 0x194C8398
[7:48:57 p.m.:66] Cleared POI
[7:49:00 p.m.:761] %   Totem Recall CheckForSafeDistance(30.0): saw Warrior - Greater Plainstrider[11] around 15 yds away
[7:49:00 p.m.:889] [AutoEquip]: I'm not equipping anything into ChestSlot as I can't replace heirloom items!
[7:49:00 p.m.:889] [AutoEquip]: I'm not equipping item Lionfur Armor of inventory type Chest as there are no slots to equip it into
[7:49:04 p.m.:467] Changed POI to: Type: Kill, Name: Greater Plainstrider
[7:49:08 p.m.:537] %   Totem Recall CheckForSafeDistance(30.0): no hostiles/profile mobs in range - took 1 ms
[7:49:08 p.m.:537] %   Need rest: TotemsWereSet() and recall CheckForSafeDistance(30.0)= true
[7:49:08 p.m.:537] %   Need rest: target:30.5118980407715 atkable:True hostile:False, profile:True alive:True
[7:49:08 p.m.:537] Activity: Resting
[7:49:08 p.m.:538] %   RESTING START: 100% health,  100% mana
[7:49:08 p.m.:538] %   - status REST [me]:  h/m:100.0%/100.0%, combat:False, melee:1, range:0, rooted:False, immobile:False, silenced:False
[7:49:08 p.m.:554] %   RESTING ENDED: 100% health,  100% mana
[7:49:12 p.m.:844] Activity: Moving towards Greater Plainstrider
[7:49:13 p.m.:831] Stop Button pressed. User has stopped the bot.

 

[alexthepope]

HonorBuddy Mode: RaF/instance
Shamans Location:Marudon
What should have happened (be specific): Heal only once.
What did happen (be specific): Heal twice even after the target is well above the percentage that the bot is allow to heal them.
System time of issue (log time stamp): (still new to this does it want my time? 1:01 A.M)


I've noticed that even though the target is at 98% hp, my shaman starts to cast healing surge and the honorbuddy states that the target is at 67%

 

[bobby53]

HonorBuddy Mode: RaF/instance
Shamans Location:Marudon
What should have happened (be specific): Heal only once.
What did happen (be specific): Heal twice even after the target is well above the percentage that the bot is allow to heal them.
System time of issue (log time stamp): (still new to this does it want my time? 1:01 A.M)

I've noticed that even though the target is at 98% hp, my shaman starts to cast healing surge and the honorbuddy states that the target is at 67%

alexthepope, Thank you very much for the excellent issue post! I'll definitely look at your log file in more detail later today. To use the example you gave, the health% at the time the heal was started actually was 67%, but the health % of the target updates while the spell cast is underway. There is a varying amount of delay in the WOW game client between the point where a casted healing spell has completed and the WOW Client updates the amount of health for your target. The update of the internal value occurs just prior or in conjunction with the visible update. Currently if the heal is begun for the selected heal target (so nearby member with the lowest % hp) at >= 70% health or the Shaman and heal target are NOT in combat, the CC will wait for the health of the target to change. If the Shaman or its heal target ARE in combat and the starting health was less than 70%, it does not wait. The delay between the completion of the spell cast and the hp% being updated varies, so 70% is an arbitrary value selected as the point where risking an extra heal is worth the cost of not introducing an unnecessary delay in beginning the next heal. The purpose is to help the Shaman (and its group) survive situations with heavy damage, as the amount of time in the delay is sometimes unacceptable in heavy damage situations. So that's the explanation of what is occurring given the stated example. I'll look at the log file in detail this weekend and get back to you.

 

[bobby53]

Ok how's this. This is the log of killing a sunscale lasher, i stopped it when he began moving to the next mob.

[7:48:33 p.m.:484] %   Exiting Combat
[7:48:39 p.m.:702] Cleared POI
[7:48:45 p.m.:117] %   Totem Recall CheckForSafeDistance(30.0): saw Warrior - Greater Plainstrider[11] around 5 yds away

rsync, My apologies for your issue. I can see several delays (the two greatest being for 6 seconds each beginning at the timestamp [7:48:33 p.m.:484] and another at [7:48:39 p.m.:702] -- together these would represent a 12 second pause and nothing visible occurs when the Cleared POI message is displayed). It appears this is occurring within HonorBuddy and not the CC, but there isn't enough detail to determine whether its due to HonorBuddy settings, etc. Earlier portions of the log file include a great deal of information about your HonorBuddy and ShamWOW setup that is needed to fully evaluate an issue. Post #2 in this thread is the Frequently Asked Questions-FAQ page [link--click here] and contains details on the information needed when posting an issue. There is a template there you can copy and paste if needed. Thanks for your help with gathering the needed info, Bobby53

 

[frozty96]

Can you please fix the Healbot? Using Instancebuddy and even if i select Healbot in the CC settings, its DPSing and healing which makes me OOM in 1 sec

 

[zeldrak]

Can you please fix the Healbot? Using Instancebuddy and even if i select Healbot in the CC settings, its DPSing and healing which makes me OOM in 1 sec

Just wondering if you went into the CC and set it to heal only? Is that what you meant when you said you set it to healbot? Sorry for asking as I haven't used ShamWoW to heal yet. I've been strictly DPS'ing since i'm still below 80.

I just remember a setting in the CC itself that said Heal Only, Heal before combat, and combat only. Just wondering if you set it to only heal and no combat.

 

[bobby53]

Can you please fix the Healbot? Using Instancebuddy and even if i select Healbot in the CC settings, its DPSing and healing which makes me OOM in 1 sec

frozty96, Please visit Post #2 in this thread. Frequently Asked Questions-FAQ [link--click here] has details on the information needed when posting an issue. There is a template there you can copy and paste if needed. Once the requested information is available, I will look into this further for you and if the problem is identifiable will provide a fix in an upcoming release. As a general rule of thumb, I will look into your concern with as much care as you spend preparing your post.

So why would a log file be needed with a post? Here are a few of the many questions the post quoted above raises:

1. What was the starting mana level? I'm not aware of any combination of spells that can cause a Shaman to deplete its mana pool that quickly so have to assume it was low to begin with since it went OOM in 1 second.

2. Which program version was in use? The version in use is always important, but in this case specifically since there was a change in this area recently to encourage Resto Shaman to perform certain types of DPS to take advantage of new 4.0.1 Resto Talents (mentioned in the Change History posted.)

3. What settings were being used? There is no setting in CC Configuration for ShamWOW that is called Healbot but there are a couple that you may have been referencing, so I do not know specifically what settings are in effect. The result is I cannot assess what impact the configuration had on your botting session or what opportunities you have to adjust them.

I appreciate you taking the time to post and let me know about your issue, but frankly stating it needs to be fixed with no debug log file attached to help identify an issue is a waste of your time and mine since I can't do anything with that info other than reply with my standard log file request post. I elaborated further here to explain why the complete debug log file is needed since to most users it may not be obvious since I rarely receive them with the initial post from someone regarding an issue, criticism, or behavioral question. There are simply too many possibilities to make it worth anyone's time to guess about what may be happening, so a complete debug log file is needed for every post where I am being asked to look into making a change of any type.

So I'll be happy to look into this further for you and address your concerns once I receive the information needed to do so. Thanks again for your post,
Bobby53

 

[zeldrak]

Log file request #1,982 and counting...

LoL

Poor bobby... I've seen this far too many times, and I admit that sometimes I'm the cause of such a request as I forget to post logs, but yes you always ask for logs and when you get them you get the problem fixed almost immediately. And, also, I agree with some of the other members when they say that you should be hired to make, or assist in making, a global CC that would fit with all classes and specs. Your ShamWoW CC is money, my friend. I use it in IB, as enhanced since I'm still leveling, and half the time I end up being MT/OT, and not to mention, first in DPS (second in DPS only if there's an OP warlock, mage, hunter, or paladin in the group which happens a lot nowdays with the easily obtainable heirloom items with the grindable JP). I survive bad pulls. PvP is hilarious to watch when I rip through the opposing teams (unless they're better geared and higher level than me, then I just give them a run for their money until I get ganked by 4-on-1's). With your CC and HB my shaman has become a totem dropping M1A2 Abrams Battle Tank. Pure awesomesauce.

 

[cryogenicrooster]

I've been using this for a few days now in instances healing. Bobby this is one epic CC, keep up the good work mate. Thanks for your efforts.

 

[hypocrisy818]

Hey first of all, thanks for this amazing CC. I have one problem though, It has all of sudden started spamming Call of elements and then Totemic Recall throughout entire fights while using instancebuddy. The log does not show anything

I also forgot to add that it always uses heroism prematurely in adds while in instancebuddy, and this causes nerd rage from players 90% of the time.

 

[gimik]

Hey Bobby, since the last update at first it was having the same problem but now its running perfectly. Just every now and then it won't heal or it will outrun the tank and pull mobs but the 2nd part is prolly an IB issue. Either way thanks for helping fix my problem, great CC and great support! +rep

 

[bobby53]

Hey Bobby, since the last update at first it was having the same problem but now its running perfectly. Just every now and then it won't heal or it will outrun the tank and pull mobs but the 2nd part is prolly an IB issue. Either way thanks for helping fix my problem, great CC and great support! +rep

Thanks for the follow up gimik, glad you are getting better results and thanks for the rep. The issue of running past the point where it should stop is due to the same type of problem you were having before however. IB or the CC determines the character is out of range and starts it moving towards the tank, but then the slow down or cpu bound process takes over. By the time IB or the CC gets control again the Shaman is past the tank. Just keep an eye out for it and at some point you may need to look into whats causing the performance bottleneck for you more deeply.

 

[bobby53]

Hey first of all, thanks for this amazing CC.

hypocrisy818, Sorry for your issues and you're very welcome. Glad its of use to you.

The log does not show anything

I appreciate your analysis regarding the log file, but I'll still need it attached to your issue to be able to provide any support.

It has all of sudden started spamming Call of elements and then Totemic Recall throughout entire fights while using instancebuddy.

That happens when the instance you are running isn't meshed, or the Navmesh server is down. I'll need a log file to confirm that is what is happening in your case.

I also forgot to add that it always uses heroism prematurely in adds while in instancebuddy, and this causes nerd rage from players 90% of the time.

I don't get these results in my testing, but in looking it over quickly I did see an issue with Bloodlust. I'll need a complete debug log file if you can provide one to confirm what I found was your issue.

Frequently Asked Questions-FAQ [link--click here] has details on the information needed when posting an issue. There is a template there you can copy and paste if needed. Once the requested information is available, I'll be happy to look into this further for you by analyzing the log file content against the data flow and state transitions of the CC and and if I can identify a problem will provide a fix in the next release.

Thanks for your help, Bobby53

EDIT: Don't worry about the log file unless you have the ones from your runs just prior to posting the issue. A new version of ShamWOW will be posted tomorrow (if I can complete testing) that should fix it. Until then, users should uncheck the Use Bloodlust On Bosses option on the RAF/Instances tab. Since you cannot AFK InstanceBuddy, you can cast Bloodlust manually for now or skip casting it (which only results in nerd rage about 10% of the time) until the fix is available.

 

[bobby53]

I've been using this for a few days now in instances healing. Bobby this is one epic CC, keep up the good work mate. Thanks for your efforts.

Thanks cryogenicrooster! Appreciate the post regarding your success!

 

[Dexter]

instance buddy

HonorBuddy Mode: Grind/PVP/Mixed/Quest/RaF instance

Shamans Location: mana tombs

What should have happened (be specific): i died. went to grave yard

What did happen (be specific):was no route mapped out for instance buddy to run to


System time of issue (log time stamp):

 

[kayes]

Just wanted top say thank you for this CC, when I tested it with instancebuddy my jaw dropped

 

[mezz0]

Tried to heal in the obsidian sanctum yesterday Used Nesox' combat/heal bot together with ShamWow.
At first I tried Raf - Combat assist, but since it's a raid and there is no raf leader the RAF bot won't work.

So I tried nesox' combat/heal bot. I have used that before for on the spot healing stuff and it worked just fine

yesterday however for some reason it decided that it wasn't going to heal but dps in resto spec

See the attached logfile; around 4:05:49 PM:863 somewhere around the first trashpack it decided to pop bloodlust...
big eyes of disbelief from all my guildies, hehe

Gathering from it's behaviour (and had a quick look at your source and the IsRAF() function) I suspect that it didn't go into raf mode, but pve mode. I realise that this is a bit of a grey area inbetween the bot (raf/combat/etc) and the cc, but do you have any ideas what could be changed to allow healing in raids ? I don't need 'follow' code in the bot, I can move manually. Just trying to find a way to have it use your shaman healbot logic in a raid environment (like raf, but leaderless as in a raid)

 

[bobby53]

HonorBuddy Mode: Grind/PVP/Mixed/Quest/RaF instance
Shamans Location: mana tombs
What should have happened (be specific): i died. went to grave yard
What did happen (be specific):was no route mapped out for instance buddy to run to
System time of issue (log time stamp):

Dexter, Corpse runs are handled by the Bot which in the case you reported sounds like it was InstanceBuddy. You will want to post in the InstanceBuddy thread [link -- click here] regarding this. The CC (in this case ShamWOW) only controls movement when you get into combat or are rezzing a player. The rest of the time InstanceBuddy controls the movement. Thanks for the post and good luck with your character, Bobby53

 

[bobby53]

Tried to heal in the obsidian sanctum yesterday Used Nesox' combat/heal bot together with ShamWow.
At first I tried Raf - Combat assist, but since it's a raid and there is no raf leader the RAF bot won't work.

So I tried nesox' combat/heal bot. I have used that before for on the spot healing stuff and it worked just fine

yesterday however for some reason it decided that it wasn't going to heal but dps in resto spec

See the attached logfile; around 4:05:49 PM:863 somewhere around the first trashpack it decided to pop bloodlust...
big eyes of disbelief from all my guildies, hehe

Gathering from it's behaviour (and had a quick look at your source and the IsRAF() function) I suspect that it didn't go into raf mode, but pve mode. I realise that this is a bit of a grey area inbetween the bot (raf/combat/etc) and the cc, but do you have any ideas what could be changed to allow healing in raids ? I don't need 'follow' code in the bot, I can move manually. Just trying to find a way to have it use your shaman healbot logic in a raid environment (like raf, but leaderless as in a raid)

mezz0, Thanks for the descriptive issue post and complete debug log file! You were right on the money with the RAF / PVE confusion. A couple things are at work in the situation you described so I'll break each down below.

1) Bloodlust. There is an issue with Bloodlust right now that was reported a couple posts before yours. I should have a release out today to resolve it for you. If you use before that just be sure to disable the Use Bloodlust on Bosses option in the RAF / Instance tab of CC Configuration for ShamWOW.

2) Healing. To heal a group, there needs to be a tank identified which at a minimum will determine who gets Earth Shield, whose death causes the Shaman to cast Earth Elemental Totem, etc. The tank is identified in HonorBuddy by the Bot setting the RaFHelper.Leader internal value to the appropriate character in the group. InstanceBuddy and the RaF/Combat Assist bot set this correctly. I submitted code to Nesox for this in the Combat / Healer bot, so I'll follow up with him to see where we stand on getting it added. If it isn't going in soon I'll provide the plug-in I wrote for myself for public use.

3) Workaround. At the moment, here is setup needed to Heal raids:
a. Bot: RAF / Combat Assist, Plugin: Mr. AutoFight
b. Raid Leader must be tank, and Raid Leader must be in your 5 man party within the raid. These are current constraints imposed by RAF / Combat Assist presently.
c. Check 'Disable CC Movement' on the General tab of CC Configuration for ShamWOW.

One the RAF / Combat Assist bot and/or the Combat / Healer bot are revised, this setup should be much more straight forward with no constraints on grouping, etc.

4) Leaderless healing. I'll give this some additional thought, but I'm reluctant to add support for a special case that feels like it should be resolved by fixing the RAF bot and updating the Combat / Healbot to include tank identification.

Thanks again for the detailed post,
Bobby53