Pretty sure helicontrol.calhelitarget is an overriding permission for helicontrol.callheliself, so that might be why it worked![]()
HeliControl
Moved
Total Downloads: 35,361 - First Release: Sep 18, 2015 - Last Update: Apr 19, 2018
- 5/5, 74 likes
-
-
Sorry I've been trying for ages -
make a group: "heli" or whatever you wanna call it
grant the group with:
grant group heli helicontrol.callheliself or helicontrol.callhelitarget
grant group helihelicontrol.cooldown.0 or whatever one you want. (configure it first)
grant group helihelicontrol.limit.0 or whatever one you want. (configure it first) (Also, it wouldn't allow me to callheli without this) -
As for the heli taking a while to come, I'm pretty sure it's just how Rust spawns them, which is really far out in the map, in most cases. -
Yeah, I figurws the limits permission out through trial and error.
The heli takes way longer to come with this setup then it does when you use the regular /callheli permission (helicontrol.callheli) and it seemed to lose focus in where it was going, or maybe it re-focused on someone else before returning to original destination, not sure on that. Is there a check to see where the closest spawn is and maybe force it to spawn at that point? idk lol -
Needing help with this, so im setting the heli time to be every 1 hour and the heli is spawning when ever it likes
-
-
-
-
-
The config option looks like:
Code:"DisableDefaultHeliSpawns": false,
-
10:50 [Error] Error while compiling HeliControl.cs(1612,92): error CS1503: Argument `#3' cannot convert `ulong' expression to type `int' on STAGING branch.
-
-
I'll upload fixes when it's officially released, in case more is 'broken' at that time. -
-
Rust update, bug report
[Oxide] 06:14 [Error] Error while compiling HeliControl.cs(1612,92): error CS1503: Argument `#3' cannot convert `ulong' expression to type `int' -
Shady757 updated HeliControl with a new update entry:
1.0.42
-
-
Working fix:
Attached Files:
-