A client-server message containing instructions for manually driving a robot.
Indicates the game is finished and should be restarted
Indicates the game is waiting for a user to respond
A two-way message indicating a game has been interrupted.
Note this does not include the game ending as a part of the normal flow of moves.
A server-client message used to tell player two a game has started.
A two-way message containing a single move.
A server-client message defining the current position of a game. Used to allow clients to reconnect.
A client-server message used to register a websocket with the server.
A client-server message used to update a variable (like rotations per square) on a robot.
A message sent from server to all clients for updating the robot simulator.
Generated using TypeDoc
Defines messages sent across web sockets between the server and the client (and/or the client and the server).
To add a new message, first add a member to MessageType, then create a corresponding class which extends
Message
and implements thetype
method and thetoObj
method. Finally, add a corresponding case toparseMessage
in./parse-message
.