Skip to content

Resource integrity and request limits ​

Keep the original folder and filenames ​

Install the resource as VoidAC, including capitalization. Keep server/server.lua, server/runtime.js, client/client.lua, the NUI files and the original manifest paths unchanged. From the next protected build, a different resource name disables protection and prints a download/reinstall message in the console.

The package has a signed file inventory. Renaming, deleting or editing an original file breaks verification. This prevents an altered installation from silently continuing to report that protection is active. Download a complete package and replace the installation; never generate your own hashes or edit the signed inventory. Settings are stored in the dashboard database and survive a resource replacement.

Approved top-level external manifest includes remain supported as described in resource integration. They do not permit changes to original VoidAC lines or filenames.

Keep add_ace resource.VoidAC command.stop allow before ensure VoidAC in server.cfg. It allows an integrity failure to stop the resource. Without this ACE, protection is disabled and the console instructs you to stop the resource manually. File checks cannot prevent a person controlling the entire server from modifying its runtime; central license and permission checks remain necessary.

Rate limiting without losing bans ​

The API applies separate request budgets to validation, join checks, synchronization and live monitoring. Server budgets apply only after the current key, bound IP, subscription and verification lease have been checked. A busy live stream does not consume the ban synchronization budget.

Client reports also have individual budgets per player. Server-side detections and confirmed ban execution are not blocked by a different player's flood. A banned player is dropped immediately. Database changes are batched and retried if synchronization fails; an HTTP 429 does not mean a ban was cleared or ignored.

The resource follows the API retry delay before another synchronization attempt. Do not add a loop that repeatedly requests validation or sends duplicate bans. If a connection check cannot complete, it must show its validation error rather than treat the player as unbanned.

PHP admin limits authentication submissions separately from normal database actions. Website login, registration, verification codes and account emails also have their own limits.

VoidAC documentation