rhdemo / 2021-frontend-wss Goto Github PK

Currently a game reset triggers a flow that calls initialisePlayer again. This works, but isn't ideal since the client has no idea what's happened. Instead we should handle this gracefully, and send a message to notify the client that the game has been reset and that they need to refresh or click the "new game" button.

CC @kylebuch8 WDYT?

When an attack is processed and stored we should add a timestamp to it. This can be used to reliably determine attack order and for metrics.

The score for a player will be computed using a separate service so we should remove this field from the player model.

A player has a limited time window to attack. This is enforced by the frontend code. If the frontend code randomly selects an attack for the player, then we need to know.

To achieve this we will add a human property to the attack payload. If it is set to false, then we know that the attack was not the result of the user, but instead randomly chosen by the client code.