Advanced Vehicle Trunk

No. Advanced Trunk is not a traditional stash. It spawns interactive props inside the trunk (cones, weapons, equipment) that players select to take items or place gear on the ground. Actions can be used repeatedly by default. Players cannot put items back into the trunk unless you customize the bridge code yourself.

You need a target system: ox_target or qb-target. A framework is optional. On vMenu or standalone servers without an inventory, trunk props still work, but actions that give inventory items will not add real items to a player inventory.

Yes. Any valid GTA prop model works. The script spawns its own props; it cannot make existing baked-in vehicle trunk visuals interactive. You can position spawned props to line up with the vehicle's built-in trunk look.

This is the most common issue. The script auto-detects most vehicle spawn methods, but not CreateVehicleServerSetter. If your garage, dealership, or spawn script uses that method, add this server export right after the vehicle is created:

exports.gs_advancedtrunk:AddTrunkProps(vehicle)

Props may work with /car but fail from a garage until this export is added to the garage spawn code.

Garage scripts (jg-advancedgarages, vms_garagesv2, qs-advancedgarage, wasabi_ambulance, and similar) often spawn vehicles in a way the script cannot hook automatically. Add exports.gs_advancedtrunk:AddTrunkProps(vehicle) in the garage script's server-side vehicle spawn function.

Try these checks:

• Temporarily disable the global job gate (Config.Target.Trunk.GlobalJobRequirement.Enabled = false) to rule out job restrictions.
• Make sure the vehicle model is listed in Config.Vehicles and has a matching trunk layout in Config.Trunks.
• Update to the latest script version. Older builds had timing issues with driver detection.
• Confirm the server export is called after every spawn path, not just admin commands.

Each prop action can have its own job list in Config.Trunks. There is also a global job gate in Config.Target.Trunk.GlobalJobRequirement. Make sure your job names match your framework exactly.

Debug mode is for building trunk layouts, not normal gameplay. Set Config.Debug = true, restart the script, sit inside the vehicle, then use the debug commands. For normal use, open the physical trunk door through target first.

Addon cars sometimes lack a proper bumper_r bone. Try chassis or boot instead and reposition props using debug mode. Add the vehicle model to Config.Vehicles and assign or create a trunk layout in Config.Trunks.

Yes. Use Config.AdditionalCameraOffsets in config.lua to tweak the camera view per vehicle model.

If your server logs something like "tried to spawn a disallowed item," add those items to the allowlist in server/sv_config.lua, or review SVConfig.EnableItemCheck. Disabling the check is possible but not recommended because it weakens protection against abuse.

Not by default. The stock behavior only gives items or spawns props. To toggle give/remove behavior (for example a broom in and out), customize Functions.GiveItem in bridge/sv_bridge.lua.

Yes. A per-prop ForceInvisible = true option exists for cases where you want selection without a visible prop. Invisible props still need a valid hitbox and should be first in line of sight for mouse selection. Config.HighlightMode = 'lightup' is another option.

The prop model likely has broken or missing collision. Test spawning the prop on its own in the world. As a workaround, set Config.UseKeyboardForSelection = true.

No. Only separately spawned entities can be targeted. Built-in vehicle mesh parts are part of the vehicle model, not standalone entities.

Call this export before the vehicle is removed:

exports.gs_advancedtrunk:RemoveTrunkProps(entity)

If props still linger, your garage delete function may bypass the normal entity removal flow. Remove any old manual gs_advancedtrunk:ResetTrunk snippets from garage scripts; they are no longer needed.

Yes. Prop actions in config can call exports. For advanced behavior (such as spike strips or shields), you can override SpawnPropOnGround in a custom client file loaded last in fxmanifest.lua.