WB plugin to migrate also? Or migrator component? How would it active deactivate? Game mode dev decides their user should migrate from json to bin files instead and wants it to happen automatically after mod update?
we could do this in the persistence manager. add a function to get load context and one for save context, they can be different on migrate.
force load all für migration? -> must do this.
->>>> if we need to load all anyway, maybe instead we should grab all available save types we know from attr registration, load them, not spawn but save into target db context
Startup parameter or explicit function to call via script. --migrate --migrate-from="sourceDb" --migrate-to="targetDb"
Migrate(dataSourceFrom, dataSourceTo)
Load from old db, and save to new db, so all goes through script for upgrades and saved in the latest version the
database source setting in the config to add an entry called "MigrateFrom" and then its read from there and saved into the db given as an option to save and load to normally
WB plugin to migrate also? Or migrator component? How would it active deactivate? Game mode dev decides their user should migrate from json to bin files instead and wants it to happen automatically after mod update?
we could do this in the persistence manager. add a function to get load context and one for save context, they can be different on migrate.
force load all für migration? -> must do this.
->>>> if we need to load all anyway, maybe instead we should grab all available save types we know from attr registration, load them, not spawn but save into target db context