This issue is only here to extend LittleBigRefresh/Refresh#864 to here aswell.
The worker would probably "only" have to take all assets from the main data store which might include keys or level links (levels, plans, level chunks?), deserialize them, look for any SlotID used by a key/level link to reference a user level, and if there are any such SlotIDs, bump their IDs and reserialize the changed asset into a new file. Something to keep in mind is that if we update one such asset, we would also have to update all references to this asset in all assets which depend on it, and then reserialize those aswell.
This issue is only here to extend LittleBigRefresh/Refresh#864 to here aswell.
The worker would probably "only" have to take all assets from the main data store which might include keys or level links (levels, plans, level chunks?), deserialize them, look for any
SlotIDused by a key/level link to reference a user level, and if there are any suchSlotIDs, bump their IDs and reserialize the changed asset into a new file. Something to keep in mind is that if we update one such asset, we would also have to update all references to this asset in all assets which depend on it, and then reserialize those aswell.