Skip to main content

Handling Bans

112 is a global ban handler for SB games. You can access it by making a GET request to https://api.ocbwoy3.dev/bans.

Schema​

Example Schema
{
	"UserId": {
		"Reason": "Reason",
		"Moderator": "Moderator's Name",
		"Expiry": 0, // Ban Expiry (Unix Seconds, 0=Perm Ban)
		"ModeratorID": 0 // Moderator's Discord ID
	}
}

A populated banland would something like this:

banland.json
{
	// i use nix btw :3
	"1083030325": {
		"Reason": "112-SB Test Ban",
		"Moderator": "OCbwoy3",
		"Expiry": 1719925542,
		"ModeratorID": 486147449703104523
	},
	(...)
}

The example banland.json indicates, that...

iUseNixBTW (A Roblox user with the ID of 1083030325) was banned by OCbwoy3 for the reason: 112-SB Test Ban

The user's ban expires on July 2 2024 at 13:05 UTC+0

Handling Bans​

Kick Messages

You MUST include something like ocbwoy3.dev/appeal in the kick messages when a user is banned using 112, so the user can appeal! This must be in every kick message, where a user is banned using 112, no matter if it's a legacy ban or not.

script.lua
print(game:GetService("HttpService"):GetAsync("https://api.ocbwoy3.dev/bans",true))
Legacy and Permanent bans

Permanent bans have "Expiry" as 0
Legacy 112 bans have "ModeratorID" as 0

For example, in PrikolsHub Anti-Logger V2, according to the example schema above, OCbwoy3's kick message would be:

Kick Message
Banned by OCbwoy3 | Unbanned on Jul 2 2024 @ 13:05 UTC+0 | ocbwoy3.dev/appeal - 112-SB Test Ban

Try to keep your messages as concise as this.