Sam Range Alert

Sam Range Alert 1.0.0

Warns helicopter pilots when approaching sam sites
Documentation License Version History Discussion
This Rust plugin warns helicopter pilots when flying too close to active sam sites, helping them avoid getting shot down. It checks the pilot's heading and speed and only alerts when they're actually flying toward a sam, not just nearby. Works with minicopters, scrap transport helis, and any other flyable helicopters.




Permissions

  • samrangealert.use - Required for a player to receive sam alerts while flying.

Configuration

JSON: 
{
  "Version": "1.0.0",
  "Scan Interval Seconds": 0.25,
  "Early Warning Range (outer)": 420.0,
  "Danger Zone Radius (actual sam range approx)": 350.0,
  "Heading Tolerance Degrees (must be moving roughly toward sam)": 100.0,
  "Alert Only If Sam Is Powered": true,
  "Alert Only If Sam Has Ammo": true,
  "Ignore Sams In Defender Mode": true,
  "Repeat Alert Delay Seconds": 3.0,
  "Enable Toast Notifications": true,
  "Also Send Chat Alerts": false
}
  • Scan Interval Seconds - How often to check each helicopter's position, in seconds.
  • Early Warning Range - Distance where a blue warning is shown if the pilot is flying towards a sam site. This gives players a chance to turn around before danger.
  • Danger Zone Radius - The range where the sam is most likely to engage. Once the heli enters this radius, a red danger alert is shown.
  • Heading Tolerance Degrees - How directly the pilot must be flying toward the sam for a warning to show. Lower values mean they must be flying straight at it, higher values are more forgiving.
  • Alert Only If Sam Is Powered - If true, only powered sams will be considered for alerts. Turn off if you want all sams to be considered regardless of power.
  • Alert Only If Sam Has Ammo - If true, only sams that actually have rockets loaded will trigger warnings. Helps avoid spamming players when the sams can't shoot anyway.
  • Ignore Sams In Defender Mode - If true, ignores sams that are temporarily in defender mode.
  • Repeat Alert Delay Seconds - Sets a cooldown per player between alerts, to avoid constant spam while flying.
  • Enable Toast Notifications - If true, alerts show as on-screen toasts (gametip).
  • Also Send Chat Alerts - If true, sends the warning text to chat in addition to the toast HUD popup.

Localization

JSON: 
{
  "Warn.Outer": "Sam ahead {0}m. Change course!",
  "Warn.Danger": "<color=#ff5555>WARNING:</color> You are in Sam range ({0}m)!"
}
  • Like
Reactions: kaffeebohne, SONuvaGUN and (Manky)sieve
Author
VisEntities
License duration
Unlimited
Price
7.99 USD
First release
Last update

Ratings

0.00 star(s) 0 reviews
Donate

Also by VisEntities

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 -