Skip to Content
Mizu InterfaceDependencies

Dependencies

ℹ️
Mizu Interface has zero required dependencies.

It is entirely standalone — no ox_lib, no framework required to use the base features.

Core Dependencies

✅
None required
The resource is fully standalone. Rendering runs in a completely isolated JS/CSS UI thread.

Supported Frameworks

mizu_interface auto-detects your environment on startup and adapts its behavior accordingly — inv_busy hooks, permission checks, and player metadata all connect automatically.

QBCore
QBCore
qb-core
  • ✓ Permission checks for /announce
  • ✓ inv_busy state sync
  • ✓ Notification routing
QBOX
QBOX
qbx_core
  • ✓ Permission checks for /announce
  • ✓ inv_busy state sync
  • ✓ Notification routing
ESX
ESX Legacy
es_extended
  • ✓ Permission checks for /announce
  • ✓ Notification routing
  • ✓ Player group detection

Radial Menu Replacement

mizu_interface automatically declares itself as a provider for native radial menu resources via the FiveM provide system. You do not need to run any of these alongside it:

qb-radialmenuqbx_radialmenuesx_radialmenu

Stub exports (AddOption, RemoveOption, setupSubItems, setupAppItems) are provided automatically to prevent crashes from scripts that try to interact with native radial menu APIs.

Optional Integrations

While not required, these systems unlock additional features automatically:

🛡️
txAdmin
Automatically captures Announcements, Restart Warnings, Player Warnings, Kicks, and DMs — styling them through mizu_interface.
📦
ox_inventory
Progress bars and radial menus set inv_busy state to prevent item exploits during actions.
📡
Discord Webhook
Route announcement logs to a Discord channel. Set in Config.Announce.Logging.
📊
FiveManage V3
Send announcement metadata to FiveManage centralized logging. Set in Config.Announce.Logging.
Last updated on
Mizu InterfaceInstallation