Patrol Heli No Go Monuments

Patrol Heli No Go Monuments 1.0.0

Sign in to download
Prevents the patrol helicopter from flying over specific monuments
Documentation License Version History Discussion
This plugin blocks the patrol helicopter from patrolling certain monuments. Any monument added to the config will be avoided by the heli when choosing a destination.




Configuration

JSON: 
{
  "Version": "1.0.0",
  "No Go Monuments": [
    "airfield_1",
    "powerplant_1"
  ]
}
  • No Go Monuments - A list of monument names where the patrol helicopter is not allowed to fly.
    Note: Safe zones like Outpost and Bandit Camp are automatically ignored by the patrol helicopter, so there's no need to add them to this list.

Monument Names

Here is a list of known monument names that you can use in the configuration:
  • airfield_1
  • ferry_terminal_1
  • bandit_town
  • compound
  • desert_military_base_a
  • desert_military_base_b
  • desert_military_base_c
  • desert_military_base_d
  • excavator_1
  • fishing_village_a
  • fishing_village_b
  • fishing_village_c
  • gas_station_1
  • harbor_1
  • harbor_2
  • junkyard_1
  • launch_site_1
  • lighthouse
  • military_tunnel_1
  • mining_quarry_a
  • mining_quarry_b
  • mining_quarry_c
  • powerplant_1
  • radtown_small_3
  • satellite_dish
  • sphere_tank
  • stables_a
  • stables_b
  • supermarket_1
  • trainyard_1
  • warehouse
  • water_treatment_plant_1
  • water_well_a
  • water_well_b
  • water_well_c
  • water_well_d
  • water_well_e
  • OilrigAI
  • OilrigAI2
  • Like
Reactions: (Manky)sieve
Author
VisEntities
Downloads
11
First release
Last update

Ratings

0.00 star(s) 0 reviews
Donate Contribute on GitHub

Also by VisEntities

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

Cart

Total -