Skip to main content
atlasBridge issues usually come from resource names, start order, provider detection, missing NUI files, or incorrect convars.

​
Resource name issues

The folder must be named: 
atlasBridge
If the folder is renamed, Atlas resources cannot find the bridge correctly.

​
Provider detection picked the wrong system

Auto-detection only sees resources that are already started. Fix by starting dependencies before atlasBridge: 
ensure ox_inventory
ensure qbx_core
ensure atlasBridge
Or force the provider: 
setr atlas:framework "qbx"
setr atlas:inventory "ox"

​
Inventory actions fail

Check:
  • Inventory resource is started before atlasBridge.
  • atlas:inventory is correct.
  • Item keys exist in the inventory.
  • The player has enough space/weight if your inventory enforces capacity.
  • The Atlas resource is using the same item keys listed in its config.

​
Money actions fail

Check:
  • Framework provider is correct.
  • Account names match your framework, usually cash or bank.
  • The framework resource starts before atlasBridge.
  • Custom framework adapter returns expected values.

​
Notifications or menus do not show

Check:
  • atlasBridge/web/dist/index.html exists.
  • atlas:ui is set correctly.
  • ox_lib starts before bridge if using ox UI.
  • Per-subsystem overrides are not forcing an unavailable provider.
Example safe fallback: 
setr atlas:ui "own"

​
Death detection does not trigger

Some Atlas resources use bridge death detection to stop active gameplay cleanly when a player dies. If that does not happen on your server:
  • Confirm atlasBridge is started before the Atlas resource.
  • Test with the default setup first; bridge detects most normal deaths automatically.
  • If your death/ambulance system uses its own event, set atlas:deathEvent to that event name.
setr atlas:deathEvent "baseevents:onPlayerDied"

​
Discord does not work

Check:
  • Bot token is set with set, not setr.
  • Guild ID is correct.
  • Bot is in the guild.
  • Bot has permissions to read members/roles required by your setup.
set atlas:discord:token "YOUR_BOT_TOKEN"
set atlas:discord:guild "YOUR_GUILD_ID"

​
Debugging process

1

Enable debug temporarily

Add setr atlas:debug "true" while testing.
2

Restart in order

Restart framework, inventory, target/UI, then atlasBridge, then Atlas resources.
3

Read the first error

Fix the first bridge error before chasing errors from dependent resources.
4

Force providers if needed

If auto-detection is wrong, use explicit convars.
5

Turn debug off

Set setr atlas:debug "false" before production.