smdv-dv is a simple and reliable vehicle deletion command for FiveM servers.
This documentation applies to version 1.0.0, which includes all current functionality and fixes.
The script safely deletes vehicles using modern FiveM methods, avoids common engine issues (such as players falling under the map), uses ox_lib for UI, and logs all deletions to Discord.
- Place the smdv-dv resource folder into your server’s resources directory.
- Ensure ox_lib is installed and started before smdv-dv.
- Add the resource to your server configuration so it starts automatically.
- Restart or start the server.
Once started, the delete command will be available in-game.
To use smdv-dv version 1.0.0 correctly, your server must have:
- A FiveM server with OneSync enabled
- ox_lib installed and functioning
- A Discord webhook URL for logging (optional but recommended)
All configuration is handled in the shared configuration file.
You can customize:
- The command name used to delete vehicles
- The search radius for finding nearby vehicles
- The cooldown between uses
- UI behavior such as progress indicators
- Discord webhook settings
- All player-facing messages
Version 1.0.0 is fully configurable without modifying core logic.
When the command is used, the script automatically selects the correct vehicle.
Priority order:
- If the player is inside a vehicle, that vehicle is targeted.
- If the player is not inside a vehicle, the nearest vehicle within the configured radius is targeted.
A progress indicator may be shown depending on configuration. Once complete, the vehicle is deleted and the player is notified.
The client handles:
- Command input
- Vehicle detection (inside or nearest)
- ox_lib UI and notifications
- Safely removing the player from the vehicle before deletion
If the player is inside the vehicle, they are exited and repositioned safely to prevent falling through the map.
The client then sends the vehicle’s network ID to the server.
The server handles:
- Validating the network ID
- Resolving the entity safely
- Removing any occupants
- Deleting the vehicle using server-safe methods only
- Sending confirmation back to the client
- Logging the action to Discord
No client-only natives are used on the server in version 1.0.0.
When Discord logging is enabled, each deletion records:
- Player name and server ID
- Whether the vehicle was inside or nearby
- Vehicle model hash
- License plate (if available)
- Network ID
- Player coordinates at the time of deletion
This provides a clear audit trail for staff and server management.
¶ Error Handling and Safety
Version 1.0.0 includes safeguards to prevent:
- Invalid native usage
- Server-side crashes
- Players spawning under the map
- Silent failures
If a vehicle cannot be resolved or no valid target exists, the deletion is safely cancelled and the player is notified.
If the command does nothing:
- Confirm ox_lib is running
- Check the search radius in the configuration
- Ensure the resource is started
If Discord logs do not appear:
- Verify the webhook URL
- Check server connectivity
- Confirm webhook permissions
If players fall under the map:
- Ensure the latest client file from version 1.0.0 is installed
- Confirm the safe exit logic has not been removed
- Keep cooldowns reasonable to prevent spam
- Enable Discord logging for accountability
- Avoid running multiple DV scripts at once
- Restart the server after configuration changes
- Initial public release
- ox_lib-based UI
- Safe vehicle targeting (inside or nearest)
- Server-safe deletion logic
- Full Discord logging
- Player safety handling to prevent map fall-through
smdv-dv version 1.0.0 focuses on doing one thing well:
safely deleting vehicles without causing errors, instability, or immersion-breaking issues.