As a Roblox developer, I would like to see documentation on the limitations applied to the newly released banning API. Mainly, I would like more documentation on the following:
What users cannot be banned?
I know for a fact that UserId 1 can not be banned, but I have no clue why. I would love if there could be further documentation on which users can not be banned and why.
What occurs when a banned user attempts to join?
Do any signals get fired that could identify this case? What happens if they attempt to teleport to the place? Do they get a teleport failure or simply get kicked out entirely?
Are ban private-reasons filtered?
It is stated that, at the minimum, public ban messages are filtered, but it is never clarified if it also applies to private ban reasons, too.
What occurs if a user gets banned while in-experience?
Both when a player is in the current server and a different server. Is this reliable?
Is there any way to determine if a player is banned?
This specifically relates to alt-account detection. Does the OpenCloud API for checking UserRestriction status factor this in? Do the lua APIs factor this in?
It would also be convenient to have the FAQ on the DevForum announcement also mentioned somewhere on the documentation site
This one was answered in the exact devforum post you linked to…
I cant be certain, but I’m pretty positive they are not going to be filtered. Roblox says that they can be used for scriptable logic, so filtering something which will never be shown to the client wouldnt make sense.
My question is whether this ‘eviction’ is guaranteed and/or does it work when the function is fired via OpenCloud / a separate server. This isn’t mentioned very well, and given that we can’t delete ban-history logs, I’d rather not be forced to test it out to ensure it works.
Sorry it seems I mixed up the inheritance and excludeAltAccount parameters, I’ll edit my OP; thanks for helping me notice.
The question is mainly whether there are other accounts that have this unbannable state (since this is important to ensure we don’t continously try an operation which will never succeed) and why this restriction even exists; developers can already ban such users via their own methods and using UserId 1 for testing purposes seems like it would be a common use-case.
What would prevent you from creating a new test place and trying out the API there? I agree the information from DevForum should also be available on the documentation though, or at least a link to the announcement.
To clarify a bit more, the issue isn’t solely the fact that I need to run a test to see if it works but rather that the test would need to be done at-scale to account for varying server conditions. Unfortunately, I do not have the time or resources to run a test at such a large scale.
I don’t understand the reason for using user id 1 for testing as that’s the official roblox account, or even the reason of testing in the first place. You just call a function and that’s it.
As for other users that may have this unbannable state, it’s most likely any roblox administrator and the game owner.
