# QBCore fishing scripts

No official QBCore repository named `qb-fishing` was available at the exact `qbcore-fivem/qb-fishing` 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. Third-party fishing resources differ in items, inventory integrations, zones, economy logic, and licenses.

## Evaluate a candidate

- Verify the actual source repository and license.
- Read its manifest and config before installing dependencies.
- Confirm catches, rewards, item removal, and sale prices are validated server-side.
- Test inventory-full, disconnect, restart, duplicate-event, and multi-player cases.
- Import only SQL shipped and documented by the selected project.

Use the [Cfx.re releases section](https://forum.cfx.re/c/development/releases/7) and the [marketplace checklist](/docs/resources/marketplaces). This page does not provide generic install commands because there is no single canonical 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 bait consumption, catch eligibility and sale payouts 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 |
| --- | --- |
| Catch reward | Out-of-zone, missing bait and repeated catch requests do not grant items. |
| Item capacity | A full inventory does not consume bait or lose a purchased item without a defined recovery path. |
| Sales | The server verifies owned items and configured prices; a forged client quantity cannot raise the payout. |

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.
