Your character does not pass the admin check of the detected framework — ESX admin/superadmin, QBCore god/admin or the command ace. Check the console line Successfully loaded the framework. — if it says standalone on an ESX or QBCore server, your framework starts after Shell Creator. See Claiming Admin Access.

• Confirm OneSync is enabled, and that ox_lib and qs-shellcreator-props start before qs-shellcreator — all three are hard dependencies.

• An oxmysql error about qs_shells means the table was never imported. Run the SQL from Installation.

Invisible pieces mean qs-shellcreator-props is not started, or was renamed. Empty item cards mean the qs-shellcreator folder was renamed: the interface loads its pictures from nui://qs-shellcreator/web/images/.

"Failed to upload image. Please check your fivemanage token." or "FiveManage token not set" — paste a valid FiveManage token in server/webhooks.lua and restart. The shell itself is saved either way; edit and save it again later to give it a photo.

screenshot-basic is not running. Every save takes a photo, so it must be started before Shell Creator.

A shell cannot be saved or previewed without a spawn point. Construction → Spawnpoint, then click on a foundation.

The build holds Config.MaxObjects props. Remove decorations or tiles, or split the interior into two shells. Raise the limit only if players do not crash in large shells — the limit exists because of GTA's object pool.

"You must have foundations on the current floor before going up!" — lay at least one foundation on the floor you are on first.

• "Upper floor required!" — build the foundations of the floor above first, then come back down.

• "Insufficient space for stairs! (2 grids required)" or "No floor found in back and center grid" — the stairs use the tile you click and the one behind it; both must be foundations. Move the cursor to turn them the other way.

• "The same stairs model already exists in this grid!" — pick another model to swap it, or another colour to repaint it.

Roofs belong to the floor you are on, so it needs foundations. Roofs are never placed over stairs or under a tile of the floor above — that is by design.

• "A foundation wall already exists in this direction!" — that edge is an outer wall already. Interior pieces only go between two tiles or on an open edge.

• "An object has already been placed in this direction!" — delete the piece on that edge first.

• "You must create a floor first…" — there is no foundation under the cursor.

A wall cannot hold a door and a window, on either face. Remove the existing one in Destroy mode first. Adding a second door on the same tile removes the first — there is one door per tile.

• "No floor found for decoration!" — point at a foundation.

• "This edge already has a fixed position furniture!" / "This cell center already has a centered furniture!" — wall-snapped and centred pieces take one slot each; use the next edge or tile.

• "The same decoration object already exists at this position!" — the same prop is already there.

• "Decoration object could not be created! Model: …" — that model does not exist on your server; check the name in Config.Objects.furniture and that its resource is streamed.

Saving from the builder always stores the void as on. Open the shell in the manager, untick Has Void and press the manager's Save.

Stairs are not part of the undo history. Remove them with Destroy instead.

• Check the model name in your housing config matches the shell id: qs_shells_<id>.

• qs-shellcreator must be started on the server — the model only exists while it runs. Start it before the housing script.

• The interior builds once the player is within 100 m of the spawned object; a teleport straight inside is caught and the player is held in place until it is ready.

The entrance in your housing config is out of date. Copy the export code again from the manager after any change to the spawn point, and make sure you used a Shell format for a script that spawns the shell itself, and an IPL format only for fixed interiors.

Too many objects for GTA's pool. Lower Config.MaxObjects so new builds stay smaller, and slim down the heaviest shells — decorations and many small tiles add up fastest.

The shell was stored without a spawn point. Edit it, place one, and save.

Your character does not pass the admin check of the detected framework — ESX admin/superadmin, QBCore god/admin or the command ace. Check the console line Successfully loaded the framework. — if it says standalone on an ESX or QBCore server, your framework starts after Shell Creator. See Claiming Admin Access.

• Confirm OneSync is enabled, and that ox_lib and qs-shellcreator-props start before qs-shellcreator — all three are hard dependencies.

• An oxmysql error about qs_shells means the table was never imported. Run the SQL from Installation.

Invisible pieces mean qs-shellcreator-props is not started, or was renamed. Empty item cards mean the qs-shellcreator folder was renamed: the interface loads its pictures from nui://qs-shellcreator/web/images/.

"Failed to upload image. Please check your fivemanage token." or "FiveManage token not set" — paste a valid FiveManage token in server/webhooks.lua and restart. The shell itself is saved either way; edit and save it again later to give it a photo.

screenshot-basic is not running. Every save takes a photo, so it must be started before Shell Creator.

A shell cannot be saved or previewed without a spawn point. Construction → Spawnpoint, then click on a foundation.

The build holds Config.MaxObjects props. Remove decorations or tiles, or split the interior into two shells. Raise the limit only if players do not crash in large shells — the limit exists because of GTA's object pool.

"You must have foundations on the current floor before going up!" — lay at least one foundation on the floor you are on first.

• "Upper floor required!" — build the foundations of the floor above first, then come back down.

• "Insufficient space for stairs! (2 grids required)" or "No floor found in back and center grid" — the stairs use the tile you click and the one behind it; both must be foundations. Move the cursor to turn them the other way.

• "The same stairs model already exists in this grid!" — pick another model to swap it, or another colour to repaint it.

Roofs belong to the floor you are on, so it needs foundations. Roofs are never placed over stairs or under a tile of the floor above — that is by design.

• "A foundation wall already exists in this direction!" — that edge is an outer wall already. Interior pieces only go between two tiles or on an open edge.

• "An object has already been placed in this direction!" — delete the piece on that edge first.

• "You must create a floor first…" — there is no foundation under the cursor.

A wall cannot hold a door and a window, on either face. Remove the existing one in Destroy mode first. Adding a second door on the same tile removes the first — there is one door per tile.

• "No floor found for decoration!" — point at a foundation.

• "This edge already has a fixed position furniture!" / "This cell center already has a centered furniture!" — wall-snapped and centred pieces take one slot each; use the next edge or tile.

• "The same decoration object already exists at this position!" — the same prop is already there.

• "Decoration object could not be created! Model: …" — that model does not exist on your server; check the name in Config.Objects.furniture and that its resource is streamed.

Saving from the builder always stores the void as on. Open the shell in the manager, untick Has Void and press the manager's Save.

Stairs are not part of the undo history. Remove them with Destroy instead.

• Check the model name in your housing config matches the shell id: qs_shells_<id>.

• qs-shellcreator must be started on the server — the model only exists while it runs. Start it before the housing script.

• The interior builds once the player is within 100 m of the spawned object; a teleport straight inside is caught and the player is held in place until it is ready.

The entrance in your housing config is out of date. Copy the export code again from the manager after any change to the spawn point, and make sure you used a Shell format for a script that spawns the shell itself, and an IPL format only for fixed interiors.

Too many objects for GTA's pool. Lower Config.MaxObjects so new builds stay smaller, and slim down the heaviest shells — decorations and many small tiles add up fastest.

The shell was stored without a spawn point. Edit it, place one, and save.