rorykoehein / warx Goto Github PK

• work with steps/game loop on the server
• server to collect all client input for a step, don't process yet
• server to process all client input for each loop (calculate new game state)
• server to send new game state (or diff?) to client every ~50ms
• client to render every 16ms, render ~75ms in the past
• client to ignore any message that arrives after a newer message
• use linear interpolation to position the object along the path (could possibly use css transitions for this)

https://www.slideshare.net/MarioGonzalez15/realtime-html5-multiplayergameswithnodejs-7868336/22-ulliSo_we_set_up_a
https://github.com/lance-gg/lance/blob/master/src/ServerEngine.js

• drop bomb at the position of the player
• make radius so that player can just escape
• high reload time or as power-up

• minify the keys and values? direction becomes d, left becomes l, etc.
• Use something else than json? msgpack

• how to determine admin user?
  • save hashed admin password in ENV
  • create command line tool to generate password hash

features:

• kick players
• add/remove bots
• send messages
• reset game
• change rules

This application shares some actions between server and client, actions can be
marked as any of these:

• client-to-client actions (i.e. opening a panel)
• client-to-server actions (i.e. connect-request, move request)
• server-to-client actions (i.e. new connection, player moved)
• server-to-server actions: update server state without directly sending to client(s)

The server should dictate these types to the client somehow.

Actions which are client-to-server or server-to-client will also be dispatched
at its origin. This means actions must be unique between client and server.
This should be tested somehow (todo), possibly at runtime.

Make servers call home to central hub, so players can join different servers with different rules/config

• only listen to keydown and keyup
• fire START_MOVE on keydown and END_MOVE on key up, with direction
• let a timer on the server and client take take of the individual steps
• possibly on END_MOVE let the server correct the clients position (in case out of sync)

Try Lerna

• 'sign in' with username
• add messages

And scale world to screen

• temp invisibility
• faster reloads until dead
• fast movement?
• larger explosions?

• general cleanup before publishing
• make sure no api keys (circleci?) or other stuff is public

• toggle scoreboard on top of screen
• show username, kills, deaths, time on server

• fire rockets which explode on impact of player, bomb or impact of walls

• fix positioning/layout (login, game, info, choose server screens, score screens)
• full screen mode
• mobile controls
• info/score buttons
• PWA: service worker, add to home screen

Probably RxJS or Sagas

turn on/off

sounds:

• shoot
• spawn
• dead/hit
• enter game?
• move?
• first place?

on server and client?