Notifications
Clear all
Topic starter
06/06/2026 8:53 pm
Hello, what is the recommended workflow for migrating one's project to a newer version of the MSH framework?
If there is none, it would've been good to be something to consider for the future updates, since it would be beneficial for most of the users.
I've tried to create my own classes by deriving from MSH, but after updating to 0.4, it's all broken. I need to debug and fix most of my blueprints.
It's that big of a hassle, so I'd rather stay on an older version or just wait for the 1.0 release before starting to use the framework for my project.
06/06/2026 10:07 pm
Hello, what is the recommended workflow for migrating one's project to a newer version of the MSH framework?
If there is none, it would've been good to be something to consider for the future updates, since it would be beneficial for most of the users.
I've tried to create my own classes by deriving from MSH, but after updating to 0.4, it's all broken. I need to debug and fix most of my blueprints.
It's that big of a hassle, so I'd rather stay on an older version or just wait for the 1.0 release before starting to use the framework for my project.
Hey, thank you for your question.
Right now, to update the project, you’ll need to download the latest version of the framework from the launcher and then manually migrate your custom content (such as characters, animations, and any Blueprint modifications) into the new version step by step.
I understand this can be frustrating. once we reach version 1.0, we plan to introduce a dedicated DIY section on our website. This will remove the need to always download the full project. Instead, you’ll be able to follow guided steps to apply updates manually whenever needed. However, until we reach version 1.0, each update introduces significant changes to the project, so the current method will remain as I mentioned for now.