MXI Sentinel Documentation
Complete setup instructions and technical reference for deploying MXI Sentinel v4.0.0 anti-cheat engine on FiveM and connecting to MXI Nexus Cloud.
1. Installation Guide
MXI Sentinel v4.0.0 is a hybrid C# (.NET Assembly) and Lua resource. Follow these steps to install it on your FiveM dedicated server or RDP.
Extract the resource folder to your FiveM server resources directory:
2. Database Setup
Import the install.sql file into your MySQL / MariaDB database.
3. server.cfg Configuration
Add your MXI Nexus License Key and environment convars to your FiveM server.cfg file:
# === MXI SENTINEL CONFIGURATION === set mxi_sentinental_license "MXI-YOUR-GENERATED-LICENSE-KEY" set mxi_nexus_api "https://mxi-nexus.vercel.app/api/log" set mxi_server_id "mxi-rp-1" # Webhooks (Discord Alerts) set mxi_webhook_bans "https://discord.com/api/webhooks/YOUR_BAN_WEBHOOK" set mxi_webhook_admin "https://discord.com/api/webhooks/YOUR_ADMIN_WEBHOOK" # Integrity & DRM Secrets set mxi_gatekeeper_key "MXI_GK_7f3a9c2e4b1d8f5a6e0c3b9d" set mxi_allowed_hostname "Your FiveM Server Name" # Ensure Load Order ensure oxmysql ensure mxi_sentinental
Session Tracking
In v4.0.0, the MXI Nexus platform automatically tracks your server sessions. By analyzing `lastSeen` timestamps and event streams, Nexus can track distinct server sessions across up to 24h of active connection logs, visible in the Sessions tab.
Challenge-Response Heartbeat
v4.0.0 introduces a cryptographic Challenge-Response Heartbeat mechanism. The client script must respond to dynamic server-side generated challenges every 60 seconds. Missing the heartbeat results in an automatic session timeout.
Temp Bans
You can now issue Temp Bans directly from the MXI Nexus dashboard or via in-game command. Unlike permanent HWID bans, Temp Bans automatically expire based on Unix timestamp expiry.
Migration from v3 to v4
Upgrading from v3.0 to v4.0.0 is straightforward:
- Replace the old mxi_sentinental folder with the new v4.0.0 resource.
- Ensure your license key is still valid on the MXI Nexus dashboard.
- The database schema remains the same, but the cloud API will now support session tracking natively.
- Restart your server to initiate the v4.0.0 Challenge-Response Heartbeat.
Troubleshooting & FAQ
Q: License Validation Failed on Server Startup?
Ensure you added set mxi_sentinental_license in server.cfg before ensure mxi_sentinental, and verify that the license is marked Active in MXI Nexus.