Demo: Autowalk

[#HB]

Originally Posted by qoaway

best strategy to autowalk is always execute A* in parts, so as a result you wont have to load the whole map and solves packet loss and server lagging problem

I see, so his way will definitely mess up on that condition.

[JellyBitz]

Originally Posted by sandsnip3r

I send the move request. Once the server responds that movement has begun, I calculate the time required to reach the destination.

Originally Posted by #HB

Wouldn't it fail to reach its destination if you had packet loss or server was lagging?

It's self explanatory, it won't fail even with lag.
Of course, time calculations must be accurate.

[sandsnip3r]

Originally Posted by #HB

Wouldn't it fail to reach its destination if you had packet loss or server was lagging?

You send a packet that says "move to pos x,y" and then the server responds with "character moving to x,y". If you have packet loss then I guess you'll just need to detect a timeout for the response from the server (which I have implemented). As far as lag, that's not really an issue. That's just gonna result in less fluid movement.

[bimbum*]

Originally Posted by sandsnip3r

You send a packet that says "move to pos x,y" and then the server responds with "character moving to x,y". If you have packet loss then I guess you'll just need to detect a timeout for the response from the server (which I have implemented). As far as lag, that's not really an issue. That's just gonna result in less fluid movement.

interesting you planning to publish it ?

[sandsnip3r]

Originally Posted by #HB

I see, so his way will definitely mess up on that condition.

"TCP guarantees delivery of data and also guarantees that packets will be delivered in the same order in which they were sent."

Though I've seen cases where the server seems to ignore my request. Maybe traffic throttling or something

Originally Posted by bimbum*

interesting you planning to publish it ?

The pathfinding algorithm is open sourced:

I've also open sourced a nice visualization tool

[#HB]

Originally Posted by sandsnip3r

You send a packet that says "move to pos x,y" and then the server responds with "character moving to x,y". If you have packet loss then I guess you'll just need to detect a timeout for the response from the server (which I have implemented). As far as lag, that's not really an issue. That's just gonna result in less fluid movement.

Aha, I got you. I thought you were calculating time after your request not after receiving a response.

[sandsnip3r]

Now I'm testing with more characters, more complex regions, and faster speed. It's still behaving flawlessly: