Troubleshooting

Learn how to fix the most common issues with the AntiCheat

Common Issues and their solutions

IssueSolution
"Couldn't check for update"Ensure the server has internet access and verify that github.com is reachable and not blocked by a firewall.
Stuck on "wx_anticheat: Deferring connection..."Check the server console for errors. The most common cause is that the provided SQL file has not been imported into your database.
"You lack the required entitlement to use wx_anticheat"Confirm that the server is owned by the same CFX Keymaster account that purchased the anticheat.
Admins getting detectedFirst, make sure wx.Debug is disabled in the main config. If the issue persists, verify that admins are correctly registered (see the Admins section).
Error parsing script / Failed to load scriptEnsure your server artifact version is 5181 or higher. You can download the latest version from here.
"Failed to verify protected resource"The anticheat resource may have been corrupted during FTP transfer. Confirm that the .fxap file is uploaded correctly, as some FTP programs may skip it.
Poor server performanceIncrease the OCR interval in the main config. If performance issues remain, disable the OCR feature entirely.
False DetectionsSet the detection handler to LOG and monitor logs for false positives. Disable detections that are confirmed to be false. Also test your scripts, as some (e.g., vehicle shops) may temporarily make players invincible or invisible, causing false flags.
Objects getting deletedCheck the objectAttach option in your config. If enabled, ensure the deleted object is properly whitelisted. Also review the object blacklist table to confirm the object is not listed there.
"No such export * in resource wx_anticheat"1. Verify that the anticheat resource has not been renamed.
2. Confirm that the export you are calling actually exists. Refer to the Available exports.