DLLarson
commented
1 year ago Unfortunately, I haven't thought of any straightforward way to achieve this yet.
Yes, it can be tricky. It's not unlike source control with GIT. We need a merge operation that can handle collisions (two players moving the same piece in two different move files for instance.) Resolving the collisions is where the difficulty arises.
The current approach either insists on game state perfection but allows the player to ignore state purity and apply the moves anyway. In essence, collisions are ignored--the last applied move file wins.
-Dale
wsu-cb
The current CB code checks that the initial state of a
.gmvfile matches the current state of the.gaminto which it is being loaded, and presentsCSelectStateDialogif the initial states don't match. However, that isn't ideal for games where players naturally take actions in parallel, for example, the programming phase of Roborally. In that case, either the players have to explicitly define a turn order, which slows down the game, or they have to effectively opt out of the error checking provided by the game state comparison (by using the "Use current game state" option ofCSelectStateDialog).It would be nice if we could find some middle ground so that games can proceed in parallel as much as possible while still performing error checking. Unfortunately, I haven't thought of any straightforward way to achieve this yet.