docs
This commit is contained in:
parent
8c649b3be6
commit
823f1cfafe
12
README.md
12
README.md
|
@ -16,14 +16,14 @@ For eg, having a chess serialization that allows for 2 kings is _okay_, since th
|
|||
|
||||
|Game|State|Partial State|Transform|RPC|Game Engine|
|
||||
|---|---|---|---|---|---|
|
||||
|Sushi Go|:white_check_mark:|||||
|
||||
|Sushi Go|✓|||||
|
||||
|
||||
Meanings:
|
||||
|
||||
**State**: Support to serialize the current state of any game. Just the state specification.
|
||||
**Partial State**: State specification for partial state (if any). Just the partially observable state that the players would get.
|
||||
**Transform**: Code to transform the state -> partial state given other parameters.
|
||||
**RPC**: Code to send state transforms over the wire. Or moves
|
||||
**Game Engine**: Code for the server
|
||||
- **State**: Support to serialize the current state of any game. Just the state specification.
|
||||
- **Partial State**: State specification for partial state (if any). Just the partially observable state that the players would get.
|
||||
- **Transform**: Code to transform the state -> partial state given other parameters.
|
||||
- **RPC**: Code to send state transforms over the wire. Or moves
|
||||
- **Game Engine**: Code for the server
|
||||
|
||||
Only the first 2 are covered in the project.
|
Loading…
Reference in New Issue