Command Reference
Permanent Bans
BAR distinguishes between session bans (:ban) and permanent bans (:pban / :pbanid).
:banadds the user to an in-memory banned table. The ban is cleared when the server shuts down — it only affects the current session.:pban/:pbanidwrite ban data to Roblox DataStore, persisting across all servers and server restarts. On joining, BAR checks DataStore for the player’s User ID and kicks them if a permanent ban entry exists.
UseLegacyBan = false is set in ExtraSettings, BAR also calls Roblox’s native Ban API (Players:BanAsync), which applies the ban at the platform level across all universes and alternate accounts (ExcludeAltAccounts = false behavior depends on your configuration).
:pbans.
Server Lock
:slock sets a server-locked flag that prevents players with permission level 0 (Public) from joining. Any player who attempts to join a locked server is immediately kicked with the Server Lock Reason message defined in main_script.lua:
:unslock to reopen the server to all players. The lock is session-scoped and resets when the server restarts (unless LockedOnStart = true is set in ExtraSettings).
Messaging Commands
BAR provides several ways to communicate with players::sm <Text>— Broadcasts a full-screen message with the title set toServer Message(or your configured value). The message text is filtered through Roblox’s chat filter for each recipient.:m <Text>— Same as:smbut uses the sending admin’s display name as the title, making it clear who sent the message.:h <Text>— Sends a hint-style notification (smaller, top-of-screen) with the admin’s name as the title.:pm <User(s)> <Text>— Sends a private pop-up message to specific players. Recipients can reply directly through the BAR UI. BAR enforces Roblox’s chat privacy settings — if two players cannot communicate, the PM will not be sent.:globalm <Text>— Uses Roblox’sMessagingServiceto broadcast a message across all servers of the place simultaneously.
:shutdown sends a full-screen message containing the configured Shutdown Reason to all players before kicking them. The reason can be customized in main_script.lua via ['Shutdown Reason']. Shutdown events are logged to the DataStore shutdown log, which is viewable with :shutdownlogs.