WarnSystem

WarnSystem lets your staff warn players, keeps a full record for each one, and mutes the repeat trouble makers by itself, with no other plugin needed.

Every server has that one player who will not let it go. WarnSystem gives your staff a fair way to handle them: a written warning with a reason, a record that sticks, and a mute that fires on its own once the warnings pile up. Clear rules, clear consequences, no shouting match. The mute is built in, so there is no second plugin to install, and every action can land in your staff Discord channel.

Supported Features

• A record that sticks: every warning is kept per player with the reason, who gave it and when.
• The mute fires itself: once a player reaches your warning limit I mute them without anybody having to remember to.
• It gets firmer: switch on escalation and each warning past the limit mutes for longer, up to a ceiling you set.
• The mute is built in: I watch chat and drop a muted player's messages myself, so there is no other plugin to install for it to work.
• Mute by hand too: staff can mute a player for any number of minutes and lift it again whenever they want.
• Warnings can expire: old ones stop counting toward the auto mute after the days you set, while staying in the history for context.
• Online or offline: name a player who is on, or paste a player id to warn somebody who has already left.
• Commands can still work while muted: leave the setting off and a muted player may still use slash commands, so only their normal chatter is blocked. Handy when the muted one is staff.
• A private word: the warned player can be told quietly, with the reason, instead of in front of everybody.
• They can check themselves: any player can look at their own record, which cuts down the arguments a lot.
• Discord logging: every warning, mute and unmute can post to a staff webhook. It ships off.
• Reload while running: change the config and load it again with no restart.
• Your language on every notice: set it in the config and the warning a player reads comes from a plain text file you can edit, so nobody is punished in a language they do not follow.

Console & RCON Commands

Player Commands

Command names live in config.json, so rename them or switch one off. The first five are staff only. The last is for anybody.

Permissions

The staff commands are fail closed. With the Permissions plugin missing, or a player not holding the node, they simply do nothing, so they cannot be turned against you. A mute already running keeps working, and the self check command needs no node at all.

Config

To see every configuration option, visit our docs. To edit your config files the easy way, open our configuration editor.

Requirements

• AsaApi v2.01 or newer
• A Windows server running ArkAscendedServer through the AsaApi loader
• Permissions, needed for the staff chat commands, since they are fail closed without it
• A Discord webhook (optional, works without it)

Installation

1. Unzip the download and put the WarnSystem folder into ArkApi/Plugins/. Keep the folder named WarnSystem, because the loader wants the folder and the DLL to share a name.
2. Open WarnSystem/config.json and set your warning limit, your mute minutes and your command names.
3. Give your mod and admin groups the WarnSystem.Use node.
4. Want the Discord log? Open discord.json, turn Enabled on and paste your webhook URL.
5. Restart the server through AsaApiLoader.exe and watch ArkApi.log for the loaded line.

Support & Help

Hit a wall, or found a bug? Come and tell me in the Discord and we will sort it out together: https://discord.gg/8GGaEzWk9p

Frequently Asked Questions

What does WarnSystem do?

WarnSystem is a moderation tool for your staff. It records every warning against a player with the reason and who gave it, mutes a player by itself once the warnings reach your limit, and can make each further mute longer than the last.

How do I install WarnSystem?

Unzip the WarnSystem folder into ArkApi/Plugins/, set your warning limit and mute times in config.json, hand your staff groups the WarnSystem.Use node, and restart. Once it loads, ArkApi.log shows a line for it.

What happens when a player reaches the warning limit?

The mute fires on its own for the minutes you chose. With escalation on, every warning past the limit mutes for longer, capped at the ceiling you set, so it is firm without ever getting silly.

Do I need another plugin for the mute to work?

No. WarnSystem watches chat and drops a muted player's messages by itself, so there is no chat plugin or mute plugin to add on top.

Can a muted player still use chat commands?

That is your call. Leave the setting off and a muted player can still run slash commands while their normal chat is dropped, which matters when the muted one needs to unmute themselves. Turn it on and their commands are blocked too.

What if I do not run the Permissions plugin?

Then the staff commands stay locked, on purpose. They are fail closed so nobody can warn or mute without holding the node. A mute already running keeps going, and the self check command stays open to everybody.

Was any AI content used in the making of this?

The source code itself was fully created by myself. I do use ChatGPT occasionally to generate product images, and I do use ChatGPT to generate the website descriptions. I do this because I don't speak native English perfectly. I am natively from Sweden, so I use GPT to help translate and write product descriptions. I also will sometimes use GPT to write better English logs. Majority of my Free plugins are open source, so you can review the code yourself and freely fork and edit it to your liking.