Most frequent problems and how to fix them
Not every project is flawless, and WX AntiCheat is not an exception. If you run into any issues, please take a look if your issue isn't explained here. If not, feel free to join our discord and we can hopefully resolve your issue!
| Issue | Solution |
|---|---|
| "Couldn't check for updates" | This means that GitHub might be down (as the update check file is stored on GitHub), or your server cannot reach the website |
| "wx_anticheat: Deferring connection..." stuck | Check for any database errors in your server console, if you don't see any, disable wx.ConnectingCard |
| "You lack the required entitlement to use wx_anticheat" | Make sure the server owner is the same as the account that the anticheat was purchased for. Also do not forgot to restart your server after installation! Sharing keymaster assets is not possible! |
| Admins Getting Detected | Make sure the DEBUG option is turned OFF! (wx.Debug option in the Config) |
| Error parsing script / Failed to load script | Make sure your server artifact version is ABOVE 5181 |
| Failed to verify protected resource | Your resource might be corrupted, or your FTP program skipped the .fxap file, which a lot of FTP programs like to do. Try re-uploading the anticheat on your server and make sure the .fxap file is there too. I'd recommend the WinSCP FTP Program |
| 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. (On example vehicle shop scripts most of the times make the player invincible or invisible) |
| High Resmon | Limit the usage of admin menu ESP options - these options are the most intensive for client resmon |
| Poor server performance | Bump up your OCR Interval in the config, if that doesn't help, disable OCR as whole |