Skip to main content
Two files. config/core.lua is who does what, config/logs.lua is where entries go. Both ship readable, so they are yours to edit.

​
Everything is auto

Every backend setting defaults to auto, which means the bridge looks at what is running and picks it.
config/core.lua
Name one explicitly in two situations: your server runs two of something and you want to say which, or detection picked the wrong one.
config/core.lua
Detection happens once, at load time. A resource that starts after the bridge cannot be seen by it, so the fix for “it did not detect my inventory” is nearly always the start order, not this file.

​
Seeing what it picked

config/core.lua
Announce is on by default and deliberately not behind Debug. It is the first thing anyone looks at when an Awoken script says nothing happened, and asking someone to turn on debugging before they can see it wastes a support round trip. Anything reported as none usually means you do not run one, and occasionally it is the entire bug.

​
Logging

config/logs.lua
For Discord this is the full webhook URL. For Fivemerr or Fivemanage it is the API key.
Treat that value like a password. Anyone holding it can post to your channel. It lives in config/logs.lua rather than core.lua so it is easy to keep out of anything you share.
Channels are per resource, so each Awoken script can have its own feed without any of them needing to know the others exist. The list grows as you add resources, which is the reason it has a file to itself.

​
A resource we do not support yet

Every file under modules/ ships readable, one per resource the bridge talks to. If you run an in-house MDT, or a fork of a public one, you are not waiting on us. See Exports for the contract, and copy the nearest existing adapter as your starting point.