Overview
Axiom is a drs_Dev theme for ox_lib 3.39.0 · ox_target 1.18.1. It includes matching ox_lib and ox_target folders. This guide shows how to install both, change the theme settings, test the result, and update safely. A modern minimal treatment with smoked graphite glass, cloud-white surfaces, electric-mint focus states, local Inter variable typography, and a compact adaptive focus rail.
drs-ox Axiom interface preview
The matching ox_target and ox_lib interfaces included with this edition.
The menu keeps five vehicle actions visible while a mint marker shows which car is selected.
Extra details, progress, success, disabled, and read-only options share the same compact dark-and-mint design.
Requirements
- Included
- ox_lib 3.39.0 and ox_target 1.18.1
- Server
- FXServer artifact 7290 or newer with OneSync
- Resource names
- Must remain ox_lib and ox_target
- Theme selection
- Install only one drs-ox edition at a time
- Platform
- FiveM bundle; the ox_lib component also declares RedM support
Installation
Back up the installed ox_lib and ox_target resources and their configuration before replacing them.
Download the selected bundle and copy its enclosed ox_lib and ox_target folders into the server resources directory without renaming them.
Remove every other drs-ox edition so duplicate ox_lib or ox_target resource identities cannot be started.
Start ox_lib before ox_target, then start resources that depend on either component.
Validate menus, notifications, progress UI, TextUI, target options, framework restrictions, and item-restricted interactions on a development server.
Configuration
Set the default theme options
Choose the default scale, interface sounds, volume, and reduced-motion setting for the server. Players can change these options with /ox_lib; their choices affect only them and apply immediately.
setr ox:uiScale 1.00 # 0.75-1.25
setr ox:uiSounds 1
setr ox:uiSoundVolume 0.25 # 0.00-1.00
setr ox:reducedMotion 0How to use and test it
Test every part of the interface
After replacing both folders, run the included ox_lib preview commands on a private test server. Then test at least one real ox_target zone, model, entity, and global option used by another resource.
/oxtestui
/oxnotify
/oxctx
/oxmenu
/oxradial
/oxskill
/oxprog
/oxcircle
/oxtext
/oxhidetextOpen player preferences
Use /ox_lib to review the settings included with Axiom. A player's choices affect only that player and do not change the defaults for anyone else.
/ox_libAxiom design and settings
This edition changes how ox_lib and ox_target look and feel. Their resource names and supported connections stay the same.
- Typography
- Inter Variable
- Accent treatment
- Cloud white with electric mint and selective coral support
- Target presentation
- Side-mounted seven-row focus rail with a segmented aperture marker and mint in-world hover sprite
- Motion and progress
- Fast restrained fades and translations with minimally framed progress treatments
- Player theme controls
- Scale, interface sounds, sound volume, and reduced motion through /ox_lib
Axiom direction
A modern minimal treatment with smoked graphite glass, cloud-white surfaces, electric-mint focus states, local Inter variable typography, and a compact adaptive focus rail.
Differences from upstream
Presentation-focused derivative
Axiom packages ox_lib 3.39.0 · ox_target 1.18.1, then changes the compiled ox_lib interface and preference wiring plus ox_target presentation, layout, typography, and in-world hover color. Target APIs, callbacks, exports, option schemas, and framework adapters remain unchanged.
Current ox_target baseline
Axiom packages the Overextended 1.18.1 baseline with strict NUI callback mode, Norwegian and Swedish locales, and the current Overextended version-check source. Its custom focus rail already used equivalent event-scoped message handling before this update. No target APIs, callbacks, exports, option schemas, framework adapters, or configuration contracts changed.
Use the matching upstream API references
The bundle does not replace the upstream ox_lib or ox_target documentation. Use API material that applies to ox_lib 3.39.0 · ox_target 1.18.1, then validate the integration against this packaged snapshot.
Updating
Review upstream changes manually
The inherited version checkers query Overextended ox_lib and Overextended ox_target. Treat their notices as review prompts: installing an upstream release archive directly will overwrite the drs_Dev theme and can separate the tested pair.
Back up and retest the pair
Back up both active folders, merge applicable upstream fixes into a working copy, and repeat the interface, adapter, target, and dependent-resource tests before deployment.
Known limitations
Versions describe the upstream baselines
The manifests retain ox_lib 3.39.0 · ox_target 1.18.1 rather than a separate drs_Dev bundle version. Identify the installed edition by its repository and theme name when recording server changes.
Troubleshooting
The two interfaces do not match
Stop the server and confirm ox_lib and ox_target came from the same bundle. Remove duplicate resource copies from other ensured or recursively scanned folders before restarting.
A dependent resource cannot find ox_lib or ox_target
Confirm the folders retain their exact names, ox_lib starts first, ox_target starts next, and the dependent resource starts after both.
Restricted target options behave incorrectly
Verify the intended supported framework and ox_inventory were already running when ox_target started. qtarget API compatibility alone is not a QBCore authorization adapter.
Theme controls are missing from /ox_lib
Confirm both folders came from the Axiom repository rather than Classic or an upstream archive, then clear any duplicate resource copy and restart the pair.
Reference
- ox_lib remains LGPL-3.0-or-later and ox_target's included LICENSE is MIT; preserve both component licenses and upstream attribution when redistributing the bundle.
- The ox_target README files describe GPL licensing, but the packaged ox_target LICENSE is MIT. This guide follows the actual included license file.
- The bundle repositories are manual derivatives rather than GitHub-marked forks; the manifests retain their upstream authors and repository references.