Documentation
Follow the installation steps to get the script running quickly and correctly on your server, with everything you need to get started.
Before installing Quasar Fisher Job, make sure your server meets the minimum requirements. The resource requires OneSync, a working MySQL database, and both ox_lib and oxmysql installed and running.
If you're using a modern ESX, QBCore, or Qbox server, these dependencies are usually already installed.
Requirement | Status | Download |
|---|---|---|
| Required |
| Required |
| Required | Included in the download |
An inventory | Required |
|
| Optional |
| Optional |
| Optional |
Vehicle keys script | Optional | 11 scripts supported, auto-detected |
Quasar Fisher Job automatically detects your framework, your inventory and your vehicle keys script. If no keys script is found, Config.Vehiclekeys falls back to 'none' and boat rental keeps working normally. xsound is only used by the speargun and the grill boat.
After purchasing Quasar Fisher Job, the resource is automatically linked to your CFX Portal account.
Sign in to the CFX Portal using the same account used during checkout, then open Granted Assets and locate Fisher Job in your asset library. Download the latest version and extract the archive.
After extracting the download, you should have the following folders:
qs-fishingjob
qs-fishing-propsFolder | Description |
|---|---|
| Main resource (required). |
| Stream-only resource (required). Contains the |
Never rename the resource folders. They must remain qs-fishingjob and qs-fishing-props, otherwise the resource and its user interface will fail to load correctly.
Move both folders into your server's resources directory. Although the resources can be placed anywhere inside the folder, keeping Quasar resources organized inside their own directory is recommended.
A typical installation looks like this:
resources/
└── [fishing]/
├── qs-fishing-props/
└── qs-fishingjob/Once the resources have been copied, open your server.cfg and ensure every required dependency starts before Quasar Fisher Job.
ensure oxmysql
ensure ox_lib
# Framework
ensure es_extended
# ensure qb-core
# ensure qbx_core
ensure qs-fishing-props
ensure qs-fishingjobThe loading order matters. Always start your framework, oxmysql, ox_lib and qs-fishing-props before starting qs-fishingjob. If the props resource loads after the script, nets, buoys, the speargun, the skewers and the grill boat will not spawn.
Quasar Fisher Job adds around 70 items: rods, tackle, baits, fish, crabs, nets, traps, diving gear, skewers and the grill boat.
The item files included in the download are never loaded by the resource — open the one that matches your inventory and copy the entries manually.
Inventory | File | Entries go to | Images go to |
|---|---|---|---|
ox_inventory |
|
|
|
qs-inventory |
|
|
|
qb-core |
|
|
|
ESX |
| Import into the database ( | Depends on your inventory |
All 73 images are included in qs-fishingjob/web/public/images/.
The script registers its usable items automatically on startup. Only ox_inventory dispatches its own items, which is why items_ox.lua is the only file containing export blocks. If your inventory dispatches usable items by itself and is not ox, set:
Config.RegisterUsableItemsManually = trueQuasar Fisher Job stores levels, XP, earnings, records, tournaments, crab traps, achievements and admin settings inside your server's database.
No manual SQL import is required. All nine tables (prefixed with
qs_fisher) are created automatically on the first startup. The[sql]/qs-fisher.sqlfile is optional, and only included for servers that prefer to create the schema by hand.
The tables created automatically are:
qs_fisher
qs_fisher_resets
qs_fisher_rewards
qs_fisher_leaderboard_winners
qs_fisher_records
qs_fisher_tournaments
qs_fisher_crabtraps
qs_fisher_achievements
qs_fisher_configESX servers must import [sql]/items(ESX).sql, since ESX reads its item list from the database instead of a Lua file. Open your preferred database manager (such as phpMyAdmin, HeidiSQL, DBeaver, or Navicat), select your server's database and execute it. It uses INSERT IGNORE, so running it twice is completely safe.
The schema routine is idempotent, so it runs safely on every restart. On startup it also adds any missing columns, aligns the collation of every identifier column with your framework (users.identifier on ESX, players.citizenid on QB), registers the fisher job on ESX, and applies the settings saved from the admin panel before anything reads a config value.
If the collation cannot be aligned automatically, the console prints the exact ALTER TABLE statement to run manually.
The admin panel uses the command.fishing ACE. Add it to your server.cfg:
add_ace group.admin command.fishing allowMost servers already run add_ace group.admin command allow, which grants the whole command.* space — in that case an existing admin can use the panel without any extra configuration.
Permissions are always verified on the server, both when opening the panel and again on every action inside it.
After completing the installation, restart your FiveM server.
If everything has been configured correctly, the server console will display a message similar to the following:
[qs-fishingjob] framework esx · inventory ox · vehicle keys qs-vehiclekeysThis line reports exactly what the resource detected. If the framework, inventory or keys script shown is not the one you expect, check the loading order in your server.cfg — a resource that starts after qs-fishingjob cannot be detected.
Finally, join your server with an administrator account and execute the following command:
/fisheradminIf the admin panel opens successfully, Quasar Fisher Job has been installed correctly and your server is ready to go fishing.