In this guide, you will find my advices on how to migrate to Easy Hud Builder v1.1 from version 1.0. Note that everything will depend on your project, which parts of the pack you used, expanded, etc. If you encounter any difficulties don’t hesitate to contact me!

<aside> ⚠️

Before doing any of the following steps, backup your project!

If you don’t have a source control, you can simply duplicate the project to another folder in order to keep a functionning version if anything goes wrong.

</aside>

Update 1.1 brings a large overhaul of the entire system to make it more user-friendly and add many requested features! The update also brings several bugfixes and improvements across the board.. You can check out all the changes of the update in this update notes Please note: The upgrade will overwrite any modifications you may have done to the files but you will be able to keep your changes of modules definition and any external references will be preserved.

  1. First, if you have made any modifications to the Hud Modules Data Asset (custom modules, modified contexts, etc), we need to save it. If you have not modified it, you can skip this step

    To save it, first go to the folder where you created your data asset OR if you are using the default one go to EasyHudBuilder/Core/HudModulesDefinition

    image.png

    Then, simply make sure to move the DA_DefaultModulesDefinition (or your custom data asset) outside of the EasyHudBuilder folder, like in your project Content folder.

    image.png

    Finally, make sure to fix up redirectors by right clicking on the Content folder and clicking Fix up Redirectors

    image.png

    If you are using the default modules definition, I would strongly recommend renaming it to make it unique and avoid any issues. Make sure to Fix Up Redirectors again after the rename.

    You can also do this process for any Hud Module Widget you may have added directly inside the folder EasyHudBuilder/Core/HudModulesWidget. You juste need to move them outside of the EasyHudBuilder folder and fix the redirectors like shown above

  2. Then, if you wish and made any modifications to those, you can save your current config and styling in order to preserve them in the new version

    To do so, go to EasyHudBuilder/Core/GlobalConfig and locate the DA_EHB_DefaultStyling and DA_EHB_DemoConfig (or your own data asset if you created custom ones)

    image.png

    Then, repeat the same process as for the Hud Modules Data Asset, move each outside of the EasyHudBuilder folder and then Fix Up the Redirectors. I would also recommend renaming those.

    image.png

  3. Then save everything and close Unreal Engine.

  4. Open your project in your File Explorer and go to the Content folder. Delete entirely the EasyHudBuilder folder from there

    image.png

  5. Then, open your Epic Game Launcher and download the new version of Easy Hud Builder in that same project You may get a pop up saying that the files already exist, simply click Yes, replace

    image.png

  6. If you saved your own Global Config, you will need to go to the EasyHudBuilder/Core/GlobalConfig/ folder and open BFL_EasyHudFunctionUtilities, in there, open the GetHudConfigDataAsset function and modify the variable with your own data asset reference.

    image.png

    If you have not saved it, you simply need to go to the EasyHudBuilder/Core/GlobalConfig/ folder, open the DA_EGB_DemoConfig and redefine your config (such as redefining the Hud Modules Definition Data Asset if you had saved it)

    image.png

  7. As for the Hud Modules Definition, if you saved your existing data asset, we need to make a small operation for it to work properly with the updated hud system.

    To do so, go to the folder EasyHudBuilder/Core and open the EUW_HudModulesDefinitionConverter (Right Click > Run Editor Utility Widget)

    image.png

    Then, simply select the old data asset you moved to another folder, and click Convert

    image.png

    After this step, I would recommend double checking in the Assistant tool that your modules have been updated correctly and did not change layout

  8. Once you have done these steps, the pack should now be upgraded to the new version of the hud building toolkit! I would recomemend checking back the steps shown in the documentation in order to make sure nothing broke during the upgrade.

  9. If you made any custom modifications to the widgets or systems of the pack, you will also need to remake those as they were ovewritten by the file update. I would recommend checking out the documentation to remake any changes that you may need

Once again, don’t hesitate to contact me if you encounter any difficulties or issues.