AWS Lumberjack

Forestry job with trees, axe handling, progression, missions and a tablet hub.

Installation

Requirements

• ox_lib, oxmysql and a supported QB/ESX framework adapter.
• The included aws-lumberjack-props resource. Inventory items must be registered in your inventory.
• Target/clothing integrations depend on the options enabled in config. Native Qbox requires checking the QB bridge.

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 ox_target
ensure aws-lumberjack-props
ensure aws-lumberjack

Setup steps

1. Extract both aws-lumberjack and aws-lumberjack-props directly into your server resources.
2. Inspect the included SQL files and register the axes, wood and products named in the configuration; do not invent item names from another version.
3. Match the framework/inventory choices to your running resources. Disable clothing integration if no matching appearance resource is installed.

Gameplay and usage

1. Go to the configured work NPC, start duty and use the configured axe at a supported tree.
2. Check the tablet missions and leaderboard after completing a work cycle.

Configuration

• config/config.lua defines locations, trees, items, clothing and job access.
• config/sh_config.lua loads after config.lua and overrides target, language, debug and notification settings.
• Configure framework/target bridges in client/framework, server/framework and shared/bridge.lua.

Exports and integrations

No public callable export is declared with exports() in these source files. Use the documented commands or configuration; internal network events are not a trusted integration API.

Troubleshooting

• Start the included prop resource before the job.

• Test axe durability, tree respawn, sales, reconnect persistence and job restrictions.

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

Package reference

Database files

• aws-lumberjack/aws_lumberjack.sql

Configuration reference

• aws-lumberjack/config/clothing.lua (edit the table returned/defined by this file).
• aws-lumberjack/config/config.lua: Framework, Inventory, Dispatch, Phone, Wardrobe, Garage, RequireJob, LumberJackJob, Target, TargetScript, EnableEInteract, InteractDistance, DefaultNotifications, EnableMarker, HideNpcMarkerWithTarget, ShowTreeMarkers, RespawnTime, TreeBlips
• aws-lumberjack/config/sh_config.lua: Framework, Target, TargetScript, Language, DefaultNotifications, EnableEInteract, EnableMarker, HideNpcMarkerWithTarget, ShowTreeMarkers, Drawtext, DailySellLimit, Webhooks, Debug, DebugNotify, EnableDebugPrints, UseModernPanel, InventoryOverride

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.