Skip to content

Bans

Bans are kept in Fiveops; your framework’s own ban table is left alone. A player is recognised by all of their account identifiers (Rockstar licence, Discord, Steam, FiveM, Xbox, Microsoft) and, when it’s on, by their hardware ID; the ban stays even if the character is deleted. Settings live in the panel under Configuration → Bans.

Every ban has a short code (for example B7K2Q9). The player sees it on the connection screen and gives it when appealing. The code shows in the ban list in the panel and the in-game menu; type it into the search box to find that ban. It’s also its own column in the ban list CSV.

A ban issued locally while Fiveops couldn’t be reached gets its code once it reaches Fiveops.

A banned player trying to connect sees your server’s name and icon, their Ban ID, the reason, the ban date and the time left (or “Permanent”).

SettingWhat it does
ScreenCard (default): a card in the connection window. If the ban is lifted, the player gets in with Try again without reconnecting. Message box: a box in the rejection window.
Show who bannedOff by default: the player doesn’t see who banned them and appeals with the Ban ID.
NoteThe text at the bottom of the screen. Empty shows the default text.
Discord inviteThe Discord server button on the screen. If empty, the moderation bot’s whitelist invite is used.
Support linkThe Support button on the screen: an appeal form, website or ticket page.

The server icon comes from the Discord server the moderation bot is in; without the bot the Fiveops icon shows. The screen uses your server language (Configuration → General).

Plain text messages are used in two places: a player banned while in game sees this text as they’re dropped, and so does a player connecting while Fiveops can’t be reached. {reason} becomes the reason, {left} the time left and {id} the Ban ID.

FiveM creates tokens tied to each player’s computer. With hardware ID on (the default) these tokens are added to every ban, so the same computer can’t get back in on another account.

  • For an offline player or in a bulk ban, the tokens saved at the player’s last join on this server are added.
  • For a single ban you can turn off Also ban the hardware ID in the ban window (shared computer, internet café).
  • Different players can share a single token, so a block needs at least two tokens in common.
  • Tokens are specific to this server and kept only while the ban lasts: deleted at once when the ban is lifted, within an hour after it expires. Turning the setting off deletes every stored token and stops token matching on join.

If an innocent player can’t join because of a token, ask for the Ban ID on their screen, lift that ban and issue it again without the hardware ID.

Fiveops servers that turn on the registry see each other’s active bans. It’s off by default and works both ways: a server that hasn’t turned it on can’t see other servers’ bans, and its own bans stay out.

  • Only the ban’s reason, date and time left are shared. The name of the server that issued the ban, the staff member who issued it, the Ban ID and the player’s identifiers are not. Identifiers are kept in the registry as one-way hashes.
  • A lifted or expired ban leaves the registry at once. Turn the registry off and all of your bans leave it at once.
  • Only bans are shared; warnings, notes and other records are not. Hardware tokens are specific to each server, so they never enter the registry.
SettingWhat it does
Alert staff on joinOn by default. When a player with an active ban in the registry joins, staff in game with the Bans permission get an alert and an entry goes to the Punishments log channel.
Block on joinOff by default. A player with an active ban in the registry can’t join; the connection screen shows the reason and time left (not the Ban ID or the other server’s name).

The player card shows the player’s active bans on other servers (if any) as a warning at the top.

A connecting player is checked against the resource’s local copy of the ban list; hardware tokens match against that copy too. What happens is set by During a cloud outage. The registry lives in Fiveops, so it isn’t checked during an outage.