Skip to main content
Install atlasBridge before installing other Atlas resources.

​
Requirements

  • Keep the folder name as atlasBridge
  • Start your framework, inventory, UI, and target resources before the bridge
  • Keep the included atlasBridge/web/dist folder in the resource

​
Folder placement

Recommended layout: 
resources/
  [ATLAS]/
    atlasBridge/
The folder must be named exactly: 
atlasBridge

​
server.cfg

Minimal setup: 
ensure atlasBridge
Typical setup: 
ensure oxmysql
ensure ox_lib
ensure ox_inventory
ensure qbx_core

ensure atlasBridge
Then start Atlas resources after the bridge: 
ensure atlasFishing

​
Optional convars

Most servers can leave provider convars unset and let auto-detection work. If you want to be explicit, add: 
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"

​
Confirm UI files

Confirm this file exists: 
atlasBridge/web/dist/index.html
Bridge-owned UI such as notifications, progress, menus, radial UI, and interaction components may rely on this build.

​
First startup test

1

Start dependencies

Start your framework, inventory, UI, and target resources first.
2

Start atlasBridge

Ensure atlasBridge after dependencies.
3

Watch console output

Look for provider detection hints, missing NUI files, or resource-name issues.
4

Start an Atlas resource

Start atlasFishing or another Atlas resource after the bridge.

​
Next step

After atlasBridge starts cleanly, install and start the Atlas resource you purchased. For example, continue with atlasFishing Installation.