BenzyPrioAOP — 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.

In server.cfg, ensure BenzyBridge before BenzyPrioAOP. The manifest also declares dependency 'BenzyBridge', so the server enforces that start order.

Contents

• BenzyBridge (required)
• Not used
• Discord webhooks (self-contained)
• Notes

---

BenzyBridge (required)

BenzyPrioAOP includes the bridge in-process via shared_script '@BenzyBridge/init.lua' (first shared script), which builds the Benzy.* API, and uses it to gate its staff commands.

The staff-gated commands (/aop, /endprio + /cooldown staff powers, /peacetime) are checked with the bridge's unified access system:

Benzy.HasAccess(src, Config.Access.aop, 'benzy.aop')

Config.Access.<role> (in config.lua) carries four independent methods that are OR'd — a player passes if any enabled one matches:

Method	Needs	Notes
Framework	An active framework (ESX / QBCore / QBox)	Matches a job or group name. Skipped entirely on a standalone server.
Identifiers	—	Matches a raw license: / fivem: / steam: / discord: identifier.
AcePerms	—	A true/false toggle for the fixed ACE string (benzy.aop / benzy.prio / benzy.peacetime). Grant it with add_ace group.admin benzy.aop allow.
Discord	Badger_Discord_API running	Matches a Discord role ID. Skipped if that resource is not started.

Shipped defaults keep AcePerms = true and every other method disabled, so out of the box it behaves exactly like the old ACE-only setup. The fixed ACE string is passed in code as the third argument to HasAccess — it is never placed in the config, so an owner can only toggle it, not rename it.

---

Not used

BenzyPrioAOP does not use the bridge's money, inventory, or storage concerns — it grants no items, moves no money, and keeps no database. There is therefore no inventory or database fallback to configure; those systems being absent is normal and never warned about.

---

Discord webhooks (self-contained)

Prio / AOP / peacetime actions are logged straight to Discord — this is BenzyPrioAOP's own feature, not routed through the bridge. Paste your webhook URLs into Config.Webhooks in config.lua; leave a field empty to disable that log.

---

Notes

• Player state is keyed on the live server id (source) only. Prio membership is per-session and does not persist across a reconnect. This is intentional for a lightweight, standalone HUD.
• HUD layouts are saved per player on their own machine, so they survive reconnects, restarts, and clearing the server cache — no bridge or database involved.