1. A description of the suggestion

/*

 * Obtains the route associated to the WebWalkEvent

 * @return All positions on the current WebWalkEvent's route

 */

public LinkedList<Position> getRoute();

There used to be INodeRouteFinder#route methods which would return a List<IDirection> and we could just get the positions from those

 

2. How will this suggestion impact scripters and/or botters?

Ability to generate paths without having to use the default WebWalkEvent. There is nothing wrong with the current WebWalkEvent but when we are walking the same path (eg: from trees to bank when training wc) we could create our own WebWalkEvent to insert some more diversified input as the default one just interacts with the next position, doesn't ever seem to missclick, whether it uses the minimap or not is based on things that make sense (humans don't make sense). We could add some random interactions on that path as that's what most humans do, they have random input that no one can understand (not even jagex)

 

 

Observe the behavior above: it doesn't make sense - it's humanlike. The player is so lazy he won't even move his mouse while walking and will randomly switch between using the minimap or clicking visible tiles around him. He doesn't click once every 5 positions or so which makes him inefficient, he may even interact with the same tile 2 or 3 times and also interact with various camera space entities while walking (adding friends, drinking potions, eating food, joining chats, changing settings or just randomly clicking interfaces like a spastic)

 

This behavior can be implemented right now only by using predefined paths which makes it impossible to consider a "general solution" to most problems we have to solve through a script

 

3. Post any examples such as code or pictures to supplement your description (optional) ^

It's not a list of positions, it's a list of directions. You're forgetting that the direction can be "teleport", "interact with object", "talk with npc", etc.

It's not a list of positions, it's a list of directions. You're forgetting that the direction can be "teleport", "interact with object", "talk with npc", etc.

I didn't mention interactions because that would be pretty much the route methods we had in INodeRouteFinder that returned a list of IDirection. I guess the interactions would be useful too but that would mean exactly what we had before the webwalking update with DirEntity and DirTile. It's probably better resource-wise that scripters don't have access to instantiating INodeRoutefinder anymore but if there is an instance maybe we could have access to a few of its methods in the Walking class?

I didn't mention interactions because that would be pretty much the route methods we had in INodeRouteFinder that returned a list of IDirection. I guess the interactions would be useful too but that would mean exactly what we had before the webwalking update with DirEntity and DirTile. It's probably better resource-wise that scripters don't have access to instantiating INodeRoutefinder anymore but if there is an instance maybe we could have access to a few of its methods in the Walking class?

 

Certain areas and destinations require the interactions. Even if you individually know that the path does not require it, I'm trying to keep the API manageable. This was a huge issue when the decision was made to have web walking completely open in the beginning. I believe the IDirection class is hidden right now, I'll check in a bit.