Random "MoveTo" Tag issue

I am experiencing a random problem where when I use MoveTo in an OrderBot script, the bot hangs at the destination - the tag never returns UNLESS I slightly nudge the toon's position with the keyboard. Here is a snippet:

Code:

			<If Condition="IsTimeBetween(21,1)">
				<!-- Nothing to do until 1am Eorzea time, so wait at next aetheryte -->
				<TeleportTo Name="Camp Dragonhead" AetheryteId="23" />
				<MoveTo XYZ="274.5798, 295.1528, -71.25455" Name="Hotspot"/>
				<LogMessage Message= "Waiting until 1am Eorzea Time"/>
				<WaitWhile Condition ="IsTimeBetween(21,1)" />
				<WaitTimer WaitTime="5"/>
			</If>

So when this problem occurs, the toon does move to the specified location, but I never see the log message until I manually move the toon a bit.

 

Camp Dragonhead = 155

 

Yep, as I said, it's random - and it occurs in all zones for me, in a variety of different scripts. It's as if the movement code does not believe the toon has arrived within the distance epsilon you presumably use to end continuing to move the character, I suppose by sending a movement keystroke. If you could just check that code to ensure there is no condition like that (e.g., if you send the movement keystroke, and the toon does not actually change position, so you stop), I would appreciate it. Otherwise, I have no idea why this would be occurring, but even though it's very random, it is also very reliable in that it always eventually occurs, and it is making it almost impossible for me to run afk scripts effectively. If there is some way to enable additional debugging output, please let me know how to do so.

 

I might have an idea why this is happening. I am using Agil and Chanko. It appears that if these plugins run while movement is in progress, the movement does not automatically restart after the plugin complete. I have looked at the code for Chanko, and it is pretty simple - it adds a "Decorator" node to the tree that implements the "eat food" behavior. While I have a general understanding of how the game tree functions, I can find no explanation of the various semantics of the TreeSharp nodes. So I have no idea if there is a way to "interrrupt" a long running request like movement and return it to its state at the point of interrupt. Any help on this would be appreciated.

 

Its not just you.. I been encountering it myself in the last 12 hours.

Random stuck points in... here are some sections of the logs at Rev Toll.. probably a temporary glitch on the nav server?


2015-07-29 05.13
[22:06:17.811 D] Requesting path on 145 from <-386.3665, -58.87574, 147.4695> to <306.1508, 10.22671, -11.36177>
[22:06:17.901 D] Generated path to <306.1508, 10.22671, -11.36177> in 00:00:00.0899104 ms
[22:06:18.679 D] Moving to next hop: <-379.7611, -58.95636, 139.0258> (Miner's Hotspot) D: 6.354396
[22:06:19.346 D] Moving to next hop: <-379.2627, -58.95636, 138.3633> (Miner's Hotspot) D: 1.160987
[22:06:19.412 D] Moving to next hop: <-365.4517, -56.15637, 121.8148> (Miner's Hotspot) D: 22.29496
[22:06:21.817 D] Moving to next hop: <-353.3604, -55.75638, 109.6358> (Miner's Hotspot) D: 17.64382
[22:06:23.750 D] Moving to next hop: <-353.039, -55.75638, 108.8281> (Miner's Hotspot) D: 1.090052
[22:06:23.816 D] Moving to next hop: <-348.6753, -53.95636, 87.29408> (Miner's Hotspot) D: 22.52379
[22:06:26.231 D] Moving to next hop: <-348.3224, -52.85635, 79.43988> (Miner's Hotspot) D: 8.671227
[22:06:27.153 D] Moving to next hop: <-348.0878, -52.55637, 77.55396> (Miner's Hotspot) D: 2.230312
[22:06:27.350 D] Moving to next hop: <-346.3672, -49.25638, 65.30456> (Miner's Hotspot) D: 13.21249
[22:06:28.742 D] Moving to next hop: <-345.7253, -49.15637, 65.04406> (Miner's Hotspot) D: 0.9039035
[22:06:28.808 D] Moving to next hop: <-334.4642, -42.95636, 43.35462> (Miner's Hotspot) D: 25.4668
[22:06:31.521 D] Moving to next hop: <-333.783, -42.85635, 42.8441> (Miner's Hotspot) D: 1.116097
[22:06:31.586 D] Moving to next hop: <-328.7996, -41.65637, 38.97605> (Miner's Hotspot) D: 6.932581
[22:06:32.311 D] Moving to next hop: <-323.0753, -40.75638, 36.09406> (Miner's Hotspot) D: 6.753019
[22:06:32.970 D] Moving to next hop: <-220.6753, -37.25638, 29.69406> (Miner's Hotspot) D: 103.3386
[22:06:44.374 D] Moving to next hop: <-214.6465, -37.25638, 29.23778> (Miner's Hotspot) D: 6.672431
[22:06:45.083 D] Moving to next hop: <-150.2753, -31.95636, 16.89407> (Miner's Hotspot) D: 66.05241
[22:06:52.354 D] Moving to next hop: <-131.0753, -28.25638, 4.094061> (Miner's Hotspot) D: 23.75045
[22:06:54.925 D] Moving to next hop: <-105.4753, -25.35635, -2.305939> (Miner's Hotspot) D: 26.83742 <-- Died here


2015-07-29 04.31
[12:06:01.722 D] Requesting path on 156 from <32.93103, 20.295, -668.0558> to <315.842, -12.38877, -487.02>
[12:06:01.809 D] Generated path to <315.842, -12.38877, -487.02> in 00:00:00.0868498 ms
[12:06:02.205 D] Moving to next hop: <36.78768, 21.59921, -667.1664> (Miner's Point) D: 4.480206
[12:06:02.608 D] Moving to next hop: <41.80005, 20.99921, -663.578> (Miner's Point) D: 6.598322
[12:06:03.284 D] Moving to next hop: <63.2358, 20.26781, -638.5638> (Miner's Point) D: 33.40196
[12:06:06.916 D] Moving to next hop: <65.84765, 20.27895, -636.2055> (Miner's Point) D: 4.216025
[12:06:07.317 D] Moving to next hop: <82.37498, 20.64921, -622.6881> (Miner's Point) D: 21.96538
[12:06:09.680 D] Moving to next hop: <82.51538, 20.6992, -622.0474> (Miner's Point) D: 1.2789
[12:06:09.739 D] Moving to next hop: <81.51348, 20.59354, -618.436> (Miner's Point) D: 4.292524
[12:06:10.144 D] Moving to next hop: <82.55576, 20.63113, -617.2892> (Miner's Point) D: 2.105414
[12:06:10.303 D] Moving to next hop: <83.81696, 21.08519, -617.0531> (Miner's Point) D: 1.875431
[12:06:10.422 D] Moving to next hop: <108.8, 19.1992, -611.9281> (Miner's Point) D: 26.2034
[12:06:13.253 D] Moving to next hop: <120.7423, 17.94651, -608.3146> (Miner's Point) D: 13.22932
[12:06:14.649 D] Moving to next hop: <134.4, 16.1992, -599.1281> (Miner's Point) D: 17.10458
[12:06:16.473 D] Moving to next hop: <133.5188, 16.24648, -598.963> (Miner's Point) D: 0.6238725
[12:06:16.510 D] Moving to next hop: <147.2, 14.8992, -592.7281> (Miner's Point) D: 15.02791
[12:06:18.109 D] Moving to next hop: <166.1398, 10.42092, -579.0557> (Miner's Point) D: 24.34398
[12:06:20.682 D] Moving to next hop: <179.2, 6.999207, -573.5281> (Miner's Point) D: 15.37156
[12:06:22.285 D] Moving to next hop: <217.6, -3.000793, -541.5281> (Miner's Point) D: 51.46909
[12:06:27.819 D] Moving to next hop: <218.9724, -3.330035, -538.0573> (Miner's Point) D: 4.329172
[12:06:28.242 D] Moving to next hop: <221.0524, -3.276546, -537.7554> (Miner's Point) D: 2.432143
[12:06:28.440 D] Moving to next hop: <275.2, -4.70079, -535.1281> (Miner's Point) D: 54.85775
[12:06:34.447 D] Moving to next hop: <275.2, -4.70079, -535.1281> (Miner's Point) D: 0.7937416
[12:06:34.482 D] Moving to next hop: <281.6, -5.400787, -528.7281> (Miner's Point) D: 9.419835
[12:06:35.444 D] Moving to next hop: <288, -5.70079, -522.3281> (Miner's Point) D: 9.810387
[12:06:36.477 D] Moving to next hop: <292.6331, -6.44205, -519.9826> (Miner's Point) D: 5.703681
[12:06:37.041 D] Moving to next hop: <300.9161, -7.4545, -506.2761> (Miner's Point) D: 16.56435
[12:06:38.816 D] Moving to next hop: <311.4643, -8.926426, -502.1923> (Miner's Point) D: 11.83895
[12:06:40.046 D] Moving to next hop: <312.2384, -9.003104, -501.216> (Miner's Point) D: 1.881227
[12:06:40.176 D] Moving to next hop: <313.2188, -9.087209, -498.9925> (Miner's Point) D: 3.090309
[12:06:40.445 D] Moving to next hop: <315.842, -12.38877, -487.02> (Miner's Point) D: 13.28155 <-- Died here

 

I rewrote the Chanko code to prevent it from stopping in the middle of a MoveTo to eat, but the problem still occurs reliably. I will run a test tonight where I disable all plugins to see if the problem still occurs. Its odd that it will pick right up from where it stops if I just nudge it a tiny bit using the keyboard - I don't have to restart the script.

 

Unfortunately, I am still experiencing this problem. Yesterday it occurred for a while (mostly when I was moving stealthed), but ultimately seemed to go away. Last night I was running a farming profile, looked at it this morning, and the toon was standing idle - just nudged it forward with the keyboard, and the script took off again.

 

Just wondering if mastahg has had a chance to look into this anymore. Can I assume all the 2D/3D mismatches have been fixed? If so, there must be some other race condition that is causing the code that makes the toon move to stop before the code that detects arrival is satisfied. This happens for me every time I run my spoiled nodes collection script.

 

It isn't getting fixed; you'll need to wait for the new navigator, which may be a while before it is released.