Skip to main content
atlasBridge is designed to work with little configuration. In most cases, start your framework/inventory before the bridge and leave provider convars on auto. 
ensure ox_lib
ensure ox_inventory
ensure qbx_core

setr atlas:framework "auto"
setr atlas:inventory "auto"
setr atlas:ui "auto"
setr atlas:target "auto"
setr atlas:theme:color "#B9A7FF"
setr atlas:debug "false"

ensure atlasBridge
ensure atlasFishing

​
Framework

setr atlas:framework "auto"
Auto-detection checks in this order:
  1. qbx_core
  2. es_extended
  3. qb-core
  4. default
Force a provider when needed: 
setr atlas:framework "qbx"
setr atlas:framework "esx"
setr atlas:framework "qb"
setr atlas:framework "default"
setr atlas:framework "custom"

​
Inventory

setr atlas:inventory "auto"
Auto-detection checks in this order:
  1. ox_inventory
  2. qb-inventory
  3. qs-inventory
  4. ESX legacy inventory
  5. default
Force a provider when needed: 
setr atlas:inventory "ox"
setr atlas:inventory "qb"
setr atlas:inventory "qs"
setr atlas:inventory "esx"
setr atlas:inventory "default"
setr atlas:inventory "custom"

​
UI

setr atlas:ui "auto"
The UI resolver can use ox, framework UI, bridge-owned UI, or custom adapters depending on the subsystem. You can also override individual systems: 
setr atlas:ui:notify "own"
setr atlas:ui:progress "ox"
setr atlas:ui:menu "own"
setr atlas:ui:textui "own"
setr atlas:ui:context "own"
setr atlas:ui:input "own"
setr atlas:ui:skillcheck "own"
setr atlas:ui:confirm "own"

​
Target / interactions

setr atlas:target "auto"
Auto-detection checks in this order:
  1. ox_target
  2. qb-target
  3. own (bridge-owned interaction prompt)
Force a provider when needed: 
setr atlas:target "ox"
setr atlas:target "qb"
setr atlas:target "own"
setr atlas:target "custom"

​
Theme color

setr atlas:theme:color "#B9A7FF"
Use any valid hex color. This controls the default Atlas accent color for bridge UI and marker props.

​
Debug mode

setr atlas:debug "false"
Use true only while testing provider detection or bridge behavior.

​
Death detection

atlasBridge automatically detects most player deaths for Atlas resources. If your server uses a custom death system and an Atlas resource does not react when a player dies, route your death event through the bridge: 
setr atlas:deathEvent "baseevents:onPlayerDied"
Use the event name from your death/ambulance system if it is different.

​
Discord

Discord is optional. If used, store secrets with set, not setr. 
set atlas:discord:token "YOUR_BOT_TOKEN"
set atlas:discord:guild "YOUR_GUILD_ID"
Never use setr for bot tokens. setr can replicate values to clients. Use set for server-only secrets.