The plugin sounds very interesting, exactly what I'm looking for. But I still have a few questions about it.
Does the vehicle get the same Net ID or does it get a new one?
Are there any hooks that can be used when parking/unparking?
What about other entities attached to the vehicle, such as the radio, additional storage, license plate?
Would it be possible to set it so that a vehicle can only be parked out of the same spot where it was parked?
Is it possible to save the SkinnID when refueling?
The plugin would be perfect for us to save Enites and thus improve performance. The only problem is the additional plugins we use, which is where the questions arose from .
It gets a new net id when spawned, I'll see if restoring the original is possible, though I doubt it, but I'll dig into it and look for another solution if needed
Child entities like code locks and turrets can be handled. For more specific stuff, I'd need to know exactly what plugin is attaching it so I can support it properly, but yeah, definitely doable and important for compatibility
Unfortunately, we currently still use various plugins for the attached entities, including one we wrote ourselves.
For example
Storage on helicopter
Wooden panel with a number Panel with a picture at the top https://umod.org/plugins/sirens
Alright, yeah, none of these will be a problem. I'll include them in the next update. You can click the Subscribe for updates button on the plugin page to get notified when it goes live. Thanks for the suggestions
Alright, yeah, none of these will be a problem. I'll include them in the next update. You can click the Subscribe for updates button on the plugin page to get notified when it goes live. Thanks for the suggestions
It already saves the contents of storage containers and restores them when the vehicle is spawned. But if you mean blocking players from storing the vehicle when any container has items in it, that's a solid idea, I can add that
Car radio on modular cars is now preserved
I also added support for saving and restoring storage containers attached to vehicles, limited to StorageContainer type for now, but that already covers most stuff like furnaces, workbenches, lockers, etc.
Wooden signs are preserved too (as long as you're using my Vehicle License Plate plugin, which you are), nothing else needed for that
Now, if you (or other plugins) attach more custom stuff to vehicles, like signs, sirens, alarms, or whatever, I added two new hooks for that:
OnVirtualGarageSaveAttachments
OnVirtualGarageRestoreAttachments
You can use those to handle saving/restoring whatever your plugin spawns. I didn't make Virtual Garage try to save every child entity automatically because it just wouldn't work right, especially for electrical stuff. Like if a plugin wires something up or triggers it with hooks, simply saving and restoring it from Virtual Garage wouldn't bring it back to life, it'd just be a dead prop. Same with a few other things. So for now I'm sticking to storage containers (and locks are coming soon)
That was technically possible, as long as the net id was lower than the current top one (so nothing else would try to reuse it). But I didn't go with that approach, felt a bit sketchy. Instead I went with storing all custom stuff as metadata and using the new hooks to bring back whatever your plugin added to the vehicle. You can check out an example here
A few of your other suggestions that got missed will be added in the next update
Chat commands start with a /, while console commands can be entered directly in the F1 console or server console. Use find <keyword> in console to search for available commands related to the plugin. Parameters in < > are required, while [ ] are optional.
This plugin uses Oxide's permission system. Grant or revoke permissions using oxide.grant and oxide.revoke. You can assign them to individual players or groups using their Steam id or group name.
Settings are stored in the config file found under the config/ directory. You can edit this file manually, then reload the plugin to apply your changes.
Persistent data is saved in the data/ directory. This includes things like saved settings, usage stats, or player progress depending on the plugin. Deleting a data file will reset stored progress or customizations.
Language files are located in the lang/ folder. To translate messages, copy the en.json file into your target language folder (e.g. fr, de) and edit the values. Reload the plugin after changes to apply new messages.
This section lists public methods exposed by the plugin for use in other plugins. You can call these via the CallHook method. Ensure the plugin is loaded before calling its API to avoid null reference errors.
These are custom hooks that other plugins can listen for. Simply define a method with the same name and expected parameters in your plugin to handle the event. Hooks are triggered at key moments and are useful for extending or reacting to plugin behavior.
These hooks are injected into the game's code using Harmony. They let the plugin run code at key points in the game's internal logic. You can return values to block or modify behavior. Use with caution — these are powerful and can affect core mechanics.
.
