No Event Markers

No Event Markers 1.2.1

Sign in to download
Removes map markers for events such as patrol helicopters, hackable crates, and cargo ships
Documentation License Changelog (3) Reviews (1) Version History Discussion
This Rust plugin hides all event markers, such as those for patrol helicopters, hackable crates, and cargo ships, from showing up on the map, making it more challenging for players to locate them.




Configuration

JSON: 
{
  "Version": "1.2.0",
  "Disable Patrol Helicopter Marker": true,
  "Disable Hackable Locked Crate Marker": true,
  "Disable Cargo Ship Marker": true,
  "Disable Chinook Helicopter Marker": true,
  "Disable Explosion Marker": false,
  "Disable Travelling Vendor Marker": true
}
Author
VisEntities
Downloads
28
First release
Last update

Ratings

5.00 star(s) 1 reviews
Donate Contribute on GitHub

Also by VisEntities

  • Currency Sync
    Currency Sync
    Syncs player money and reward points across all your servers
  • No AFK Recycler
    No AFK Recycler
    Prevents players from staying afk while using recyclers
  • Remote Catapult
    Remote Catapult
    Lets players launch catapults from a distance with an RF signal

Latest updates

  1. 1.2.1

    Updated for Carbon compatibility.

  2. 1.2.0

    Added Disable Travelling Vendor Marker config option to remove the travelling vendor map marker.

  3. 1.1.0

    Added Disable Chinook Helicopter Marker config option to disable CH47 helicopter marker. Added...
Read more…

Latest reviews

PistOffBastd
Fantastic if you want to bring your server a little closer to Hardcore mode, but still keep the map. Just being able to remove the Patrol Helicopter Marker demands more situational awareness from you players, and it takes them by surprise when they first experience it. Having an option for removing the death marker would have got it 6 stars.
Upvote 0 Downvote
Read more…
  • About us
    Game4Freak is a Rust plugin marketplace and modding platform offering free and premium plugins for server owners looking to improve and take their servers to the next level.
  • Our
  • Your
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 -