{
"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.
HeliControl
Moved
Total Downloads: 35,361 - First Release: Sep 18, 2015 - Last Update: Apr 19, 2018
- 5/5, 74 likes
-
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. -
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 -
-
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 }
-
-
-
I miss the time when armor value was overall and not location specific made fighting heli so much easier >..> -
-
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? -
Is it possible to stop heli shooting rockets ?
-
-
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. -
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. -
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 }
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 }
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. -
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. -
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.
-
-
Is this plugin ever going to get updated? It's not working at all for me.
-
-