Overview
BenzyPrioAOP
Exports
BenzyPrioAOP exposes no Lua exports. It is driven entirely by chat commands (server-authoritative) and its own NUI, so there is no exports.BenzyPrioAOP:* surface to call from another resource. If you want to react to what it does, listen to its events instead — see EVENTS.md.
Events
Every net event BenzyPrioAOP registers or triggers, with its direction and payload. All of them are namespaced BenzyPrioAOP: and are internal sync events* between this resource's own server and client — they are not a stable public API, but they are documented here so you can see exactly how state moves.
Integrations
What BenzyPrioAOP touches outside itself, and how it degrades when those things are absent. The short version: it needs BenzyBridge, and everything else is optional. It is standalone-first — no framework, inventory, money, or database is required, and it never warns about an optional system simply not being present.