AntiCheat Troubleshooting
This section covers common issues and how to fix them.
Common Issues
| Issue | Solution |
|---|---|
| "Couldn't check for update" | Check if the server can connect to the internet and if github.com is not blocked. |
| Stuck on "wx_anticheat: Deferring connection..." | Check for any errors in the server console. Most common issue is that the SQL file has not been imported |
| "You lack the required entitlement to use wx_anticheat" | Make sure the server owner is the same as the keymaster account where the anticheat is purchased |
| Admins getting detected | Make sure to disable wx.Debug in the main config file, if that doesn't help, make sure you have registered them correctly (see Admins) |
| Error parsing script / Failed to load script | Make sure your server artifact version is above 5181. Download the latest artifact here |
| "Failed to verify protected resource" | The anticheat folder might be corrupted from the FTP transfer. Make sure that the .fxap file is being transfered correctly, as some FTP programs skips it. |
| High Client Resmon | This is caused by the Admin Panel, limit the usage of ESP options as they are the most intensive for the resmon |
| Poor server performace | Bump up the OCR interval in the main config, if that doesn't help, disable the OCR entirely |
| False Detections | Set the punish type to 'LOG' and watch the logs for detections that are false positives, then disable them. You should also test your scripts if it's not them causing these false positives. (For example: vehicle shop scripts most of the times make the player invincible or invisible) |
| "No such export * in resource wx_anticheat" | 1. The anticheat resource has been renamed 2. Literally what the error says, you are trying to call an export that doesn't exist Available exports |