Author Topic: Saving while lagging  (Read 386 times)

i've noticed that the saving process haults while having lag, but since saving is client sided, why should it? (requesting why, suggesting it be fixed?)
this would be useful for when server is crashing or somethink and you need to save real quick :D (if fixed)

It wouldn't work, because when you save, you request brick info from the server.  If the server is lagging, there is no way for it to process your request for a save.  The only way this would be possible would be if your computer had a constantly updated set of the brick locations in its RAM.  But this would be just like you hosting the server yourself, minus the map and player connections.

It wouldn't work, because when you save, you request brick info from the server.  If the server is lagging, there is no way for it to process your request for a save.  The only way this would be possible would be if your computer had a constantly updated set of the brick locations in its RAM.  But this would be just like you hosting the server yourself, minus the map and player connections.
No.
It's because events need to be grabbed from the server.
Your client already has all the brick info; Notice you must've seen a brick to be able to save it.