Skip to main content
Most atlasFishing issues trace back to start order, a renamed folder, missing items, or a missing NUI build. Work top to bottom.

​
Startup & dependencies

shared/guard.lua requires the folder to be named exactly atlasFishing. If the console prints a name-mismatch warning, the resource has disabled itself.Rename the folder back to:
Then restart it. Do not use atlas-fishing, fishing, or anything else — the guard intentionally blocks renamed installs because the bridge, NUI callbacks, and setup all assume the exact name.
atlasFishing declares dependency 'atlasBridge' and needs it started first:
Also confirm the bridge folder is named exactly atlasBridge. If atlasBridge starts after atlasFishing, fishing will not initialize.

​
Ped & interaction

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

​
Shop, items & icons

Confirm the NUI build is present:
The supplies shop, boat shop, and minigames all render from this page. If web/dist is missing, reinstall the resource package, or rebuild from source:
  • The item key exists in your inventory (see Items & Icons).
  • The payment account in Config.shop.payments is valid for your framework.
  • The player has enough money.
  • The bridge detected the correct framework and inventory — check the console for a provider error.
  • You copied the right format — try the PNG set first (items/icons/png).
  • The icons are in your inventory’s image folder (e.g. ox_inventory/web/images/).
  • The filenames match the item keys if your inventory expects that.

​
Gameplay

  • The player has fishing_rod and at least one bait.
  • Config.enabled = true and the resource is not name-guard blocked.
  • The player is near/facing water if Config.cast.requireWater = true.
  • The catch item keys exist in your inventory.
  • The inventory has room/weight available.
  • The minigame did not finish faster than Config.minigame.minMs (a too-fast success is rejected server-side).
  • The bait did not roll a fail (catch nothing) — that is expected occasionally.
  • The server console shows no item-grant errors.
Fishing should cancel if the player dies during a cast, bite wait, or minigame.
  • Config.death.enabled = true.
  • atlasBridge starts before atlasFishing.
  • Your death system fires a normal death event, or you set the bridge convar:
  • The player has sellable fish (junk is not sellable).
  • Config.sell.account is valid for your framework.
  • The fish entries have price values.
  • The inventory provider can remove the fish item.
  • Config.boatrental.enabled = true.
  • Config.boatrental.spawn points at valid water (the default is a placeholder).
  • The boat model exists.
  • The player has enough money in Config.boatrental.account.
  • The server console shows no vehicle-spawn or permission errors.

​
General debugging

1

Turn on debug temporarily

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

Read the server console

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

Test one system at a time

Shop → rod use → minigame → item grant → selling → boat rental.
4

Revert recent config changes

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