Evidence and enforcement
Legion gives staff a Discord layer for raw log files, automatic PVE enforcement, Nitrado ban/whitelist/priority lists and moderation records.
Log Feed keeps raw evidence close to the Discord feeds. Staff can download the current ADM log, a kill-only log or the stored log set when a formatted post needs backing. It is for the moments where a Discord embed is not enough and the owner needs the original server-side record.
That matters for disputes because the feeds are readable summaries, while the downloaded log is the raw evidence trail.
Autoban handles rule sets where the server already knows an action should be punished. On PVE servers, owners can enforce rules around player kills or PVP deaths instead of waiting for staff to manually catch every illegal fight. Cheat-style detection settings can also be configured separately where the live bot supports them.
The point is not to replace staff judgement for every case. It is for clear server modes where the rule is already defined: a PVE kill should ban, a PVE death caused by another player should ban, or autoban should be off and only report.
Ban, Whitelist and Priority commands write to the Nitrado-backed server lists from Discord. Staff can add, remove and view players without opening the Nitrado dashboard for every change, which keeps access tighter and leaves the action visible in the Discord moderation trail.
Moderation is the layer around those tools: permission checks, bot logs, player searches, list views and command results. Owners can keep staff-facing results in staff channels instead of letting sensitive player searches, ban actions or raw logs appear in public.
Legion reads log files for evidence, stores useful player records in the bot database and uses the saved Nitrado token when a staff command needs to update a ban, whitelist or priority list. The Discord command is the control panel; Nitrado remains the server-side source for the lists and files.
Autoban sits between the event feeds and the Nitrado list controls. When a server is configured for clear PVE enforcement, the bot can act on the matching kill or death record instead of leaving it as a normal feed post. Staff can still use the log download commands when they need the original file behind the action.
Admin player search shows why the stored data matters. Legion can link Discord users to gamertags, identify mutual servers, show associated gamertags, expose recent commands and count buttons, dropdowns and total command usage. That gives staff useful context before they decide whether a ban, whitelist, priority change or support reply is needed.
Log rotation keeps the raw file side available too. When a new log is detected, Legion can upload the previous file into Discord so staff have the source record beside the formatted feed cards. The readable embed is the quick answer. The downloaded ADM file is the evidence trail.
| Setting | Controls | Use |
|---|---|---|
/settings channel assign |
Log Feed and Bot Logs channels. | Keeps raw logs, staff command results and ban actions away from public player channels. |
/settings configure misc |
Log feed and misc staff-channel toggles such as purge/log behaviour. | Controls whether automatic log output is visible and how staff channels are maintained. |
/settings autoban config |
PVE autoban rules for kills or deaths based on server rule mode. | Lets PVE communities choose whether illegal PVP kills, PVP-caused deaths or no automatic enforcement should apply. |
| Command | Options | Use |
|---|---|---|
/logs download current |
filetype: .ADM or .txt. |
Downloads the current log file. |
/logs download kills |
Kill-only log file. | Downloads a trimmed kill evidence file. |
/ban add |
Gamertag or comma-separated gamertags. | Adds players to the Nitrado ban list. |
/ban remove |
Gamertag or comma-separated gamertags. | Removes players from the Nitrado ban list. |
/whitelist add |
Gamertag or comma-separated gamertags. | Adds players to whitelist. |
/priority add |
Gamertag or comma-separated gamertags. | Adds players to priority list. |
