Chris Swithinbank

There isn’t, although it might be possible to adapt [the debug panel logic][debug]. You can `import { CreateGameReducer } from 'boardgame.io/internal'`, get `client.initialState`, and then replay each log action as...

@Korla The way boardgame.io queues events, this behaviour is expected to me: 1. A move function is called, calling an event. 2. The `onMove` hook is triggered (immediately after the...

Once all the events have run, do you need to dispatch a further event or are you trying to do something else with the result?

It might not be all that helpful to think about the reducer directly. The library uses Redux internally, but it isn’t necessary to know that to use the boardgame.io API....

@nukeop Check out the discussion here: https://github.com/boardgameio/boardgame.io/discussions/903 There’s a working prototype linked towards the end that does what you’re suggesting for `client.moves`, but it requires a few hoops to work...

@pardahlman Yes, there are already some fields that track past/future state when using the `next` and `revert` options with `setActivePlayers`, so something similar could be used for this too. A...

Thanks for the bug report! Our React client is currently incompatible with React 18 unfortunately, we need to update it. For now you should be able to downgrade to React...

I haven’t had a chance to dive into React 18 enough to be sure, but I wonder if there’s some deprecated method used in the `WrappedBoard` class we return from...

We use [`koa-body`](https://github.com/dlau/koa-body) to parse the body of POST requests, which defaults to a 1MB JSON size limit ([source](https://github.com/dlau/koa-body#options)). Currently we use `koa-body` with no configuration in the Lobby API....

Hi @shaoster — sorry it took me so long to find time to give you some feedback. In general this all sounds solid. If I follow, we’d basically be formalising...