Your framework starts after Apartments, or is not named es_extended, qb-core or qbx_core. Move its ensure line above ensure qs-apartments and restart the server.

A Qbox property resource is running beside Apartments. Remove it — and qbx_properties or qbx_apartments if you have them. See Migrating and Updating.

The whole database.sql was imported on a server that already had player_apartments — its first line drops that table. Restore the table from a backup, then run only the update block in Migrating and Updating.

Despite the name, this comes from Apartments' language loader. The file for Config.Locale is missing, or lacks the key named. That text shows in English until you add the key to locales/<code>.json.

Config.Debug ships set to true. Set it to false in config/main.lua once the server is set up.

Restarting qs-apartments takes the interior away from anyone inside it. Restart with nobody home. A player caught by it reconnects and is put back in their apartment.

Correct behaviour for a player with no apartment. The blips appear once they own one — at spawn, with /Apartment, or at a door.

Without a target, walk right up to the door: the prompt only appears very close to the building's coords.enter. With Config.UseTarget = true, the target must start before Apartments, and Config.ZoneDebug = true draws the boxes so you can see where they are.

Their apartment belongs to another building — or, after a migration, to a building key the catalogue does not have. Check the type of their row in player_apartments against Config.ApartmentCatalog.

That building's tier has no exit door in shell_offsets.json — a new tier, or a file replaced during an update. Place it once and it is saved for everyone: Usage → Placing an exit door.

The building's tier is not a number in Config.Shells. Add that tier, or point the building at one that exists.

The shell model is not streamed. Make sure K4MB1-StarterShells — or your own shell pack — is started, and that the model name in Config.Shells is spelled exactly as the pack streams it.

The visitor walked more than 5 metres from the entrance before the resident opened. Ring again and wait at the door.

Correct behaviour for a new apartment: the owner places them with /ApartmentLocation. Moving to another building resets them too.

No supported inventory was found when Apartments started — check that it is on the list in Integrations and starts first, or set Config.Inventory by hand. With qb-inventory and no Quasar Housing on the server, change the qb-inventory bridge as shown there.

No supported clothing script was found, or yours renamed its outfit menu in an update. Set Config.Wardrobe by hand, or adjust openWardrobe() in client/custom/wardrobe/. On ESX, install one of the supported clothing scripts.

Press G at that stash and choose Remove Code, then set a new one. An admin can also clear the vaultCodes column of that apartment in player_apartments.

An apartment holds 10 codes across all its stashes. Remove one, or add Config.MaxVaultCodes = 20 to config/main.lua.

Your phone does not handle phone:CreateChargeLocation. See Integrations → Phone Charger.

The wording is shared with another Quasar script: it means you are not inside an apartment. The decoration menu only opens indoors.

Another player in the apartment has the menu open — one at a time. It frees itself when they close it or disconnect.

A robot is out cleaning. Stop it at its dock, or wait — it returns after five minutes at most.

You clicked a placed piece while on the Dynamic or Objects tab. Pieces you already own are picked and moved from the Stash tab.

A piece you already own keeps its new position only after Save Location in Furniture Management.

The model does not exist in the game — usually an addon prop that is not streamed. Stream it, or remove that piece from config/furniture.lua.

Doors swing only with Config.DynamicDoors = true and setr game_enableDynamicDoorCreation "true" in server.cfg, after a full server restart.

Furniture is bought from the decoration menu inside the apartment. FurnitureShops and IllegalFurnitures in config/furniture.lua are not read by Apartments.

Your framework does not see that player as an admin: ESX group admin or superadmin; QBCore god or admin, or the command ace. Lines added to server.cfg apply after a restart. See Admin Access.

The photo booth has nowhere to upload. Paste your token into config/fivemanage.lua and restart — or type an image URL instead of using the camera button.

Your client does not know that model. Check the spelling, and that the addon streaming it is started.

Each model can be in a category once. Edit the existing piece, or add a colour variant to it.

Pieces that ship in config/furniture.lua are removed in that file. The creator deletes only what was created with it.

Config.Cleaning is off, the apartment already holds Config.MaxJunkPerHouse pieces, or nobody has stayed inside for Config.JunkObjectTime — the clock starts again whenever the apartment empties.

Only the apartment's owner sweeps junk by hand. The cleaning robot works for anyone who starts it.

Another player started it. It goes back to its dock when they stop it, leave or disconnect, or after five minutes.

Place the dock on open floor, away from furniture legs and doorways. maxDistanceFromDock in Config.CleanerRobot keeps it close to home; lower it for a small interior.

Your framework starts after Apartments, or is not named es_extended, qb-core or qbx_core. Move its ensure line above ensure qs-apartments and restart the server.

A Qbox property resource is running beside Apartments. Remove it — and qbx_properties or qbx_apartments if you have them. See Migrating and Updating.

The whole database.sql was imported on a server that already had player_apartments — its first line drops that table. Restore the table from a backup, then run only the update block in Migrating and Updating.

Despite the name, this comes from Apartments' language loader. The file for Config.Locale is missing, or lacks the key named. That text shows in English until you add the key to locales/<code>.json.

Config.Debug ships set to true. Set it to false in config/main.lua once the server is set up.

Restarting qs-apartments takes the interior away from anyone inside it. Restart with nobody home. A player caught by it reconnects and is put back in their apartment.

Correct behaviour for a player with no apartment. The blips appear once they own one — at spawn, with /Apartment, or at a door.

Without a target, walk right up to the door: the prompt only appears very close to the building's coords.enter. With Config.UseTarget = true, the target must start before Apartments, and Config.ZoneDebug = true draws the boxes so you can see where they are.

Their apartment belongs to another building — or, after a migration, to a building key the catalogue does not have. Check the type of their row in player_apartments against Config.ApartmentCatalog.

That building's tier has no exit door in shell_offsets.json — a new tier, or a file replaced during an update. Place it once and it is saved for everyone: Usage → Placing an exit door.

The building's tier is not a number in Config.Shells. Add that tier, or point the building at one that exists.

The shell model is not streamed. Make sure K4MB1-StarterShells — or your own shell pack — is started, and that the model name in Config.Shells is spelled exactly as the pack streams it.

The visitor walked more than 5 metres from the entrance before the resident opened. Ring again and wait at the door.

Correct behaviour for a new apartment: the owner places them with /ApartmentLocation. Moving to another building resets them too.

No supported inventory was found when Apartments started — check that it is on the list in Integrations and starts first, or set Config.Inventory by hand. With qb-inventory and no Quasar Housing on the server, change the qb-inventory bridge as shown there.

No supported clothing script was found, or yours renamed its outfit menu in an update. Set Config.Wardrobe by hand, or adjust openWardrobe() in client/custom/wardrobe/. On ESX, install one of the supported clothing scripts.

Press G at that stash and choose Remove Code, then set a new one. An admin can also clear the vaultCodes column of that apartment in player_apartments.

An apartment holds 10 codes across all its stashes. Remove one, or add Config.MaxVaultCodes = 20 to config/main.lua.

Your phone does not handle phone:CreateChargeLocation. See Integrations → Phone Charger.

The wording is shared with another Quasar script: it means you are not inside an apartment. The decoration menu only opens indoors.

Another player in the apartment has the menu open — one at a time. It frees itself when they close it or disconnect.

A robot is out cleaning. Stop it at its dock, or wait — it returns after five minutes at most.

You clicked a placed piece while on the Dynamic or Objects tab. Pieces you already own are picked and moved from the Stash tab.

A piece you already own keeps its new position only after Save Location in Furniture Management.

The model does not exist in the game — usually an addon prop that is not streamed. Stream it, or remove that piece from config/furniture.lua.

Doors swing only with Config.DynamicDoors = true and setr game_enableDynamicDoorCreation "true" in server.cfg, after a full server restart.

Furniture is bought from the decoration menu inside the apartment. FurnitureShops and IllegalFurnitures in config/furniture.lua are not read by Apartments.

Your framework does not see that player as an admin: ESX group admin or superadmin; QBCore god or admin, or the command ace. Lines added to server.cfg apply after a restart. See Admin Access.

The photo booth has nowhere to upload. Paste your token into config/fivemanage.lua and restart — or type an image URL instead of using the camera button.

Your client does not know that model. Check the spelling, and that the addon streaming it is started.

Each model can be in a category once. Edit the existing piece, or add a colour variant to it.

Pieces that ship in config/furniture.lua are removed in that file. The creator deletes only what was created with it.

Config.Cleaning is off, the apartment already holds Config.MaxJunkPerHouse pieces, or nobody has stayed inside for Config.JunkObjectTime — the clock starts again whenever the apartment empties.

Only the apartment's owner sweeps junk by hand. The cleaning robot works for anyone who starts it.

Another player started it. It goes back to its dock when they stop it, leave or disconnect, or after five minutes.

Place the dock on open floor, away from furniture legs and doorways. maxDistanceFromDock in Config.CleanerRobot keeps it close to home; lower it for a small interior.