The new Roblox ban API appears to be triggering a false positive. I do not currently use the Ban API at all, yet a user reported to me trying to join my game, but getting kicked with the following message:
You created or used an account to avoid an enforcement action taken against another account by the creator of this experience (Error Code: 600)
The user first reached out to Roblox customer support, who responded saying these bans are under direct control of the experience and not a Roblox action, which the ban message also seems to point towards. However, my game does not use the new Roblox ban API, so this is not possible.
I verified that this is the case by running a request towards the ListRestrictionLogs API endpoint, and it returned an empty table. I then verified that the request was correct by banning a random user, and they did appear as the only entry in the table.
To summarize, the alt detection is somehow firing off for an user trying to play my game, despite having 0 bans in the new Ban API. I’d appreciate it if this could be looked into, as it’s currently causing confusion and unnecessary player frustration.
If I’m interpreting OP correctly, they’re saying that the new ban page (create.roblox.com/dashboard/creations/experiences/[game]/moderation/bans) has nothing on it (ie, no bans through the ban API) - In other words, there are no accounts which would have alts banned/no bans linked to the user in any way.
I’m sure about having no registered bans with the ban API, which I verified with open cloud as I mentioned. EDIT: Turned out to be wrong, see below
There is a chance the user is lying, but I don’t see what the point would be as it wouldn’t gain them anything (there are no accounts to unban). They also attached picture proof
Thanks for making me aware of this link, I didn’t know you could see bans on the dev hub. It seems that there are 4 other bans registered here that didn’t show up in the response from the API endpoint. Since it’s likely that one of these is the banned player, I’ll mark this as resolved for now until I hear back. Sorry for any confusion!