Game Architecture Roundtable (Saturday)
- Worked well: All changes to game state go through an "Arbiter." Arbiter contains a router that has different versions for single and multiplayer. Can still query data by going to the corresponding subsystem directly.
- Worked well: sniffing message stream instead of modifying all places where effect generated: simplifies architecture.
- Worked well: System A stores foos. System B can ask system A to store some extra data (opaque to A) with each foo.