aboutsummaryrefslogtreecommitdiff
path: root/protocol.md
blob: 286262008561d7aaa690687d670ddf4e2408d577 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
<!--
    Hurry Curry! - a game about cooking
    Copyright 2024 metamuffin

    This program is free software: you can redistribute it and/or modify
    it under the terms of the GNU Affero General Public License as published by
    the Free Software Foundation, version 3 of the License only.

    This program is distributed in the hope that it will be useful,
    but WITHOUT ANY WARRANTY; without even the implied warranty of
    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
    GNU Affero General Public License for more details.

    You should have received a copy of the GNU Affero General Public License
    along with this program.  If not, see <https://www.gnu.org/licenses/>.

-->

# Hurry Curry! protocol

The protocol schema is defined in [`protocol.ts`](./test-client/protocol.ts)

1. Connect to the server via ~~TCP (on port 27031) or~~ WebSocket (on
   port 27032) and send/receive json on individual lines / text messages.
2. Wait for `init` packet.
3. Send the join packet with your username.
4. The server will send the current game state:
   - `data` once for setting important look-up tables
   - `update_map` for every tile
   - `set_tile_item` for every item on a tile
   - `add_player` for every player in the game
   - `set_player_item` for every item held by a player
5. Run the game loop
   - Send your position every 40ms.
   - Send `interact` when the player interacts with a tile. Make sure to set the
     `edge` parameter consistently.
   - Receive packets
6. The Game ends. The server will remove all players and tiles. Then continue at
   step 4.

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 implemented 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:
  [controllable_player.gd](./client/player/controllable_player.gd)