-
Notifications
You must be signed in to change notification settings - Fork 0
Open
Labels
help wantedsomething you can help withsomething you can help withusabilityux/devx problemux/devx problemz-project: enginesomething in the engine itselfsomething in the engine itself
Description
Currently, one needs to create a saved GameState
, then modify that state's player list (by creating a new list as well as a new state, since everything is readonly
/immutable), and then rehydrate that state into a GameContext
just to mutate the player list.
Possible Solutions
- An API that allows players to be added/removed from the
GameContext
dynamically- e.g.
instance void AddPlayer(PlayerRole, PlayerActor)
/instance void DropPlayer(PlayerID)
- e.g.
To Investigate
- Does the in-game engine recycle IDs? e.g. 16 people on one side, one gets breached out/leaves, another tries to join
- Yes, and you don't even need 16 people on one side: if e.g.
a0
gets breached out, the next person to join becomesa0
. (at least, in "game is empty" scenarios, needs some testing for whena1
still exists)
- Yes, and you don't even need 16 people on one side: if e.g.
Additional Notes
We shouldn't worry about the case of "a player leaves, then comes back" -- in-game doesn't allow this. If you're dropped from the game, you're out of that game.
Metadata
Metadata
Assignees
Labels
help wantedsomething you can help withsomething you can help withusabilityux/devx problemux/devx problemz-project: enginesomething in the engine itselfsomething in the engine itself