Asset download
To find the asset, you must have made the purchase using your own keymaster account. Otherwise, you can use the transfer system to move the asset to a different keymaster account.
Requirements
- ox_lib (latest version)
Installation
1
Add the resources
Place both the
awoken_ui and ox_target (Awoken version) folders into your server’s resources directory. You can install just Awoken UI or just Awoken Target if you prefer, but both work best together.2
Back up and replace ox_target
The Awoken Target is a drop-in replacement that uses the same path structure (e.g.
resources/[ox]/ox_target).3
Hook into ox_lib
Add the following code to the very end of This allows Awoken UI to seamlessly override ox_lib’s UI functions. No changes are needed in any other scripts - any resource that uses
ox_lib/init.lua:lib.notify(), lib.progressBar(), lib.showContext(), etc. will automatically use Awoken UI.4
Configure server.cfg
Add the following to your The
server.cfg, making sure both resources start after ox_lib:awoken:primaryColor convar sets your accent colour globally. Any awoken-styled resource will read this value. If not set, it defaults to #00E5FF.5
Verify
Join the server and test:
- Any script calling
lib.notify(),lib.progressBar(), or other ox_lib UI functions should render with the Awoken UI theme. - Press your target hotkey (default Left Alt). The targeting eye icon should appear with the Awoken Design.
Awoken Target provides full backward compatibility with qtarget / bt-target exports, so existing scripts using those APIs will continue to work without changes.
Running QBCore with
qb-radialmenu? qb-radialmenu uses its own NUI and doesn’t hook ox_lib, so it won’t render through Awoken UI by default. See the QBCore Radial Menu guide for a small bridge that fixes this without removing the resource. QBX servers using qbx_radialmenu work out of the box, no bridge needed.Dependencies
Updating
Re-download the resource(s) from Tebex, replace the folder(s), and restart withensure awoken_ui / ensure ox_target.