Documentation
Find solutions to common issues and errors that may occur during installation, configuration, or while using the script.
[INFO] Successfully loaded the framework. none
attempt to index a nil value (global 'sfr')Cause: Config.Framework resolved to 'none'. Your core resource is not started before qs-motels-creator, or it was renamed.
Solution: fix the loading order in your server.cfg, or add your resource name to the frameworks table in config/main.lua.
Cause: the shells resource is not started.
Solution: it ships with the download — make sure it starts before the main resource:
ensure K4MB1-StarterShells
ensure qs-motels-creatorCause: bob74_ipl is missing, started too late, or the export function in Config.IplData points at a getter your bob74_ipl version does not have.
Solution: start bob74_ipl before the resource, and check the export name against your installed version.
Cause: the shell model is not streamed.
Solution: confirm K4MB1-StarterShells is running and that the model name in Config.Shells matches a .ydr inside K4MB1-StarterShells/stream/.
Cause: the item is not registered correctly, or the player is not close enough to a point.
Solution:
Register the item in your inventory — see the installation guide.
On ox_inventory the item must declare client = { export = 'qs-motels-creator.motels:UseKey' }; on every other inventory it must be useable.
The key resolves the nearest point, so the player must be close to a door, stash or wardrobe.
Config.MetaKeys = false disables the whole key-item flow.
Cause: the key metadata no longer matches the rental.
Solution: this is expected in three cases — the room was re-rented, a new key was created (which rotates unique_key), or the rental is suspended for unpaid debt. Pay the debt or issue a new key.
Cause: standalone and non-metadata inventories cannot carry info / metadata.
Solution: use a metadata-capable inventory, or set Config.MetaKeys = false.
Cause: Config.personalStashes is explicitly unsupported on standalone.
Solution: it requires an inventory whose stash API accepts an owner — currently ox_inventory and origen_inventory.
Cause: the wipe is disabled, or no adapter exists for your inventory.
Solution: check Config.wipeStashOnLeave = true and that an adapter exists in server/custom/inventory/adapters/. With Config.Debug enabled the console prints:
MotelStashWipe No adapter for inventory: <name>Unknown column 'current_motel_room'
Table 'qs_motels' doesn't existCause: the SQL file was not imported, or you imported the wrong one for your framework.
Solution: re-run the correct file from the [sql] folder — esx.sql or qb.sql.
Cause: you are referencing a motel id that no longer exists. Every qs_motel_* table cascades on qs_motels.
Solution: never delete rows from qs_motels manually while the server is running — delete the motel through the creator instead.
Cause: the permission check failed.
Solution: add your job to Config.CreatorJobs, or make sure your admin group is listed in Config.adminSettings.permissions and that your framework's playerIsAdmin bridge reports you correctly.
Cause: a validation failure after payment, almost always on a customised bridge.
Solution: enable Config.Debug = true — the rent paths log the exact reason (room_taken, max_rooms, has_unpaid_bills, duration_invalid, upgrade_required).
Cause: Config.existBillThenBlock = true.
Solution: pay at the bill center (Config.bill.pos), or set the option to false.
Cause: the motel has an owner and Config.Upgrades.roomCapacity is enabled. Rentable rooms are ceil(total * levels[level] / 100).
Solution: buy the upgrade, raise the level values, or disable Config.Upgrades.enabled.
Cause: a player may hold only one rental per motel.
Solution: this is expected behaviour. Across all motels the limit is Config.maxRoomsPerPlayer (5 by default).
Cause: the employee system is disabled, or the motel balance is short.
Solution: Config.employee.active must be true and autoSalary must not be false. With Config.storage.takeSalary = true and obligatorySalary = false, payment is skipped entirely when the balance is insufficient.
Locale <x> does not exist, falling back to default (en)
Locale <x> is missing key '<key>'Cause: Config.Locale does not match a file in locales/, or your locale file is outdated after an update.
Solution: available locales are ar bg ca cs da de en es fa fr he hi hu it ja ko nl no pl pt ru sv tr zh. For a missing key, copy it from locales/en.json — the resource falls back to English, so it is a warning, not a failure.
Cause: the resource is escrow-protected.
Solution: only these paths are editable — anything else is encrypted and your edits will not load:
config/*.lua
custom/**/*
client/custom/main.lua
server/custom/**Config.Debug = true is the shipped default.#Solution: set both Config.Debug and Config.ZoneDebug to false on a live server.