ReportSystem

Players report trouble, staff work one clean queue.

ReportSystem lets players report trouble or open a ticket, then your staff work every case from one shared queue in game, on Discord, or from the console.

Somebody breaks a rule, a player types the report command, and the case is sitting in your staff queue with an id on it before the argument in chat has finished. That is the whole job of ReportSystem. It turns loose complaints into cases your team can list, claim and close. Every case carries a status, and when reports start piling onto one player in a hurry I raise my hand and tell you loudly.

Supported Features

• Reports with an id: a player names who and what happened, and the case files itself with its own number and an open status.
• Tickets for everything else: not every problem is about a person, so a general ticket lands in the same queue.
• One queue, three states: open, claimed or closed. Nothing quietly slips down the back of the sofa.
• Work it from the console: your staff list, view, claim and close any case from the console or over RCON.
• An in game list for staff: staff holding the node can see the open cases without leaving the game.
• Discord posts: switch on a webhook and every report and ticket lands as a tidy embed in your staff channel.
• It shouts when it matters: when the same player collects several reports in a short window, an alert fires on your alert webhook, so the real problem finds you.
• Where and who: a report can carry the map, the tribe and both players' coords, so staff walk straight to the trouble.
• The reporter hears back: they get told the report went in, and told again when staff close it, which stops the did anybody even read it grumbling.
• Offline targets still count: report somebody who logged off and the case files under their name all the same.
• A guard against junk: a cooldown between reports and a shortest reason length keep the queue worth reading.
• It tidies up after itself: closed cases are pruned after a number of days you choose.
• Your language on the desk: name a language in the config and the lines players and staff read come from a plain text file you can edit, so reporting is easy in any language.

Console & RCON Commands

Command	What It Does	Where
ReportSystem.Reload	Reload config.json without a restart.	Both
ReportSystem.List	List the open cases in the queue.	Both
ReportSystem.View <id>	Show the full detail of one case.	Both
ReportSystem.Claim <id>	Mark a case as claimed by you.	Both
ReportSystem.Close <id> [note]	Close a case, with a note if you want one.	Both
ReportSystem.TestDiscord	Send a test post to your webhook.	Console

Player Commands

Every command name is set in config.json, so rename away or switch one off.

Command	What It Does
/report <name> <reason>	File a report on a player.
/ticket <message>	Open a general ticket for staff.
/myreports	See your own cases and where each one stands.
/reports	Staff only. List the open cases in game. Needs the staff node.

Permissions

Node	What It Unlocks
ReportSystem.Staff	The in game /reports list.

The one node covers the in game list and nothing else. With Permissions switched off or not installed, that list is closed to everybody and your staff work the queue from the console or RCON, which are admin only anyway. So I fail closed on the in game list and stay safe either way.

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 (optional, works without it, and it only gates the in game staff list)
• A Discord webhook (optional, works without it)

Installation

1. Unzip the download so you get a folder named ReportSystem.
2. Put that folder in ArkApi/Plugins/. AsaApi wants the folder to carry the same name as the DLL, so do not rename it.
3. Open ReportSystem/config.json and set your command names, your staff node, and your Discord webhook if you want the posts.
4. Relaunch the server with AsaApiLoader.exe.
5. Watch ArkApi.log for the loaded line, then file a test report and work it from the console.

Support & Help

Stuck on a step, or something looks off? Come and find me in the Discord and I will walk you through it: https://discord.gg/8GGaEzWk9p

Frequently Asked Questions

What does ReportSystem do?

ReportSystem gives your players a proper way to report trouble and gives your staff a queue to work it in. Each report or ticket gets an id and a status, staff claim and close cases from the console or in game, and every case can post to your Discord.

How do I install ReportSystem?

Unzip the download, keep the folder named ReportSystem, and put it in ArkApi/Plugins/. Set up config.json, restart with AsaApiLoader.exe, and look for the loaded line in ArkApi.log.

Can players report somebody who already logged off?

Yes. The reporter types the name, the case files under that name, and I tell the reporter the target was offline. Your staff still get the full report, so nobody dodges one by quitting quickly.

How do I keep the queue from filling with junk?

Two settings do that work. A cooldown makes a player wait between reports, and a shortest reason length throws out the empty ones. Closed cases are also pruned after a number of days, so old clutter clears itself.

What happens when one player gets a pile of reports at once?

That is the alarm bell built into ReportSystem. When enough open reports land on the same player inside your window, an @here alert goes to your alert webhook. You catch the real problem without having to read every case yourself.

Do I need Discord or Permissions?

Neither. Discord posts stay off until you add a webhook, and everything works in game without one. Permissions only guards the in game staff list, and without it that list stays shut while your staff use the console or RCON.

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.