Bot skips waypoints

[2face 36]

Hi, for some reason the bot keeps skipping waypoints every now and then. I'm using the Quester and set up a FollowPath. I have recorded a path and also turned of is hotspot and turned on force start from first and is complete when reaching the last. 

Now sometimes the bot just goes to the very last waypoint in the list and uses the auto pathfinding system instead of the waypoints that i defined in the list. I tested it with different set ups and different profiles. It doesnt always happen but alot of times. 

How can i force the bot to walk the path and not use the hotspot/autopathing system on the very last point in the list? 

I'm trying to make my firelands farm work 100% perfectly but alot of times it just doesnt follow the path and doesnt pull all the mobs, it just skips them and goes to the last waypoint.

I also made a bug report. Can anyone else confirm this issue ? I have seen others describing a similiar behaviour, that the bot skips waypoints. 

 

Thanks in advance!

 

//Additionally while the bot sometimes doesnt follow the path at all and just stands still, he keeps switching into Quester > FollowPath state and then into Battle Pet state every few seconds. Maybe this is connected to the issue too ?

[Droidz 2738]

Hello, if you can wait next update. I have added step type "Reset", use this step before "Pulse" step.

[krlitoz 1]

When will the next update be live? Also, as an unrelated question:

do you happen to know how to use the Scheduler without a timer? And instead just run next steps based on whether the last step finished. IS that possible? I'm trying to logout as soon as the quester step has finished isntead of waiting on the timer.

 

Thanks!!

[krlitoz 1]

What action should the reset step have prior to the Pulse step?

[Droidz 2738]

You can add at the end step type "RunLuaCode" with code 

Logout()

( http://wowwiki.wikia.com/wiki/API_Logout )

to logout character.

To use Reset:

[Mr. Robot 11]

Is there a difference between a hotspot and a waypoint? I've been having some trouble with a grinding path that keeps skipping path positions and not starting from the beginning. If there is any suggestions how to fix that please let me know.

 

Thanks,

Mr. Robot

[mich125 8]

Anyone found out how to fix bot skipping waypoints sometimes issue?

Once every few dungeon runs, bot will just skip followpath waypoints, and instead use auto pathfinding system and go to last waypoint on the list using it, same issue as in first post.

Like maybe there is a better way to force bot following certain waypoints path than followpath?

[mich125 8]

@Droidz

Any way to fix it, i have like 12 bots atm, and watching them run.

After a while, almost every dungeon run some bot will skip followpath waypoints at some point.

My profile has many followpath steps with step completed when bot is at last step, and after a while bot will change one of the followpath steps and go straight to last waypoint on this step using pathfinder i guess.

On the next run, he can change different followpath step same way, and run the one from previous run flawless, so its pretty random which one he chooses. And some runs he will run every followpath steps flawless, especially first runs he makes everything flawless, the skipping waypoints behavior happens after bot is running for some time.

If you cannot fix this, is there any way other than followpath to force bot always go by the list of waypoints, and complete step when at last waypoint, which will work flawless?

[Runaro 160]

24 minutes ago, mich125 said:

@Droidz

Any way to fix it, i have like 12 bots atm, and watching them run.

After a while, almost every dungeon run some bot will skip followpath waypoints at some point.

My profile has many followpath steps with step completed when bot is at last step, and after a while bot will change one of the followpath steps and go straight to last waypoint on this step using pathfinder i guess.

On the next run, he can change different followpath step same way, and run the one from previous run flawless, so its pretty random which one he chooses. And some runs he will run every followpath steps flawless, especially first runs he makes everything flawless, the skipping waypoints behavior happens after bot is running for some time.

If you cannot fix this, is there any way other than followpath to force bot always go by the list of waypoints, and complete step when at last waypoint, which will work flawless?

I prefer using a IsCompleteCondition for checking if he's really at the right position and then pulse the next step, instead of using the inbuild "<IsCompleteWhenAtLastPath>false</IsCompleteWhenAtLastPath>".

      <IsCompleteCondition>return (ObjectManager.Me.Position.DistanceTo2D(new Vector3(-591.455, 4074.51, 93.8132)) &lt; 10);</IsCompleteCondition>

 

[mich125 8]

But does it fix the issue of skipping waypoints?

Couse i dont think its rly about  IsCompleteWhenAtLastPath, since bot pulses steps correctly, its just that he will sometimes in a step when he has followpath:

1

2

3

4

skips 1,2,3 and go straight to 4

[Runaro 160]

1 minute ago, mich125 said:

But does it fix the issue of skipping waypoints?

Couse i dont think its rly about  IsCompleteWhenAtLastPath, since bot pulses steps correctly, its just that he will sometimes in a step when he has followpath:

1

2

3

4

skips 1,2,3 and go straight to 4

Could you please post a example FollowPath pulse from your profile?

[mich125 8]

Just now, Runaro said:

Could you please post a example FollowPath pulse from your profile?

Sure

<EasyQuest>
      <Name>GoTo14th</Name>
      <QuestId />
      <QuestType>FollowPath</QuestType>
      <QuestClass xsi:type="FollowPathEasyQuestClass">
        <Path>
          <Vector3 X="1256.431" Y="22.70191" Z="33.50569" />
          <Vector3 X="1269.236" Y="41.0107" Z="33.50568" />
          <Vector3 X="1255.751" Y="66.1565" Z="33.50556" />
          <Vector3 X="1272.432" Y="104.288" Z="33.50554" />
        </Path>
        <IsCompleteWhenAtLastPath>true</IsCompleteWhenAtLastPath>
        <ForceToStartFirstPosition>false</ForceToStartFirstPosition>
        <IsHotSpots>false</IsHotSpots>
        <IsLoop>false</IsLoop>
      </QuestClass>
      <ObjectiveCount1>0</ObjectiveCount1>
      <ObjectiveCount2>0</ObjectiveCount2>
      <ObjectiveCount3>0</ObjectiveCount3>
      <ObjectiveCount4>0</ObjectiveCount4>
      <ObjectiveCount5>0</ObjectiveCount5>
      <ObjectiveCount6>0</ObjectiveCount6>
      <ObjectiveCount7>0</ObjectiveCount7>
      <ObjectiveCount8>0</ObjectiveCount8>
      <ObjectiveCount9>0</ObjectiveCount9>
      <ObjectiveCount10>0</ObjectiveCount10>
      <AutoDetectObjectiveCount1>false</AutoDetectObjectiveCount1>
      <AutoDetectObjectiveCount2>false</AutoDetectObjectiveCount2>
      <AutoDetectObjectiveCount3>false</AutoDetectObjectiveCount3>
      <AutoDetectObjectiveCount4>false</AutoDetectObjectiveCount4>
      <AutoDetectObjectiveCount5>false</AutoDetectObjectiveCount5>
      <AutoDetectObjectiveCount6>false</AutoDetectObjectiveCount6>
      <AutoDetectObjectiveCount7>false</AutoDetectObjectiveCount7>
      <AutoDetectObjectiveCount8>false</AutoDetectObjectiveCount8>
      <AutoDetectObjectiveCount9>false</AutoDetectObjectiveCount9>
      <AutoDetectObjectiveCount10>false</AutoDetectObjectiveCount10>
      <CanCondition />
      <IsCompleteCondition />
      <RepeatableQuest>false</RepeatableQuest>
      <NotRequiredInQuestLog>true</NotRequiredInQuestLog>
      <PickUpQuestOnItem>false</PickUpQuestOnItem>
      <PickUpQuestOnItemID>0</PickUpQuestOnItemID>
      <Comment />
      <GossipOptionRewardItem>1</GossipOptionRewardItem>
      <RequiredQuest>0</RequiredQuest>
      <MaxLevel>999</MaxLevel>
      <MinLevel>0</MinLevel>
      <WoWClass>None</WoWClass>
    </EasyQuest>

[Runaro 160]

1 minute ago, mich125 said:

Sure

<EasyQuest>
      <Name>GoTo14th</Name>
      <QuestId />
      <QuestType>FollowPath</QuestType>
      <QuestClass xsi:type="FollowPathEasyQuestClass">
        <Path>
          <Vector3 X="1256.431" Y="22.70191" Z="33.50569" />
          <Vector3 X="1269.236" Y="41.0107" Z="33.50568" />
          <Vector3 X="1255.751" Y="66.1565" Z="33.50556" />
          <Vector3 X="1272.432" Y="104.288" Z="33.50554" />
        </Path>
        <IsCompleteWhenAtLastPath>true</IsCompleteWhenAtLastPath>
        <ForceToStartFirstPosition>false</ForceToStartFirstPosition>
        <IsHotSpots>false</IsHotSpots>
        <IsLoop>false</IsLoop>
      </QuestClass>
      <ObjectiveCount1>0</ObjectiveCount1>
      <ObjectiveCount2>0</ObjectiveCount2>
      <ObjectiveCount3>0</ObjectiveCount3>
      <ObjectiveCount4>0</ObjectiveCount4>
      <ObjectiveCount5>0</ObjectiveCount5>
      <ObjectiveCount6>0</ObjectiveCount6>
      <ObjectiveCount7>0</ObjectiveCount7>
      <ObjectiveCount8>0</ObjectiveCount8>
      <ObjectiveCount9>0</ObjectiveCount9>
      <ObjectiveCount10>0</ObjectiveCount10>
      <AutoDetectObjectiveCount1>false</AutoDetectObjectiveCount1>
      <AutoDetectObjectiveCount2>false</AutoDetectObjectiveCount2>
      <AutoDetectObjectiveCount3>false</AutoDetectObjectiveCount3>
      <AutoDetectObjectiveCount4>false</AutoDetectObjectiveCount4>
      <AutoDetectObjectiveCount5>false</AutoDetectObjectiveCount5>
      <AutoDetectObjectiveCount6>false</AutoDetectObjectiveCount6>
      <AutoDetectObjectiveCount7>false</AutoDetectObjectiveCount7>
      <AutoDetectObjectiveCount8>false</AutoDetectObjectiveCount8>
      <AutoDetectObjectiveCount9>false</AutoDetectObjectiveCount9>
      <AutoDetectObjectiveCount10>false</AutoDetectObjectiveCount10>
      <CanCondition />
      <IsCompleteCondition />
      <RepeatableQuest>false</RepeatableQuest>
      <NotRequiredInQuestLog>true</NotRequiredInQuestLog>
      <PickUpQuestOnItem>false</PickUpQuestOnItem>
      <PickUpQuestOnItemID>0</PickUpQuestOnItemID>
      <Comment />
      <GossipOptionRewardItem>1</GossipOptionRewardItem>
      <RequiredQuest>0</RequiredQuest>
      <MaxLevel>999</MaxLevel>
      <MinLevel>0</MinLevel>
      <WoWClass>None</WoWClass>
    </EasyQuest>

        <ForceToStartFirstPosition>false</ForceToStartFirstPosition>

To:

        <ForceToStartFirstPosition>true</ForceToStartFirstPosition>

 

[mich125 8]

Ive tried it already, didnt change this behavior sadly, like i said in my first post:

Its very random behavior, he can run this step correctly 10 times, but then next run he will skip1,2,3 and go straight to 4, and in my profile there is like 15 steps like this one, so almost each run he will do it with one of these steps.

[Runaro 160]

7 minutes ago, mich125 said:

Ive tried it already, didnt change this behavior sadly, like i said in my first post:

Its very random behavior, he can run this step correctly 10 times, but then next run he will skip1,2,3 and go straight to 4, and in my profile there is like 15 steps like this one, so almost each run he will do it with one of these steps.

Sounds weird, because he doesn't do it for me when i check this option.

But to be honest, i never let the bot repeat FollowPath's all the time, he'll only do it once for me, continue with other pulses and never will come back to the FollowPath pulse. ( leveling profile )

If this problem really persists and i'm not missing something, then you should maybe create a workaround for now. ( until Droidz did reproduce this problem and fix it, if it's really a bug )

Instead of using FollowPath, simply create RunCode's in the QuestSorted. ( weird and not clean solution, but that should at least work )

Here's an example for your coordinates you posted:

    <QuestsSorted Action="RunCode" NameClass="wManager.Wow.Bot.Tasks.GoToTask.ToPosition(new Vector3(1256.431, 22.70191, 33.50569));" />	
    <QuestsSorted Action="RunCode" NameClass="wManager.Wow.Bot.Tasks.GoToTask.ToPosition(new Vector3(1269.236, 41.0107, 33.50568));" />	
    <QuestsSorted Action="RunCode" NameClass="wManager.Wow.Bot.Tasks.GoToTask.ToPosition(new Vector3(1255.751, 66.1565, 33.50556));" />	
    <QuestsSorted Action="RunCode" NameClass="wManager.Wow.Bot.Tasks.GoToTask.ToPosition(new Vector3(1272.432, 104.288, 33.50554));" />	

But if you ask me, i would wait and see what Droidz has to say about that.

[mich125 8]

Your solution should actually work i think, will try it thanks.

[Zan 99]

You did try putting Reset> GoTo14th then Pulse> GoTo14th correct? 

[mich125 8]

yes putting reset before every goto pulse didnt help

[mich125 8]

So i rewrote my profile using @Runaro solution, just had to group up more than one waypoint in a single runcode, else its too slow. So far looks good, will monitor it longer if it skips waypoints after a while.

-----------

Ok so i monitored it for a few hours, and it fixed my issue completely, happy me:D

[dragonmase 5]

Hi, just want to add on to this, and say that I have the same issue with followpath. 

It is very obvious for my dungeon profile since my followpath involves me jumping off a cliff to faster reach a spot, whereas the pathfinder way will take a very long route and will aggro bosses along the way. 

As mentioned above, this error occurs very randomly. I run 5 bots at a time, all same level and class 100 druid, and some immediately use pathfinder instead, whereas the rest running the exact same profile and settings will followpath normally.

 

 <EasyQuest>
      <Name>Walk</Name>
      <QuestId />
      <QuestType>FollowPath</QuestType>
      <QuestClass xsi:type="FollowPathEasyQuestClass">
        <Path>
          <Vector3 X="-8439.949" Y="1517.049" Z="31.90777" />
          <Vector3 X="-8443.592" Y="1517.755" Z="31.93664" />
          <Vector3 X="-8450.298" Y="1519.057" Z="31.97351" />
          <Vector3 X="-8457.005" Y="1520.358" Z="31.9096" />
          <Vector3 X="-8464.028" Y="1521.72" Z="31.90755" />

....

<Vector3 X="-9283.733" Y="1296.911" Z="-65.21579" Type="Swimming" />
          <Vector3 X="-9288.16" Y="1292.38" Z="-65.40124" Type="Swimming" />
          <Vector3 X="-9290.884" Y="1289.235" Z="-64.56161" />
          <Vector3 X="-9293.997" Y="1285.615" Z="-63.93718" />
          <Vector3 X="-9297.251" Y="1281.873" Z="-63.75855" />
          <Vector3 X="-9300.598" Y="1278.161" Z="-63.74581" />
          <Vector3 X="-9304.547" Y="1269.946" Z="-62.25735" />

</Path>
        <IsCompleteWhenAtLastPath>true</IsCompleteWhenAtLastPath>
        <ForceToStartFirstPosition>false</ForceToStartFirstPosition>
        <IsHotSpots>false</IsHotSpots>
        <IsLoop>false</IsLoop>

 

Just to clarify, I don't want it to restart at the first position (the raid entrance), nor do I have any hotspots i want it to go to. Just simply point A to point B. 

Haven't tried the runcode method yet, will do it later, but its gonna be painful for a large raid dungeon with many aggroable bosses to skip. Just wanted to put this bug out so that @Droidz can attempt to fix it the next patch!

 

[Kraven 0]

I'm also having the problem with Reset not working. The RunCode solution works for me, but it is a pain. Any update on when Reset can be fixed?

I'm using WOTLK version.

[Findeh 34]

NWM, i'll come back when i'll gather more info