What Players See
The screens and messages players get from MonoAdmin: /report, warnings, ban, kick and whitelist messages, community service, cleanups and notices.
On This Page
Staff use the web panel and the in-game menu. Players meet MonoAdmin in a handful of places: a report window, a warning they have to confirm, the message on a ban, a kick or a refused join, a community service counter, a cleanup countdown and the announcements and shouts staff send. This page shows each one as the player sees it, with the exact wording, so you know what to expect when you issue something from the panel.
Players need nothing installed beyond joining your server. Everything on this page is drawn by the MonoAdmin resource over the game.
Reports With /report
Players can report another player, a bug or a question without leaving the game. The command is /report unless the project picked another name (see below). It exists only once the owner has switched Player Reports on, which is off by default.
Turning It On
Under Settings > Features, the Reports System module has an owner-only switch, Player Reports: “Players can type /report in game to send your staff a report. It arrives on the Reports page.” The panel shows the project’s own command in place of /report. If the Reports System module itself is off, the command stops too. Until the owner turns it on, the command is not available. If it is switched off again later, players already in the game keep the command until they rejoin, and it only tells them “Player reports are switched off on this server.”
Renaming the Command
Anyone with the Edit Settings permission can give the command another name in Settings > Features, in the Report Command box under the Player Reports switch. The new name works at once. Players already in the game keep the old name taken until they rejoin, and typing it does nothing: no window, and no message. The toast that tells a player staff replied then names the new command. The rules for a name are on Features and Modules.
The Report Window
The report command opens a window with the mouse. It has two tabs, New report and My reports.
On New report the player fills in:
- What is it about? One of A player (“Someone broke the rules”), A bug (“Something does not work”), A question (“You need help”) or Something else (“Anything else”).
- Title, up to 80 characters.
- What happened?, up to 1,000 characters.
- Players involved, up to 5, picked from the players near them in the game (the list holds up to 32).
- A switch, Attach what your screen showed when you opened this window. The window copies the game view the moment it opens and uploads it only if the player leaves the switch on and sends the report. If no screenshot could be taken, the switch says so.
The window states the privacy rule: “Staff see your report, your name and the screenshot if you attach it.” Press Send report and the player sees “Report sent. Staff will look at it.”
Limits
| Rule | What the player sees |
|---|---|
| One new report every 2 minutes | “You just sent a report. Wait {seconds} seconds before sending another.” |
| At most three open reports at once | “You already have three open reports. Wait for staff to close one.” |
| Too many reports or replies in a short time | “Too many reports or replies. Wait a few minutes.” |
| A closed report cannot be replied to | “This report is closed. Open a new one if you need more help.” |
Following a Report
My reports lists the player’s own reports with a status: Open, In progress or Closed. Opening one shows the conversation like a chat: the player’s messages on the right, staff replies on the left, and small lines for status changes. The player can reply, using Enter to send and Shift+Enter for a new line.
The player sees only their own reports. They never see staff’s internal notes, who the report is assigned to or how many messages exist. Files that staff attach are viewed in the web panel only.
If the window is closed when staff answer, a notice appears: “Staff replied to your report “{title}”. Type /report to read it.” It names the project’s own report command: after a rename to ticket, it ends “Type /ticket to read it.” Other notices say that the report is open again, that staff are looking at it, or that it was closed.
Discord tickets are reports too. A player’s tickets from your Discord server appear in My reports with a Discord label and the channel name, and replies written in the window also appear in the ticket. A player whom staff add to a ticket later sees there only what was written from the moment they joined it, and a player staff take out of it no longer sees it. See Discord Tickets.
On the staff side, these reports arrive on the Reports page with the origin In Game. See Reports.
Warnings
A warning stops the player until they confirm it. A card covers the screen with:
- You have received a warning
- The reason staff wrote
- Issued by {name}, with the date and time in the project’s time zone
- “You can continue playing once you have confirmed this warning.”
- A button, I understand, which stays greyed out for the first 3 seconds so the text is at least seen
The card takes the keyboard and mouse until they press the button. Warnings arrive one at a time. A player who was offline when it was issued sees it as soon as they join, and again on every join until they have confirmed it. If your server is offline when they confirm, the confirmation is sent after the next connection. More in Warnings, Mutes and Community Service.
Ban and Kick Messages
A ban or a kick ends with a message on the disconnect screen.
A kick reads:
You were kicked from this server.
Reason: Disturbing the roleplay
A ban reads:
You are banned from this server.
Reason: Cheating
This ban ends on Oct 12, 2026, 2:05 PM GMT+8.
The last line is one of three:
- This ban is permanent.
- This ban ends on {date}., with the date and time in the project’s time zone and the zone named.
- This ban is temporary., when a date cannot be shown. The ban holds either way.
Reasons longer than 300 characters are cut on this screen, and an empty reason reads “no reason given”. The same message appears when a banned player tries to join, whether the check is answered by the server’s copy of the bans or by MonoAdmin. See How Bans Are Enforced.
If you turned on Block joins while MonoAdmin is unreachable under Settings > Game Settings and the check cannot be made, the player sees “This server cannot check your access right now. Please try again in a few minutes.”
Whitelist Refusals
When the whitelist is on and a player does not pass, the connecting screen tells them why. A player who is not on the approved list reads, for example:
You are not on this server's whitelist.
Your Whitelist ID: R7KQM
Apply here: https://app.monoadmin.net/apply/Xk3p9QwR2tLm?id=R7KQM&k=Q2mT8vLpX4nZb7Rw9KcYhE
The link is the player’s own: it carries their Whitelist ID and a key that goes with it. The application page needs that link to tell the player where they stand or to take their application, so the Whitelist ID alone is not enough. See The Application Page.
The other refusals are:
| Situation | What the player reads |
|---|---|
| Not on the list, and the application form is off | “You are not on this server’s whitelist.”, their Whitelist ID and “Give this ID to the server’s staff.” |
| An application is waiting | “Your application is waiting for staff to review it.” and their Whitelist ID |
| Denied or rejected, and the wait is not over | “Your whitelist request was not accepted.”, their Whitelist ID, “Reason:” with what staff wrote, if anything, and “You can apply again after” a date in the project’s time zone |
| The server is open to staff only | “This server is open to its staff only right now.” |
| No Rockstar license | “This server needs your Rockstar license to check its whitelist. Make sure you are signed in to FiveM.” |
| A Discord mode, and FiveM reports no Discord account | “This server lets in members of its Discord server, but FiveM can’t see your Discord account. Open Discord on this computer, restart FiveM, and connect again.” |
| Not in the Discord server | “Join this server’s Discord (server name) to play here.” |
| In the server without a role that lets them in | “You need a role in this server’s Discord (server name) that lets you join.” |
| MonoAdmin could not be asked in time | “This server can’t check its whitelist right now. Please try again in a minute.” |
While the answer is on its way, the player sees “Checking the whitelist…”. The text you write under Settings > Whitelist as the Refusal Message is added to every one of these. The messages are plain text: staff reasons, your message and the Discord server’s name have control characters and angle brackets removed. Staff whose game account is linked get in without seeing these screens, except when MonoAdmin cannot be reached.
Community Service
A player sent to community service sees a counter on screen: “Community service: {remaining} of {total} tasks left. Go to the marker.” A marker is drawn in the world at the current task’s spot. They stand on it and the task counts, then the next spot appears.
- Each task takes at least a few seconds, and longer when the next spot is far away. MonoAdmin reads the player’s position on the server, so a modified game cannot skip tasks.
- Spots are your pickup points, or the automatic ring when fewer than two are switched on. They are placed with the Game World Editor.
- A player who walks out of the community service area is put back.
- Tasks cannot count while your server is not linked to MonoAdmin. The order stays in force, and the player stays in service until the server is linked again.
Cleanup Countdown
When staff run a vehicle, NPC or object cleanup with a countdown, every player sees a notice when it starts, and again at 60, 30, 10 and 5 seconds left (the ones that fit in the countdown):
Server cleanup: unoccupied vehicles will be removed in 30 seconds. Get into your vehicle to keep it.
The wording names the kind: “unoccupied vehicles”, “NPCs” or “objects”. A vehicle with someone in it is not removed, and players are never removed. If staff cancel before the end, players see “The cleanup of {what} was cancelled.” Staff run cleanups from the dashboard or the Self tab; see Dashboard and The Self Tab.
Announcements and Shouts
An announcement goes to every player whose game has finished loading. It is a single line of up to 300 characters, shown for between 3 and 60 seconds (staff choose 5, 10, 15, 30 or 60 seconds in the panel, and 10 seconds from the menu). Players still loading when it is sent do not see it. It is labeled Announcement.
A shout goes to one player: up to 200 characters, shown for a few seconds (the menu uses 8 seconds). Only that player sees it. Some styles sign it Staff.
A server notice is an amber toast for system messages such as a cleanup warning. Short results, for example a reply to a report or a link confirmation, appear as small toasts.
How They Look
You choose the look under Settings > Display, and it applies right away. Each kind has five styles:
| Kind | Styles (the first is the default) |
|---|---|
| Notifications | Classic, Glass, Minimal, Banner, Bubble |
| Announcements | Banner, Spotlight, Ticker, Broadcast, Toast |
| Shouts | Alert, Megaphone, Sticky, Flash, Marquee |
Staff can also send one announcement in another style than the default. Changing styles needs the Edit Settings permission. The warning, the community service counter, notices, toasts, shouts and the report window all wear the project’s theme as well. Announcements wear it too, unless the project picked an Announcement Theme of their own. Each theme draws the announcement styles in its own look. All of this is explained in Display, Themes and Time Zones.
These screens use the project’s time zone for every date they print, so staff, players and the web panel give the same time for the same moment.