Linus K.

> I thought about this when the change was suggested, but I don't think this would be possible. Not because I looked into the code, but because a pleco board...

I would be also for it. That way we also keep the history in addition to the state. We could probably just use a pgn where we save a fen...

I think I mentioned that above already a bit. That is because of the intention of a server-client-model. game_scene is probably more client, client, ui in this case. I'm generally...

Tbh, I wrote it 2 years ago, so I'm not really an expert on it anymore as well. Since I never got to actually do multiplayer, the protocol layer is...

Edit: Btw, this message was out of order again. Didn't the the above response then writing this. Sorry I didn't noticed your reply before @addcninblue (my phone only showed me...

> I also am not 100% about making ChessUpdate.Board a prerequisite for ChessUpdate.PlayerMoved since it's possible for messages to arrive out of order and hence ending up with a board...

Regarding the tests, I'm on that rn. For now I guess just basic `cargo check`. Also found a nice tool called [audit-check](https://actions-rs.github.io/#audit-check). Will probably update some dependencies to get rid...

Should be done. Apologies for commit spam on the master. Wanted to get this done fast and not drag along for a while. Also a bit rusty on GH Actions...

As far as the bot concerned, that only cares that it has the current board state and knows which player it is moving. I think so far we only need...

This seems like a nice step already. I'm gonna try this in a sec as I need to work out the linuxserver to vanilla docker changes to keep everything mounted...