Airdrop Settings (Legacy Thread)

Status
Not open for further replies.
I switched over to this plugin and learned that a supply drop will damage/destroy a minicopter if it falls on it. My players thought this was hilarious. Is this part of the plugin or perhaps did the old plugin do something to prevent damage?
 
I switched over to this plugin and learned that a supply drop will damage/destroy a minicopter if it falls on it. My players thought this was hilarious. Is this part of the plugin or perhaps did the old plugin do something to prevent damage?
Uhm, I haven't intentionally added any logic related to that. The most reasonable explanation tho is that it has something to do with the rigidbody of the minicopter. See, when the supply drop collides with the minicopter, it applies force or damage. However, this is more likely an issue on the minicopter's end. It's not really an issue per se, as Facepunch designed minicopters to take damage literally from touching anything lol
 
I would like to give an idea for this plugin, could you put an option in the configuration so that it only works with aerial supply grenades, that is, the plane that comes only every time a day passes that is by default?

I think this would be a great idea, I hope you like it and implement it.
 
I would like to give an idea for this plugin, could you put an option in the configuration so that it only works with aerial supply grenades, that is, the plane that comes only every time a day passes that is by default?

I think this would be a great idea, I hope you like it and implement it.
Do you mean applying the settings only to airdrops triggered by supply signals and not those spawned by the server?
 
Remember the idea that it can be toggled in settings to only work with supply grenades.
I haven't forgotten, but I'll get to it later, it's not a top priority right now. It's also not very straightforward since there's currently nothing in the game linking the supply signal and the cargo plane it calls, so I'd need to implement that connection myself first to make it work. It's definitely on my todo, but I'll get to it once my plate clears up a bit (y)
 
ok thank you very much I still have to wait...sorry for the inconvenience
I haven't forgotten, but I'll get to it later, it's not a top priority right now. It's also not very straightforward since there's currently nothing in the game linking the supply signal and the cargo plane it calls, so I'd need to implement that connection myself first to make it work. It's definitely on my todo, but I'll get to it once my plate clears up a bit (y)
ok thank you very much I still have to wait...sorry for the inconvenience
 
Status
Not open for further replies.
Back
Top
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.
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.
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. Make sure 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.
Cart