> For the complete documentation index, see [llms.txt](https://baobab-interactive.gitbook.io/baobab-interactive-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://baobab-interactive.gitbook.io/baobab-interactive-docs/hotshot-trucking-simulator/updates-and-testing.md).

# Updates and Testing

## Current release: 1.33.2 beta

* The first-job guide follows equipment, pickup, paperwork, loading, straps, and delivery. It is controlled from dispatch and supports hiding/replaying without resetting a job.
* The fleet contains one configured company work truck at level 1, compatible with the 20-, 30-, and 40-foot flatbeds. Trailer unlocks remain 1, 3, and 6.
* Development diagnostics commands and trace logging have been removed. Gameplay validation, recovery safeguards, and important error reporting remain.
* The supported commands are `/hotshot`, `/cancelhotshot`, `/manifest`, `/dotinspect`, and the permission-protected `/hotshotreset`.
* The release includes the 1.33.1 QB/ESX player-lookup compatibility fix.

The first-job guide was introduced in 1.33.0. Convoy contracts are not included in this release.

When migrating from the older documentation, update `Config.Access` to the supported permission fields and modes, and keep your intended access policy. See [Frameworks and access](/baobab-interactive-docs/hotshot-trucking-simulator/frameworks-and-access.md). The current release defaults are permission-restricted, not public access.

## Update an existing server

{% stepper %}
{% step %}

## Finish active work

Have drivers finish or cancel contracts and return equipment.
{% endstep %}

{% step %}

## Back up the current installation

Back up the installed resource, custom configuration, and actual server KVP storage.
{% endstep %}

{% step %}

## Stop Hot-Shot

Stop Hot-Shot during maintenance.
{% endstep %}

{% step %}

## Install the update

Install the complete updated runtime and manifest together.
{% endstep %}

{% step %}

## Merge configuration

Merge your settings into the new config structure, preserving intended permissions, identity scope, fleet, and locations.
{% endstep %}

{% step %}

## Keep the resource name stable

Keep the deployment resource name stable.
{% endstep %}

{% step %}

## Start services

Start dependencies and Hot-Shot in order.
{% endstep %}

{% step %}

## Test before reopening work

Test an existing profile and a fresh contract before reopening work.
{% endstep %}
{% endstepper %}

{% hint style="warning" %}
Keep old runtime backups outside automatically started resource collections. Do not restart vehicle resources while their models are in use.
{% endhint %}

## Acceptance checklist

* A new level-1 driver can collect the company work truck and compatible 20-foot starter trailer and receive Building Materials.
* The first-job guide can auto-start for an eligible new driver, hide, replay, and follow the current objective without advancing gameplay.
* Equipment progresses from Preparing to Ready and the engine actually operates.
* Pickup contact interaction, signing, retry, and cargo preparation work.
* Each crate lifts, seats, confirms once, and can recover when loose.
* The forklift returns correctly and all straps can be secured.
* Another player sees cargo, straps, and equipment consistently.
* Delivery removes only current-stop cargo after the required strap actions.
* Multi-stop completion, backhaul acceptance, cancellation, and cleanup behave correctly.
* Return Rig handles both vehicles and a retry after one vehicle has already returned.
* Service/rebuild and persisted trailer condition work with the chosen models.
* DOT consent, decline, walk-around, and reporting work with two real players.
* Intended permitted and denied users receive the correct access.
* Framework payments, optional keys, reconnects, and character changes work on the selected integration.
* Existing progress survives a planned restart.

{% hint style="info" %}
These checks are a test plan, not a record that this documentation task ran them.
{% endhint %}

## Offline development checks

Development copies may include Lua and JavaScript regression tools plus `tools/validate.ps1`. These are development tools, not commands or files required in the clean runtime package. Use tools from a source checkout matching the release you are testing. The validation runner accepts a Lua executable and optional browser checks.

Example from the source repository in PowerShell, after installing/providing Lua 5.4 and Node.js:

```powershell
.\tools\validate.ps1 -LuaPath 'C:\path\to\lua.exe'
```

Use a real executable path. Offline/mocked checks do not replace real FiveM physics, framework, multiplayer, or performance testing.

## Assets and attribution

Keep the bundled cargo YDR/YTD/YTYP files and original cargo notices together. The manifest mounts the cargo archetypes.

The locally served Barlow fonts include their attribution and SIL Open Font License in `web/fonts/SOURCES.md` and `web/fonts/OFL.txt`. Retain those notices with distributions.

Vehicle models are separate assets; follow the terms supplied with each vehicle package.

## Keeping documentation current

Use `fxmanifest.lua` for the resource version and the active `config/` files for current values. Older README release notes and comments may describe earlier deployment profiles.

When changing a default, update the relevant configuration table, player instructions, and troubleshooting entry together. Review the 20/30/40-foot layouts independently when changing cargo quantities or deck placement.

This documentation snapshot was checked against the 1.33.2 beta runtime and release configuration on October 7, 2026. It does not certify an untested release package or guarantee a fixed resource-time figure.