Open gnibeda opened 2 years ago
Hi @gnibeda, thanks for pointing this out!
This is indeed a problem with the current architecture. A way to solve it would be to force a maximum number of movement actions per second or a minimum delay between actions and drop out the others. Since we are doing client-side prediction, we would also need to make sure they are dropped/ignored on the client as well.
I'll keep this issue open as a next to do.
Due to how movement implemented on client and server, there is possibility to hack movement speed by sending additional messages to the server. You can change client code adding loop to increase movement speed 20x times:
Code can be simply moddified in chrome browser during runtime in devtools.