Skip to main content

​
General Questions

Yes, if you want to use the preset houses. The K4MB1-Starter-Shells are free and required for the default shell configurations. If you don’t have them, you’ll need to configure your own shells or use IPL interiors.You can also find community-created presets in our Discord Snippets channel that use different shell packs.
The script supports QBCore, QBOX, and ESX frameworks. Make sure to configure the Framework setting in config/main.lua to match your server.
While the script works best with Project-X-Burner and Project-X-Tasks (both free), you can modify the config to disable these features if you don’t want to use them. However, using these scripts provides a more complete criminal progression system.
Place the minigames in your standalone or minigames folder. Make sure they are started in your server.cfg before the House Robbery V2 resource.
Some items like x_burner and x_tablet are optional and can be disabled in the config. However, items like advancedlockpick, x_device, x_stethoscope, glass_cutter, and bag are required for the robbery mechanics. Items such as loot and props are not required if you want to fully use your own, Check the installation guide for the complete items list.
  • Enable EnableLasers in house config
  • Ensure preset has laser configuration
  • Make sure mka-lasers resource is running

​
Configuration Questions

House presets define the interior layout and lootable spots. You can create custom presets using the LoadHousePreset() function in config/presets.lua.Check our Presets Guide for detailed instructions on:
  • Creating exit coordinates
  • Adding lootable spots, props, and cash
  • Configuring safes, paintings, and displays
  • Setting up tenants and pets
  • Adding lasers and alarms
You can also find community presets in our Discord Snippets channel.
Tiers control the difficulty, rewards, and features of robberies. Configure them in config/tiers.lua.Tips for balancing:
  • Start with low spawn chances in Tier 1 (10-30%)
  • Gradually increase spawn chances in higher tiers (70-90%)
  • Give better items in higher tier loot tables
  • Increase XP rewards for higher tiers
  • Add more security features (tenants, pets, lasers) in higher tiers
  • Require better tools for higher tiers
See our Tiers Guide for complete configuration details.
Shells are custom interior props that can be placed anywhere on the map. They’re more flexible and easier to configure.IPLs are built-in GTA V interiors at fixed coordinates. They’re more detailed but limited to specific locations.Check the Houses Guide for detailed setup instructions.
Add new houses in config/houses.lua under either ["Shells"] or ["IPL"] categories.Each house needs:
  • Tier: Difficulty level (1-6)
  • DoorCoords: Entrance location with heading
  • Optional: ScoutingSpots, security features, dispatch settings
Use the Houses Guide for step-by-step instructions and examples.
Carryable props allow players to physically carry stolen items to their vehicles. Configure them in config/main.lua under Config.CarryProps.For each prop you need:
  • Item name (matching your inventory)
  • Prop model name
  • Bone ID for attachment
  • Offset and rotation values
  • Animation dictionary and name
See our Carryable Props Guide for complete instructions on adding and adjusting props.
Yes, most features can be toggled on/off:
  • Tenants/Pets: Disable in tier config or set spawn chance to 0
  • Safes/Paintings/Displays: Set Enable = false in tier config
  • Lasers/Alarms: Disable per-tier or per-house
  • Carryable Props: Set Config.CarryProps.Enable = false
  • Scouting: Disable scouting spots in house config
  • Phone/Tablet: Disable in main config
All features are modular and can be customized to fit your server’s needs.

​
Troubleshooting

Console warnings help identify configuration issues. Here’s what each warning means and how to fix it:

​
Shell Configuration Warnings

Invalid shell model: [HouseName]
  • The shell model specified in your tier configuration doesn’t exist or isn’t loaded
  • Check that the shell name in config/tiers.lua matches an actual shell resource
  • Make sure the shell resource is started

​
Tier Configuration Warnings

Invalid approach in tier [X]: ‘[approach]’
  • You specified an approach type that doesn’t exist (e.g., ‘van’ or ‘Gangster’ instead of ‘gangster’)
  • Valid approaches: door, gangster, payphone, locksmith, hacking, maid, valet
  • Check your tier configuration in config/tiers.lua for typos
  • Approach names are case-sensitive

​
Preset Configuration Warnings

House preset “[name]” already exists in Config.PresetHouseCoords[InteriorType]. Overwriting it…
  • You have duplicate preset names in your configuration
  • This can happen if you’re using multiple preset files or added the same preset twice
  • The script will use the last defined preset with that name
  • Rename one of the presets to avoid conflicts

​
Missing Resource Warnings

projectx-tasks resource was not detected, either turn off Project X Tasks config option or download it from our website
  • You have tasks integration enabled but the resource isn’t installed
  • Solution 1: Download Project X Tasks from projectx.gg
  • Solution 2: Set Config.[Project X Tasks] = false in config/config.lua
projectx-burner resource was not detected, either turn off Project X Burner config option or download it from our website
  • You have burner phone integration enabled but the resource isn’t installed
  • Solution 1: Download Project X Burner from projectx.gg
  • Solution 2: Set Config.[Project X Burner] = false in config/config.lua
bl_dialog resource was not detected, either set Config.Dialog = ‘ox’, or download it from the minigame zip in the README
  • You have bl_dialog selected but it’s not installed or started
  • Solution 1: Download bl_dialog from the minigame zip file
  • Solution 2: Set Config.Dialog = 'ox' in config/config.lua to use ox_lib dialog
pickle_xp resource was not detected, either turn off XPSystem config option or download pickle_xp
  • You have XP system integration enabled but pickle_xp isn’t installed
  • Solution 1: Download pickle_xp from github.com/PickleModifications/pickle_xp
  • Solution 2: Set Config.XPSystem = false in config/config.lua to disable XP integration

​
Conflicting Resource Warnings

Remove or delete qb-houserobbery or the script will not work properly
  • You have the old QBCore house robbery script running alongside this one
  • This will cause conflicts and errors
  • Remove qb-houserobbery from your resources folder or stop it in server.cfg
Remove or delete qbx_houserobbery or the script will not work properly
  • You have the QBOX house robbery script running alongside this one
  • This will cause conflicts and errors
  • Remove qbx_houserobbery from your resources folder or stop it in server.cfg

​
Auto-Detection Warnings

[Config.Dispatch.Resource] You have auto detection on for dispatch resource, but your dispatch resource is not started or supported by default
  • Auto-detection couldn’t find a supported dispatch system
  • Solution: Manually set Config.Dispatch.Resource in config/config.lua to your dispatch system name
  • Check the supported dispatch list in the FAQ above, if we still dont support it you will need to manually integrate it in the opensource folder, if its server side set the resource name in Config.Dispatch.Resource to customsv and edit opensource/server.lua, if its client side set the resource name in Config.Dispatch.Resource to customcl and edit opensource/client.lua
[Config.Framework] You have auto detection on for framework resource, but your framework resource is not started or supported by default
  • Auto-detection couldn’t find a supported framework (QBCore, QBOX, ESX)
  • Solution: Manually set Config.Framework in config/config.lua to your framework name
  • Supported values: 'qb-core', 'qbx', 'esx', if we dont support your framework you will need to manually integrate it in the opensource folder.

​
Interaction System Warnings

Your interaction system is set to “ox-target”, which is incorrect. The correct value is “ox_target”
  • You have a typo in your interaction system configuration
  • Change Config.Interaction = "ox-target" to Config.Interaction = "ox_target" in config/main.lua
Your interaction system is set to “qb_target”, which is incorrect. The correct value is “qb-target”
  • You have a typo in your interaction system configuration
  • Change Config.Interaction = "qb_target" to Config.Interaction = "qb-target" in config/main.lua