Warnings, Mutes and Community Service

Bans end a player’s session. Warnings, mutes and community service are the lighter tools: they keep the player in the game and change what they can do or see. This page explains how each works from the moment you issue it. Issuing and revoking are the same for all three and are described in Punishments.

Warnings

A warning is a message the player must read and confirm before they carry on. Issue one with Warn on a player’s profile, or Warn from the Issue Punishment menu on the Punishments page. It needs the Warn permission and a reason of up to 500 characters.

What the Player Sees

A card appears over their screen with:

• the title “You have received a warning”,
• your reason,
• “Issued by” and your name,
• a button, I understand, that is disabled for the first 3 seconds so it cannot be dismissed without reading,
• the line “You can continue playing once you have confirmed this warning.”

If a player has several waiting, they see them one at a time, in order. After they press I understand, the next one appears.

When It Is Shown

• Player online. The warning appears immediately.
• Player offline. It is saved and appears when they next join. The toast says “Saved. Alex is offline and sees it when they next join.”
• Not confirmed yet. A warning stays Active until the player confirms it, however long that takes, and it is shown again on every join until they do. There is no expiry.

In the Panel

Open the warning to see Acknowledged: the time the player confirmed it, or “Not yet: shown to the player when they are next online”. Once confirmed, its status is Completed.

The confirmation is passed to MonoAdmin when the server is connected. If it is not, the server holds it and sends it after the next connection. It holds it in memory only, so if the game server restarts before that, the confirmation is lost and the player sees the warning again.

Revoking a warning leaves it in the player’s history, marked as revoked. Warnings do not count towards bans automatically: MonoAdmin keeps the record, and your rules decide what a third warning means.

Mutes

A mute stops a player from using one channel of communication. There are two types, and a player can have both at once.

Mute	Stops	Works with
Voice Mute	The player’s voice chat.	Servers using Mumble or pma-voice.
Text Mute	The player’s text chat messages.	Servers using the default chat resource.

See Voice and Text Mutes for the resources MonoAdmin works with and what the panel shows when your server cannot apply one.

Issuing a Mute

On the player’s profile, choose Mute Voice or Mute Text, or Mute from the Issue Punishment menu and pick Voice chat or Text chat. It needs the Mute permission. Choose a duration of 10 minutes, 1 hour (the default), 1 day, 7 days or Until lifted, and give a reason.

The panel only offers what your server can do. If your server cannot mute that kind of chat, the dialog says “This server’s resource can’t mute voice chat.” (or “text chat”) and the confirm button stays disabled. A connected server decides this; while the server is offline the panel goes by what your framework could do.

How a Mute Behaves

• Mutes are kept in your server’s local copy, like bans, so they survive a restart and work without MonoAdmin.
• A mute is applied again every time the player rejoins, for as long as it lasts.
• It is lifted automatically when it expires or when you revoke it. If you revoke it while the server is offline, it is lifted when the server reconnects.
• A player who is offline can be muted. The mute starts as they join.
• The resource does not show the player a message when a mute starts or ends. If you want them to know, tell them with Shout or in your usual channel.

Community Service

Community service sends a player to a marked area to complete a number of tasks, as a lighter alternative to a ban. Issue it with Service on a profile, or Community Service from the Issue Punishment menu. It needs the Community Service permission. You set the number of tasks, from 1 to 500; the dialog starts at 10.

What Happens

1. If the player is online, they are moved to the community service area straight away, wherever they were. If they are offline, service starts when they join.
2. A marker appears in the world and a counter on screen: “Community service: 7 of 10 tasks left. Go to the marker.”
3. The player walks to the marker. Standing on it counts a task.
4. The next marker appears at a different spot, never the same one twice in a row.
5. When the last task is done, the service ends, the status becomes Completed, and the player is released.

The player cannot walk away: anyone who leaves the area is put back at its center within a couple of seconds. The order stays in force through restarts and rejoins until the tasks are done or you revoke it.

The server, not the player’s game, decides whether a task counts. It checks that the report matches the task it handed out, that the player is really standing within a few metres of the marker, and that enough time has passed to have walked there. Faking the report from the client gains nothing.

Progress is counted by MonoAdmin, so a task cannot be counted while the server cannot reach it. The marker stays where it is, and the task counts once the link is back.

In the Panel

The details of a community service show Progress, such as “3 of 10 tasks done”, as a bar. Revoking cancels the remaining tasks and releases the player; the dialog says so.

The Area and the Task Spots

Where service is done is a setting of the whole project, not of one punishment. It has a center, a radius and a list of pickup points where players collect trash. Until you change it, it is centered on Legion Square with a radius of 40 metres.

• You place the area and its points in game with the Game World Editor, which needs the Game World Editor permission. The web panel only shows the result, under Settings > Game Settings, in Community Service Area. See Game World Editor.
• With fewer than two pickup points switched on, players are sent to an automatic ring of eight spots around the center.
• If you move the area while players are serving, each one gets a new task in the new area and is moved there if they are outside it.

One at a Time

A player can have one active voice mute, one active text mute and one active community service order at a time, alongside any number of unconfirmed warnings. If you try to issue a second of the same kind, the dialog tells you to revoke the first. Revoke it or let it end, then issue the new one.

Related

• Punishments covers durations, reasons, statuses and revoking.
• What Players See shows these screens from the player’s side.
• How Bans Are Enforced explains the local copy that also holds mutes and community service.