File Details
MonolithDKP-1.6.3.zip
- R
- Nov 23, 2019
- 415.31 KB
- 80.7K
- 1.13.2
- Classic
File Name
MonolithDKP-1.6.3.zip
Supported Versions
- 1.13.2
- This update contains no new features or updates. It is a preparatory update aimed at officers. 2.0 will feature an extensive overhaul of the system, how it keeps records and broadcasts them. It is crucially important that migration instructions are followed to prevent duplicate data leading to dramatically incorrect databases. In the next update, Officers will be prompted with instructions to migrate their current tables. This can ONLY be executed by ONE officer. All remaining officers will be prompted to delete their data to accept the migrated data from the selected migrating officer. Please coordinate accordingly over the next few days to avoid issues. Once the data is broadcasted, if incorrect, is difficult to correct.
-When an officer chooses to migrate, the GM public note will be updated with that officers name to indicate to all other officers that the database has already been migrated, asking them if they would like to delete their current data (PLEASE backup your SavedVariables file prior, just in case), and instructing them to get a broadcast from that officer to complete the process. Forcing a sync can be completed by clicking the table status indicator on the bottom left of the main GUI. Once this migration has occurred, all data is persistent. In the event the migration gets somehow bunked, the only way to revert is to have all officers that have received broadcasts delete their saved variables file and put a backed up copy simultaneously. This must be done simultaneously because if you delete it and log in, if an officer has the new indexed tables, they'll simply broadcast it back to you immediately. Once migration has completed for all officers, the GMs note indicating the migrating officer can be deleted. ONLY do this once you're certain all officers have the new tables.
-Additionally, all members must update to 2.0 or later. Older versions will not be compatible. View the YouTube video linked below for a quick rundown on how migration must work to prevent any problems moving forward.