Frequently asked questions

Purchases happen in the DVmods Discord. Join the server and open the purchase channel or a ticket to get payment and delivery instructions.

The current payment methods are listed on Discord when you make a purchase.

Support runs on Discord. Tell us your server framework and any error message so we can get started quickly.

Refunds are covered in the refund policy. Ask on Discord before buying if you are unsure the product fits your server.

Copy the dvac resource into your server resources folder and add your license key (set dvac_license) and ensure dvac to server.cfg. Screenshots also need the open-source screenshot-basic resource. Everything else is configured in the web panel.

The ESX bridge is included. Core detections (movement, weapons, explosions, entities, rules) work without a framework. QBCore, QBox and vRP bridges are planned; you can also write your own, as the bridge is an open file.

The anticheat is designed to be light. There are no Wait(0) loops on the server, checks are staggered across players and heavy work (network, crypto) runs in a separate JS bridge. We will publish measured numbers during beta testing.

Every module starts in log-only mode, so you see detections before enabling punishments. Strike points, grace periods, the whitelist (ACE, ESX groups, panel) and unbanning from the panel all help. Every ban has a code the player can use to appeal.

Player identifiers (e.g. Rockstar license, Discord ID), names, sessions, detections and punishments. IP addresses, images and old data are deleted after a retention period you can adjust in the panel. Data is separated per server at the database level.

Yes. Detections run on the server, bans and settings are cached locally and events are queued for later. The license has a signed grace period.

The anticheat is in development. Join the Discord to become a beta tester and hear first about pricing and launch.