Skip to main content
atlasFishing uses real inventory items for the rod, bait, and catches. If an item is missing, players may be unable to buy supplies, use bait, receive a catch, or sell it. The keys must match between config.lua, your inventory definitions, and (for some inventories) the icon filenames.

Definition files

The resource ships ready-to-copy item files in items/, generated to match config.lua exactly:
Paste the block from items/ox_inventory.lua inside the returned items table in ox_inventory/data/items.lua, then drop the icons into ox_inventory/web/images/.
See Installation → Inventory items for the full step-by-step.

Required item keys

Labels can change freely; keys must match the config and your inventory.

Rod

The rod is registered usable automatically by the script (Bridge.Inventory.RegisterUsableItem(Config.rod.item)) — no extra wiring. Just make sure the item exists.

Baits

Catches (24 fish)

Junk catches in the default config (conch, scallop, clam, oyster, starfish, sea urchin) are not inventory items. They have no item key — they only produce a “you pulled up junk” result with a prop, so they need no definition. You can disable them entirely with Config.junk = { enabled = false }.

Icons

Icons ship in both formats:
Copy the format your inventory supports into its image folder. PNG is the safest choice — many inventory UIs still expect PNG filenames. Use WebP only if you know your UI supports it.
These inventory icons are separate from the shop / bait-radial / sell-radial art, which loads from the resource’s own images/ folder by default. See Config.Images for the artwork system (local PNGs, missing-file fallback, and switching to a CDN).

Renaming an item

If you rename an item, update every reference:
1

Inventory definition

Change the key in your inventory item file.
2

Config

Update the matching key in Config.rod.item, Config.baits, Config.fish, or Config.shop.items.
3

Icon filename

Rename the icon file if your inventory expects filenames to match item keys.
4

Restart

Restart the inventory resource, atlasBridge, and atlasFishing.

Common mistakes

The item key may not exist in your inventory, or the payment account in Config.shop.payments may not be supported by your framework.
Confirm every fish key from Config.fish exists in your inventory item definitions, and that the inventory has room.
Your inventory image folder may use a different path or extension rule. Copy the PNG set first and confirm the filenames match the item keys.