Is it normal that when I "turn" the camera stays still? Makes it quite unplayable for me (I tried both "Free camera" enabled/disabled, it didn't change anything)
Really cool to be able to test this directly, thanks for setting it up.
I found something I would qualify as a bug: if you click on the right of any text, the cursor is placed at the beginning of the line, where I would expect to have it at the end.
boardgame.io only runs game logic on the server, and it censors the State just before sending it to each client. This strategy makes the UI feel less responsive, but it keeps things simple.
The Swords and Ravens blog post recommends resolving actions on the client when they don't require secret information, but resolving other actions on the server. You'd also need to resolve actions on the server when they involve RNG.
I don't recommend resolving actions on the server in any situation:
For actions that require secret information, you would filter the actions sent to the client of any secret information and make sure the code handling the action can handle both the action and the filtered actins.
For actions involving RNG, make all randomness rely on a seed. This seed would be stored server-side and passed along the action when sent to the client. This makes sure the clients can deterministically reproduce the update.
Thank you for this comment. I was assuming that meteor died some time ago when mongo was getting a hiding and Apollo/graphql came on the scene. I'm glad you pointed this out (that it isn't dead) and that infact they are releasing v3 soon (from a quick website scan)
Yes v3 is very welcome, v2 only works on outdated Node versions and package compatibility is becoming an issue...
It's definitely not a ghost town, but the community feels smaller and pace is a little slow.
I'm a bit in the same boat, I found nothing that can replace it.
