Getting protected

The website

1. Get a signup licence key from whoever runs your QuantiX deployment (a platform administrator issues these).
2. Go to /signup, redeem the key, and create your community. This makes you its owner - the only role that can change tenant settings, manage staff, and wipe data.
3. Sign in from then on with Continue with Discord. There is no password: whoever holds the Discord account that created the community, or anyone given the owner/admin/moderator role from inside the panel, can sign in.
4. From Settings, add each of your FiveM servers. Adding a server is what makes an ingest token available for step 3.

Discord

1. Invite the QuantiX bot to your Discord server from your platform administrator's invite link (it needs permission to read guild roles, post messages, and create threads in whichever channel you route alerts to).
2. In the panel, go to Settings → Discord and generate a setup code. It is single-use and expires in 15 minutes.
3. In your Discord server, run /setup <code> <channel> - the channel you pick is where detections get posted.
4. Each staff member links their own Discord account from Staff so bot actions are attributed to them, not to "the bot".
5. Optional: map Discord roles to staff roles, or to whitelist access, from Staff and Whitelist respectively - either lets your existing Discord roles decide who can moderate or who can join, instead of adding people one at a time.

The FiveM server

1. Download the resource below and unzip it into your server's resources/ folder.
2. In the panel, open the server you added in step 1 and issue it an ingest token. Copy it now - it is shown once.
3. Add to your server.cfg:

   set corevia_api_url "https://cixnservices.xyz"
   set corevia_token   "cvia_i_..."   # the token from step 2, treat it as a secret
   ensure corevia_ac

4. Restart the resource (or the server). The panel's Settings page shows the server going from "never connected" to "online" once it successfully checks in.

Download

Loading the current build…