# QBCore hunting scripts

No official QBCore repository named `qb-hunting` was available at the exact `qbcore-fivem/qb-hunting` path on 2026-10-13 (HTTP 404). Check the [qbcore-fivem organization](https://github.com/qbcore-fivem) and the actual provider source; this name alone does not identify a canonical supported implementation. Community hunting scripts can use different entity ownership, weapon, inventory, reward, and persistence models.

## Evaluate a candidate

- Confirm author, repository, license, and maintained branch.
- Inspect entity ownership and proximity validation on the server.
- Verify rewards cannot be triggered with arbitrary network IDs or animal types.
- Measure spawning loops and cleanup under representative load.
- Test disconnects, resource restarts, inventory-full behavior, and concurrent processing.

Find candidates through the [Cfx.re releases section](https://forum.cfx.re/c/development/releases/7) and apply the [marketplace checklist](/docs/resources/marketplaces). Do not use SQL or events from a generic page as though they belong to every implementation.

## Install only an identified implementation

1. Record the repository or supplier, license, release/commit and compatible framework and inventory versions.
2. Compare its `fxmanifest.lua` dependencies, imported scripts and declared exports with your installed resource names. Use the [Compatibility Analyzer](/tools/compatibility-analyzer) for a local static check; missing-from-selection findings require source or server confirmation.
3. Back up the isolated test database before applying the selected project's documented migrations. Check table/item names against that project's actual source; do not substitute another fork's SQL.
4. Follow the author's configuration and start-order instructions, then inspect server and client logs. Diagnose the first missing dependency/export before changing game logic.
5. Run the acceptance cases below on an isolated server and preserve the exact revision and results before production installation.

## Runtime acceptance checklist

Review animal ownership, distance, processing and rewards in the server implementation. Treat client-supplied claims as untrusted;
[Cfx.re's event-security guidance](https://docs.fivem.net/docs/developers/server-security/)
explains the server-validation boundary. The following are acceptance requirements, not results
verified for an unidentified resource.

| Case | Expected behavior to verify |
| --- | --- |
| Harvest reward | Wrong animal types, distant entities and repeated processing do not grant rewards. |
| Concurrency | Two players processing the same animal receive at most the intended single reward. |
| Lifecycle | Disconnects and resource restarts release reservations and clean up owned entities without affecting other resources. |

If these checks fail, capture the first server error, dependency versions and reproducible request
sequence for the author. Do not publish credentials, player identifiers or a full server.cfg.
An encrypted or unavailable server implementation leaves the reward/security review unverified;
a clean static report cannot certify it. This page intentionally supplies no universal events,
exports or install command for unrelated third-party products.
