Start here
ls_trucking is a configurable freight-career resource. Complete the framework, inventory, interaction, vehicle, route, contract, service-bay, and progression configuration before opening the job to players.
On this page
ls_trucking
A complete freight career, not another checkpoint route.
QboxQBCoreESXND FrameworkND CoreStandaloneOX LibOX MySQLOX TargetQB Target
What you need
Requiredox_lib and oxmysql
Interactionox_target, qb-target, or OX TextUI
FrameworkSupported framework or standalone mode
InventorySupported inventory system
Install and start
- 01
Place ls_trucking in your server resources.
- 02
Add the matching inventory items from the install folder when required.
- 03
Configure the framework, routes, vehicles, trailers, contracts, service bay, and random events.
- 04
Ensure dependencies before ls_trucking and verify the database startup summary.
Recommended start orderplain text
ensure ox_lib
ensure oxmysql
# ensure your selected framework and inventory
ensure ox_target # or your selected interaction resource
ensure ls_truckingConfiguration checkpoints
Select one framework mode
Choose Qbox, QBCore, ESX, ND_Framework, legacy ND_Core, or standalone behavior and keep the related player and job settings consistent.
Select the interaction layer
Configure ox_target, qb-target, or the supported OX TextUI path. Start the selected interaction resource before ls_trucking.
Build the freight catalog
Review routes, contracts, package and trailer work, job vehicles, progression ranks, contractor licensing, private fleets, service-bay options, and random events.
Install inventory items when required
Add the applicable item definitions when required by the inventory selected through Config.Inventory.System. ND Inventory registration is handled automatically.
Let the resource prepare its database
Normal installation is automatic: the resource creates missing tables and runs supported migrations at startup. The included SQL file is a backup and recovery reference, not a routine install step.
Validate the resource
Validate the complete job loop
Test dispatch access, contract acceptance, vehicle retrieval, cargo loading, delivery verification, payment, reputation, route history, and vehicle return as one continuous session.
Commandsplain text
/trucking
/truckreceiver
/truckui
/lsservice
/canceltruckingReview startup diagnostics
Use the resource's startup summary and console output to confirm the chosen framework, inventory, interaction system, and database are available. The default receiver and dispatch keys are F2 and F3.
Common checks
Dispatch opens but work cannot start
Check job access, contract configuration, available route and vehicle entries, and whether the selected framework mode can resolve the player.
Targets or prompts are missing
Confirm the configured interaction system is installed, started first, and matches the option selected for the resource.
Progress does not persist
Confirm oxmysql starts before ls_trucking and review the server console for database initialization or query errors.
An inventory handoff fails
Verify the selected inventory bridge and required item definitions match the running inventory resource.
Source and release notes
- Test configuration changes on a development server before applying them to an active economy.
- A healthy startup reports that automatic database setup and migrations completed.
- The repository LICENSE is GPL-3.0; retain it with redistributed copies.