Recent content by Eddie Flats

  1. Eddie Flats

    Solved Helicopter Not Staying Locked to Caller

    I think I understand now. Thank You for putting up with me and my confusion. The heli isnt running anymore as long as I dont have a team mate anywhere on the map so I can tell folks that if they want to fight it alone, leave whatever team your on. We will not be seeking the refund you were...
  2. Eddie Flats

    Solved Helicopter Not Staying Locked to Caller

    Call profile in colt.json (only thing I touched is adding colt in the suffix area) "Call Profiles": [ { "Enabled": true, "Lock On Caller": true, "Include Caller Allies (teammates, friends, clanmates, and clan allies)": true, "Suffix": "colt", "Number To...
  3. Eddie Flats

    Solved Helicopter Not Staying Locked to Caller

    Man do I feel stupid. I set the suffix in the colt heli profile to colt thinking it just needed a name to match the call command... "Call Profiles": [ { "Enabled": true, "Lock On Caller": true, "Include Caller Allies (teammates, friends, clanmates, and clan allies)"...
  4. Eddie Flats

    Solved Helicopter Not Staying Locked to Caller

    Sorry for sending the wrong file. These are the call commands for all the tiers we use in GUIShop. When I asked about this in the game4freak discord, I was told the running away behavior was a "feature" to mimic a vanilla heli. Sounds like there is hope for us yet. Thanks for taking your...
  5. Eddie Flats

    Solved Helicopter Not Staying Locked to Caller

    I had to turn off the helis from this plug. Got tired of the complaints. "where did my heli go?" every hour. Folks die and it leaves and shoots innocent folks and 9/10 times someone other than the owner shoots it down. AM I missing a setting that would stop this? Anyone know of another...
See 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 -