No Heli Rockets

No Heli Rockets 1.0.0

Blocks rocket firing and flare deployment in attack helicopters
Documentation License Version History Discussion
This Rust plugin disables rocket and flare use on the attack helicopter. It blocks firing for pilots and gunners, and can optionally prevent loading rocket or flare ammo. Use the bypass permissions if certain players should be exempt.




Permissions

  • nohelirockets.bypass.rockets - Lets the player fire attack-heli rockets and load rocket ammo (ignores the block).
  • nohelirockets.bypass.flares - Lets the player deploy flares and load flare items (ignores the block).

Configuration

JSON: 
{
  "Version": "1.0.0",
  "Show Toast When Blocked": true,
  "Block Loading Rockets And Flares": false
}
  • Show Toast When Blocked - Shows a red on-screen toast to the player when a rocket/flare action is blocked.
  • Block Loading Rockets And Flares - When true, players can't load rockets or flares into the attack heli. When false, loading is allowed, but firing rockets and deploying flares are still blocked unless the player has a bypass permission.

Localization

JSON: 
{
  "Blocked.Rockets": "You cannot fire rockets.",
  "Blocked.Flares": "You cannot deploy flares.",
  "Blocked.LoadRockets": "You cannot load rockets into this helicopter.",
  "Blocked.LoadFlares": "You cannot load flares into this helicopter."
}
Author
VisEntities
License duration
Unlimited
Price
7.99 USD
First release
Last update

Ratings

0.00 star(s) 0 reviews
Donate

Also by VisEntities

  • Remote Siege Tower
    Remote Siege Tower
    Allows players to remotely control siege towers using RF transmitters
  • Currency Sync
    Currency Sync
    Syncs player money and reward points across all your servers
  • Better Give
    Better Give
    A modern replacement for the give command, with support for offline delivery, custom items, and more
Back
Top
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.
Cart

Cart

Total -