Skip to main content
Awoken Bridge owns no gameplay. It answers one question, “who does X on this server”, so that every other Awoken resource can stop carrying its own copy of the answer. You install it once. Every Awoken script that talks to another resource depends on it.

​
Asset download

Once you buy from our official website, the asset lands in your Cfx.re portal. Download it from there. The asset must sit on the keymaster account that made the purchase, or transfer it across first.

​
What you need

Required

ox_lib, and nothing else.

Detected, not required

Your framework, inventory, target, dispatch, phone, keys, fuel and logging resource. Whatever is running gets picked up.
Works on QBox, QBCore, and ESX, and standalone with no framework at all.

​
Install

1

Drop the folder in place

Put the awoken_bridge folder into your server’s resources/. Keep the folder name exactly awoken_bridge: it is the name every other resource calls its exports by.
2

Set the ensure order

server.cfg
Order matters more here than anywhere else. Detection is a resource state check at load time, so anything that starts after the bridge is invisible to it. Everything it should find goes above it, and every Awoken script goes below it.
3

Start the server and read one line

The bridge prints what it picked for each job at boot. That line is the first thing to look at whenever an Awoken script says nothing happened.

​
Updating

Re-download the asset from your Cfx.re portal, replace the folder, and restart.
Replacing the folder overwrites config/. Back it up first if you have named anything explicitly in there.

​
First check

Anything reported as none is usually correct, meaning you do not run one. Occasionally it is the whole bug, so it is worth a glance before raising a ticket.

Configuration

Naming a backend when detection guesses wrong.

Exports

The surface every Awoken script is written against.