if (!Settings.location.getArea().contains(myPosition())) { //If not in woodcutting area
  log("Left area, heading back...");
  targetPosition = Settings.location.getTreePosition(); //Get area centre position
  localWalker.walk(targetPosition, true); //Move to position
  break;
}

Sometimes when I'm walking, the player doesn't stop on the exact target location but nearby.

When this happens the player doesn't want to move anymore.

As you can see in the code sample, I'm catching this however the player doesn't start moving anymore on calling walk.

Edited December 31, 201510 yr by lisabe96

if (!Settings.location.getArea().contains(myPosition())) { //If not in woodcutting area  log("Left area, heading back...");  targetPosition = Settings.location.getTreePosition(); //Get area centre position  localWalker.walk(targetPosition, true); //Move to position  break;}

Sometimes when I'm walking, the player doesn't stop on the exact target location but nearby.

When this happens the player doesn't want to move anymore.

As you can see in the code sample, I'm catching this however the player doesn't start moving anymore on calling walk.

what client version are you using

what client version are you using

2.4.25

2.4.25

 

Use the new walking API in the latest client version

 

2.4.25

Right now the devs are re-doing most if not all of the walking in the API right now, so the transition is pretty rough. Its a difficult thing to debug so patience from the users is VERY appreciated. It should be back to business by Monday

I worked around it with some checks right now,

doesn't hurt to have those anyways, even if the system would be working smooth

Edited January 1, 201610 yr by lisabe96