WARDENConnect with a Nitrado long-life token to discover your accessible game servers.
SERVER OWNER / COMMAND CENTRE
YOUR SERVER.
YOUR CONTROL.
Connect a Nitrado server and organise the management features shown in your reference screenshots. Public file tools remain available without a connection.
NOT CONNECTEDNitrado connection not started
01 / STATUS
OWNER OVERVIEW
Welcome messages, reaction roles, tickets, levelling and other community features.
Use a map image, place pins and keep a local marker set for a selected server.
OPEN MAP →Existing file utilities plus the tools listed in your Brigade Killfeed screenshots.
OPEN TOOL LIBRARY →Experimental build: Nitrado status, player list, read-only settings, supported setting changes, stop/restart, log discovery and allowlisted file editing use the API connector. Discord automation and browser-local planners are still previews.
02 / SERVER LINK
NITRADO CONNECTION
CONNECT YOUR SERVER
Enter the Nitrado long-life access token generated for your own Nitrado account. The connector checks the token and lists the game servers it can access.
- Use a token with only the permissions this hub needs.
- The token is sent to the same-site backend, never to browser storage.
- This preview keeps the token in page memory only. Refreshing or closing the page clears it.
- Never paste your token into Discord, public chats, screenshots or support tickets.
Nitrado describes long-life tokens as valid for many years and explicitly says to keep them secret. Nitrado API documentation ↗
Nitrado permission notes: server stop/restart requires
ROLE_WEBINTERFACE_GENERAL_CONTROL; online-player reads require ROLE_WEBINTERFACE_GAME_RCON_READ; settings use ROLE_WEBINTERFACE_SETTINGS_READ / ROLE_WEBINTERFACE_SETTINGS_WRITE; file reads require ROLE_WEBINTERFACE_FILEBROWSER_READ; file edits and same-folder copies also require ROLE_WEBINTERFACE_FILEBROWSER_WRITE; backup listing requires ROLE_WEBINTERFACE_BACKUPS_READ. Token validation does not guarantee every action is permitted.Deployment requirement: The Nitrado API connector is included in this project as a Cloudflare Worker route. The dashboard drag-and-drop ZIP workflow cannot compile a Pages
functions/ folder; this package uses the supported _worker.js advanced-mode file for the API route. It still needs a live Cloudflare deployment and real Nitrado account testing before it can be called verified. Cloudflare advanced mode docs ↗SERVER FILE DISCOVERY
Browse server directories and search for configuration or access-list files.
No server selected.
LIVE SERVER CONTROL
Actions below are sent to the selected Nitrado game server. Stop and restart require an explicit confirmation. The API documentation currently exposes stop and restart, but not a separate immediate start action.
Connect and select a server to load its status.
ONLINE PLAYERS
No player data loaded.
SERVER SETTINGS
Read current Nitrado settings, then change one setting by category and key. Nitrado permissions apply. Confirm every live change before sending it.
Settings have not been loaded.
No setting changes sent.
SERVER LOGS
Search Nitrado's file browser for .ADM and .RPT log files. Availability depends on your service permissions and server paths.
No log search run yet.
SERVER FILE EDITOR
Load a server file for inspection. Supported configuration files can be edited and saved with a same-folder pre-edit copy; ADM/RPT logs are read-only. Writes are limited to 1 MB and an allowlist of configuration filenames.
No file loaded. Saving creates a pre-edit copy on Nitrado first.
NITRADO BACKUPS
View available Nitrado backups. The current official API documentation exposes backup listing and restore, but does not document manual full-server backup creation. Warden Hub automatically creates an on-server copy of any supported config file before overwriting that file.
No backup list loaded.
For a full server backup, use the Nitrado panel's backup controls. Warden Hub will not pretend a file-copy is a full server snapshot.
03 / COMMUNITY
DISCORD MANAGEMENT
The community features from your screenshots, grouped in one place. These cards are feature entries, not live bot controls yet.
04 / AUTOMATION
SCHEDULED TASKS
Plan several tasks with separate times and notification channels. This saves a local task plan only; a connected bot/backend must execute the schedule.
No task plans yet. Add one above.
05 / PLAYER ACCESS
BANS & WHITELIST
SERVER BAN LIST
Keep a draft list of player identifiers for review.
SERVER WHITELIST
Keep a draft list of approved players.
The lists above remain local drafts. Use live file search to locate server-side ban or whitelist files when Nitrado exposes them. Open supported files in the editor to inspect them. File formats and names vary by game/server setup, so Warden Hub does not assume one universal path or automatically parse every format.
FIND SERVER ACCESS FILES
Connect to Nitrado first.
06 / ACCESS CONTROL
PERMISSIONS
07 / WORKSHOP
DAYZ TOOL LIBRARY
The 10 existing tools remain available. The additional entries from your screenshots are included in the full catalogue with honest development labels.