THE SHORT ANSWER
Roblox announces Ban Lists launching January 29, 2027, enabling cross-game bans via Creator Dashboard and extended BanAsync API. Creators can share lists privately or publicly, migrate existing external lists via Open Cloud APIs, and set in-game rules. Roblox warns public shared lists carry risk.
- Ban Lists launch January 29, 2027, before Scoped User IDs rollout
- Single list can block a player across all linked games simultaneously
- Lists managed in Creator Dashboard; sharing options include private, specific creators, or public
- BanAsync API extended with optional BanListIds parameter for multi-list bans
- Open Cloud APIs support migration of existing external ban lists
- New in-game rules tab configurable from Creator Dashboard
- Roblox cautions that linking public shared ban lists poses risk to players
Roblox will launch Ban Lists on January 29, 2027, giving creators a native way to ban players across multiple games at once. The feature arrives ahead of the previously announced Scoped User IDs rollout and is designed to replace the off-platform ban tools many developers currently rely on — tools the company says often violate policy.
How Ban Lists Work
A ban list is a collection of banned player IDs that can be linked to any game the creator owns. Once linked, the list takes effect immediately, though rollout speed depends on list size. Creators manage lists in the Creator Dashboard, where they can create new lists, add or remove entries, configure sharing permissions, and triage appeals.
Lists can be kept private, shared with specific creators, or made public. Roblox explicitly warns that linking to public shared lists carries risk for players, and recommends creators maintain their own lists or use only trusted private shares.
API Integration
The existing BanAsync API gets a new optional BanListIds parameter. A single call can add a player to multiple lists at once, avoiding repeated requests. Example usage shown in the announcement:
Local Players = game:GetService("Players")
Players:BanAsync({
UserIds = { player.UserId },
Duration = -1,
DisplayReason = "Repeated exploit usage",
PrivateReason = "Detected via anti-cheat fingerprint XYZ",
BanListIds = { "bl_2H8sJq...", "..." }
})
Duration = -1 indicates a permanent ban. The PrivateReason field is visible only to moderators and list owners.
Migration Path
Developers currently running external ban databases can import them through Open Cloud APIs. Required fields per entry: User ID (mandatory), Game ID (optional), Ban Reason (optional), Ban Date (optional — defaults to import timestamp). This lets established communities move years of moderation history onto the platform without manual re-entry.
In-Game Rules Display
Games will gain a new in-game tab showing the creator-defined rules. The rule text is set and updated from the Creator Dashboard, giving players a consistent reference point and helping creators meet the transparency principle Roblox cites: users must know the policy behind any moderation action taken against them.
Principles and Appeals
Roblox frames the launch around four pillars: user privacy (activity sharing stays under user control), transparency (rules visible to players), appeals (every banned user gets a consistent appeal path), and abuse protection (systems to deter framing via deceptive links or fabricated evidence). List owners handle appeals through the Creator Dashboard; the process is built into the list management workflow.
The company says community feedback shaped the final design. Off-platform ban operators are expected to transition to the native system once it goes live.