Skip to content

Install VoidAC ​

You need a FiveM server, an active VoidAC license and access to the server's files and console. Use a current FXServer artifact; the resource uses FiveM's Node.js 22 runtime.

1. Download your resource ​

Sign in to the dashboard, open your server and choose Download on Overview.

The browser downloads voidac.zip and shows the commands to add to server.cfg. You can download twice within 30 seconds. If you reach that limit, the button shows when you can try again.

Existing installation?

A new download replaces the previous resource key. Replace the whole package, including voidac.key. To update a running installation without changing its key, use Update FiveM resource.

2. Put VoidAC in resources ​

Extract the ZIP and place its VoidAC folder inside your server's resources directory. Avoid an extra nested folder.

text
resources/
└── VoidAC/
    ├── fxmanifest.lua
    ├── voidac.key
    ├── voidac.integrity.json
    ├── client/client.lua
    ├── server/server.lua
    ├── server/runtime.js
    └── web/

Keep the included key file in this folder. Do not paste a dashboard license label into it: the resource expects its issued 32-character server key.

All settings are managed from the dashboard. There is no editable config.lua. The bridge is built into server.lua; the updater and evidence uploader use the same JavaScript runtime. An unused configuration file from an older installation is archived locally as .voidac-legacy-config.lua on startup.

Keep the resource code and signed inventory unchanged. From 1.8.32, you may add standalone external server_script, client_script and shared_script references to fxmanifest.lua without changing its original content. See Manifest integrations. External resource code is not signed or reviewed by VoidAC.

3. Add to server.cfg ​

Add these lines before gameplay resources that integrate with VoidAC:

cfg
add_ace resource.VoidAC command.restart allow
add_ace resource.VoidAC command.stop allow
ensure VoidAC

ensure starts the resource. The restart permission is used by the updater; the stop permission lets VoidAC shut itself down on a failed file or license check. These do not enable a full-server restart.

Folder names are case-sensitive on Linux. Keep the folder named VoidAC; if you rename it, update both commands and any integration references.

4. Start the resource ​

Save server.cfg and start or restart your server. If it is already running, use its console:

text
refresh
ensure VoidAC

When replacing a currently running installation, use restart VoidAC after refresh instead of ensure.

On the first valid start, the license binds to this FiveM server's public IP. The dashboard then receives the installed version, server name and player activity. Choose your detection settings and support Discord before opening the server to players.

Check the console

If the dashboard stays disconnected, look for [VoidAC] and [VoidAC License] messages. See Troubleshooting before repeatedly downloading or restarting.

Optional: restart the full server from the dashboard ​

This is separate from a normal resource update. Only enable it when txAdmin supervises FXServer and you want authorized dashboard admins to be able to disconnect everyone and restart the server:

cfg
set voidac_dashboard_restart 1
add_ace resource.VoidAC command.quit allow

Do not grant generic command allow permissions. See installation guide for the confirmation flow and required dashboard permissions.

Keep the key private ​

Never publish voidac.key, upload it to a public repository or include it in a support screenshot. A package belongs to one license and one bound server IP. Moving to a different public IP requires an IP reset.

Update an existing installation ​

Open your server's Overview. Updates in the dashboard shows the published changes; release history is not duplicated in these docs.

  • Update FiveM resource requests an installation on the connected server, with a confirmation and progress display. You need Settings → Edit.
  • Auto Update installs a published release automatically and restarts only the VoidAC resource.
  • Download creates a fresh ZIP and replaces the installation key. Replace the entire package, including its new voidac.key; do not mix files from different downloads.

The updater checks the release signature and file hashes before and after installation. Your key and centrally saved settings are retained during an in-place update. A failed installation rolls back rather than marking itself complete. Added external manifest references are retained; the rest of the signed manifest is replaced by the new official version.

The FiveM process needs write access to the VoidAC folder, including its .voidac-update staging directory. An EACCES, EPERM or read-only filesystem error requires your hosting provider to fix ownership or write permissions. Do not use chmod 777 or run FiveM as root. After repairing access, request a new update or run voidac_update from the server console.

Versions 1.8.10 and older require one manual full installation before using the current updater. New detections may be configured in advance, but their minimum resource version must be running before they can work.

Restart after installation ​

Automatic updates restart only VoidAC. A dashboard-driven installation may show Restart later and Restart now. Later keeps the running code until a restart; it does not undo the installed files.

A full-server restart requires Settings → Edit, Resources → Edit, a running txAdmin monitor and the explicit voidac_dashboard_restart / command.quit opt-in shown above. A second confirmation precedes the warning and shutdown. All players disconnect; txAdmin must restart the FiveM process. Do not enable this on an unsupervised server.

Use the dashboard's progress and the [VoidAC Update] console lines to check the result. Completion is confirmed only when the new resource reports its running version; a click alone is not a successful update.

VoidAC documentation