- ESX
- QBCore
- Qbox
FREE Chop Shop
Free QBCore chop shop script with two mission types, reputation-gated export runs, configurable vehicle parts, NPC flatbed collection, and police dispatch integration — rated 4.11/5 by the community.
ProdigyRP 2.0-inspired ox_target UI redesign for FiveM. Smooth eye animations, sprite icons, configurable colors and transparency. Drag-and-drop install, all frameworks supported.
ox_target works well. Its default UI, though, looks like it belongs on a different server than your custom HUD, MLO interiors, and character creator. This redesign keeps ox_target's full interaction logic intact and replaces only the visual layer — smooth eye icon animations, sprite-based action icons, active zone highlight effects, and a color scheme you configure to match your server's identity.
The interaction eye and action list are rebuilt with animated transitions rather than static pop-ins. When a player looks at an interactable zone, the eye icon moves into position smoothly, the active zone highlights on hover, and action icons use configurable sprites rather than text-only labels. None of this changes how ox_target registers zones or fires events — every existing interaction defined in your other resources works without modification.
Framework-independent — works with any server setup running ox_target and ox_lib. Compatible across ESX, QBCore, Qbox, and standalone configurations.
These are two separate products. The Prodigy 2.0 Inventory System handles item storage and metadata. This target redesign handles only the interaction UI layer — you can run both together, or either independently. They share the ProdigyRP aesthetic lineage but are otherwise independent resources with no shared dependencies between them.
Servers that have already invested in polished MLOs, custom HUDs, and branded UI and then notice their interaction system still looks like a stock release. At £15 (currently reduced from £30), it's the lowest-friction way to bring the interaction layer in line with the rest of the server's visual standard.
Use the documentation included with the download as the final authority. This plan helps you prepare a rollback, install in the right order, and verify the resource before it reaches players.
Open the supplied documentation before moving files or changing the database. Build the install order from the package, not from assumptions.
Ready when Every dependency and required file has a place in your install plan.
Prepare the server so the change can be reversed cleanly if the resource conflicts with your current stack.
Ready when You can restore the previous database, files, and configuration.
Apply only the changes supplied for this resource, keeping dependency and startup order intact.
Ready when The resource starts without missing files, exports, tables, or dependencies.
Restart the test server, watch both server and client consoles, and exercise the resource before opening it to players.
Complete when The intended flow works twice with no new console errors.
ProdigyRP 2.0 Inspired Target | ox_target Redesign
Contact support
We are in the middle of converting everything over from esx to qbox right now and this was honestly the easiest part of the switch so far. Dragged it in, replaced the old ox_target eye visuals, and it just works across all our scripts without touching a single zone file. Changed the main color in the config to match our ui and havent had to look at it since.
Dropped this straight onto our QBCore setup running ox_target and ox_inventory. The default eye look was starting to feel really dated compared to the rest of our UI. Took maybe five minutes to adjust the hover colors and icon spacing. Matches the rest of our script suite now without breaking any existing target options.
Reviews are moderated before appearing. Purchased the product? Your review gets a VERIFIED badge automatically.
ProdigyRP 2.0 Inspired Target | ox_target Redesign is a FiveM resource for esx, qbcore, qbox servers. Review the product details, requirements, and compatibility notes before ordering.
Use the included files and documentation as the source of truth for installation, configuration, dependencies, and any stated performance information.