Skip to main content
atlasBridge is the shared foundation that every Atlas resource depends on. It exposes a single global Bridge table that normalizes your server stack — framework, inventory, UI, target, Discord — so Atlas scripts run the same on ESX, QBox, QB-Core, or standalone without you editing each resource. Server owners install it once and start it before every other Atlas resource. For most servers there is nothing to configure: the bridge auto-detects your framework, inventory, and target system at startup.

Install atlasBridge

Place the resource, add the integration line to your scripts, and set the start order.

Configuration

The full convar reference — framework, inventory, UI, target, theme, Discord.

Custom framework

Run an unsupported framework? Fill the editable adapter against the contract.

Troubleshooting

Fix startup, detection, UI, theme, and Discord issues.

​
What atlasBridge handles

  • Framework — normalized player, job, and money helpers (Bridge.GetJob, Bridge.AddMoney, …).
  • Inventory — normalized item operations (Bridge.Inventory.AddItem, HasItem, …).
  • UI — notifications, progress bars, menus, context menus, text UI, inputs, skill checks, confirmations, and a radial menu.
  • Target / interaction — ox_target, qb-target, or the bridge’s own world-anchored prompts.
  • Networking — a protected client↔server layer with scrambled event names, token proofs, validation, and rate limiting.
  • Entities — server-authoritative spawning and tracking, with automatic cleanup on disconnect.
  • Discord — role and member helpers when a bot token is configured.
  • Permissions — ACE- and Discord-role-aware permission nodes.
  • Theme — a shared accent color for Atlas UI and marker props.

​
Supported stacks

Everything below auto-detects. You only set a convar when you want to force a choice or run something unsupported (custom).
The bridge’s own NUI is the default — it has zero dependencies. ox_lib is opt-in: set atlas:ui "ox" (and start ox_lib) to use it. Anything a chosen provider does not implement falls back to the bridge’s own NUI.

​
Where to go next

Install it

The single install page: placement, integration, and start order.

Configure providers

Every convar with its values, default, and meaning.

Provider detection

How auto-detection resolves and when to force a provider.

Developer reference

Build on the Bridge global — networking, data, UI, Discord.
Keep the resource folder named exactly atlasBridge. Consumer scripts load it with @atlasBridge/init.lua; renaming the folder breaks that path and every dependent resource.