Owner setup and server control
These commands are the control layer behind Legion: connect the Nitrado server, assign Discord, route channels, configure feed output, manage restarts and make supported file edits without asking owners to hand-edit every path.
Setup commands connect the Nitrado token, assign the Discord server, create the starting channel layout and activate log downloading for the selected DayZ service.
Setup is the part that makes every other page work. Without the token, Legion cannot read logs or use Nitrado file paths. Without Discord assignment and channel routing, the bot may parse records correctly but have nowhere useful to post them.
Settings commands control server name, logo, embed colour, channel routing, location output, players-online output, glitch feed routing and other database-backed choices Legion uses when posting feeds.
These settings decide what players and staff actually see: which feed goes where, whether posts include full map links or safer near/no-link output, which glitch items are separated, and how the server is branded in embeds.
Scheduler commands handle restart-related gameplay edits and timing-dependent actions so changes can be applied in the right server window instead of during active play.
It is used for edits that should line up with restarts, such as base damage windows or gameplay file changes. Owners can configure the schedule, view it, cancel it and keep scheduler log output separate from player-facing feed channels.
Nitrado commands work through the saved token to read server state, dashboard settings and file paths without owners needing to copy the same Nitrado details into every feature.
That covers practical server management: dashboard settings, damage toggles, server name/description, automated tasks, status checks and restart-related control. Discord becomes the owner panel while Nitrado remains the server host behind it.
Event spawner helpers generate supported event/object files from owner-provided values so admins can add events without rebuilding XML by hand.
It is for supported DayZ event types such as items, statics, vehicles, animals and infected. The owner provides the event values and Legion builds the file pieces that normally require repetitive XML edits.
File helpers download, edit and upload supported server files for known folders and gameplay sections, including supported damage toggles and base file edits.
The file commands target known Nitrado folders such as database, environment, custom and mission files. Supported gameplay helpers can adjust registered object/spawn gear references or damage settings without making owners manually find the same path each time.
Legion stores the server service ID, token, map, Discord guild, channels and owner settings. When a feed or command runs, it uses those saved details to know which Nitrado server to read, which file path belongs to that map and which Discord channel should receive the output.
The point is to remove repeated manual file hunting. Owners still choose what changes are allowed, but the bot handles the correct service selection, Nitrado API call, supported folder target and Discord response.
Generated helpers work the same way. Teleporter generation starts from Object Spawner marker positions and turns them into supported teleport files. QR generation takes a URL, coordinates and orientation and turns it into an Object Spawner sign entry. File commands still keep the owner in control; they just remove the repeated path and formatting work.
| Area | Controls | Result |
|---|---|---|
| Setup | /setup token, /setup assign discord,
/setup channels, /setup activate
|
Adds the service connection, links it to the Discord guild, builds the starter channel layout and enables log download/processing for that server. |
| Channel routing | /settings channel assign and
/settings channel create
|
Decides where feeds, maps, economy, logs, status and moderation output posts. |
| Feed output | /settings configure locations,
/settings configure glitchfeed, /settings playersonline
|
Controls per-feed location detail, watched placement groups, player online text/voice/command behaviour and whether public channels get safer output. |
| Server actions | /server restart, /server stop,
/server delete stop, /server break loop
|
Lets permitted staff handle restart and stop-file issues through Discord. |
| Files and generated helpers | /file download, /file gameplay edit,
/file base, /generate teleports file, /generate qrcode sign
|
Downloads or edits supported files, updates known gameplay sections and generates Object Spawner-based helper files using the selected server's Nitrado path. |
| Command | Options | Use |
|---|---|---|
/setup token |
Nitrado token setup. | Adds the server connection Legion uses for logs and server files. |
/setup assign discord |
Discord assignment. | Links the selected Nitrado server to the Discord guild. |
/settings view |
Server selection. | Shows the current settings and channel routing. |
/settings channel assign |
Feed/status/economy/log channel and target channel. | Routes output to the correct Discord channel. |
/settings configure locations |
Per-feed location visibility options. | Controls exact, near and link-style location output. |
/server restart |
Selected server. | Restarts the Nitrado server through Discord permissions. |
/scheduler gameplay edits |
Supported gameplay edits and scheduling. | Schedules supported gameplay changes around restart timing. |
/file gameplay edit |
Supported gameplay edit type and values. | Applies supported gameplay.json edits without manual path hunting. |
/generate teleports file |
Object Spawner input and marker names. | Generates supported teleporter files. |
/generate qrcode sign |
URL, coordinate and orientation fields. | Generates an Object Spawner QR sign file. |
