Ox Target for FiveM: setup, zones and interaction options

What Ox Target does and what it depends on

The Ox Target installation guide describes a standalone targeting resource with extra functionality for ox_inventory and supported frameworks. It names ox_lib as a dependency and lists ox_core, esx and qbx_core integrations. Standalone targeting and framework-dependent item or job checks are different capabilities.

Install the intended release using the original project instructions and record the dependency versions. Before connecting a shop, inventory or job, verify that the targeting interface itself can open and display a simple option. This gives you a baseline for identifying which integration introduces a failure.

Choose a zone, model or entity API

A fixed location and an object moving through the world need different targeting approaches. The client API distinguishes model registrations, networked entity IDs, local entity handles and geometric zones. Select the scope you intend instead of registering a global option merely because it appears to work.

Start with a diagnostic box zone

The source-backed example below creates a named zone and a selectable option that only prints a diagnostic message. Replace the demonstration coordinates with a location you control on staging. It does not open an inventory, grant an item or implement a business interaction. Magnate has not run this example in the game.

The client API returns a zone ID and supports removing a registered zone. Keep that lifecycle in your integration plan: starting a resource, stopping it and restarting it should leave the intended number of options. For a dedicated test resource, declare ox_target as a manifest dependency and put this example in a client script.

local zoneId = exports.ox_target:addBoxZone({
    name = 'magnate_demo_zone',
    coords = vec3(0.0, 0.0, 0.0), -- replace with your staging location
    size = vec3(1.5, 1.5, 2.0),
    rotation = 0.0,
    debug = true,
    options = {
        {
            name = 'magnate_demo_action',
            label = 'Test interaction',
            distance = 2.0,
            onSelect = function()
                print('Magnate diagnostic option selected')
            end
        }
    }
})

-- In the appropriate cleanup path while ox_target is running:
-- exports.ox_target:removeZone(zoneId)

Option visibility and action selection are separate checks

The TargetOptions reference documents distance, groups, items and canInteract controls. Groups and item checks depend on framework integration. It also defines a single-action priority: onSelect, export, event, serverEvent, then command. If an option contains several action fields, do not expect all of them to run.

For a first integration, choose one intended action and trace it from selection to result. If the diagnostic print works but a later inventory action fails, keep the successful targeting baseline and inspect the integration’s callback or event. Changing the zone size will not repair a missing inventory export.

Do not use a hidden option as server authorization

Cfx’s event-security guide explains that clients can trigger network events and recommends validating server-side state for sensitive actions. If selecting a target leads to a purchase, item grant or job reward, validate the relevant conditions in the server-side operation rather than trusting that the UI hid the option.

Write the expected rule with the feature: who can perform it, from where, with which items and how often? Use the actual framework data and resource API to implement those checks. The diagnostic example deliberately performs no transaction; adding a money or inventory event requires its own implementation and tests.

Troubleshoot the first failed step

First distinguish an eye that never opens, an option that is absent and an option that can be selected but produces the wrong result. Keep the exact client or server error and installed versions with each report. A screenshot of an absent prompt does not show which condition prevented it.

Connect targeting to the rest of the server

For an interior, test the room and entrance independently from the target zone. For crafting, the interaction location is one part of a recipe and inventory workflow. For a shop, check that the intended item and payment operation completes, not only that the target label appears.

Use the inventory guide for framework compatibility, the keybind guide for conflicting controls and the map guides for environment packages. A blip is a separate map icon; the blip creator does not register a target interaction. These are current GTA V/FiveM workflows and do not establish GTA VI support.

Questions, answered.