Skip to main content
Most atlasFishing issues come from start order, renamed folders, missing items, or missing NUI files.

​
Resource blocked on startup

If the console says the resource name is wrong, rename the folder back to: 
atlasFishing
Then restart the resource.
Do not rename the resource to atlas-fishing, fishing, or anything else. The script intentionally blocks renamed installs.

​
Bridge not found

Make sure atlasBridge exists and starts first: 
ensure atlasBridge
ensure atlasFishing
Also confirm the bridge folder is named exactly: 
atlasBridge

​
Fisherman ped does not spawn

If there is no fisherman to interact with:
  • Confirm Config.enabled = true and the resource is not blocked by the name guard.
  • Check Config.ped.coords — the default is a placeholder; you may be looking at the wrong spot. Use the map blip (Config.ped.blip) to find it.
  • Make sure atlasBridge started first; the ped is created through Bridge.Ped.
  • If you set Config.ped.interact.method = 'target', confirm ox_target or qb-target is installed and detected by the bridge, otherwise switch back to interact.

​
Shop or minigame does not open

Confirm the NUI build exists: 
atlasFishing/web/dist/index.html
If it is missing, reinstall the resource package or rebuild the web app if you are developing from source.

​
Cannot buy items

Check:
  • Item key exists in your inventory.
  • Payment account exists in your framework.
  • Player has enough money.
  • atlasBridge detected the correct framework and inventory.
  • Console does not show an inventory provider error.

​
Rod cannot be used

Check:
  • Player has fishing_rod.
  • Player has bait.
  • Config.enabled = true.
  • The player is near/facing water if Config.cast.requireWater = true.
  • The resource is not blocked by the name guard.

​
No fish received after success

Check:
  • Catch item keys exist in your inventory.
  • Inventory has room/weight available.
  • The minigame did not finish faster than Config.minigame.minMs.
  • Server console has no item grant errors.

​
Fishing does not cancel on death

Fishing should cancel if the player dies during a cast, bite wait, or minigame. Check:
  • Config.death.enabled = true.
  • atlasBridge starts before atlasFishing.
  • Your death system fires a normal death event, or you set atlas:deathEvent.
setr atlas:deathEvent "baseevents:onPlayerDied"

​
Selling does not pay

Check:
  • Player has sellable fish items.
  • Config.sell.account is valid for your framework.
  • Fish entries have price values.
  • Inventory provider can remove the fish item.

​
Boat rental issues

If boat rentals do not work:
  • Confirm Config.boatrental.enabled = true.
  • Move Config.boatrental.spawn to valid water.
  • Check the boat model exists.
  • Confirm the player has enough money in Config.boatrental.account.
  • Check the server console for vehicle spawn or permission errors.

​
Debugging steps

1

Turn on debug temporarily

Set Config.debug = true, restart, reproduce the issue, then turn it off.
2

Check the server console

Look for resource-name, bridge, inventory, or NUI errors.
3

Test one system at a time

Test shop, rod use, minigame, item grant, selling, then boat rental.
4

Revert recent config changes

If the default config worked before editing, compare your changed item keys, accounts, and coordinates.