There isn’t a way to view banned players on shared experiences anymore. Trying to access the page returns the “You need permission to access this content” page.
Allowing only the place owner to view this page is now absurd, considering that I have banned the players. For example, I now want to copy all the banned users and apply them to a different place. What am I now unable to do.
Why isn’t there a section to see all players that have been unbanned. You can use GetBanHistoryAsync() but you would need a userID to use it, it cant be used to check all banned/unbanned users.
Honestly what’s the point releasing this API while it’s incomplete, alt detection is still not fixed, only reason I’m using this API. I’ll never understand this. It’s like ads, adding them all around the map just to get 10 Robux a month in my 50-100 ccu game, pointless.
Is anyone else experiencing issues with the ban api in the last hour? Can’t unban or ban users via either the opencloud method, or just an actual script in live games?
there is an Syntax Error in the Code Sample for Banning Users
I genuinely hope the alt detection works soon, I had to manually deal with one exploiter and their 83 ALTERNATIVE ACCOUNTS
This is the first page, I hit the maximum limit of IDs for one bulk
These accounts were all tied to a group, with the owner of them also being the holder of the said group.
What even felt the need to give us access to a nonexistent feature???
Any update on this for 2025? Would love to see this be effective.
This so awesome!!!, We can finally ban people who evade bans with alt detections.
This update is actually very good!!
Don’t get excited too soon. The alt detection doesn’t work at all.
So I made this ban api into an admin command and banned an alt with alt accounts to true but it doesn’t ban my main account too (the account who ran the command) what should be banned too
I got false-banned from a game because my friend went onto my wifi and got banned. It works, but not as intended.
@oopsiemachine
Are the issues with this API going to be acknowledged? This system has been seemingly abandoned. The alt-detection is completely broken and has remained so since its release over half a year ago. Can an engineer at least acknowledge that the system is currently flawed and does not properly detect the alts that it should? Numerous developers have pointed out the failure of this API, yet there has been no communication acknowledging the issues.
I’m tempted to submit a bug report because clearly this system is not functioning as it should be. I don’t understand why Roblox continues to make it so difficult for developers to protect their games from nefarious users.
Any updates on this being addressed in 2025? @oopsiemachine - the lack of functionality leaves a LOT to be desired.
after a lot of testing i have come to a conclusion
the anti alt does indeed work, however: it does not detect freshly made alts as of right now. alts need to be used for a bit before they’re noticed
Half a year and this API is still broken. This is the magic of what’s supposed to be part of our developer share!
there is also an Syntax Error in the Code Samples for BanAsync and UnbanAsync
the code samples are Banning Users and Unbanning Users
Syntax Error: Expected ‘(’, ‘{’ or when parsing function call, got ‘)’
Even that is broken now?! LOL
That’s exactly why I reverted back to the old way for my admin. Waste of my time.
Wait this is so embarrassing. I intended to throw in some typing for clarity but it’s clearly not how it should be done. I’ll get that fixed 
We have not abandoned work on improving this API. We are still in the planning stages for what we want to release this year, but I am optimistic that it will be a material improvement over what we released last year, especially when it comes to bolstering your own anti-cheat systems.
As for the alt accounts service, we are very aware that this is the biggest issue with what we have released so far. However, I do want the chance to explain why it is what it is right now. We sometimes call it the sibling problem. How should our systems disambiguate the difference between one real person creating two accounts on the same machine versus two siblings sharing the same family computer? To us, this is a big user experience problem that we cannot just waive away, so we try to incorporate other signals that might change our confidence in the accounts being linked or not. With all of that taken into account, our confidence threshold is necessarily very high, resulting in many false negatives.
