Roblox Ban Lists: How Cross-Game Bans Will Work

If you run more than one Roblox game and keep a shared ban list in a DataStore, a web database or a Discord bot, Roblox just told you what replaces it. On November 9, 2026 it announced Ban Lists: a list of banned players that lives on the platform, gets filled through BanAsync, and can be linked to any number of your games. It launches on January 29, 2027.

This post covers the new system only. For the Ban API it builds on (every BanAsync field, unban scope, alt accounts, device blocks) read the Roblox Ban API guide first.

Every screenshot in Roblox's announcement is labelled "not final design", so treat the UI here as a preview.

What Roblox announced, and why now

The timing is not a coincidence. Roblox's June 10, 2026 Scoped User IDs announcement gives players "a unique User ID for each game that they visit", and its update the same day said groups of games with shared moderation "will be impacted", promising "Ban API improvements to facilitate cross-game sharing of ban lists" before the wider rollout. A list keyed on one global user ID stops matching once the same player can arrive in your second game under a different ID.

Ban Lists are that promised improvement. The November 9 post says Roblox plans "to launch ban lists on January 29th, 2027 before Scoped User IDs", and closes by saying it will share Scoped User ID updates "as we get closer to rollout in January". The Scoped ID thread's own roadmap had listed October 2026 for the broad rollout; its latest update, dated September 1, 2026, said Roblox would share "full details on the updated solution and timeline in October."

How a ban list works, end to end

Your current setup keeps working. Roblox says that if you don't ban across games you "won't need to use ban lists", and that existing custom moderation systems and standard BanAsync calls "will continue to work".

Filling a list: BanListIds on BanAsync

Players:BanAsync() gets a new optional field, BanListIds, an array of list IDs. This is Roblox's example, trimmed to a single list ID:

local Players = game:GetService("Players")

Players:BanAsync({
	UserIds = { player.User },
	Duration = -1,
	DisplayReason = "Repeated exploit usage",
	PrivateReason = "Detected via anti-cheat fingerprint XYZ",
	BanListIds = { "bl_2H8sJq..." },
})

Two things to notice. One call can add a player to several lists, so you don't need a BanAsync per list. And the example passes player.User, the new User value that Scoped User IDs introduced, rather than player.UserId. As of November 10, 2026 the Players reference in Roblox's creator-docs repository does not yet document BanListIds, and still describes UserIds as an array of user IDs. Write against the reference until it changes; the snippet above is a preview of launch-day usage, not something to ship today.

Linking a list to a game

A linked list covers the entire game. You enter a ban list ID in Creator Hub, and you can only link lists you own, lists another creator shared with you, or public lists. Roblox says the list "will immediately begin rollout" on linking, with the rollout time depending on the list's size.

The rule that matters most: there is no per-game override. In Roblox's words, "Players on any linked ban lists will be banned, there is no individual game level override. If you want full control, use your own ban list." If a shared list bans someone you want to keep, you can forward their appeal to the list owner, but the ban stands until the owner acts or you unlink the whole list.

Sharing: private, named creators, or public

A list is private to its owner until you share it. You can share it with a specific set of creators, or make it public so anyone can link it. Shared lists are read-only to everyone except the owner.

Roblox staff answered the obvious abuse question in the thread: public lists "do not automatically apply to other games", and a list owner cannot attach a list to games they don't control, because "other Creators must consent to their use." Staff also said Roblox is not planning a public directory of ban lists, and that a ban list breaking the ban guidelines or Community Standards (a discriminatory one, for example) can be reported to Roblox.

The announcement itself warns that linking a public list means "you no longer have control over who may participate in your game", and recommends your own list or a friend's instead. In practice, a public list hands your door policy to a stranger whose list you can't edit.

Group lists follow existing group permissions. Per staff replies, members with the "Configure bans for all group games" permission can manage group-owned lists, and you can share a list with a developer who has permissions in another group so they can apply it to that group's games.

What a banned player sees

Three player-facing surfaces arrive with the system:

• A rules tab on every game. You write the rules in the Creator Dashboard. The tab shows the game's own rules plus the rules of every ban list linked to it.
• An in-game prompt that appears as soon as BanAsync fires, carrying the ban reason. Roblox says it is the creator's responsibility to give "a clear ban message including the rule that was broken."
• A ban message on the game's details page, with a button to start an appeal. A staff reply adds that the message will name the lists the player is on.

You don't have to restate Roblox's Community Standards as game rules. Staff said the rules tab is for game-specific or list-specific rules, such as not deliberately going out of bounds, and that you may also ban for off-platform harassment or fraud if you list it as a rule.

Appeals land with the game creator first

Players appeal from the game details page, and the appeal becomes a ticket for the game's creator, not Roblox support. If the ban came from a list you don't own, you see the appeal first and can forward it to the list owner. A staff reply adds a setting to auto-forward all ban-list appeals to their owners.

Staff answers in the thread fill in the rules:

Roblox says it is the game creator's job to choose which lists to link and to unlink one that causes problems, giving non-responsive appeals as an example.

Moving an external ban list onto Roblox

If you keep a list off-platform today, Roblox will offer Open Cloud APIs to import it, and a staff reply says import will also be available directly in Creator Hub. These are the fields to prepare:

Open Cloud coverage is promised across both the ban list system and the appeals system. Roblox's own wording is that off-platform list owners "will be able to transition" to the native system, and the announcement notes that off-platform solutions are often against its policy. If you run one, plan the move rather than waiting to see whether it survives Scoped User IDs.

Smaller changes staff confirmed in the thread

Several replies from Roblox staff on November 9 and 10 go beyond the original post:

• UnbanAsync is getting the same PrivateReason field as BanAsync, so you can log why someone was unbanned.
• Bans in the dashboard will be searchable by display and private reason and filterable by properties such as time range.
• Lists can be created from the game's page in Creator Hub as well as through Open Cloud.
• Ban lists sit under a game, since they inherit the existing ban system's permissions. If you want a list detached from any live game, staff suggested creating a holder game to own it.

None of these is in the reference documentation yet, so treat each as a stated plan until it ships.

Quick Action Checklist

• Leave single-game bans alone; standard BanAsync keeps working and you don't need a list.
• If you ban across games, plan one list you own and link it to each of your games after January 29, 2027.
• Start writing per-game rules now; the rules tab and ban messages are where players will read them.
• Put evidence in PrivateReason and moderator notes; Roblox's appeal-review mockup shows the private reason next to the ban.
• Export any off-platform list into User ID, Game ID, ban reason and ban date columns, ready for import.
• Treat public lists as high risk: there is no per-game override, so a bad ban needs the list owner or an unlink.
• Keep BanListIds and User-based ban code out of production until the Players reference documents them.