How to Add a Custom Shell to esx_property (ESX)
To add a custom shell to esx_property on ESX Legacy, start the shell resource before the housing script, paste the generated entry inside Config.Interiors.Shells of esx_property/config.lua, set Config.Shells = true, and restart. The entry comes from a shell exported by the FiveMRides Shell Studio.
- Resource: unzip the shell into
resourcesand addensure my_shelltoserver.cfgbeforeesx_property. - Config: paste
configs/esx_property_shell.luainsideConfig.Interiors.Shells = { ... }ofesx_property/config.lua, and setConfig.Shells = true. - Storage: the Storage point needs ox_inventory, as esx_property itself does.
- Tested in game: ESX Legacy 1.16.4 with esx_property on FiveM Legacy: arrival on the floor, interior doors, Wardrobe and Storage prompts at our spots, exit back at the door.
How do I add a custom shell to esx_property?
- Unzip the shell. Unzip the ZIP from the Shell Studio so you have one folder with an
fxmanifest.lua, astreamfolder and aconfigsfolder. - Copy it to resources. Copy the folder into your server
resourcesfolder and keep its name. - Start it first. Add
ensurefollowed by the folder name toserver.cfg, on a line beforeesx_property. - Turn shells on. In
esx_property/config.luasetConfig.Shells = true. - Paste the entry. Copy the entry from
configs/esx_property_shell.luaand paste it insideConfig.Interiors.Shells. - Restart and test. Restart the server, create a property with the new interior, enter it and check the Wardrobe and Storage prompts.
What does the generated entry look like?
The numbers are an example, yours are calculated from the entrance, the exit, the wardrobe and the stash points you set in the editor:
{
label = "Modern flat",
value = "my_shell",
positions = {
Wardrobe = vector3(2.1, -1.4, -1.2),
Storage = vector3(-1.8, 0.6, -1.0),
},
type = "shell",
pos = vector3(0.0, 4.5, 0.0)
},
- esx_property has one anchor point per property. The player arrives at the anchor and the leave menu is drawn within a few metres of it. The shell is created so that the floor under the anchor lands exactly where the script expects it, and
poscarries the difference. - The anchor is the exit spot of your project when it has one, otherwise the entrance spot. Set an exit in the Markers tab so the door of the shell is the leave point.
- Wardrobe and Storage are positions relative to that anchor. The script draws them on the floor.
How do I test it?
Before you create any property, type /shelltest my_shell with the resource started. The shell appears under you and you stand at the entrance. Type it again to leave. /shellclock 23 sets your own clock to night to check the lights.
Frequently asked questions
Why must the shell start before esx_property?
The housing script asks for the shell model when a player enters a property. If the shell resource is not running yet, the model cannot load. Put the shell ensure line above the housing script and restart.
The Storage prompt does not open anything.
The Storage of esx_property works with ox_inventory only. Check that ox_inventory is installed and started, then test with a new property.
Do I need a heading for the arrival?
No. esx_property sets no arrival heading, so the player faces the way the game decides. Place your entrance so that both directions look fine.
I changed the offsets but my property did not move.
The positions are copied into each property when it is created. Create a new property after you change the config.
What if the esx_property resource changes later?
The entry was checked and tested against the esx_property of ESX Legacy as of November 2026. The ESX team may rewrite the resource later, so check the header of the generated file, which names the version it was checked against.
Does it work on GTA V Enhanced?
Not yet. The shells are built for FiveM on GTA V Legacy.