XML Error Detection
Scans your server's XML config files and alerts you on Discord the moment a syntax error is introduced.
What it does
DayZ servers use XML files for a large part of their configuration — types.xml controls loot, events.xml controls spawns, mapgroupproto.xml controls buildings, and more. A single misplaced tag or missing bracket in any of these files can cause the entire server to fail to start correctly.
The XML Detection module scans your configured XML files on a regular schedule (every 10 minutes) and posts an alert to Discord the moment a syntax error is found. It also posts again when the error is fixed, so you know when you're clear.
How it works
- Vigil downloads each configured XML file from your Nitrado server
- It validates the file using a strict XML parser
- If an error is found for the first time, it posts an alert with the file name, the error message, and the line number
- It tracks which errors it has already alerted on — you won't get spammed with the same error every 10 minutes
- When a previously-errored file passes validation, Vigil posts a resolution alert
Configuration
Scan paths
A list of file paths on your Nitrado server to scan. Enter one path per line. Paths are relative to your server's game root directory.
Example paths:
mpmissions/dayzOffline.chernarusplus/db/types.xml
mpmissions/dayzOffline.chernarusplus/db/events.xml
mpmissions/dayzOffline.chernarusplus/cfgspawnabletypes.xml
You can find the exact paths for your server's XML files by browsing your Nitrado file manager. Look inside the mpmissions folder for your active mission.
Alert on resolution
When enabled, posts a second alert when a previously-errored file now passes validation. Useful confirmation that your fix worked.
What the alert shows
When an error is found:
- The file path (shortened for readability)
- The parser error message
- The line number where the error was detected
Suggested Discord channel
#admin-alerts — this is operational information for server admins, not something players need to see.
Vigil scans files at most once every 10 minutes regardless of how frequently the module runs. This is to avoid excessive Nitrado API calls.