I was expecting a concrete response from support, because after many exchanges, more than ten, it has been really difficult to get a proper answer. At this point, here is what I can share:
“In this case, this request was escalated for further review so we can provide you with accurate information. Upon double-checking, our team found that your islands were suspended due to severity violations, and will remain locked. However, you can create new island/projects in your account.”
This is obviously not the response we were expecting, so I explained the situation again in detail and I am waiting for it to be handled differently, since these island suspensions are due to moderation issues!
I’ll keep you updated.
On your side, have you been able to do anything? We are still waiting for help from an Epic staff member here! @Flak
I’ve published several maps already with the codebase that I use and there weren’t issues. I’ve attempted to update the problematic code, but it just gets flagged again and again.
Once I managed to publish an island (after about 10 attempts), but after submitting a new update for that map, it just got rejected again. Exact same code, same project, but it just randomly worked once.
Although they all seem different, we agree there’s indeed a false-positive problem, since none of the reported items are actually problematic.
We’re doing this to improve the system so that as few people as possible are affected, or even banned, in the future due to errors.
If you’d like to help, add a comment and I’ll include your false positive.
I hope this summary helps the staff resolve these issues. @Flak
i agree something is wrong. I think at this point just getting this post acknowledged is a good first step as i still haven’t tried publishing my island yet and its been weeks waiting for someone to say… the issue is fixed.
Hello, another one of our projects has been banned, apparently for not complying with Rule 1.1.
The ban email says: Content/stats_lobby.verse(23,5, 23,73)
This refers to the line: BillboardText_stats_winrate <localizes> (w : int) : message = "{w}%"
Why {w}? Because we thought that textual content (actual words) in the message could trigger false positives.
Our project is disabled—we’re unable to publish or modify it !
UPDATE:
Another one of our projects, yes, another one, has been permanently banned due to apparent non-compliance with rule 1.1. The line: BillboardText <localizes> (votes : int) : message = "{votes}"
UPDATE AGAIN:
We appealed these decisions and received a message stating that the sanctions were upheld. We’re therefore back to square one—this time with even more projects banned and completely blocked.
Tried to publish a new version again today after about 6 weeks of inactivity. And the issue is EXACTLY the same. The entire line S2M<localizes><public>(Data : string)<transacts> : message = "{Data}" is flagged as inappropriate language.
At this point, I don’t think Epic cares, so I’m out - Good luck to everyone who can suffer through this terrible ecosystem
Can we please have an explanation as to why a string in a :message is flagging rejections then ???
This was my issue
What in that line is referencing drugs or alcohol this makes no sense.
Then after numerous times and changes i got the publish but then in a random amount of time i will no doubt receive a section from Epic for having x amount of rejected published.
- Good luck to everyone who can suffer through this terrible ecosystem