"
qwave wrote:
"
Let me help you than, if you don't trust the client. Everything that is sent to you must be verified and corrected as needed. Therefore, if the client said that it moved from x to y via path B, but the server says that is impossible and you are now stuck on obstacle C. The client and server are now out of sync. The client now has to be corrected. Please elaborate on how your system prevents this and how this is not desync.
If the server says that is impossible, then yes, the client is desynced. Why is that difficult to understand?
What the hell do you think causes desync now? If your ENTIRE proposal is a solution to desync and you can still desync exactly how has your proposal solved anything?
|
Posted byTantabobo#6200on Nov 20, 2013, 1:32:43 AM
|
"
You can't simply say that it will have no impact based on your assumptions of how things work. Without testing of some sort you have no idea how long it will take or what it will entail.
GGG has stated how this works. Read their posts.
|
Posted byqwave#5074on Nov 20, 2013, 1:33:42 AM
|
"
What the hell do you think causes desync now? If your ENTIRE proposal is a solution to desync and you can still desync exactly how has your proposal solved anything?
Further proof that you haven't even read or understood any of it.
Last edited by qwave#5074 on Nov 20, 2013, 1:34:45 AM
|
Posted byqwave#5074on Nov 20, 2013, 1:34:08 AM
|
"
qwave wrote:
"
Let me help you than, if you don't trust the client. Everything that is sent to you must be verified and corrected as needed. Therefore, if the client said that it moved from x to y via path B, but the server says that is impossible and you are now stuck on obstacle C. The client and server are now out of sync. The client now has to be corrected. Please elaborate on how your system prevents this and how this is not desync.
If the server says that is impossible, then yes, the client is desynced. Why is that difficult to understand?
Well it means your client can cheat desyncs due to collisions, the client can create a state which the server deems as correct because it falls on a collision, and because the client is trusted this is allowed
|
Posted bydeteego#6606on Nov 20, 2013, 1:35:04 AM
|
"
Well it means your client can cheat desyncs due to collisions, the client can create a state which the server deems as correct because it falls on a collision, and because the client is trusted this is allowed
The client is not trusted. The server still validates all input in the same way that it currently does. It cannot 'cheat desyncs'. That doesn't even make sense.
Last edited by qwave#5074 on Nov 20, 2013, 1:36:31 AM
|
Posted byqwave#5074on Nov 20, 2013, 1:36:04 AM
|
"
qwave wrote:
"
Well it means your client can cheat desyncs due to collisions, the client can create a state which the server deems as correct because it falls on a collision, and because the client is trusted this is allowed
The client is not trusted. The server still validates all input in the same way that it currently does. It cannot 'cheat desyncs'. That doesn't even make sense.
No it is trusted, at least when dealing with RNG
|
Posted bydeteego#6606on Nov 20, 2013, 1:37:30 AM
|
|
Can you guys wait for the next GGG answer instead of arguing pointlessly? It seems clear to me that the OP has somewhat of an idea of what he's talking about, or else the discussion would have ended way before. So let GGG decide if it's worth something or not?
That would be much more constructive than the last like 4 pages which were mainly double posts and arguing.
IGN: TimeForSpectralThrow / iLikeShockNova Last edited by Daxtreme#7537 on Nov 20, 2013, 1:38:29 AM
|
Posted byDaxtreme#7537on Nov 20, 2013, 1:38:11 AM
|
|
It's not trusted at ALL, ESPECIALLY not with RNG.
|
Posted byqwave#5074on Nov 20, 2013, 1:38:23 AM
|
|
Daxtreme: Good point. I need to stop replying to people that have clearly not read or understood the main post.
|
Posted byqwave#5074on Nov 20, 2013, 1:39:31 AM
|
"
qwave wrote:
It's not trusted at ALL, ESPECIALLY not with RNG.
Then your system won't work
|
Posted bydeteego#6606on Nov 20, 2013, 1:40:03 AM
|
