Moving to hunting ground waypoint 'hunting ground center'

Hi,
atm I am using HB mostly for the tillers farming and planting stuff. Unfortunately since the update 716 (oder 15) all the profiles I found are not working anymore. Sometimes they go through, but most of the time the bot gets stuck with the following message:

Moving to hunting ground waypoint 'hunting ground center'

When you move it by hand it tickles around and circles, when you try to move away a bit it runs back and starts turning around... My guess is the bot is trying to target somethin, but cant. But I am not sure...

The thing is with the old bot the profiles are still working...

Here is a log (this time with Brodies Plugin - yes I know he is gone for the moment and the profiles are not uptodate, but until version 715 it worked just fine and still now sometimes the profile runs through smoothly) but all other profiles I tested for the farm have the same issue.

Is there a working porfile for planting and harvesting atm?

 

already did. i always clear the cache before using the bot and after a problem, too. the problem occurs again...

 

quest? which quest? ^^ I am not questing...
The problem occurs while the bot tries to plant enigma seeds (or any other seeds) on the farm. sometimes it gets stuck at planting new seeds or to be more exact on the specials after planting...

 

This is a problem with the 718 build. InteractWith behavior has had some changes and now breaks a lot of profiles, trying to interact with stuff that's not there. More common on the Tillers type stuff where QuestID is not relevant.

I've managed to almost work around if for most my Tillers profiles (which are custom versions of Brodiemans), but I've seen it a few times in questing profiles as well. (Adding the TerminateWhen directive, which should not be necessary when WaitForNPCs is set to false, and the MobID's no longer exist)

I'm presuming/hoping the devs are aware (or one of them glances at this), as unfortunately the "support" staff will just give a canned response, as they did to you "do it manually" which is no help for a profile I run daily on 11 farms.

Crossing fingers it's fixed in next release.

 

hmm, no other idea Tony? It would be great if that could be fixed (bot side not profile side), so we still can use the good old profiles, since it is quite hard to find real good new profiles...

 

In case you want to modify your profiles to work around it:

Modifications to Alluring and Wiggling:

Code:

<!-- Alluring -->
	<CustomBehavior File="Message" Text="Alluring Crop..." LogColor="Green" />
	<While Condition="ObjectManager.GetObjectsOfType&lt;WoWUnit&gt;().Any(u =&gt; new [] { 66122, 63178, 63222, 66107, 63147, 60070, 63243, 63259, 66079, 63159, 65913, 65985, 66012, 65964, 66039, 66002 }.Contains((int)u.Entry) &amp;&amp; u.Distance &lt;= 100)" >
		<CustomBehavior File="InteractWith" MobId="66122" MobId2="63178" MobId3="63222" MobId4="66107" MobId5="63147" 
											MobId6="60070" MobId7="63243" MobId8="63259" MobId9="66079" MobId10="63159"
											MobId11="65913" MobId12="65985" MobId13="66012" MobId14="65964" MobId15="66039" MobId16="66002"
			NonCompeteDistance="0" PreInteractMountStrategy="DismountOrCancelShapeshift" WaitForNpcs="False" WaitTime="500"
			TerminateWhen="!ObjectManager.GetObjectsOfType&lt;WoWUnit&gt;().Any(u =&gt; new [] { 66122, 63178, 63222, 66107, 63147, 60070, 63243, 63259, 66079, 63159, 65913, 65985, 66012, 65964, 66039, 66002 }.Contains((int)u.Entry)) " />
	</While>
	
<!-- Wiggling -->
	<CustomBehavior File="Message" Text="Wiggling Crop..." LogColor="Green" />
	<While Condition="ObjectManager.GetObjectsOfType&lt;WoWUnit&gt;().Any(u =&gt; new [] { 66133, 63189, 63233, 66117, 63146, 60029, 63254, 63270, 66089, 63169, 65924, 65993, 66020, 65971, 66047, 66010 }.Contains((int)u.Entry) &amp;&amp; u.Distance &lt;= 100)" >
		<CustomBehavior File="InteractWith" MobId="66133" MobId2="63189" MobId3="63233" MobId4="66117" MobId5="63146"
											MobId6="60029" MobId7="63254" MobId8="63270" MobId9="66089" MobId10="63169"
											MobId11="65924" MobId12="65993" MobId13="66020" MobId14="65971" MobId15="66047" MobId16="66010"
			NonCompeteDistance="0" PreInteractMountStrategy="DismountOrCancelShapeshift" WaitForNpcs="False" WaitTime="1000" 
			TerminateWhen="!ObjectManager.GetObjectsOfType&lt;WoWUnit&gt;().Any(u =&gt; new [] { 66133, 63189, 63233, 66117, 63146, 60029, 63254, 63270, 66089, 63169, 65924, 65993, 66020, 65971, 66047, 66010 }.Contains((int)u.Entry)) " />
	</While>

Modifications to Runty:

Code:

<!-- Runty -->
	<CustomBehavior File="Message" Text="Runty crop..." LogColor="Green" />
	<While Condition="ObjectManager.GetObjectsOfType&lt;WoWUnit&gt;().Any(u =&gt; new [] { 66130, 63186, 63230, 66114, 63150, 60218, 63251, 63267, 66086, 63166, 65920, 65990, 66017, 65968, 66044, 66007 }.Contains((int)u.Entry) &amp;&amp; u.Distance &lt;= 100)" >
		<CustomBehavior File="InteractWith" MobId="66130" MobId2="63186" MobId3="63230" MobId4="66114" MobId5="63150"
											MobId6="60218" MobId7="63251" MobId8="63267" MobId9="66086" MobId10="63166"
											MobId11="65920" MobId12="65990" MobId13="66017" MobId14="65968" MobId15="66044" MobId16="66007"
											NonCompeteDistance="0" PreInteractMountStrategy="DismountOrCancelShapeshift" WaitForNpcs="False" WaitTime="3000" 
											TerminateWhen="!ObjectManager.GetObjectsOfType&lt;WoWUnit&gt;().Any(u =&gt; new [] { 66130, 63186, 63230, 66114, 63150, 60218, 63251, 63267, 66086, 63166, 65920, 65990, 66017, 65968, 66044, 66007 }.Contains((int)u.Entry) &amp;&amp; u.Distance &lt;= 100)" />
		<CustomBehavior File="Misc\RunLua" Lua="JumpOrAscendStart()" WaitTime="1500" />
	</While>

I'm sure any dev looking at this will agree that the profile having to make these work arounds is wrong, and the InteractWith behavior should stop itself when there are no MobIDs left, as it did before 718 (This profile had been running flawlessly for months), and as per the "WaitForNPCs" notes in the documentation.

 

Thanks Wullie I will try that...

 

if you would, please post a full log as an attachment so we can see whats going on.
http://www.thebuddyforum.com/honorbuddy-forum/honorbuddy-guides/35945-guide-how-attach-your-log.html

 

Hi CodenameG,
the log in the first post is a complete log, but I made a new one:
View attachment 1408 2013-12-31 12.46.txt

I did not stop the bot so you can clearly see where it is stuck. At the end point of this log the bot is stuck forever... It does not move again. When I move the toon by hand it runs back to the point where it was stuck and stays there or moves around in very little "ticks"...

and here is another one:

View attachment 4496 2013-12-31 13.03.txt


ok this problem is not only limited to the farming profiles... I today ran Kick's Profile for about 2h and I had the same issue...


Here is the log (from Kick's profile):

View attachment 4780 2013-12-31 13.46.zip

 

happy new year to all of you!

any news on this?

 

Tony, CodenameG?
Really nothing?

 

Yes this bug sucks realy. I hope they fix it asap.

 

Even a "we're working on it" would be nice...

 

its on your end, just complete what quests you have in your logs manually.

for some reason the profile is stuck on those engima things.

 

Seriously? Not even going to acknowledge this problem which a number of different people have started to get specifically since 718 with profiles that worked perfectly before is a problem on the HBCore side?

What's more annoying is twice in the thread now it's been explained that there are no associated quests yet you've not even give the time to tune your canned answer to reflect that. Why make us jump through so many hoops to report problems, it just alienates your users.

Surely InteractWith should terminate when there are no more MobIds available and WaitForNpcs is set to false, how can this *not* be an issue?

 

yes, but they are with brodies or cava's profiles, NOT with kicks. theres nothing wrong with the core, its the profile.

 

So 718 brings changes to the documented workings of InteractWith which I can't see any notifications about anywhere, but this is by design and is working as intended. Other than breaking a number of profiles, what do these changes seek to accomplish, and when will the documentation be updated to reflect the changes so profile designers have an understanding and a means to repair profiles in line with these changes?

 

CodenameG PLEASE read the last part of my post #11...

focus please on that part:

to specifiy it a bit more: it was in (i will look up the zone's name) and the toon should click an item for a mob to be attackable. but the object could not be clicked... so the toon just stood around and HB gave the same last line, with that the farming profiles end (are broken): " Moving to hunting ground waypoint 'hunting ground center' " ....

I had the problem ALSO with kicks profile while leveling a hunter... it is therefor NOT limited to cavas or kicks profiles... and as Wullie already stated the problem first occured with one of the last updates of HB. I am not 100% sure if it was the last one (718) I think the problems started with the 716 update...

I am pretty sure this problem does not come from "our end" of the line...