When we will have storing of fights (game sessions), they would contain references to map, protobase entities and players commands, and in case we would make any sort of changes to protobase /maps then we could have desync of replaying the fights (in case of static data), so we would need to have some sort of history, where we know which kind of game data setup snapshot was used for particular game. We could store some version system (maybe additional column with version for each entity) and store for each game session a version number and obtain data for particular version (or the one which is closest older to needed version)
Could be done in sync with hash storing issue #9 and provide clients values for comparison of actual versions and earlier versions if needed for restoring saved games/replays
When we will have storing of fights (game sessions), they would contain references to map, protobase entities and players commands, and in case we would make any sort of changes to protobase /maps then we could have desync of replaying the fights (in case of static data), so we would need to have some sort of history, where we know which kind of game data setup snapshot was used for particular game. We could store some version system (maybe additional column with version for each entity) and store for each game session a version number and obtain data for particular version (or the one which is closest older to needed version)
implementation is a matter of discussion