charleswinter / hurley

hurley

hurley's Issues

SDL2/SDL_image.h: No such file or directory

sandy@debian:~/repos/hurley$ make
gcc -g -Wall -Iinclude ./src/sql_driver/adapter.c ./src/core/init.c ./src/core/main.c ./src/core/loop_handler.c ./src/images/loader.c ./src/sock_server/server.c ./src/hero/init.c ./src/hero/movement.c -o hurley -lSDL2 -lSDL2_image
./src/core/init.c:4:28: fatal error: SDL2/SDL_image.h: No such file or directory
#include <SDL2/SDL_image.h>
^
compilation terminated.
./src/images/loader.c:4:28: fatal error: SDL2/SDL_image.h: No such file or directory
#include <SDL2/SDL_image.h>
^
compilation terminated.
Makefile:10: recipe for target 'build' failed
make: *** [build] Error 1

Server Client Comms

Phase e.g. Movement, shooting

1. Client asks server for next phase start time
2. Server replies with a fixed time e.g. 17:10:23 UTC
3. Client subtracts current time from this time, and starts a timer
4. Once client timer finishes, movement selection is unlocked for the player and the phase begins.
5. Once movement selection is unlocked, a second timer is started to display how long a player has to make their selection (~20secs)
6. Each time a player right-clicks on the map, a line is shown showing their path, and the server is informed of their intention. (Later we can show players the selected path of their teammates!
7. Once the client timer is finished, the client tells the server.
8. The server waits until all player timers are finished.
9. The server takes the last posted movement for all players, calculates where they actually moved (collisions if two players selected the same space for example) and updates its internal model.
10. a. Meanwhile, clients wait a fixed time, say 2 seconds and then ask the server for the latest positions.
    ⁃ b. The reply for the request of step 7 contains the updated player steps.
11. The server replies and the movement is drawn for the player.

---- REQUESTS ----

GET - next phase start time <- a fixed point in time
POST - initial player movement selection. <- 201 OK
PUT - updated player movement selection. <- 203 Updated
--- EITHER ---
POST - client timer has finished <- 200 OK
GET - updated player locations <- a big piece of JSON with all paths and location
--- OR ---
POST - client timer has finished <- a big piece of JSON with all paths and location