Ogi’s vehicle-respawn is a QBCore script for recreating tracked vehicles after they disappear. It is not an add-on car and has no vehicle model download or spawn name. The reviewed repository manifest identifies version 1.0.0.
Fix startup before installation
The creator lists QBCore and baseevents and uses the resource name vehicle-respawn. However, the supplied config.lua assigns Config.RespawnCheckInterval and Config.PlayerDistanceForDespawn without initializing Config. Its manifest loads no earlier initializer. This revision needs that defect corrected before startup; it is not a ready-to-run package as supplied.
Integrate deliberate deletions
The server tracks vehicles in memory after the QBCore left-vehicle event. Every configured interval it checks for a missing plate and a player inside the configured radius; defaults are two minutes and 100 meters. This resolves the contradictory nearby/no-nearby wording in the README. Tracking is not persisted across server restarts. Garages and cleanup scripts must remove tracking before intentionally deleting vehicles, or a stored vehicle may return.
Validate permissions and failure paths
The supplied AddVehicleNoDespawn and RemoveVehicleNoDespawn handlers accept client-provided plates without ownership checks there. Have a developer authorize tracking changes and integrate the removal event correctly for client and server contexts. Test garage storage, impound, disconnects, failed spawns and duplicate plates. The client also contains an unbounded ownership-wait loop. These limitations need review before live use; no reliability or performance certification is claimed.