If you're currently deep into your production with Hyper V2 modules, the decision to upgrade depends on several factors:
1. General Advice for Active Projects:
o In normal development situations, especially when actively programming, it's generally advised not to update. External updates from Unreal Engine or any marketplace asset can potentially conflict with your ongoing work, considering the frequent changes to your own architecture.
2. Easy Update if you did not change any code:
o If you've primarily worked on the environment or something similar and haven't extensively modified the code of Hyper Assets, updating can be relatively straightforward.
3. Important Notes for Updating:
o Always make a backup and use version control before attempting any update.
o Note that I cannot provide assistance in the updating process, and I don't maintain a log of every specific node change due to the extensive nature of updates.
4. Updating Your Current Project:
o If you haven't changed any code, consider removing all Hyper files, migrating, and integrating them anew.
5. Additional Considerations:
o Document any changes you make to my specific code.
o Ensure your own data tables are backed up before updating.
o Maintain the same folder structure to avoid overwriting files if they've been moved.
6. Product Philosophy:
o My products are sold "as is" and aren't regularly updated with new features. Updates focus on bug fixes and incremental improvements. You purchased a system for specific reasons in that current state while not expecting constant feature updates.
7. File Structure and updating:
o I aim to keep the file structure consistent for easy migration. However, if deemed necessary I can change. When you have the same versions and file structures, you can migrate the new files over your existing project but be aware that this will overwrite any changes in the code and the data table.
o After migration, re-add your custom additions and reimport your own data table.
o In the new updates I have changed the file structure I have created a Core folder that includes all the fundamentals of the architecture of an asset. E.g. Datastructures, Abstract Classes, Interfaces, etc. All the implementations are outside of the core files. Because of these changes, you cannot overwrite the files with older products easily.
8. Selective Code Integration/Cherry picking:
o For those deeply immersed in their projects, having implemented substantial code modifications, selectively picking specific portions of code for integration into your own project can be a strategic approach. This method proves beneficial for advanced users, allowing them to leverage the advantages of the new template while preserving their existing project structure.
9. Conclusion:
o Generally, updates may not be necessary. Consider the outlined steps carefully if you decide to update, ensuring the smooth integration of the latest assets into your project.