For the complete documentation index, see llms.txt. This page is also available as Markdown.

Integrations

Cdev Ludus Gaming is built with a flexible bridge system that supports multiple frameworks, inventories, and interaction resources. Auto-detection is enabled by default for seamless setup.


🌐 Supported Integrations

⚠️ If a resource is not listed below, it is not officially supported. Custom integrations can be implemented through the bridge system.


🧩 Frameworks

Framework
Status
Notes

QBox (qbx_core)

✅ Fully Supported

Uses qb-core compatibility layer.

QBCore

✅ Fully Supported

Native integration.

ESX Legacy (es_extended)

✅ Fully Supported

Uses persistent identifier for player linking.

Custom Framework

⚠️ Bridge Required

Manual implementation via bridge system.


🎒 Inventories

Inventory
Status
Notes

ox_inventory

✅ Fully Supported

Use server.export = 'cdev_ludus.useLudusBoard' and consume = 0.

qb-inventory

✅ Fully Supported

Useable item registered automatically.

qs-inventory

✅ Fully Supported

Useable item registered automatically.

Custom Inventory

⚠️ Bridge Required

Implement via public/bridge/inventory/.


🎯 Interaction Systems

System
Status
Notes

ox_target

✅ Fully Supported

Supports Font Awesome icons (e.g. fas fa-dice).

qb-target

✅ Fully Supported

Native target integration.

DrawText

✅ Built-in

No external resource required.

Custom Target

⚠️ Bridge Required

Implement via public/bridge/target/.


🔔 Notifications

System
Status
Notes

ox_lib

✅ Preferred

Used automatically when available (e.g. QBox).

QBCore

✅ Supported

Uses QBCore:Notify.

ESX

✅ Supported

Framework / ESX notify path.

Native

✅ Fallback

Used if no supported system is detected.


🗄 Database

Requirement
Status

oxmysql

✅ Required

Tables auto-created on boot:

  • cdev_ludus_players

  • cdev_ludus_match_history

  • cdev_ludus_player_history


⚙️ Bridge Configuration

You can override auto-detection in config.lua:

Last updated