Fishing
Integrations and Data
Configure frameworks, inventories, notifications, targets, vehicle keys, translations, exports, and local data storage.
On this page10 sections
Framework bridge
The framework is detected automatically.
Supported setups are ESX, QBCore, Qbox, ox_core, vRP, and standalone.
The bridge also checks framework-specific player-load events for pending ranking rewards.
Notifications and targets
Config.Notify.provider supports auto, ox_lib, okok, mythic, qbox, qb, esx, native, and custom.
Automatic detection prefers ox_lib, then okokNotify, mythic_notify, framework notifications, and the GTA ticker.
ox_target and qb-target also detect automatically. Without either, NPC interactions use markers and keys.
Inventory and vehicle keys
The bridge supports ox_inventory, qb-inventory, qs-inventory, codem-inventory, origen-inventory, and framework inventories.
Boat keys support qbx_vehiclekeys, qb-vehiclekeys, wasabi_carlock, cd_garage, and mk_vehiclekeys.
Add custom integrations in the relevant bridge file.
Steam avatars
Config.SteamAvatars resolves ranking avatars from SteamID64 values server-side.
Use an API key for reliable lookups. Public profile XML is the fallback.
Clients receive only the final image URL. Failed lookups use player initials.
Exports and events
The fishingrod client export supports ox_inventory rod use.
Use sc_fishing:useItem as the fallback client event for other inventories.
The script also uses sc_fishing:notify, sc_fishing:deleteRodProp, and an internal callback event.
Translations
Set Config.Locale to choose locales/en.json or locales/pl.json.
New languages start as a copy of en.json. Missing keys fall back to English.
Fish labels and descriptions live in the configuration, not locale files.
Local data storage
All persistent data is stored in database/database.json.
It includes EXP, tasks, rods, history, counts, records, collection state, rankings, rewards, and boosts.
Writes flush every five seconds and during resource shutdown.
A corrupt data file is backed up and replaced. Startup continues without a database server.
Data retention
Catch history retains the latest 100 entries for each player.
Players are identified by their framework identifier.
Keep those identifiers stable when changing framework versions.
Custom integrations
Use Config.Notify.provider = 'custom' for your own notification resource.
Custom zones must return a handle with a remove() method.
Custom coin payouts receive the player source, amount, and identifier.
Locale behavior
English and Polish ship with the resource.
Missing locale keys fall back to English.
Item names and fish descriptions remain in configuration files.
The interface's relative history timestamps remain English.