Skip to content

Bans & evidence ​

VoidAC stores bans in its central database. Resource updates do not clear them, and copying a different local folder is not an unban.

Review a ban ​

Open Bans in your server's dashboard and select a record. Check the player, identifiers, detection, reason and timestamp. Use the identifier buttons to copy the available Steam, Discord or Rockstar identifiers.

If capture and upload succeeded, the details include a screenshot and a video clip. The screenshot is captured for the incident; the recording uses the client's rolling buffer. Banning does not wait for a recording to upload.

Use Copy image link or Copy media link for available evidence. Treat copied links as sensitive: do not post another player's evidence publicly without a reason.

Remove a ban ​

You need edit access to Bans on the server that issued the ban. Choose Remove ban and confirm. The action is recorded in the audit log.

You cannot remove another server's ban through your own server's dashboard. Marking a detection as a false positive is available for automatic bans, not manual bans.

Player lookup ​

Use Lookup to search a name or identifier, for example:

text
discord:123456789012345678
steam:76561198000000000
license:your-rockstar-license

Linked identifiers and shared ban records are returned when recorded in the database. A player may have several identifiers of the same type. Public account information is displayed only when the external account can be resolved; an ID's format alone is not proof that an account exists.

Lookup can show bans from other VoidAC servers with their reason and available evidence. It does not reveal their private player IPs or device tokens. Use Offline ban for a known identifier when the player is not connected, if you have permission to ban on your server.

Missing evidence ​

Evidence is not guaranteed for every record. It can be missing when the client cannot capture its game, disconnects before upload or does not yet have a complete rolling recording. Old or manual records may not contain media either.

The resource does not attach a short fragment and label it a 10-second recording. Check the client and server console around the incident before retrying. Media retention is bounded by storage limits; do not treat an evidence URL as permanent archival storage.

Version 1.8.14 retries recorder startup while the game renderer warms up, uses a dedicated recording canvas, and accepts video-only evidence if a screenshot fails. Discord attachment uploads queue and retry HTTP 429 responses. Large capture batches are split before synchronizing with the database.

The current recorder retains its latest completed ten-second segment. It may end before the incident; it is not a frame-exact recording ending at the detection time. The first complete clip is available only after recorder startup and buffer warmup.

VoidAC documentation