Migration from v1

In version 1 of the system, all settings were stored in a MonoBehavior which was located in a scene. Users would have to make this object as DontDestroyOnLoad to keep it alive across scenes, and it was generally cumbersome to keep it up to date – and many users misunderstood the setup and added multiple such objects to the scene.

To remedy this situation, version 2 uses a ScriptableObject to hold all the settings for the DebugSystem. That makes the system much easier to set up, keep it up to date, and makes working with it much more streamlined.

When updating from version 1, the old BugTrackingManager class will still work, but its UI will display the migration wizard. Migration is as simple as pressing a single button – a new ScriptableObject in your Resources folder will be created and all settings will be transferred. If they haven’t been already, all settings will also now be encrypted at the same time.

After the migration you may remove the BugTrackingManager from your scene.

Was this page helpful?