Upgrading
Updating the kit #
- Back up your project (or commit it to version control).
- Import the new version from the Package Manager (My Assets) over the old one. Keep every file ticked.
- Read the changelog (
CHANGELOG.mdnext to the kit's README, and the Changelog page of the online docs) for anything marked Upgrade note.
Your own data is safe: pieces you made, your settings and your scenes live outside the kit's folder
(Assets/AllInOneRuntimeBuildingKitData/ by default), so an update never touches them.
What the kit promises between versions #
- Saves keep loading. Save files carry a format number. A newer kit reads older saves; pieces whose definition was removed are skipped and named in the load report, never silently lost.
- Piece IDs never change. Saves and multiplayer name pieces by their ID, not their name or file, so you can rename and move Piece Definitions freely.
- Your code keeps compiling. Public types, members, serialized fields, menu items and script GUIDs are recorded at each release and an automated test fails if any of them is removed or renamed. Anything that has to change gets a replacement first and the old name keeps working (marked obsolete) until the next major version.
- Minor and patch updates are free for existing owners.
Moving to 1.0.0 #
1.0.0 is the first release on the Asset Store, so there is nothing to migrate.
A note on removed files #
Importing a .unitypackage never deletes files. If a version ever stops using a file, it stays harmless in your
project; you may delete it when the changelog says so.