When the spreadsheet was created by thymaro#5985, there were columns for beta1, beta2, release1 and release1.X with the values: confirmed and needs check.
I removed the columns beta2, release1 and release1.X, because they are currently not in use, take up visual space in the spreadsheet, and can easily be added later, when the need for them arises.
Currently the beta1 column is misused to mark which columns need to be verified by other users, and not if it is contained within the beta (they all are currently included by definition, except for mistakes).
While the idea is good to track which entries exist in which version of the game, it's not going far enough and isn't great to maintain.
When items are removed or added from the game, a simple confirmed or missing is enough.
When items are moved to another location, they might get marked as missing and is marked as new in the new location.
There is no way to figure out what has changed between versions.
There is only usable data for the most recent game version.
What I have in mind is having one sheet per game version that contains all data that exists in that version. Data that is missing is removed in the new sheet, new data is only added to the new sheet and changes can be made to all fields in the new sheet (except for the ID).
When a new game version is released, you just copy the most recent sheet and use that as the master.
Contra: ID generation need to be unique over all sheets. The same ID in different versions refers to the same game object.
This would also allow the interactive map to offer a view to older game version, where it just uses an older sheet as a data source, reinitialize all markers and changes the baseLayer to load different map tiles (images).
When the spreadsheet was created by thymaro#5985, there were columns for
beta1,beta2,release1andrelease1.Xwith the values:confirmedandneeds check.I removed the columns
beta2,release1andrelease1.X, because they are currently not in use, take up visual space in the spreadsheet, and can easily be added later, when the need for them arises.Currently the
beta1column is misused to mark which columns need to be verified by other users, and not if it is contained within the beta (they all are currently included by definition, except for mistakes).While the idea is good to track which entries exist in which version of the game, it's not going far enough and isn't great to maintain.
confirmedormissingis enough.missingand is marked asnewin the new location.What I have in mind is having one sheet per game version that contains all data that exists in that version. Data that is missing is removed in the new sheet, new data is only added to the new sheet and changes can be made to all fields in the new sheet (except for the ID).
When a new game version is released, you just copy the most recent sheet and use that as the master.
Contra: ID generation need to be unique over all sheets. The same ID in different versions refers to the same game object.
This would also allow the interactive map to offer a view to older game version, where it just uses an older sheet as a data source, reinitialize all markers and changes the baseLayer to load different map tiles (images).