Sorry to resurrect an old thread - this one comes up first in search results.
I find the content folder worfklow confusing when trying to use marketplace assets.
Half the Marketplace assets need the user to “create project” and half are “Add to project”.
The most difficult thing is not being able to really organise a content folder. if a user purchased 10 marketplace assets, they end up with many many folders in the root of their content folder.
I would love some advice on managing this. Is following example below the best way to use marketplace assets?
The user purchases multiple Marketplace assets. For example: “AnimationPack01”, “DialogAnimations”, “SeatedAnimations”.
The 3 animation packs all support the “Add to Project” workflow.
Since these 3 packs are all “Animations” BUT the naming is inconsistent, the user wants to put all 3 into a subfolder called “MarketplaceAnimations”
If the user decides to do this, if one of the 3 animation packs is updated by the creator in the future, they must do the following:
- update the Marketplace item in the epic launcher
- create a new empty unreal project called “Test”.
- Open the “test” project and add an empty “MarketplaceAnimations” folder to this test project
- Close the project, return to the launcher and use the “Add to project” feature to add the updated pack to the empty “test” project.
- open the “test” project again and move the updated asset pack folder into the “MarketplaceAnimations” folder
- Migrate the entire “MarketplanceAnimations” folder from the “test” project to the user’s production project, overwriting all assets.
Is that workflow recommended? It seems to be the only way to keep a content folder slightly organised but still be able to update the assets again if they are updated.
Is there a better method?