Compatibility
description: Check supported frameworks, dependencies, permissions, and notifications.
Compatibility
Compatibility
| Category | Compatible with |
|---|---|
| Frameworks | Framework-agnostic — vehicle deletion logic doesn't depend on any framework. Native notification hooks exist for ESX and QBCore, plus a print fallback if neither is running. |
| Required dependency | ox_lib — hard dependency, used for lib.callback (all client↔server communication) and NUI. The resource will not start without it. |
| Permissions | ACE permissions only (Config.AcePermission) — no dependency on framework job/rank systems, group-based permission resources, or Discord role checks. |
| Player spawn detection | Listens for QBCore:Client:OnPlayerLoaded, qbx_core:client:playerLoaded, and esx:playerLoaded (in addition to its own resource start) to correctly re-open the countdown card for players who reconnect mid-wipe. |
| Discord logging | Any standard Discord webhook URL — no bot token or extra Discord integration resource required. |
| UI | Custom NUI (HTML/CSS/JS), fully independent of framework — same behavior on ESX, QBCore, QBX, or standalone. |
{% hint style="success" %}
Because the cleanup logic works directly on native vehicle/object entities (not framework-owned vehicle records), yei-carwipe works identically regardless of which framework — or none — your server runs.
{% endhint %}
Notification fallback
| Framework detected | Notification method used |
|---|---|
es_extended running | esx:showNotification |
qb-core running (and ESX not running) | QBCore:Notify |
| Neither running | Falls back to a server console print |
Not required
yei-carwipe does not depend on: oxmysql or any database, ox_target/qb-target, ox_inventory, or any vehicle-keys resource — it has no interaction with vehicle ownership, only with live entities currently spawned in the world.
Last updated on July 27, 2026
← Back to the store