Troubleshoot Banner Apartments
Check resource startup, room assignment, door access, saved outfits, and persistent storage.
On this page
The resource fails to start
- Confirm the folder is XSC_BannerHotel and contains fxmanifest.lua directly inside it.
- Use the complete processed Cfx download, including its .fxap and protected files, with the entitled server account.
- Check that the framework, QBX compatibility bridge when used, all five ox dependencies, the Riot map, and selected appearance provider are started.
- Check the first server-console error for a missing dependency or database problem. The oxmysql connection must target the intended database and permit the required tables.
- Confirm you did not start two copies of the hotel resource.
A character has no room
- Run /room after the character finishes loading.
- Check Assignment.Enabled and AssignOnPlayerLoaded, then confirm the framework emits the expected QB lifecycle events.
- Check the room import message and confirm enabled room records exist with captured door, stash, and wardrobe data.
- Check occupancy in /banner_admin. Rooms held by temporarily disconnected players remain reserved during the configured grace window.
- Use staff diagnostics to inspect the lease rather than deleting room or stash records to force reassignment.
Existing database room records prevent the default automatic import from replacing them. A missing lobby finder interaction is also expected until RoomFinderZones is configured; players can use /room instead.
Doors are missing or access is incorrect
Check that ox_doorlock started before the hotel. With stock ox_doorlock, have an online administrator with the configured Banner command access and command.doorlock permission run /banner_syncdoors in game. A compatible createDoorlock server export is optional; the in-game editor fallback handles installations without it.
Inspect the door sync result and use /banner_doordebug when needed. Confirm the installed map matches the supplied room coordinates, and test access using the character assigned to that room.
The wardrobe does not open
- For Unknown wardrobe provider, check that Clothing.Provider matches an entry in Clothing.Providers.
- For Wardrobe resource ... is not started, start the selected provider and verify its configured resource name.
- For illenium, verify its QB saved-outfit compatibility event is available and that another clothing system is not handling the same event.
- Use the assigned character near the room's wardrobe interaction. Check captured wardrobe coordinates if the target is absent.
- Manage saved outfits through your appearance resource; legacy Banner clothing price and category fields do not configure that menu.
Storage or reconnect behavior looks wrong
A new temporary room can still use the same character's personal stash. With default cleanup settings, releasing a lease preserves items. If existing items appear missing after a configuration change, check whether the stash prefix, character identifier, or ps-housing bridge setting changed before altering database records.
Check ox_inventory startup and errors, the configured capacity, optional supporter bonuses, and the room's stash coordinates. For reconnect behavior, review StaleLeaseMinutes and the release-on-unload/drop settings; an expired room lease may be reassigned even though the character's storage persists.
Get help with your installation
Include the resource version, framework and dependency versions, selected wardrobe provider, the relevant console error, and steps to reproduce the problem. For room or door issues, include the affected room code and diagnostic output with private player details removed. Do not share database credentials, license keys, or protected source files.