Documentation
Fixes for the most common Quasar Motorhome problems: the server closing on start, the door prompt missing, no exit inside, stashes not opening, decoration locked and players stuck in a bucket.
What goes wrong most often, what it actually means, and what to do about it. For anything not listed, set Config.Debug = true for a while: every step is printed to the server and F8 consoles.
The console prints The console will close because qs-motorhome changed its name! first. The resource folder was renamed. Rename it back to exactly qs-motorhome.
The SQL was not imported, or the wrong file was. Import [sql]/esx.sql on ESX (it alters users) or [sql]/qb.sql on QBCore (it alters players).
The framework was not detected — it starts after qs-motorhome, or it is renamed. Move it above in server.cfg. On Qbox, add ['qbx_core'] = 'qb' to the frameworks table in config/main.lua.
The shell model is not streamed. Make sure K4MB1-Motorhomes and K4MB1-StarterShells are started, and that every model in Config.Shells is a shell your server actually streams.
The Motorhome [props] resource is not installed or not started. It is a separate download in the CFX Portal.
Either the vehicle's model is not in Config.Vehicles, or its doorOffset points somewhere else — the prompt only shows within 1.5 metres of that point. Turn on Config.Debug and use /motorhome:offsets to see where the door is. With Config.UseTarget on, look for the option on the vehicle itself.
The plate is not registered to that player in owned_vehicles or player_vehicles. Vehicles spawned with an admin menu have no owner. Buy or register the vehicle, or have the owner use /vanGivekey.
Correct behaviour. Shared keys are kept in memory and cleared when the resource or the server restarts. Give the key again.
That tier has no exit point yet. Aim at a spot inside the interior and press Enter; it is saved to shell_offsets.json for everyone and the next entry works normally. A point outside the interior is refused. Only tier 1 ships with an exit, so do this once per tier after installing.
The server could not write shell_offsets.json. Check that the file is not read-only and that the server user can write inside the resource folder.
They were left in a motorhome's routing bucket — usually after a crash or a restart while inside. /rt puts them back in bucket 0.
The visitor walked away from the door. [G] Open door only lets them in while they are within 2 metres of where they rang.
No supported inventory was detected, so there is no stash to open. Start your inventory before qs-motorhome, or map it in the inventories table. If the stash asks for a code, someone set a vault code on it.
The motorhome already holds ten codes. Remove one from a stash you no longer need to lock.
Your clothing script was not detected and the default wardrobe is being used. Start it earlier, or add it to the wardrobes table.
Another player inside already has the editor open. It frees itself when they close it or disconnect.
Correct behaviour. Stop the cleaning robot and wait for it to reach its dock first.
Add setr game_enableDynamicDoorCreation "true" to server.cfg, keep Config.DynamicDoors = true, and restart the server.
A furniture item points at an object your server does not stream. Fix the object name in config/furniture.lua or the furniture creator, or start the resource that streams it.
The free camera looks like noclip. On FiveGuard, set Config.FiveGuard to its resource name. For other anticheats, whitelist freecam for qs-motorhome.
Put your token in config/fivemanage.lua and restart, and make sure screenshot-basic is running. Or paste image URLs instead of photographing.
Correct behaviour. Furniture from config/furniture.lua is removed by deleting it from the file; the creator only deletes what it created.
Stand within 1.5 metres of the motorhome's door. If the player sees a police message, fewer than Config.ReqPoliceCount officers are online (on QBCore, on duty) — set it to 0 to allow break-ins at any time. If the item is not usable at all, it does not exist in your inventory under the name in Config.LockpickingItem.
Correct behaviour. They are removed when the motorhome is more than 30 metres away, and they are not saved across sessions. Placement is also cancelled if you walk more than Config.MaxSpawnDistance (15 m) away while placing.
Still stuck? Open a ticket and include your framework and inventory, your
server.cfgload order, and the server and F8 console output withConfig.Debug = true.
