I don't have a full idea, I would suggest just piping out messages via store dispatches from the websocket
But the only downside there is that you can't trigger actions from the reducer, so you'd have to have the dispatcher aware of all possible messages (that could be a good or bad thing)
> Could we make the game server handle this and let the client only display it in response? Imagine a server-side logic like `while PlayerA is not ready OR PlayerB is not ready, push information message every X seconds" or something along those lines. Thoughts?