AWS Fishing

Fishing with configurable species, bait, progression, daily tasks and a browser UI.

Installation

Requirements

• ox_lib, oxmysql, the framework detected by shared/framework.lua and the inventory used by server/core.lua.

Startup order

This example selects one framework and target. Use the resources matching your configuration and start dependencies first.

ensure oxmysql
ensure ox_lib
ensure qb-core
ensure ox_inventory
ensure aws-fishing

Setup steps

1. shared/config.lua returns the configuration table; edit its keys directly rather than adding Config.* assignments.
2. Register the rod, bait and fish names found in shared/config.lua and the server item adapters.
3. The server creates the fishing table; inspect migrations before using an existing table from a different script.

Gameplay and usage

1. Use the configured rod near a valid fishing zone. H stops fishing and J opens the bait menu by default.
2. /setfishlevel is a staff function; confirm framework permissions.

Configuration

• shared/config.lua: Locale, Fish, Bait, zones, stores and UI settings.
• Boats and BoatReturnPoints are empty/commented in this supplied version, so boat rental is not enabled by default.

Exports and integrations

• aws-fishing.useRod — see aws-fishing/client/client.lua for its arguments and client/server context.

Troubleshooting

• Test catching, bait consumption, sale prices, daily missions and level persistence.

• Verify the built UI assets load with no F8 errors.

• Include the package version, framework and exact server/F8 error when requesting support. Remove private tokens and player data.

Package reference

Database files

No standalone SQL file is included. Check the installation steps above for tables created by server code.

Configuration reference

• aws-fishing/shared/config.lua (edit the table returned/defined by this file).

Frequently asked questions

Does this need Keymaster or an escrow key?

The Lua sources in this delivery package were readable in the static audit. No /assetpacks requirement is added by this package. Required framework, inventory and map resources still need to be installed separately.

Can I change the folder or database table names?

Keep the supplied folder names. Historical event, SQL and KVP identifiers are retained to protect existing integrations and saved data. Renaming a table or event requires a separate migration.

Why is an interface or item missing?

Check the startup order, selected framework/target adapter, inventory item definitions and the server/F8 console. The package does not install an entire framework or inventory for you.

Has this been tested on my server?

ZIP integrity, source readability, script syntax and manifest references were checked locally. Multiplayer gameplay, your framework version and integrations require a FiveM server acceptance test before a public release.