Maps are repeatedly getting rejected due to harmless debug Print(), strings and messages

Summary

My maps are repeatedly getting rejected for violation of rule
1.10 Appropriate Language Only
due to Print() debug, strings or internal message strings, as confirmed in the mails sent by the moderation team.

Please select what you are reporting on:

Unreal Editor for Fortnite

What Type of Bug are you experiencing?

Publishing

Steps to Reproduce

Have debug prints such as
Print(“Player is spotted and not hidden, so we loop aggro”)

or strings such as
var BossID:string = “What Boss does this ID belong to?”

or messages such as from the NPC behavior Verse template
OnNavigateErrorMessage(Agent:agent, X:float, Y:float, Z:float):message =
“NPC Agent = Agent: Hit error moving to X,Y,Z, please refer to Island Settings Navigation debug”

in your project and publish the map.

Expected Result

No rejection

Observed Result

The project will occasionally fail content review and get rejected due to violation of rule 1.10 Appropriate Language Only.

Platform(s)

Fortnite Creator Portal

Island Code

4131-0707-4626

Upload an image

Additional Notes

Hope this doesn’t get me banned since it’s been happening quite often.

While not a bug, I have had people tell me about this and having their whole map being removed and inaccessible to UEFN too simply due to a print statement that doesn’t even have anything in the game. Seems like auto mod is tagging things that don’t need to be tagged

hi @Adb

An indie dev had this, and the only way that worked was to put the messages into small pictures, static mesh, then the thumbnail analyser code would look at the picture and be more interested in a duplicated image being owned by someone else.

The duplicate image had the word “Weapon Rack,” and the fix for this was to change the font.

Someone else used another billboard and sent a diagnostic message to the billboard