Setup

Install Wheel Pop or migrate wheel behavior from Realistic Vehicles.

#New Installation

Install and start the latest zyke_lib.
Download Wheel Pop and keep the folder name zyke_wheelpop.
Add the item definitions from extras/items to your inventory and copy the included images.
Configure shared/unlocked/config.lua.
Start the resources in this order:

cfg
ensure zyke_lib
ensure zyke_realisticvehicles # optional
ensure zyke_vehicleterrain    # optional
ensure zyke_wheelpop

The default items are:

Item	Purpose
`wheel_scanner`	Opens the wheel integrity overview.
`vehicle_wheel`	Stores a picked-up loose wheel and its fitment metadata.
`tirekit`	Repairs the nearest damaged or failed wheel.

#Moving From Realistic Vehicles

Wheel settings previously lived in Config.DamageSystem. They now belong to Config.WheelPop.

Move wheelLossIntegrityNotifications, wheelLossIntegrityMenu, wheelLossVisual, and wheelItem directly into Config.WheelPop.
Move the tire-kit portion of repairItems; the general repairKit remains part of Realistic Vehicles.
Move wheel-related preset overrides, such as wheelLossDirectIntegrityDamage, into Config.WheelPop.overrides.
Keep full-repair events in both resources when those events should repair both body damage and wheels.

Start from the new Wheel Pop defaults, then reapply only intentional overrides. This preserves current fixes and revised preset values.

Wheel Pop works independently. If your installed Realistic Vehicles version still contains the old wheel implementation, update it before enabling zyke_wheelpop so two resources do not manage the same wheel state.

Existing integrations can continue using the stable Realistic Vehicles aggregate persistence payload when both resources are installed. Direct Wheel Pop integrations should use GetWheelLossData and SetWheelLossData from zyke_wheelpop.