Bot suddenly stops attacking mobs

[cabana344]

Hey people,

testing out HB trial for the moment and already having issues. I started leveling an UD mage today and HB took him to lvl 8 fairly quickly without serious problems. After my character got to lvl 8 and handed in some quests I decided to let him grind a few levels, however this does not work because my bot suddenly is not able to attack mobs anymore. Can't pull, doesn't even melee. If my character gets attacked by mobs, it just dies. It does target mobs and keeps facing them, though.

I am using HB 2 Questing Beta, Project E Mage CC and Undead 1-20 profile by pessach. Note: I'm having the same problems with a HU mage and a HU paladin, using different profiles and cc's. Also installed a clean en.client of WoW and didn't change a thing regarding keybindings.

Any advice?

Thanks in advance.

 

[Tony]

Hb2 is on beta so there are some bugs
but there are 2 stable versions out there
Hb 1.331 and 1.333

 

[ski]

Can you link me to the profile? Seems there's an error in it:

[21:18:39.4357] [Navigator] Could not generate path from {X:2234,709 Y:252,9175 Z:33,70691} to {X:0 Y:0 Z:0}!
[21:18:39:529] No suitable hotspots in Undead 9-11.
[21:18:39:529] No hotspots have been defined!

Also, unless you specifically want to test the beta I'd use HB 1.333 for stable leveling, at least for another week or two until the beta is more stable.

 

[ski]

Can you try this xml instead of the one it normally comes with? There were some untagged vendors I removed, but the rest looks fine.

 

[cabana344]

Hi,

thanks for your quick replys. I forgot to mention that I tried multiple versions of HB:

HB2 Questing Beta
HB2 Beta 10
HB (Version that is linked on your website, should be 1.333?)

I'm going to try stable build with the new .xml and report afterwards.

EDIT: Here we go. Bot targets, but does nothing else except facing mobs. This is stable build, new profile and Project E 1.9.

 

[ski]

Looks like its not casting, I'll forward this thread to CodenameG so he can give us his input as I've never used it before.

 

[CodenameG]

Looks like its not casting, I'll forward this thread to CodenameG so he can give us his input as I've never used it before.

this is because its the advanced targeting is conficting with the mob targeting in hb2, for killing quest mobs.
[21:18:56:482] Killing NPC Decrepit Darkhound at distance 22
[21:18:56:482] Pulling with Fireball
[21:18:56:497] Killing NPC Decrepit Darkhound at distance 22
[21:18:56:575] Activity: Evaluating pull targets.
[21:18:56:591] Activity: Pulling Decrepit Darkhound now.
[21:18:58:60] Pull()...switch
[21:18:58:263] Killing NPC Decrepit Darkhound at distance 24
[21:18:58:263] Pulling with Fireball
[21:18:58:263] Killing NPC Decrepit Darkhound at distance 24
[21:18:58:325] Activity: Evaluating pull targets.
[21:18:58:325] Activity: Pulling Decrepit Darkhound now.
[21:18:59:950] Pull()...switch


it will do things like, at first how it did the double pull, its because honorbuddy knows its not on the quest mob, and ReInvokes the Pull() code. if you look on the release page i specifically mention this bug for this release of honorbuddy 2.

 

[ski]

this is because its the advanced targeting is conficting with the mob targeting in hb2, for killing quest mobs.
[21:18:56:482] Killing NPC Decrepit Darkhound at distance 22
[21:18:56:482] Pulling with Fireball
[21:18:56:497] Killing NPC Decrepit Darkhound at distance 22
[21:18:56:575] Activity: Evaluating pull targets.
[21:18:56:591] Activity: Pulling Decrepit Darkhound now.
[21:18:58:60] Pull()...switch
[21:18:58:263] Killing NPC Decrepit Darkhound at distance 24
[21:18:58:263] Pulling with Fireball
[21:18:58:263] Killing NPC Decrepit Darkhound at distance 24
[21:18:58:325] Activity: Evaluating pull targets.
[21:18:58:325] Activity: Pulling Decrepit Darkhound now.
[21:18:59:950] Pull()...switch


it will do things like, at first how it did the double pull, its because honorbuddy knows its not on the quest mob, and ReInvokes the Pull() code. if you look on the release page i specifically mention this bug for this release of honorbuddy 2.

Thanks CNG

 

[cabana344]

However, even though I disabled "Advanced Targeting" it still doesn't work. Bot won't actually pull any mobs and does not even buff himself.

So what can I do about it? Also, I am using stable build now. Not HB2.

Thanks for your replys.

 

[CodenameG]

However, even though I disabled "Advanced Targeting" it still doesn't work. Bot won't actually pull any mobs and does not even buff himself.

So what can I do about it? Also, I am using stable build now. Not HB2.

Thanks for your replys.

theres no way to disable it, you would have to pull it from the core of the CC, untill questing becomes more stable, i dont think that updating and pulling features is a good thing to do at this time.

 

[cabana344]

theres no way to disable it, you would have to pull it from the core of the CC, untill questing becomes more stable, i dont think that updating and pulling features is a good thing to do at this time.

Why? When I open CC config while the bot is running I should be able to disable it by unchecking it?

Also, I am not using Questing Beta, mate. I use the latest stable build available for download on the website. It's not HB2 and not HB2Questing.

There must be a way to fix this problem, from what I can see a lot of people are using this bot and I can't. Why am I the only one having these issues? :X

 

[CodenameG]

Why? When I open CC config while the bot is running I should be able to disable it by unchecking it?

Also, I am not using Questing Beta, mate. I use the latest stable build available for download on the website. It's not HB2 and not HB2Questing.

There must be a way to fix this problem, from what I can see a lot of people are using this bot and I can't. Why am I the only one having these issues? :X

so this is happening on the HB1 version of the CC? if thats the case, make sure your pullsettings are correct, some people did report that issue in certain spots in azeroth, such as bolean tundra. also next time, these kinda things need to go in the CC thread, so other people having the same problem can find answers relating the the CC your using. instead of finding false information that dosnt pertain to the CC they are currently using.
there is no ETA for a fix for this, the only thing i can recommended is changing locations.

 

[cabana344]

I am new to this bot and it's forums, so I wasn't really sure what is causing my problem.

Well, checked pull settings, nothing wrong there. There aren't many options to configure anyway. Did work fine for the first 8 levels. I will try to bot again once I reach The Barrens.

 

[patto92]

Ive had this same problem, But using beta 10 fixed it for me

 

[cabana344]

It's me again.

Now that I arrived in the Barrens I tried to bot again, however I'm getting the same error. Like I said before, I tried three different bot versions and different profiles and areas. I attached the log to my post, you've got to scroll down a bit until 16:31.

I started it in The Crossroads and it went along to accept all quests, once it tried to kill the first mob it just kept staring again.

I used this profile: http://www.buddyforum.de/showthread.php?46-Horde-1-60-by-bliik