FiveM Vehicle Refunds: Handling Cars, Boats, and Aircraft Claims
Vehicles are the trickiest refunds to get right
Vehicle refunds are more complex than items or money. Vehicles have properties, modifications, fuel levels, and often exist in multiple database tables. Getting them wrong means duplicate vehicles, missing mods, or database corruption. Here's how to handle them properly.
Understanding vehicle data structures
Vehicles in FiveM are stored with extensive metadata. Beyond the model, you're tracking modifications, colors, plate text, fuel, engine health, and ownership history. Each framework handles this differently.
-- Typical vehicle properties object
local vehicleProps = {
model = 'adder',
plate = 'ABC123',
mods = { engine = 4, brakes = 3, suspension = 2 },
colors = { primary = 12, secondary = 0 },
fuel = 65.5,
engineHealth = 1000.0,
bodyHealth = 1000.0
}ESX vehicle refund process
ESX stores vehicles in owned_vehicles table with a vehicle column containing JSON properties. When refunding, you must insert a complete record with valid properties, not just the model name.
- Query the player's citizenid or identifier
- Construct full vehicle properties with default mods if unknown
- Insert into owned_vehicles with state = 'garage'
- Vehicle appears in player's garage on next login
QB Core vehicle refund process
QB Core uses player_vehicles table with mods stored as JSON. The process is similar to ESX but column names differ. Ensure you match the exact schema your server uses—custom resources may modify it.
Important Note
Always generate a new plate for refunded vehicles. Reusing the original plate can cause conflicts if the vehicle was legitimately sold or transferred before the loss occurred.
Handling vehicle modifications
Players care deeply about their vehicle mods. A stock refund of a fully upgraded car feels like a partial refund. Capture mod data when possible, or establish a policy about mod restoration.
- Option 1: Refund with maximum modifications (generous but costly)
- Option 2: Refund stock, compensate mod value in cash
- Option 3: Require players to provide mod screenshots for restoration
- Option 4: Use LD Refund System's automatic mod preservation
Special cases: Boats and aircraft
Boats and aircraft follow similar patterns but may use different garage resources. Some servers have separate hangars or marinas with their own database tables. Verify where each vehicle type is stored.
- Check if your server uses unified or separate storage for vehicle types
- Aircraft often have additional metadata (weapons, countermeasures)
- Boats may lack modification support depending on your resources
- Verify the spawn location makes sense (don't spawn boats on land)
Insurance and replacement policies
Many servers implement insurance mechanics. If a vehicle was insured, players can claim through that system instead of staff refunds. Understand your server's insurance before processing vehicle refunds manually.
“We redirect 70% of vehicle loss reports to our insurance NPC. Only true server-fault losses go through staff refunds. This cut our vehicle refund queue by 80%.”
Vehicle refunds require attention to detail. Take time to understand your server's specific implementation, and always test refunds in a staging environment before going live.
Need a smarter refund flow?
LD Refund System automates Discord approvals, in-game claims, and audit logging so your staff stay focused on players.