Skip to content

Laser eyes & rockets ​

Available from VoidAC 1.8.32 under Detections → Laser eyes / rockets. This is an event-driven server check: it does not add a per-frame client scan.

What it checks ​

MethodCheck
Unauthorized projectilesRepeated rocket or energy-weapon projectile requests without the corresponding weapon in the server's replicated player state.
Laser and raygun damageRepeated raygun, railgun or laser damage requests that do not agree with the player's observed weapon or a recently validated shot.

The network event alone is not proof of cheating. VoidAC checks the player's ped, selected weapon and repeated mismatches. Weapon hashes are normalized so signed and unsigned representations match. Recent weapon changes receive a grace period, and valid shots are remembered to avoid treating delayed impacts as new unauthorized attacks.

Vehicle occupants are excluded because mounted weapons use a different weapon state. Cosmetic laser beams with no network projectile or damage event are not detectable through these checks. This is not a guarantee against every menu or attack.

Configure the detection ​

  1. Start with Log on a test server; this is the default. In Log mode this detection does not cancel the event.
  2. Test legitimate RPGs, rayguns, weapon switching and scripted attacks.
  3. Review the reported event weapon, server-selected weapon and confirmation count.
  4. Choose Warn, Kick or Ban only after checking your gameplay. Confirmed suspicious events are also cancelled in those modes. A single mismatch does not automatically ban a player.
SettingDefaultPurpose
Confirmations3Separate mismatches required before acting. One simultaneous burst damaging several targets is not counted as several independent shots.
Time window5,000 msPeriod in which repeated mismatches accumulate.
Weapon-switch grace750 msDelay after a newly observed selected weapon before checking mismatches.
Exempt weaponsEmptyWeapons excluded completely. Adding WEAPON_RPG also permits that effect without a matching selected weapon; use sparingly.
Trusted resourcesEmptyResources allowed to authorize a short scripted exception through the server export. A resource name alone does not permanently whitelist its players.

Authorize a scripted effect ​

Add the gameplay resource's exact name to Trusted resources. Then call this from its server code, after validating the player's permission:

lua
local allowed = exports['VoidAC']:AllowProjectiles(playerId, 3000)
if not allowed then return end
-- Run the validated scripted effect here.

Never place this behind an unrestricted client-triggered network event. TX detection exemptions and explicit detection ACEs remain separate options; they do not give a player dashboard or command access.

Evidence and troubleshooting ​

Confirmed reports use the normal VoidAC logs, central player records and configured punishment. Screenshots and recordings are best effort, not a requirement for enforcement. A client disconnected immediately may not finish uploading new evidence.

If a legitimate script is reported, keep the detection in Log while comparing its weapon behavior. Prefer a short trusted-resource exception to a permanent weapon exemption. If OneSync weapon natives or player state are unavailable, this detection skips the check rather than inventing a match or a ban.

VoidAC documentation