aboutsummaryrefslogtreecommitdiff
path: root/protocol.md
diff options
context:
space:
mode:
authormetamuffin <metamuffin@disroot.org>2024-06-21 12:39:50 +0200
committermetamuffin <metamuffin@disroot.org>2024-06-23 19:26:47 +0200
commit1ab1fd8cc03678ac180673884eff098821bcecd2 (patch)
treefc4d4668628dd4cd45b7d57c4efe74fec135ecba /protocol.md
parent607b3509f6bfd7d8ca39b12d01a6428689bb3ded (diff)
downloadhurrycurry-1ab1fd8cc03678ac180673884eff098821bcecd2.tar
hurrycurry-1ab1fd8cc03678ac180673884eff098821bcecd2.tar.bz2
hurrycurry-1ab1fd8cc03678ac180673884eff098821bcecd2.tar.zst
refactor movement
Diffstat (limited to 'protocol.md')
-rw-r--r--protocol.md7
1 files changed, 7 insertions, 0 deletions
diff --git a/protocol.md b/protocol.md
index 7f86df7b..093bce58 100644
--- a/protocol.md
+++ b/protocol.md
@@ -19,3 +19,10 @@ The protocol schema is defined in [`protocol.ts`](./test-client/protocol.ts)
Collisions are handled by the clients. Whenever to players collide the player
with the greater PlayerID is responsible for updating their own momentum and
sending a packet to update that of the other player.
+
+## Movement
+
+Movement is handled mostly client-side. Therefore it is implement three times:
+- In the test-client: [movement.ts](./test-client/movement.ts)
+- For customers in the server: [movement.rs](./server/src/customer/movement.rs)
+- In the client: [movement.rs](./client/scripts/player.gd)