How VoidAC works
VoidAC has three parts: the website, your FiveM resource and the VoidAC services. Configuration and saved player records live in the central database; the resource supplies live game information and applies authorized actions on your server.
From purchase to a connected server
- Create and verify your website account. Google and Discord connections are linked under Account settings, not shared between accounts.
- Redeem an unused product key in the dashboard. Creating or receiving a key is not the same as redeeming it. Only the account that redeems it owns that server.
- Download the server's ZIP and follow Installation. The generated
voidac.keyis the resource credential, not the product key displayed in an order. - Start the resource. The first validated connection binds the installation to the FiveM server's public IP.
- Check Overview for the resource connection, version and subscription. Your display name is editable; the bound server address is not.
Downloading again replaces the resource credential. An in-place resource update preserves it. Moving hosts requires an approved IP reset, not a manually edited key or address.
Where settings are saved
Change detection methods, actions, thresholds, preferences and webhooks in the server dashboard, then Save. The resource receives the saved configuration through its authenticated connection. There is no editable config.lua to maintain.
An offline server can keep its saved configuration, bans and player history. Editing requires an active license and the relevant team permission. Live players, cleanup commands and monitoring require a running resource. An expired or disabled license locks customization; renewing it does not delete your settings.
Ownership and team permissions
The owner can invite team members by e-mail or linked Discord ID under Team Access. Set each person's permissions explicitly. Website account roles, server team permissions, in-game VoidAC ACE permissions and txAdmin permissions are different systems.
TX trust exempts selected automatic detections for authenticated TX staff. It does not add them to the website team or grant VoidAC commands. Existing bans, device checks and licensing still apply. See Preferences.
Detections and enforcement
Each detection has an enable switch, an action and one or more independent methods. A disabled parent detection disables its methods. New methods require their minimum resource version; saving a switch cannot add missing code to an older resource.
Use Log when testing. Investigate real reports and integrate legitimate gameplay actions before selecting stricter enforcement. For scripted teleports, repairs or effects, use a short server-side integration exemption, not an unrestricted client event.
Bans, lookup and evidence
Bans are saved centrally and checked for the relevant server when a player connects. Removing a ban requires permission for the server that issued it. A staff member on one server cannot remove another server's ban.
Lookup associates identifiers observed together with the same player. Saved records can contain multiple Steam or license identifiers. External Discord/Steam enrichment depends on those services; an identifier alone does not prove an account exists or that someone cheated.
Authorized lookup users can see shared ban records and available evidence. Private data such as IP addresses and device tokens must not be shared through the public-facing lookup view. Screenshots and recordings can be missing if capture fails or a client disconnects; they are not guaranteed after an instant ban. See Bans & evidence.
Releases and integrity
Published packages use a signed inventory covering the official files. Allowed external manifest references are described in Resource integration. The API independently checks key validity, server binding and the active subscription. Recent resources also exchange a fresh verification challenge and a short central verification lease.
File measurements are self-reported by a customer-controlled host; they are not hardware-backed proof that arbitrary local code is unmodified. Obfuscation does not make software uncrackable. VoidAC authorization remains server-side, and private signing material is not included in the customer ZIP.
View published release notes in Updates on the website or in the Discord changelog channel. The docs explain operation rather than maintaining a second release-history page.
Quick task guide
| Task | Where to go |
|---|---|
| Install or replace the resource | Installation |
| Move to another public server IP | Server settings |
| Change methods and thresholds | Detection rules |
| Exempt staff from selected detections | Preferences |
| Authorize a legitimate script action | Resource integration |
| Review or remove a ban | Bans & evidence |
| Select streams or find live players | Map & monitoring |
| Fix a key, connection or update error | Troubleshooting |
