HeliControl

Moved

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

5/5, 74 likes
  1. {
    "UseGlobalDamageModifier": false,
    "ModifyDamageToHeli": true,
    "DisableHeli": true,
    "UseCustomLoot": false,
    "UsePermissions": false,
    "GlobalDamageMultiplier": 4.0,
    "HeliAccuracy": 2.0,
    "MaxHeliRockets": 0,
    "HeliBulletDamageAmount": 5,
    "HeliSpeed": 25.0,
    "MainHealth": 10000.0,
    "MainRotorHealth": 750.0,
    "TailRotorHealth": 375.0,
    "MaxLootCratesToDrop": 6,
    "pistol.eoka": 5.0,
    "pistol.revolver": 5.0,
    "pistol.semiauto": 5.0,
    "rifle.ak": 5.0,
    "rifle.bolt": 8.0,
    "smg.2": 5.0,
    "smg.thompson": 5.0
    }
    Helis are still able to spawn with DisableHeli as true.
     
  2. Are you sure you're modifying the correct config file? You want to modify HeliControl.json in oxide\config.

    It looks like you're modifying HeliControlWeapons.json in oxide\data, which is not what you want to modify, except for changing the damages on weapons.
     
  3. Nope i am editing HelicControl.json thats exactly what it shows on my Server Panel, i'll even show you.
    That Screen shot is what im seeing on my server panel, mind you those settings are now Default because i went and reinstalled the plugin.

    Those Screenshots show default and editited i'm not editing the wrong file dude, i can read.

    Only thing i can think of is that the Helicontrol.json is only being downloaded partially by clanforge, which there is absolutely nothing i can do about that, so if you could can you post the entire .json as a text code so i can go and manually replace what shows up on my end and see if that makes any sort of difference.

    Because what shows on overview Vs on screen looks totally different.
     

    Attached Files:

    Last edited by a moderator: Aug 30, 2016
  4. Firstly, I hope you know I'm not trying to be rude. I know you can read, but as I said before, I'm trying to help with no knowledge of the environment you're using, so some of the questions I ask may seem a little dumb.

    It's really strange that it would be forcing it's own default config, but you might be right about it. There's already a default config on the overview, but I'll paste it here for your ease:


    Code:
    {
      "AutoCallHeliIfAlreadyExists": false,
      "BaseHealth": 10000.0,
      "BulletSpeed": 250,
      "CallHeliEverySeconds": 0.0,
      "CooldownPlayersCanCallMultiple": false,
      "CooldownPlayersCanCallToTarget": true,
      "Cooldowns": {
        "Cooldown.0": 86400.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
      },
      "DisableDefaultHeliSpawns": false,
      "DisableGibs": false,
      "DisableHeli": false,
      "DisableNapalm": false,
      "GibsHealth": 500.0,
      "GibsTooHotLength": 480.0,
      "GlobalDamageMultiplier": 1.0,
      "HeliAccuracy": 2.0,
      "HeliBulletDamageAmount": 20.0,
      "HelicopterCanShootWhileDying": true,
      "HeliSpeed": 25.0,
      "HeliStartSpeed": 25.0,
      "HeliStartTime": 0.0,
      "LifeTimeMinutes": 15,
      "Limits": {
        "Limit.0": 5,
        "Limit.1": 5,
        "Limit.2": 5,
        "Limit.3": 5,
        "Limit.4": 5,
        "Limit.5": 5,
        "Limit.6": 5,
        "Limit.7": 5,
        "Limit.8": 5,
        "Limit.9": 5
      },
      "LockedCrates": true,
      "MainRotorHealth": 750.0,
      "MaxHeliRockets": 12,
      "MaxLootCratesToDrop": 4,
      "ModifyDamageToHeli": false,
      "RocketDamageBlunt": 175.0,
      "RocketDamageExplosion": 100.0,
      "RocketExplosionRadius": 6.0,
      "TailRotorHealth": 375.0,
      "TimeBeforeUnlockingCrates": 0.0,
      "TimeBetweenRockets": 0.2,
      "TurretBurstLength": 3.0,
      "TurretFireRate": 0.125,
      "TurretMaxTargetRange": 300.0,
      "TurretTimeBetweenBursts": 3.0,
      "UseCustomHeliSpawns": false,
      "UseCustomLoot": false,
      "UseGlobalDamageModifier": false,
      "WaterRequiredToExtinguishNapalm": 10000
    }
    You should be able to copy and paste that into your current one on your server. Alternatively, you may just have to contact your provider, sorry that I can't be anymore helpful, but I really am trying. :)
     
  5. Yea i put all of that in saved and applied, did the unload and load updatehelis still doing all the heli's default actions.
     
  6. Then at this point I'm truly out of ideas. I have to assume the config is working fine for all other plugins? As I said before, the only other thing I can tell you to do, at this point, is to contact them ask them to see if they can find out what the issue is, and why the default config on their side is very incorrect.
     
  7. Problem is, that if we have to get them to install it for us, i think that costs money, so sadly looks like we gotta deal with the helies rediculously OP damage.

    I miss the time when armor value was overall and not location specific made fighting heli so much easier >..>
     
  8. You should still be able to question them about it without being charged. Alternatively, try posting in the Rust section and see if someone else can help you, since I'm sure there's others who have experience and can help you a lot more than I have.
     
  9. hi,
    I'm using this plugin on my server and all works perfect! but I seen this can be used with admin menu along with a few other plugins.. is there a way I can add this to the admin menu with a command? or is it a case it may or may not appear in the admin menu?
     
  10. Is it possible to stop heli shooting rockets ?
     
  11. I'm not sure how "admin menu" works, so I can't really say.


    Set the max amount of rockets in the config to 0.
     
  12. when changing the values in the config file which way are the numbers? for example I want to change the accuracy of the heli and its currently "HeliAccuracy": 2.0 if I want it to be more accurate would I change the number higher or lower? also the heli goes down way to easy at the moment can I change damage given to the heli from guns? or would I just have to change the main and rotor health of the heli?

    Thanks.
     
  13. You can reduce the amount of damage weapons do to it, which probably the most effective way, or you can change the health, which is a little less effective.

    I believe the lower the number the more accurate, but I can't quite remember. That config value actually just changes the rust console setting, so it's handled by Rust.
     
  14. Is anyone else having issues with players who have the permissions for the limits (helicontrol.limit.1, helicontrol.limit.2, etc) not being able to call helis unless they are also granted the helicontrol.callheli permission? And then when granted that, they can call as many helicopters as they want regardless of the limit?

    I seem to have fixed it by editing the plugin source code. In the callheli chat command method, line 739, it has the following:

    Code:
                if (!canExecute(player, "callheli", false) && cooldownTime == 0f)
                {
                    return; //if cooldown time is not 0f, then it means this player is permitted because of cooldown permission
                }
    You've used cooldownTime == 0f as the expression, but your comment specifies if cooldown time is NOT 0f. I think because of this, I was getting the "You do not have permission to use this command" message, and no heli was being called.

    I replaced it with the following code:

    Code:
                if (!canExecute(player, "callheli", false) && cooldownTime != 0f)
                {
                    return; //if cooldown time is not 0f, then it means this player is permitted because of cooldown permission
                }
    I also went through the callheli method and replaced all the canExecute(player, "callheli") with canExecute(player, "callheli", false), because it would say the player didnt have permission, then call the helicopter anyway. The false boolean in canExecute specifies that the error message shouldn't be sent.

    Not sure if you want to look into this Shady757, I might just be doing something wrong in the case of the limits not working unless the helicontrol.callheli permission is given, in which case they can call as many as they want. Maybe there should be a player call command and an admin call command, should fix up the permissions messages and whatnot.
     
  15. I think you misunderstood the code and the comment. If the player does not have permission to callheli and the cooldown time is 0f, that means they do not have the cooldown permission either, in which the return stops the rest of the code from being excuted. What you just did is make people who have any cooldown time other than 0f and can't use the permission callheli unable to use the command.

    This is a bit of a messy place of the plugin, and it's really been bothering me and I've been trying to make it better, hence the delay on the updates. I've also changed the way canExecute works and the sending of messages, so that's cleaned up. I'm not sure why you're having the issue you described, you should only grant callheli if you want people to be able to call a heli on whoever, where ever, whenever and how ever many times they want, that's the intention of the permission.

    Judging by the start of your post, you didn't grant the cooldown permission which I believe is a requirement. This is a limitation of the current code, and if you have the cooldown set to 0, so they can call it immediately, it will return. For now, to fix this, you can set the cooldown of a permission to 1 second, and then grant that permission.
     
  16. Ah, my bad, I didn't pick up on the helicontrol.cooldown.1 permissions, as the main post isn't very descriptive in that regard. I'll revert the plugin to the official version and give that a try.
     
  17. No problem, it's not something I even thought of 'til now, so thanks for bringing it up. I'll try to make the code allow for either cooldown or limit, and not requiring both. I'll also try to improve the overview a bit.
     
  18. Is this plugin ever going to get updated? It's not working at all for me.
     
  19. "...Not working at all" does'nt help the developer to solve "your" problem. The plugin mainly itself is working.
     
  20. Yeah, it's going to be updated, but it probably won't fix your issue. Can you explain a little bit more, please? You say it's "not working at all", does this mean there's an error on startup? The plugin fails to compile? Commands don't work? Permissions don't work? I just need more info. Thanks.