Best Way to Refactor Content Drawer Directorys

Development Platform & Builds
, , ,
1

First of all, I would like to apologize that this question doesn’t fit the category of platforms and builds very well, I am still new to the forums and couldn’t find a category that made much more sense. I came here to ask about the viability of refactoring a content drawer on UE4.26.2. Basically, we have an unreal project with 3 years and 9 teams’ worth of progress on; however, neither team followed the conventions of the last so what we inherited is basically a jumbled mess as far as folders and assets are concerned. We would like to refactor the project completely(move all the assets around into a folder structure that makes sense) but I’ve heard some mixed responses as to whether this is a good idea or not(breaking references, corrupting levels etc). If I move assets around in the drawer itself and fix up the referencers is that enough? Is that safe most of the time? Basically, what would you guys do in this situation as an experienced unreal developer(something I am not).

Also if anyone knows what categories I should switch this question over too pls let me know

2

Hello Daddyboul,

Using the content-browser to reorganize assets is the way to go. (As opposed to reorganizing in file explorer) Since that way the references will get noticed and updated. You can periodically run ‘fix up redirectors’ on the folders as well.

I’d make a copy of the project, and then organize the copy. That way if something gets borked you can fall back to the original.

You might also want to package the project during your refactoring. (More of a superstition, but It could avoid a situation where you try to package down the road and have asset problems)

Also as a ‘my project is way too messy’ protip: you can select levels (.umap) and migrate them to a new project, this will move everything that the level uses.

There’s also a Content Browser filter ‘Other Filters → Not Used in any Level’ that could help clean things up.

Cheers!

3 Likes
3

Super duper helpful response. This should be more than enough information to help us with the refactoring. Thanks a bunch, and the fast response is greatly appreciated!

1 Like