It would be nice if this was eventually extended to groups to then allow for the prevention of malicious users from causing chaos in any other games under the group. I am sure this is easily doable with the cloud features, but it would be more convenient if it were built-in. This feature would also probably integrate nicely with the incoming group updates as well.
5 Likes
this is going to be great! this will heavily effect future moderations for games
1 Like
Beautiful, now I can hopefully permanently block particular “users” that enter our places repeatedly with alts.
I’m trying to be careful with how I type here and trying to maintain a professional attitude but it’s hard when you have actual “users” that have nothing better to do coming right back in repeatedly with alts for the past 8+ years to just harass us more.
And yeah as you can probably hear it within this text, I’m pretty exhausted with it.
So hearing this is pretty nice for an update, please give us more utilities like this.
2 Likes
This feature is definitely really fruitful, I do have one nitpicky complaint, and it’s the: “Here’s a message from the creator:”
It just feels extremely out of place, kicking didn’t have it either, it also just feels “icky” to me, not sure exactly how to describe it. I feel like just a simple, “You have been banned from this experience with the following reason:” or something along those lines would be a lot more professional.
3 Likes
what took so long for this to be considered? this is WAY overdue
2 Likes
I love you, Roblox
Marry me
1 Like
This method will be protecting your experience from alt accounts to avoid the local ban.
1 Like
Is there a way to detect if a player is using an alt account without having to ban them? If not I’d really appreciate a way to do so.
3 Likes
Hey, have you tried this on the engine side?
What HTTP error are you getting from it?
1 Like
Not sure if you’re aware, but GetBanHistoryAsync does not work in Studio, even on the Server.
1 Like
Also, a much larger issue is the fact that BanAsync and UnbanAsync (especially Unban) does not work in Studio, even on the Server, making it possible for a Developer to permanently ban themselves from their own game …
Please fix.
1 Like
You accidentally had /user-restrictions in the url variable twice. Here is the fixed version:
const url = `https://apis.roblox.com/cloud/v2/universes/4570608156/user-restrictions:listLogs?maxPageSize=10?filter="user == 'user/355661302'"`
If you’d like you could use my opencloud wrapper instead: https://open.blox.wiki/cloud/userRestrictions/listRestrictionLogs
Below is the function that wraps endpoint you are having issues with getting to work:
import { UserRestrictionsApi } from "openblox/cloud"
const { data: logs } = await UserRestrictionsApi.listRestrictionLogs({
universeId: 5795192361,
placeId: 18210254887,
userId: 6193495014,
});
npm install openblox
4 Likes
Thanks for the questions! The filter is mostly the same as the in-game chat filter, but we’ve made sure that the filter will allow you to include additional information such as appeal or contact information as long as you meet Roblox’s Community Standards requirements.
For example, in your ban messages, you are allowed to reference brand names and platforms:
“Visit the Discord in my group/experience page”
“Message me on Twitter or X”
Mentions of personal information or direct links are not allowed in this message field. This includes posting a specific username or handle, or providing a direct link to a Discord server or X account.
For more info, check out our API usage guidelines page: Users and Players | Documentation - Roblox Creator Hub
14 Likes
The banning API should stop players from being able to change their like/dislike on the game. If a player is banned for exploiting, its unfair that they can then leave a dislike on the game when they broke the rules.
9 Likes
Is both the DisplayMessage & PrivateMessage filtered or just DisplayMessage? Cause I definitely seeing people storing tables in PrivateMessage as a string then converting it back to a table during runtime to store information and if it filters privatemessage that could cause some issues.
3 Likes
Thanks for pointing that out 
!
Your package looks great as well, good job!
1 Like
FINALLY! Been waiting a while for this. OpenCloud accessibility definitely excites me the most. Looking forward to better detection and more in the future.
I was wondering that aswell, because what happen if one person gets banned and someone else get caught in the cross fire and get banned aswell? if they making it like just a lucky guess that person is a alt, and not on stand by.
Could there be an additional setting to this where it simply lets you know a user was banned and lets us handle it on our side? Im sure some developers would appreciate that small option. Not all players who get banned are immediately booted from a game after all.
1 Like
Please do not filter it automatically, leave that responsibility to the developer. See Introducing the Ban API and Alt Account Detection - #107 by Daw588.