You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The game should save a copy of the move history as a series of (username, move) tuples. That's all we would need in order to replay the game.
Saving (username, move, state) tuples would mean the entire game could be viewed without having the engine replay the game. That might better.
I think this should be a field in NDB outside of game and state ... a list of json objects where each object is a {'user': mitch, 'move': 'go north', 'state': }. Obviously then we'll need to store the starting state as well.
The text was updated successfully, but these errors were encountered:
The game should save a copy of the move history as a series of (username, move) tuples. That's all we would need in order to replay the game.
Saving (username, move, state) tuples would mean the entire game could be viewed without having the engine replay the game. That might better.
I think this should be a field in NDB outside of game and state ... a list of json objects where each object is a {'user': mitch, 'move': 'go north', 'state': }. Obviously then we'll need to store the starting state as well.
The text was updated successfully, but these errors were encountered: