{"id":22060,"date":"2026-06-11T12:17:30","date_gmt":"2026-06-11T12:17:30","guid":{"rendered":"https:\/\/xgamingserver.com\/blog\/fivem-ox-target-setup-guide\/"},"modified":"2026-06-11T12:17:30","modified_gmt":"2026-06-11T12:17:30","slug":"fivem-ox-target-setup-guide","status":"publish","type":"post","link":"https:\/\/xgamingserver.com\/blog\/fivem-ox-target-setup-guide\/","title":{"rendered":"FiveM ox_target Setup Guide: Third-Eye Interaction (2026)"},"content":{"rendered":"\n

ox_target is the go-to third-eye targeting resource for FiveM roleplay servers. It lets players hold a key to open a radial interaction menu tied to world zones, entities, peds, and vehicles \u2014 powering everything from job actions to shopkeeper prompts. This guide walks you through installation, configuring your first zones, using the core client exports, and migrating away from the older qtarget API.<\/p>\n\n\n\n

Prerequisites<\/h2>\n\n\n\n

ox_target has a single hard dependency: ox_lib<\/strong>. The resource’s own fxmanifest.lua<\/code> declares dependency 'ox_lib'<\/code>, and its shared_scripts<\/code> load @ox_lib\/init.lua<\/code> at startup. If ox_lib is missing or starts after ox_target, the resource will error immediately and no interactions will register. Install ox_lib first from github.com\/overextended\/ox_lib<\/a>, then proceed.<\/p>\n\n\n\n

Installation<\/h2>\n\n\n\n

Download a release from github.com\/overextended\/ox_target\/releases<\/a> and extract the folder into your server’s resources<\/code> directory. The folder must be named ox_target<\/code>.<\/p>\n\n\n\n

Open your server.cfg<\/code> and add the ensure lines in the correct order \u2014 ox_lib must appear before ox_target, and both must appear before any resource that calls ox_target exports:<\/p>\n\n\n\n

ensure oxmysql\nensure ox_lib\nensure ox_target\n\n# your scripts that use ox_target come after this line\nensure my_shop_resource\nensure my_job_resource<\/code><\/pre>\n\n\n\n
That is all that is required for a basic setup. ox_target ships with framework detection built in, so it will automatically pick up ox_core, ESX (esx-legacy), or QBX (qbx_core) if those are present \u2014 no extra configuration is needed to unlock job\/group filtering.<\/p>\n\n\n\n
Optional Convars<\/h2>\n\n\n\n
You can tune ox_target behaviour via setr<\/code> convars in server.cfg<\/code>. Add any of these before the ensure ox_target<\/code> line:<\/p>\n\n\n\n
# Hold key to open targeting (0) or toggle on\/off (1). Default: 0\nsetr ox_target:toggleHotkey 0\n\n# Key used to activate targeting. Default: LMENU (Left Alt)\nsetr ox_target:defaultHotkey LMENU\n\n# Draw a dot at the centre of box zones. Default: 1\nsetr ox_target:drawSprite 1\n\n# Enable built-in default interactions (e.g. doors). Default: 1\nsetr ox_target:defaults 1\n\n# Show zone outlines for debugging. Default: 0\nsetr ox_target:debug 0\n\n# Allow left-click to select an option. Default: 1\nsetr ox_target:leftClick 1<\/code><\/pre>\n\n\n\n
Declaring ox_target in Your Own Resource<\/h2>\n\n\n\n
Any resource that calls ox_target exports must load ox_lib’s init file. A minimal fxmanifest.lua<\/code> for a script that uses ox_target looks like this:<\/p>\n\n\n\n
fx_version 'cerulean'\ngame 'gta5'\nlua54 'yes'\n\nshared_scripts {\n  '@ox_lib\/init.lua',\n}\n\nclient_scripts {\n  'client.lua',\n}\n\ndependencies {\n  'ox_lib',\n  'ox_target',\n}<\/code><\/pre>\n\n\n\n
The dependencies<\/code> block tells FiveM to refuse loading your resource if ox_lib or ox_target is missing, giving you a clear error rather than a silent failure.<\/p>\n\n\n\n
Core Client Exports<\/h2>\n\n\n\n
All interaction is defined through client-side Lua exports. The four you will use most are addBoxZone<\/code>, addLocalEntity<\/code>, addEntity<\/code>, and addModel<\/code>. See the FiveM server hosting docs<\/a> for wider server-setup context.<\/p>\n\n\n\n
addBoxZone<\/h3>\n\n\n\n
addBoxZone<\/code> creates a rectangular targetable area in the world. It accepts a single Lua table and returns a numeric zone ID you can use later to remove it:<\/p>\n\n\n\n
-- client.lua\nlocal zoneId = exports.ox_target:addBoxZone({\n  coords   = vector3(150.2, -1040.5, 29.37),  -- world position\n  size     = vector3(2.0, 1.5, 2.0),           -- width, depth, height\n  rotation = 45.0,                              -- heading in degrees\n  debug    = false,                             -- set true to see the box outline\n  options  = {\n    {\n      label    = 'Open Shop',\n      icon     = 'fa-solid fa-store',           -- Font Awesome class name\n      onSelect = function(data)\n        -- data.entity, data.coords, data.zone are available here\n        TriggerEvent('my_shop:open')\n      end,\n    },\n  },\n})\n\n-- Remove the zone when your resource stops\nAddEventHandler('onResourceStop', function(resourceName)\n  if resourceName == GetCurrentResourceName() then\n    exports.ox_target:removeZone(zoneId)\n  end\nend)<\/code><\/pre>\n\n\n\n
The icon<\/code> field takes a Font Awesome class string (e.g. 'fa-solid fa-car'<\/code>), not an image path \u2014 this is one of the key differences from qtarget.<\/p>\n\n\n\n
addLocalEntity<\/h3>\n\n\n\n
addLocalEntity<\/code> attaches interactions to a specific entity handle that only exists on the local client \u2014 useful for props or peds your script spawned:<\/p>\n\n\n\n
local prop = CreateObject(`prop_atm_01`, 200.0, -800.0, 31.0, true, true, false)\n\nexports.ox_target:addLocalEntity(prop, {\n  {\n    label      = 'Use ATM',\n    icon       = 'fa-solid fa-credit-card',\n    distance   = 1.5,\n    canInteract = function(entity, distance, coords, name, bone)\n      -- return false to hide the option without removing it\n      return not IsPedInAnyVehicle(PlayerPedId(), false)\n    end,\n    onSelect   = function(data)\n      TriggerEvent('banking:openATM')\n    end,\n  },\n})<\/code><\/pre>\n\n\n\n
addEntity (network entities)<\/h3>\n\n\n\n
When an entity exists across the network (e.g. a vehicle or ped synced via OneSync), use addEntity<\/code> and pass the network ID<\/em> instead of the local entity handle:<\/p>\n\n\n\n
-- netId obtained from server or another resource\nexports.ox_target:addEntity(netId, {\n  {\n    label       = 'Impound Vehicle',\n    icon        = 'fa-solid fa-truck-tow',\n    groups      = 'police',   -- only players with the 'police' job see this\n    onSelect    = function(data)\n      TriggerServerEvent('police:impound', NetworkGetEntityFromNetworkId(data.entity))\n    end,\n  },\n})<\/code><\/pre>\n\n\n\n
TargetOptions Field Reference<\/h2>\n\n\n\n
Every export that accepts an options<\/code> table expects an array of TargetOption objects. The fields available on each option are:<\/p>\n\n\n\n
Field<\/th>Type<\/th>Required<\/th>Notes<\/th><\/tr><\/thead>
label<\/code><\/td>string<\/td>Yes<\/td>Text shown in the interaction menu<\/td><\/tr>
icon<\/code><\/td>string<\/td>No<\/td>Font Awesome class name (e.g. fa-solid fa-key<\/code>)<\/td><\/tr>
iconColor<\/code><\/td>string<\/td>No<\/td>CSS colour for the icon<\/td><\/tr>
name<\/code><\/td>string<\/td>No<\/td>Identifier used when removing specific options later<\/td><\/tr>
distance<\/code><\/td>number<\/td>No<\/td>Max range in metres; defaults to 2.0<\/td><\/tr>
groups<\/code><\/td>string \/ string[] \/ table<\/td>No<\/td>Job, gang, or group required (framework-dependent)<\/td><\/tr>
items<\/code><\/td>string \/ string[] \/ table<\/td>No<\/td>Inventory item(s) required to see the option<\/td><\/tr>
canInteract<\/code><\/td>function(entity, distance, coords, name, bone)<\/td>No<\/td>Called every frame; return false to hide the option<\/td><\/tr>
onSelect<\/code><\/td>function(data)<\/td>No<\/td>Fires on selection (highest priority)<\/td><\/tr>
event<\/code><\/td>string<\/td>No<\/td>Client event triggered on selection<\/td><\/tr>
serverEvent<\/code><\/td>string<\/td>No<\/td>Server event triggered on selection<\/td><\/tr>
command<\/code><\/td>string<\/td>No<\/td>Command executed on selection<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
Migrating from qtarget \/ qb-target<\/h2>\n\n\n\n
ox_target ships with a compatibility shim at client\/compat\/qtarget.lua<\/code> and declares provide 'qtarget'<\/code> in its manifest, so resources that call the old exports.qtarget:*<\/code> or qtarget global functions will be redirected automatically for common cases. However, Overextended explicitly states that this shim does not and will never cover 100% of qtarget’s behaviour \u2014 it is a stopgap, not a permanent replacement.<\/p>\n\n\n\n
For a clean migration, rewrite your calls manually. The main differences are:<\/p>\n\n\n\n