Chaining the 15 directions together with the semi-colon command binder, allows the tracking to work properly and not get lost. I tried it several times in both directions.Jor'Mox wrote: ↑Fri May 18, 2018 8:49 pmThe trick is, there shouldn't be any difference between entering the movements manually as compared to sending them via this particular function. What happens if you just spam in directions REALLY fast? Also, what if you have some other bit of code inputing a number of movement commands for you all at once (say, an alias that walks you along a particular path by sending the commands all at the same time)?
Also, I didn't expect that changing to the code I gave would change anything, it was definitely just a "here is a coding tip" sort of thing.
The print statement in the speedwalk function correctly shows the route, and the movement is there to get from A to B (15 moves) but the glowing tracker gets lost.