Admin

Moderating Hookr — who counts as an admin, the Moderation screen in the app, the /hookr 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 on the Profile tab, with a count of open reports.

  • Reports: each report shows the reported profile (photos, bio), the reason, the reporter's note and the chat between them, unsent messages included. Actions: dismiss, remove one photo (the bin on a photo), remove the profile, or ban (with a reason the player sees).
  • Banned: every banned account, with an Unban button.
  • Log: the latest moderation actions and who took them.

Removing a profile deletes its photos and ends its matches; the player can make a new one. A ban ends its matches, hides the account from every deck and closes its open reports.

Command

/hookr works in chat for admins and in the server console:

CommandDoes
/hookr reportsHow many reports are open (the console also lists them)
/hookr ban <account> [reason]Ban an account
/hookr unban <account>Unban an account
/hookr removeprofile <account>Remove a profile
/hookr removephoto <account> <number>Remove a photo; 1 is the main photo

<account> is the account's number (shown on every report as #12) or its username with an @ in front, for example @user482913.

Logs

Every action is written to the oxide_hookr_admin_log table and to the server log (through o-link's logger, as an event), with the admin, the action and the account. A removed photo's address stays in the table; the server log gets only the photo's number and position.