Admin
Moderating Glitch — who counts as an admin, the Moderation queue in Studio, what a ban does, the /glitch command and where admin actions and payments are 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:
add_principal identifier.license:<id> group.admin
add_ace group.admin admin allowIn the app
Admins see Moderation in Studio, with a count of open reports.
- Open / Closed: reports on channels and on chat messages, with the reason, the reporter's note and the reported message. Actions: dismiss, ban the account, end the live stream. A player can't report the same channel or message again while their first report is open.
- Live: every live stream with its real and simulated viewers, and End.
- Bans: every banned account, with Unban.
- Log: the latest admin actions and who took them.
A ban stops the account streaming, chatting, following and paying, ends its live stream, removes it from any stream it is watching and keeps it out. It also covers the character behind the account: a new account of the same character is banned too. Nobody can subscribe or cheer to a banned channel. A stream an admin ends (from the app, /glitch end, a ban or the phone's /phone endstream) earns nothing from the simulated audience; real support already paid stays.
Command
/glitch works in chat for admins and in the server console:
| Command | Does |
|---|---|
/glitch partner <channel> [on|off] | Grant or remove Partner and the check mark; without on or off it switches |
/glitch popularity <channel> reset | Set popularity to 0 |
/glitch popularity <channel> set <value> | Set popularity |
/glitch popularity <channel> add <value> | Add to popularity (negative takes away) |
/glitch ban <channel> [reason] | Ban an account from Glitch |
/glitch unban <channel> | Unban it |
/glitch end <channel> | End a channel's live stream |
/glitch reports | How many reports are open (the console also lists them) |
/glitch live | Who is live, with simulated and real viewers |
<channel> is the username (with or without @) or # and the account number. Popularity always stays between 0 and Config.Audience.popularityMax (2000 by default).
Partner changes show at once: viewers of a live stream see the check mark appear or go, and the channel's payout rates change from its next tick.
Logs
Every admin action is written to the oxide_glitch_admin_log table and to the server log through o-link's logger. Payments, cash-outs and refused requests are logged too.
Configuration
Every Glitch option across its three config files — what a stream earns with the defaults, the app, money, tiers and earnings, the simulated audience and categories, and the simulated chat, emotes and chat lines.
Admin Guide
Every /phone command, player keys, the in-game settings editor section by section, the admin tools inside the phone's apps, and how to grant admin access in oxide-phone.