Let us use a differently named folder structure for our assets / main folder with assets in sub folders

I would like to request a change to the publishing rules, specifically that the assets need to be in a single folder (inside content), named after the asset.

Instead I would like to be able to use a named “main folder”, which contains the folder for the specific assets + a “commons” folder, for shared files across different assets.
When publishing multiple assets, it is common for them to share certain files, e.g. materials and textures. So it makes more sense to have a “commons” or “shared” folder, to reduce duplicates and thus file size.

An example could look like this:

Content

  • Main Folder (e.g. publisher name or name of asset theme, like “modular vehicles”)
    • Asset 1
    • Asset 2
    • Shared

Sadly, the current publishing rules do not allow that. Which imo is a bad ruling, although I understand the idea to prevent confusing with FAB customers.

However, as a dev and FAB customers myself, I don’t add 1000 assets to my project at once. I add one, or maybe two or three at a time.
So naturally there is only a few “new folders” to check, and usually I rename and move them into other folders anyway.

Furthermore, asset folders are rarely exactly named the same as on the FAB page, and often have quite different names, requiring to look inside anyway to see what it actually is.

Thus a change to the publishing folder naming rule, allowing us to use a main folder with asset specific sub folders + a “shared” sub folder, would not really add to the confusion of the customer;
Instead it would actually clear up the content folder if multiple assets from the same seller are used and also reduze file size + simplify the annoying procedure of cleaning up duplicates / unnecessary files in a project later on = a better experience for the customer.

It would be great if this change could be made, or if we could get an official word from the FAB team if this is allowed already. :slight_smile:

It is already possible to do so. I am doing it in all of my Products.

Just call your main Root Folder as your Publisher Name and Create whatever you want to create under that.

I have Published about 12 Listings (Since 1 and Half Year) without any Problem.

The problem seems to be that some reviewers for new published FAB content seem to not accept such folder structure (a main folder + asset specific sub folders).

Thus it would be nice to get an official word from the FAB team about this being allowed.

2 Likes

Official word from the FAB would help yeah

2 Likes

If that is the case, then. I think you should further escalate Issue via Support mail under Publisher Category.

I really had great experience with there support, In my case I sent it for Chaos Plugins since they were essential part of Engine but some of Plugins were Experimental, hence were not allowed to used as dependency. So they created exception on rules for every Chaos Plugin for everyone, and I never Faced rejection after that (Probably other creators too).
I hope in your case too, they create Exception for using Publisher name, not only for you but for everyone else as well.

It is really important to reduce Asset Duplication for End User, specially for Game Development, It should be must for every Marketplace Asset.

1 Like

It shouldn’t be a thing that you are escalating to support every single thing. Rules as written ( Asset File Format and Structure Requirements in Fab | Fab Documentation | Epic Developer Community ) state that:

The Content directory must only contain one subdirectory. This subdirectory must be named after your product (the Pack directory) and it should contain all other directories and assets.

And UEM rules were the same for that. So your assets basically slipped through reviews as they don’t follow current rules.

1 Like

True.

Maybe my Product names are bit longer, maybe that’s the reason they never reject my Listing for ‘Product Structure‘. (Even on Unreal Marketplace).

However, @spacegojira is right, Fab should allow Publishers to use their name as Root Folder.
Sending them mail would ‘Guarantee Response‘ from Fab compared to Forum. Perhaps it would create exception rule for other publishers (Who want to use their name as Root Folder) as well.

In meantime, lets hope for response from Fab Team in Forums.

@SkyeEden @skfabby could we please get an official response to this, to clear up this matter?

1 Like