Recurse: W4D1
Recurse - W4D1
Haven't checked in most of last week.
The theme of a game jam started within Recurse is "Lost Signals" -- building on some work from "impossible day", I am going to focus on getting a good framework setup for multiplayer connectivity. I want it to be robust as the game reloads (due to HMR development), in addition to having resiliency when a websocket connection breaks.
Here's a snapshot of where I'm currently at with the project
Here is a quick demo of what works, as-is:
Space invaders demo at end of day W31D1
Unfortunately, this one is not online yet, as it requires a websocket server up to work!
Here are some cool 'lost signals connections' that do work:
- when a client disconnects or refreshes, it can reconnect to the active session
- when the server closes, it dumps a JSON snapshot of the currently running games so they can be restore and resumed
- ← Previous
Recurse: W3D1