Added support for per-player daily call limits. Each call profile now has a Daily Call Limit value: set it to any positive number to restrict how many times a single player can summon that helicopter during a UTC day; keep it at 0 to leave calls unlimited.
You can now adjust rocket damage for each tier with the new Rocket Damage Multiplier setting. A value of 1 keeps the default damage, values below 1 (e.g., 0.5) reduce it, and values above 1 (e.g., 2) increase it.
Added integration with the XPerience plugin to reward XP when a helicopter is destroyed.
Added integration with the LootTable plugin. Enable the new Use Loot Table Preset setting to have helicopter crates auto-populated via presets (falls back to AlphaLoot/custom/vanilla if isn't present).
Improvements:
Reduced the chance of helicopters failing to spawn over the ocean.
Bug Fixes:
Fixed an issue where clicking buttons in the shop ui played sounds that nearby players could hear.
Fixed an issue where helicopter wreckage was not being altered based on the tier settings.
Added pagination to the helicopter shop ui for tiers exceeding 10 entries. Players can now click numbered page buttons at the top-left to browse additional pages of helicopter tiers.
Added support for running chat, client, or server commands when a helicopter is destroyed. See Death Commands for details on how to configure them.
Added integration with the Skill Tree plugin to reward XP upon helicopter destruction.
Fixed an issue where using the call command from the server console would spawn the helicopter for the command caller (which doesn't exist on the server console) instead of the specified target player.
Increased the maximum attempts for random spawn selection, improving reliability on larger maps.
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. 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.
