HeliControl

Moved

Total Downloads: 35,359 - First Release: Sep 18, 2015 - Last Update: Apr 19, 2018

5/5, 74 likes
  1. Yeah, they still use /callheli. Basically if they can only call on themselves and were to use /callheli SomeOtherPlayer'sName it would say they can only call it themselves. The cooldown value is in seconds, yes, hence the default being so high.

    And yeah, the description needs cleaned up a bit in multiple places but just getting around to working on plugins has been difficult with my limited time recently.
     
  2. Well, it looks like I will need config for cooldown.It won`t let me give any cooldown higher than 0.It would simply say the permission does not exist.

    Basically, I want them to be able to call one heli with cooldown of two hours.
     
  3. Here's an example where the cooldown permission is "Cooldown.0" (what you'd grant the player), set to 2 hours in seconds.

    Code:
      "Cooldowns": {
        "Cooldown.0": 7200.0,
        "Cooldown.1": 86400.0,
        "Cooldown.2": 86400.0,
        "Cooldown.3": 86400.0,
        "Cooldown.4": 86400.0,
        "Cooldown.5": 86400.0,
        "Cooldown.6": 86400.0,
        "Cooldown.7": 86400.0,
        "Cooldown.8": 86400.0,
        "Cooldown.9": 86400.0
      },
    
     
  4. Code:
    Failed to call hook 'CanBeTargeted' on plugin 'HeliControl v1.1.7' (InvalidCastException: Cannot cast from source type to destination type.)
      at Oxide.Plugins.HeliControl.DirectCallHook (System.String name, System.Object& ret, System.Object[] args) [0x00000] in :0
      at Oxide.Plugins.CSharpPlugin.InvokeMethod (HookMethod method, System.Object[] args) [0x00000] in :0
      at Oxide.Core.Plugins.CSPlugin.OnCallHook (System.String name, System.Object[] args) [0x00000] in :0
      at Oxide.Core.Plugins.Plugin.CallHook (System.String hook, System.Object[] args) [0x00000] in :0
    Failed to call hook 'CanBeTargeted' on plugin 'HeliControl v1.1.7' (InvalidCastException: Cannot cast from source type to destination type.)
      at Oxide.Plugins.HeliControl.DirectCallHook (System.String name, System.Object& ret, System.Object[] args) [0x00000] in :0
      at Oxide.Plugins.CSharpPlugin.InvokeMethod (HookMethod method, System.Object[] args) [0x00000] in :0
      at Oxide.Core.Plugins.CSPlugin.OnCallHook (System.String name, System.Object[] args) [0x00000] in :0
      at Oxide.Core.Plugins.Plugin.CallHook (System.String hook, System.Object[] args) [0x00000] in :0 
    What does this mean? Anyone can help?
     
  5. Wulf

    Wulf Community Admin

    Looks like we missed a change in the Rust update. You'll have to wait for the next Oxide build to fix it.
     
  6. Does helicontrol.callheli (gives you access /callheli) give players ability to call the heli to other players?

    I want to give people the ability to call the heli, but not call it on a player. I'll give them the strafe ability to call it to them if they want to fight it.
     
  7. helicontrol.callheli will give them full access to the command, they can call it on anyone/anywhere. As of the current version, you only have the options to give them callheli (the full 'admin' version of the permission, essentially), and helicontrol.callhelitarget and helicontrol.callheliself , which means they'll either have to be able to call it on themselves or a target. The permission(s) may be changed in the future to add an option that allows a player to only call one in general, not on a target or themselves.
     
  8. Thanks. I would like to see a new permission combining callheli and strafeheli. This way players could call the heli to themselves.
     
  9. I hope you don't mind my asking; why do you need them to be able to call it and then have to use strafe for it to come to them? You can call directly to the target (and that functionality already exists) - I'm just curious why the extra option.
     
  10. Strafing the heli to yourself is great, but that requires the heli to have spawned. So if you want to fight the chopper, you have to wait for it to spawn and then strafe it to you. I'm looking to give players the ability to call it and strafe it so they don't have to wait for it, but I don't want them to call the heli if they can use it to attack other players by specifying the destination or target.

    Keep in mind also that when you use a mod to skip night, it sometimes screws up the spawn times of the heli so it won't spawn as often. This makes it more important for a player to be able to call it.
     
  11. How to configure a helico every hour thanks
     
  12. Code:
    "Spawning - Automatically call helicopter after this many seconds": 3600.0,
     
  13. for some reason calling a heli to a position makes them hover at the position and they do not move until someone attacks them.... anyone have this issue?? I called 3 to a position and they just hover there... even after being shot at a lot... they finally reacted and started attacking but at first from that hover position.

    20170513080028_1.jpg 20170513080041_1.jpg 20170513080347_1.jpg
     
    Last edited by a moderator: May 13, 2017
  14. I noted that Chopper Survival does the same things so I suspect that this is not related to heli control but some rust update.
     
  15. Indeed, I was going to reply that I think there was some recent Rust change that has caused this. I'll try to see if there's a workaround.

    EDIT: Now that I think about it, I believe there was a Reddit post where someone claimed it happened on a vanilla server as well. This will most likely have to be fixed by Facepunch.
     
    Last edited by a moderator: May 14, 2017
  16. OK so I found this article:

    Helicopter bug (for Helk) • r/playrust

    and realized I was calling them to a position too high so I lowered it and then it all worked out.
     
  17. hey mate, I seem to have another issue, it might be related to the facepunch patch aswell.. appartently the users that has callheli.self and callheli.target command can also call in with /callheli and apparently they are able to call in multiple helicopters even tho Ive put in the config that only 1 is allowed.. I changed it from -1 to 1 and that should be that its only allowed 1 in the map right?
     
  18. Hmm.... I'm not sure what would be causing it to allow more than the max you set. Just to be sure, you did reload the plugin after saving the config when you changed it to 1 from -1, right?
     
  19. Code:
    HeliControl.cs(184,22): warning CS0114: `Oxide.Plugins.HeliControl.LoadDefaultMessages()' hides inherited member `Oxide.Core.Plugins.Plugin.LoadDefaultMessages()'. To make the current member override that implementation, add the override keyword. Otherwise add the new keyword
    c:\rustexp\steamcmd\rust\Oxide.Core.dll (Location of the symbol related to previous warning)
    HeliControl.cs(330,17): warning CS0219: The variable `transform' is assigned but its value is never used
    HeliControl.cs(44,14): warning CS0169: The private field `Oxide.Plugins.HeliControl.DisableHeliRockets' is never used
    HeliControl.cs(1671,24): warning CS0649: Field `Oxide.Plugins.HeliControl.ItemDef.amountMin' is never assigned to, and will always have its default value `0'
    HeliControl.cs(1672,24): warning CS0649: Field `Oxide.Plugins.HeliControl.ItemDef.amountMax' is never assigned to, and will always have its default value `0'

    NotWorked
     
  20. Those are all warnings, not errors. The plugin will still work fine.