Troubleshooting

description: Resolve common yei-carwipe installation, permission, and cleanup issues.

Troubleshooting

Troubleshooting

The resource refuses to start / red "SECURITY ALERT" banner in console

server/init.lua checks its own resource name on boot. If the folder isn't named exactly yei-carwipe, it prints a red alert box and automatically stops itself half a second later.

Fix: rename the resource folder back to yei-carwipe and restart the server.

ox_lib errors on start / resource won't load

yei-carwipe declares ox_lib as a hard dependencies entry in fxmanifest.lua and relies on lib.callback for every client↔server call.

Fix: make sure ox_lib is installed and started before yei-carwipe in server.cfg:

ensure ox_lib
ensure yei-carwipe

"You don't have permission to use this command"

• Confirm you added the ACE correctly in server.cfg:

add_ace group.admin yei-carwipe.use allow
add_principal identifier.license:YOUR_LICENSE group.admin

• Check that Config.AcePermission in shared/config/config.lua matches the ACE string you registered.
• Remember the check runs for every command and every panel button — including opening the panel itself.

{% hint style="info" %} Commands run from the server console (source 0) always bypass the ACE check. {% endhint %}

The countdown card doesn't show up for players

• Make sure the wipe actually started — check /carwipestatus or look for the "Wipe Started" log in Discord (if webhook logs are enabled).
• If it only fails for players who reconnected mid-wipe, that's unusual — the client automatically asks the server for the current countdown state on spawn/resource start and re-opens the card if a wipe is active.

Vehicles aren't getting deleted

This is very often by design, not a bug:

• A vehicle with a driver or any passenger is always skipped.
• A vehicle inside a zone listed in Config.IgnoreZones is skipped.
• A vehicle whose model is listed in Config.BlackListVehicles is skipped.

Fix: review those three settings in Configuration if vehicles you expect to be wiped are surviving.

Objects/props aren't being deleted

Config.Objects is false by default — object cleanup is opt-in. Set it to true if you also want props removed, and review Config.IgnoreZonesObjects for exclusion zones.

Scheduled or interval wipes never trigger

• Check that Config.Schedule.Enabled or Config.IntervalTime.Enabled is actually set to true — both come disabled out of the box on purpose (no wipe runs automatically on a fresh install).
• For Config.Schedule, confirm each entry in Times uses the "HH:MM" 24-hour format (e.g. '06:00', '18:00').
• If both automations are enabled at once, Schedule takes priority and the interval timer won't re-arm itself after a wipe — this is intentional to avoid overlapping wipes, not a bug.

The Discord webhook isn't sending anything

• Config.DiscordLogs.webhook is empty by default — paste your webhook URL there.
• Confirm Config.DiscordLogs.enabled is true.
• Enable Config.Debug temporarily — the console will print whether the webhook request succeeded (HTTP 204) or failed, including the status code.

The admin panel doesn't open, or looks broken

• The panel is opened via NUI focus (SetNuiFocus) — if another NUI resource is stealing focus at the same time, it can conflict. Try closing other open menus first.
• ui/js/script.js is minified/obfuscated as shipped for anti-leak protection — if you need to customize panel behavior beyond what Config.UI and Lang.UI expose, contact Yei Studios rather than trying to patch the minified file directly.

{% hint style="info" %} For anything not covered here, enable Config.Debug and reproduce the issue — most internal errors and permission checks print to the server console with the [yei-carwipe] prefix. {% endhint %}