Change the way GPS servers work so high altitude configurations work.

The current way GPS works is the client broadcasts a "PING" message, and the servers respond with their location.

Now, say I had a GPS server at the height of 255, so I could take advantage of the maximum rednet distance of 384. Then I had a client at near bedrock level, but it's maximum distance would be 64.

Due to the current way the GPS protocol works, that setup will not work. The reason being that the client cannot send a "PING" message to the GPS server because the client is too low.

What I ask is, to change the way GPS servers work. Instead of acting on a clients ping, send out a message every 0.05 seconds containing the location of the GPS server. That way GPS clients can be at any height and they can still find their location.

Every GPS server spamming packets every tick? Can't think why that would be undesirable… :D/>/>

Fatal_Exception, on 07 October 2012 - 07:58 AM said:

Every GPS server spamming packets every tick? Can't think why that would be undesirable… :D/>/>

Ah, I forgot to mention that the delay should be configurable and there also should be command line options for the GPS server to turn this feature on or off.

chiloxsan, on 07 October 2012 - 07:54 AM said:

The current way GPS works is the client broadcasts a "PING" message, and the servers respond with their location.

Now, say I had a GPS server at the height of 255, so I could take advantage of the maximum rednet distance of 384. Then I had a client at near bedrock level, but it's maximum distance would be 64.

Due to the current way the GPS protocol works, that setup will not work. The reason being that the client cannot send a "PING" message to the GPS server because the client is too low.

What I ask is, to change the way GPS servers work. Instead of acting on a clients ping, send out a message every 0.05 seconds containing the location of the GPS server. That way GPS clients can be at any height and they can still find their location.

Have you actually tried the scenario you say doesn't work? When signals are transferred, it uses the maximum range of the sender and the receiver, so a computer at the world cap can not only send messages 384 metres, it can also receive all messages in the same range.

dan200, on 07 October 2012 - 09:55 AM said:

chiloxsan, on 07 October 2012 - 07:54 AM said:

The current way GPS works is the client broadcasts a "PING" message, and the servers respond with their location.

Now, say I had a GPS server at the height of 255, so I could take advantage of the maximum rednet distance of 384. Then I had a client at near bedrock level, but it's maximum distance would be 64.

Due to the current way the GPS protocol works, that setup will not work. The reason being that the client cannot send a "PING" message to the GPS server because the client is too low.

What I ask is, to change the way GPS servers work. Instead of acting on a clients ping, send out a message every 0.05 seconds containing the location of the GPS server. That way GPS clients can be at any height and they can still find their location.

Have you actually tried the scenario you say doesn't work? When signals are transferred, it uses the maximum range of the sender and the receiver, so a computer at the world cap can not only send messages 384 metres, it can also receive all messages in the same range.

Sorry Dan, but I did not try that scenario. I just had a quick skim through the GPS code and I assumed that the distance rule applied only to data being sent.

chiloxsan, on 07 October 2012 - 10:06 AM said:

dan200, on 07 October 2012 - 09:55 AM said:

chiloxsan, on 07 October 2012 - 07:54 AM said:

The current way GPS works is the client broadcasts a "PING" message, and the servers respond with their location.

Now, say I had a GPS server at the height of 255, so I could take advantage of the maximum rednet distance of 384. Then I had a client at near bedrock level, but it's maximum distance would be 64.

Due to the current way the GPS protocol works, that setup will not work. The reason being that the client cannot send a "PING" message to the GPS server because the client is too low.

What I ask is, to change the way GPS servers work. Instead of acting on a clients ping, send out a message every 0.05 seconds containing the location of the GPS server. That way GPS clients can be at any height and they can still find their location.

Have you actually tried the scenario you say doesn't work? When signals are transferred, it uses the maximum range of the sender and the receiver, so a computer at the world cap can not only send messages 384 metres, it can also receive all messages in the same range.

Sorry Dan, but I did not try that scenario. I just had a quick skim through the GPS code and I assumed that the distance rule applied only to data being sent.

Surely trying it out would take less time than writing a thread claiming something doesn't work when it does? Closing this topic