Custom Shells for qb-houses, qbx_properties, bcs_housing and loaf_housing
A shell exported from the FiveMRides Shell Studio also comes with a config for qb-houses (through qb-interior) and qbx_properties, and with a list of values for bcs_housing and loaf_housing, plus a shell.json with every offset for any other housing script. These configs were checked against the code of the scripts that are public. They were not tested in game: only ps-housing and esx_property were.
- Tested in game: ps-housing and esx_property.
- Checked against the script code, not tested in game: qb-houses with qb-interior and qbx_properties. The header of each generated file names the repository and the commit it was checked against.
- Values only: bcs_housing and loaf_housing are paid scripts. Their shell config format is not public, so the files list the values to type in and do not pretend to be a config.
- Any other script:
shell.jsonholds the offsets.
How do I use a shell with another housing script?
- Install the shell resource. Unzip it into
resourcesand addensure my_shelltoserver.cfgbefore your housing script. - Test the shell alone. Join the server and type
/shelltest my_shellto walk through the shell before any housing script is involved. - Open the right config. Open the file in the
configsfolder that matches your script. - Paste or type the values. Follow the comments at the top of the file: where to paste it, or which values to type into your script.
- Restart and try a property. Restart the server, make a test property, enter it and leave it.
Which file goes where?
| Script | File in configs/ | Where it goes |
|---|---|---|
| qb-houses with qb-interior | qb-houses_qb-interior_export.lua | Three steps described in the file: an export at the end of qb-interior/client/optional.lua, a new tier branch in qb-houses/client/main.lua, and a stash weight for that tier in qb-houses/config.lua |
| qbx_properties | qbx_properties_interior.lua | Inside interiors = { ... } in qbx_properties/config/shared.lua |
| bcs_housing | bcs_housing_values.txt | A list of values to type into the script, follow its own documentation |
| loaf_housing | loaf_housing_values.txt | A list of values to type into the script, follow its own documentation |
| Any other script | shell.json | Copy the numbers you need |
qb-houses (with qb-interior)
qb-houses builds its interiors through qb-interior. The generated file adds an export that calls the CreateShell export of qb-interior, then a new tier (101, the first free number after the shells that ship with the script) that qb-houses uses for your shell, and a stash weight for that tier. Create the house with /createhouse <price> 101 or set the tier in your house tool. qb-houses places the shell 30 m under the house entrance. The stash, wardrobe and logout points are set in game by the owner with the house menu; the file lists the offsets from the shell origin to help you find the right spot.
qbx_properties
The entry goes in interiors and the key is the model hash. It holds the arrival point, the exit, the clothing, stash and logout spots, all measured from the shell origin, and the script puts the shell 50 m under the property door. The heading of a shell interior is ignored by the script, so orient the room with the layout in the editor. Spots are copied into each property when it is created, so a changed config does not move properties that already exist.
Offsets for any other script (shell.json)
Every spot is an offset from the centre of the shell, in metres, with a heading in degrees. z in shell.json is the floor level, so add about 1.0 for a point where the script puts a standing player. Many housing scripts use their own origin convention. If you arrive in the wrong place, change the teleport offset by the difference, and leave the shell where it is.
Frequently asked questions
Is the qb-houses config tested in game?
No. It was checked against the public code of qb-interior and qb-houses, and the header of the file names the commit. Test it with a new property on a copy of your server first, and use /shelltest to check the shell itself.
Is qbx_properties tested in game?
No. It was checked against the public code of the qbx_properties repository, and was not run in game.
Why are bcs_housing and loaf_housing only a list of values?
Both are paid scripts and their shell config format is not published, so we cannot give a verified config. The file lists the model name, the label and every offset for the entrance, exit, stash, wardrobe and logout, and you enter them in the script the way its documentation says.
Which housing scripts are supported?
There are configs for ps-housing, qb-houses (with qb-interior), qbx_properties, esx_property, bcs_housing and loaf_housing, plus shell.json for any other script. Only ps-housing and esx_property are tested in game.
I arrive in the wrong place inside the shell.
Your script uses another origin convention. Change the teleport offset by the difference. Do not move the shell model.
Do I have to start the shell before the housing script?
Yes. Put the ensure line of the shell above the housing script, then restart.