Overview
Classic is a matched drs_Dev theme bundle containing ox_lib 3.39.0 and ox_target 1.17.3. Install the enclosed folders together under their original resource names so shared imports, exports, adapters, and qtarget compatibility continue to resolve correctly.
Requirements
- Included
- ox_lib 3.39.0 and ox_target 1.17.3
- 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
- 01
Back up the installed ox_lib and ox_target resources and their configuration before replacing them.
- 02
Download the selected bundle and copy its enclosed ox_lib and ox_target folders into the server resources directory without renaming them.
- 03
Remove every other drs-ox edition so duplicate ox_lib or ox_target resource identities cannot be started.
- 04
Start ox_lib before ox_target, then start resources that depend on either component.
- 05
Validate menus, notifications, progress UI, TextUI, target options, framework restrictions, and item-restricted interactions on a development server.
Configuration
Install the matched pair
Copy the bundle's inner ox_lib and ox_target directories into the server resources folder. Keep those exact folder names and remove or archive the previous pair outside the active resource tree.
Meet the shared baseline
Use FXServer artifact 7290 or newer with OneSync enabled. ox_lib must start before ox_target, and both must start before every resource that consumes their imports or exports.
Use the Classic preference scope
Classic keeps the baseline /ox_lib settings for notification position, notification audio, and locale. The scale, interface-sound, sound-volume, and reduced-motion controls belong to Redline, Ironclad, Heritage, and Axiom and are not present in Classic.
Start adapters before ox_target
Start Ox Core, ESX, qbx_core, or ND Core first when target options use framework group checks. Start ox_inventory first for item-count restrictions. The qtarget provider name preserves API compatibility but does not add plain QBCore job or gang authorization by itself.
Usage and validation
Validate every interface surface
Run the bundled ox_lib preview commands on a development server after replacing the pair, then validate at least one real ox_target zone, model, entity, and global option from a dependent resource.
/oxtestui
/oxnotify
/oxctx
/oxmenu
/oxradial
/oxskill
/oxprog
/oxcircle
/oxtext
/oxhidetextOpen player preferences
Use /ox_lib to review the settings exposed by Classic. Player preference changes are client-local and do not change the server defaults for other players.
/ox_libBundle design and settings
The edition changes the presentation layer while retaining the established resource identities and integration surface.
- Typography
- Inter
- Accent treatment
- Neutral white and gray
- Target presentation
- Compact tree and branch layout with a white in-world hover sprite
- Motion and progress
- The compact baseline; no separate bundle-level motion preset is documented
- Player theme controls
- Baseline notification, audio, and locale controls through /ox_lib
Classic direction
Compact dark radial panels, local Inter typography, neutral gray borders, white hover inversion, a small center dot, and the established tree-and-branch target layout.
Differences from upstream
Presentation-focused derivative
Classic supersedes the older standalone ox_lib and ox_target site listings as one matched package. Against those prior public snapshots, the bundle includes its compiled interface build, positions the radial cursor lower on screen, and uses a neutral-white target hover sprite.
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 and ox_target 1.17.3, then validate the integration against this packaged snapshot.
Updating
Review upstream changes manually
The inherited version checkers query Overextended ox_lib and CommunityOx 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 3.39.0 and 1.17.3 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.
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.