Looking for tips on best practices for merging Marketplace Packages that require
into my Team’s existing project. My concerns are Configuration File merging and Package Upgrading. I ran into all sorts of issues in the past with this and want to devise a workflow that doesn’t break the project when adding these types Assets and upgrading them. My goal is to maintain a modular design without directly modifying the packages by creating child assets from those that support inheritance, and cloning assets that don’t support inheritance (ie: UMG Widgets :mad:).
My current Project File Structure looks something like this:
Content [Root] -GameLayer -AdoptionLayer --ADOPT_Subproject_1 --ADOPT_Subproject_2 -StagingLayer -Subproject_1 -Subproject_2
GameLayer is where all the Game Core files and Glue code.
AdoptionLayer is were I store my modified versions of a Subproject Child BP and Clones, essentially matches the original Subproject with the prefix ADOPT.
StagingLayer is work space to add/migrate project assets to the content, then move them into the appropriate directories.
SubprojectA,*B,*C,etc is the Subprojects migrated into the Content Directory.
So the current workflow of getting a Marketplace Project (subproject) into the main project is to
- Create Project
- Create Folder in Main project Content Directory
- Migrate Project to Main project Content Directory
I’m open to any ideas to improve the efficiency and ease of use for this process.