Moderation notices being added to unpublished projects

Summary

Apparently, you can get moderation notices on assets within projects that have never been published. This should NOT happen EVER! Especially if the project doesn’t even have a private playtesting code. This only seems to happen after starting an edit session with the moderated asset.

Also, I know it is the stupid AI Moderation that is causing this. Epic GET RID OF IT! IT IS TERRIBLE AND ONLY CAUSES PROBLEMS!

Please select what you are reporting on:

Unreal Editor for Fortnite

What Type of Bug are you experiencing?

Assets

Steps to Reproduce

  1. Upload any asset that could potentially break a rule, like a copyrighted texture
  2. Make sure something in the world references it.
  3. Start an edit session and wait for the stupid AI moderator to flag it.

Expected Result

No moderation notice should happen unless the project was published

Observed Result

I am getting moderation notices for an unpublished project

Platform(s)

ALL

Upload an image

Screenshot 2026-10-29 154950.png

Additional Notes

The attached screenshots are showing why this is a problem to begin with. As everyone is well aware, Epic doesn’t have the best track record of adding everything to creative. They almost always miss a few weapons, items, props, devices, or even whole prefabs and galleries. Naturally this would lead people to adding those things themselves. This is done by “porting” assets to UEFN which is basically reimporting stuff that is considered a disallowed object into your own content folder. This also means that it will follow the same asset reference structure that it does internally, only this time it is in your project’s content folder. In order to make a 1:1 recreation, you need to have EVERYTHING that gets referenced. The problem? Sometimes deep within those reference trees are copyright assets, like this Stark Industries login screen. This is only referenced as a default texture for the IO login screen, which replaces it with an IO version. The Stark Industries logo is NEVER seen in game, it is only referenced by the material.

My point being, Epic if you are going to moderate stuff like this, then you need to get your act together and start going through EVERYTHING missing that is or once was in Battle Royale and start actively readding it. It might be a long list of things, but the more you wait the longer that list is going to be.

My suggestion for UEFN would be to remove the asset whitelist and exposure system, and replace it with a blacklist that ONLY blacklists 3rd party assets. ALL 1ST PARTY ASSETS SHOULD BE AVAILABLE IN UEFN!!! You just need to either stop removing stuff from the files, or make a system that lets players download assets from game feature plugins and then use them in their project as long as those game feature plugins are NOT based on 3rd party assets. Also combine the blacklist with the asset exposure system but just make it so whatever is on the blacklist is hidden. Right now, the exposure system seems to be separate from the whitelist which causes UEFN to hide stuff that actually DO pass validation.

This is not a bad thing, it is actually a good feature implemented to help us!

It does not prevent you from publishing, neither is a real applied sanction on your map or account.

It is a intended added feature, explained on patch notes and is meant to help developers to catch problems early-on, instead of being surprised during publishing attempts.

It does not block project editing, neither limits anything on your account or publisher profile, It does not affect unpublished projects, edit/playtest sessions and so on…

If you are just playing around and don’t plan to release the map, it is fine, you can just ignore the warning and continue working normally.
If you plan to release the map in the future, that warning is not “new”, is just as I said, purely to tell in advance so you can re-think or avoid problems later, instead of being jumpscared with them after publishing attempts.

During publishing, the same assets would be flagged afterwards the same way as always did, and that warning is just a help to inform you beforehand. It is not a new notice that did not existed before, it is just being said as soon as possible, instead of only during publishing attempts… (So you can avoid wasting time instead of fighting back and fourth with publishing attempts)