Admin

Moderating Leakd — who counts as an admin, the Moderation screen and verified badge in the app, the /leakd command and where every action is logged.

Admins are the players who pass o-link's admin check (olink.framework.IsAdmin). With the standard QBCore or QBX server.cfg, your admins already pass. On ESX, players in an ESX admin group pass. To make anyone else an admin, add these two lines to server.cfg, with the player's license in place of <id>, and restart the server:

server.cfg
add_principal identifier.license:<id> group.admin
add_ace       group.admin             admin allow

In the app

Admins see Moderation in the menu on their Profile tab.

  • Open and Closed: reports on posts, comments, stories and accounts, with the reason, the reporter's note and what was reported. Actions: Remove (the post, comment or story is gone everywhere), Ban (with a reason the player sees) and Dismiss.
  • Bans: every banned account, with Unban.
  • Lives: lives on air now, with End.
  • Log: the latest moderation actions and who took them.

On anyone's profile, the menu (…) also has Give verified badge or Remove verified badge.

A ban hides the account's posts, stories, comments and lives from everyone, ends its live, takes it off any live it is watching (and keeps it out), and closes its open reports. The player sees the ban and its reason when they open Leakd.

Command

/leakd works in chat for admins and in the server console.

CommandDoes
/leakd verify <username> [on|off]Gives (default) or takes the verified badge
/leakd ban <username> [reason]Bans the account
/leakd unban <username>Lifts a ban
/leakd endlive <username>Ends the account's live
/leakd reportsHow many reports are open (the console also lists them)

Every action, from the app or the command, goes to the oxide_leakd_admin_log table and the server log with who took it.

On this page