Skip to main content
Check that: (1) the prop’s model name exactly matches the GTA model — no typos, (2) the prop is enabled in the admin panel, (3) your target system is configured correctly, and (4) the player’s cooldown hasn’t already expired for that prop model.
Your license hash is not in Config.Licenses. Run the following in your server console to find your exact hash, then add it to config.lua:
Target system changes require a resource restart. Use the Restart Resource button in the Danger Zone section of the admin panel — it saves your config and restarts automatically.
The resource must have write permission to its own folder on the FXServer. Check file permissions. The server console will log an error if SaveResourceFile fails.
Only object entities (GTA entity type 3) can be captured. Vehicles and peds are ignored. Walk to within 20 metres of the prop — that is the maximum raycast range. Also make sure you are pointing directly at the prop’s mesh, not slightly past it.
Yes — use the custom category. The search bar still finds them by model name, label, and tags regardless of category.
No — one item is awarded per search by design to keep the economy balanced. The quantity is randomized between the loot entry’s min and max values.
Yes. Open the prop editor in the admin panel, click Edit Loot Table, make your changes, and save. Changes apply immediately with no restart required.
The Unique Prop config takes priority. If a prop at specific coordinates matches both a global entry and a unique entry, the unique loot table and settings are used for that instance.
The search log is held in server memory only. It does not persist across resource restarts. Enable Discord webhook logging in config.lua for a persistent audit trail.