The server's license key belongs to a different Cfx.re account from the one that bought the pack. Generate a server key on the purchasing account, put it in sv_licenseKey and restart. Download the pack again from that same account.

The folder is not inside resources/, or its name doesn't match the ensure line. Also check that extracting didn't leave a folder inside a folder of the same name (qs_wooden_shell_pack/qs_wooden_shell_pack/): fxmanifest.lua must sit directly inside the folder you ensure.

The server could not verify the protected files. Either a file was changed or only part of the folder was copied, or the server artifacts are too old. Download the pack again, replace the whole folder without editing any file, and update FXServer if your build is old.

The creator checks every model in Config.Shells before showing it, and this one doesn't exist in your game. Either the name is misspelled in Config.Shells, the pack isn't started, or it was started while you were already connected. Check the spelling against the Map Guide, make sure ensure qs_wooden_shell_pack is in server.cfg, then restart and reconnect.

The five entries are not in the Config.Shells of the qs-housing that is running, or qs-housing wasn't restarted after the edit. Once they are there, they are the last five in the list, so step back from the first shell to reach them.

The exit point was aimed outside the shell, for example through a window or at the outer wall. Aim at the floor just inside the front door and confirm again.

The house was saved without an exit. qs-housing opens the exit selector straight away: aim at the floor just inside the front door and confirm. The exit is saved for every later visit.

Config.Shells was reordered, or a line was inserted in the middle. qs-housing remembers each house's shell by its position in the list, so the houses now point at other shells. Put the list back in its original order and add the Wood Living lines at the end. Houses created while the order was different may need their shell chosen again.

The model never loaded on that player's game. Usually the pack isn't started, the model name in the housing script is misspelled, or the pack was started after the player joined.

• Check the server console for Started resource qs_wooden_shell_pack.

• Compare the model name in your housing script with the Map Guide, character by character.

• Reconnect after starting the pack for the first time.

The shell loaded, but the housing script puts the player in the wrong spot, because its door offset for that shell is wrong. Use the door offsets exactly as listed. The usual mistakes are dropping the minus sign on Z, which lifts the player above the floor, and giving qs_wooden_shell_03 a heading near 0 instead of 179.42, which turns the player to face the door.

This is normal. The pack is about 17.7 MB, and the first time a player's game needs a shell it may still be loading the model. After that it comes from the player's cache.

The housing script spawns its shells too close together. Keep spawn points at least 25 m apart, since the largest shell, qs_wooden_shell_01, is 22.3 m deep.

The server's license key belongs to a different Cfx.re account from the one that bought the pack. Generate a server key on the purchasing account, put it in sv_licenseKey and restart. Download the pack again from that same account.

The folder is not inside resources/, or its name doesn't match the ensure line. Also check that extracting didn't leave a folder inside a folder of the same name (qs_wooden_shell_pack/qs_wooden_shell_pack/): fxmanifest.lua must sit directly inside the folder you ensure.

The server could not verify the protected files. Either a file was changed or only part of the folder was copied, or the server artifacts are too old. Download the pack again, replace the whole folder without editing any file, and update FXServer if your build is old.

The creator checks every model in Config.Shells before showing it, and this one doesn't exist in your game. Either the name is misspelled in Config.Shells, the pack isn't started, or it was started while you were already connected. Check the spelling against the Map Guide, make sure ensure qs_wooden_shell_pack is in server.cfg, then restart and reconnect.

The five entries are not in the Config.Shells of the qs-housing that is running, or qs-housing wasn't restarted after the edit. Once they are there, they are the last five in the list, so step back from the first shell to reach them.

The exit point was aimed outside the shell, for example through a window or at the outer wall. Aim at the floor just inside the front door and confirm again.

The house was saved without an exit. qs-housing opens the exit selector straight away: aim at the floor just inside the front door and confirm. The exit is saved for every later visit.

Config.Shells was reordered, or a line was inserted in the middle. qs-housing remembers each house's shell by its position in the list, so the houses now point at other shells. Put the list back in its original order and add the Wood Living lines at the end. Houses created while the order was different may need their shell chosen again.

The model never loaded on that player's game. Usually the pack isn't started, the model name in the housing script is misspelled, or the pack was started after the player joined.

• Check the server console for Started resource qs_wooden_shell_pack.

• Compare the model name in your housing script with the Map Guide, character by character.

• Reconnect after starting the pack for the first time.

The shell loaded, but the housing script puts the player in the wrong spot, because its door offset for that shell is wrong. Use the door offsets exactly as listed. The usual mistakes are dropping the minus sign on Z, which lifts the player above the floor, and giving qs_wooden_shell_03 a heading near 0 instead of 179.42, which turns the player to face the door.

This is normal. The pack is about 17.7 MB, and the first time a player's game needs a shell it may still be loading the model. After that it comes from the player's cache.

The housing script spawns its shells too close together. Keep spawn points at least 25 m apart, since the largest shell, qs_wooden_shell_01, is 22.3 m deep.