> 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/troubleshooting.md). # Troubleshooting ## Dispatch does not open Check server startup errors, the actual resource name, and whether the character is loaded. Verify `Config.Access.trucking` and the yard position in the installed config. The current mobile key is F3. Older notes referring to F7 do not match this configuration. Try `/hotshot` while parked in the driver's seat of an approved truck, or use the physical yard. ## Access denied after updating The release requires `hotshot.trucking` for trucking and `hotshot.dot` for inspections under its default `discordace` policy. Check actual ACE grants and your DiscordAcePerms role mappings if used. Old `ace`/`either`/`both` mode names and `Config.Integrations.access` are unsupported; follow the migration in [Frameworks and access](/baobab-interactive-docs/hotshot-trucking-simulator/frameworks-and-access.md). ## First-job guide is missing Open normal dispatch and use **First-job guide** or **Replay guide**. A previously hidden/completed guide, prior completed deliveries, or `autoStart = false` can prevent automatic display. `Config.Tutorial.enabled = false` disables the guide entirely. Preferences are shared across characters on the same client; changing characters does not clear them. If controls or the overlay are missing after an update, check that the complete runtime and web files were installed together, then restart during maintenance. The guide cannot bypass denied access or a return-only dispatch view. ## Loaded QB/ESX character is not recognized Check the selected framework and startup order. Version 1.33.2 includes the 1.33.1 player-lookup compatibility fix; update the whole resource if running an earlier affected build. Check server errors and verify that the framework reports the player as loaded. ## Wrong yard or missing equipment The reviewed yard is at `1002.0067, -2366.0708, 30.5111`. Confirm you edited the running copy, not an unused development folder. Check that your configured truck and trailer resources are installed and started. Verify exact model/resource names, startup order, truck/trailer compatibility, and player level. If all bays are blocked, clear them and retry. Avoid repeatedly spawning replacements during a pending checkout or return. ## “Bring your reserved trailer” Collect a trailer through Hot-Shot Equipment Yard. A visually identical trailer from another menu is not your registered assignment. Check that you are using the trailer selected for the contract and an approved compatible truck. ## Vehicle is Ready but the engine will not run Check the server's key/engine resource. The current `vehicleKeys = "none"` setting does not grant keys. On Qbox, configure the optional adapter if appropriate. Other key systems need an integration. Record the exact preparation/engine error and return/recollect safely after correcting the cause. ## Pickup is blocked by paperwork At an enabled shipping-contact site, arrive in the pickup circle and press E, then speak to the worker on foot and sign. Keep the assigned rig parked. Opening `/manifest` remotely does not bypass contact signing. At sites without a contact, sign normally and follow the pickup prompt. If automatic preparation fails after signing, correct the reported issue and interact with the contact again. ## Only one freight type appears At level 1, Building Materials is expected. Current unlocks are Crated Equipment at 3, Portable Generators at 5, and Pipe Bundles at 7. The 20-foot trailer supports Building Materials in this build. Pipe requires a 30/40-foot trailer. Board refresh, trailer assignment, compatibility, and equipment levels also affect available work. ## Crate will not load or has tipped Use the correct selected piece, green deck slot, and assigned forklift. Keep the crate upright and settled, then withdraw the forks fully. Wait for deck collision/confirmation. For a loose tipped piece, clear the recovery area and use the hold-R prompt. See [Cargo handling](/baobab-interactive-docs/hotshot-trucking-simulator/cargo-handling.md). ## Delivery seems stuck Stop the assigned rig in the destination marker and remove all current-stop straps. Current automatic delivery has no forklift or receiving-circle stage. If your config sets `requireUnloading = true`, follow the legacy unloading prompts instead. Route, cargo identity, stopped-rig, and job checks still apply. ## Return or service is blocked Finish/cancel the job and any other active work. Use your registered equipment at the physical yard. Returns use the shared area; service uses the configured bay rules. Exit vehicles, clear occupants and nearby vehicles, and follow the menu's specific reason. A truck can be returned separately after its trailer has already been stored. ## Inspector access is unexpected Inspect `Config.Access.dot`. The release uses `mode = "discordace"` with `permission = "hotshot.dot"`. Verify the player actually receives that ACE permission. For a job policy, check the active job, minimum grade, and duty status. If another inspection is active, complete, decline, or cancel it before starting another. Self-inspection is not supported. ## Earnings or progress appear missing Standalone earnings are records, not framework bank deposits. For PAYMENT NOT CONFIRMED, inspect balances and server logs before manual compensation. For missing progress, check the resource name, framework, selected character, and `profileScope`. Changing identity scope does not migrate previous saves. Preserve existing KVP data. ## What to include in a support report Provide version 1.33.2 beta (or your actual manifest version), framework and key resource, relevant config, truck/trailer models, job phase, reproduction steps, and matching F8/server console errors. Include whether another player sees the same issue. Remove credentials and private identifiers from shared logs. No live multiplayer acceptance or performance result is implied by this documentation.