Rust Chinook control

Discussion in 'Plugin Requests' started by mcphee, Apr 6, 2018.

  1. Im sure someone is probably already making this, The chinook event on a timer would be nice rather than going by time of day, Because if you are using the skip night plugin it seems to void the event (According to Alistair)
     
  2. You can use TimedExecute ;)
     
  3. As Adriok said, when you skip night, airplane/chopper/chinook stop working because it never end a normal time cycle, so you have to use another way to spawn it, the simpliest way is to use TimedExecute as said, or wait for a private/public Helicontrol like
     
  4. I tried timedexecute to spawn the ch47scientists.. It spawns the heli but all it does is fly around and then leave.. never once have I seen it drop a locked box.. The only way I can get a locked box is if i spawn codelock
     
  5. Ya i tried spawning myself and it will just fly around for a while and leave, if you shoot at it the scientist will shoot back but that's about it, it doesn't drop anything.
     
  6. I have PVP enabled only during the night on my server. Would be nice if I could customize the timers for Chinook event to happen only during the night. Same for other events in case I decide to change those.
    Any built-in way of managing them... or maybe a plugin? I can't find googling anything like that.
     
  7. TimedExecute spawn at zero coordinate (spawn ch47scientists.entity), after which ch47 is dyed. :(
     
  8. DynamicPVP Is kind of a solution from another approach. Creates PVP zone at the event location. Based on the description the plugin doesn't work 100% perfectly tho.

    Has anyone found or is there even a command to call Chinook event? Like supply.call or heli.call. ch47.call doesn't work.
    ...maybe those are custom oxide commands and have to be added.
     
    Last edited by a moderator: Apr 8, 2018
  9. spawn ch47scientists - and you can use TimedExecute to set real-time for events to start using that command
     
  10. I assume it spawns at pointing location? Because calling it from RCON got me "spawned ch47scientists.entity[931716] at (0.0, 0.0, 0.0)" and they were stuck underground.
    Other than that they executed the event as intended if spawned above ground. Still would be nice to have a command to call the event at random location like the original server's event.
    [DOUBLEPOST=1523181436][/DOUBLEPOST]Ok, thanks for the plugin suggestion. That should work. Now I need to figure out how to randomize the spawn location for the Chinook event.
     

  11. Mine spawns underground with this How did you fix that?
     
  12. Did you spawn it from the RCON? Or F1? If you spawn it from RCON it spawns it at 0, 0, 0 coordinates, which are in the middle of the map underground. When I spawned it from the game console, it spawned at the point I was looking at.
    I didn't get a chance yet to test it, but I guess we could try to add coordinates at the end of the command to spawn it in the middle of the map only change the Z axis to above ground. It was X, Y, Z right?
     
  13. Yeah i can do it manually but as soon as it goes trough rcon it crashes, Im really shitty with coordinates tho
     
  14. Can try something like - spawn ch47scientists 0,0, 0,0, 50,0
     
  15. spawn ch47scientists 0,0, 0,0, 50,0
    spawn ch47scientists (0,0, 0,0, 50,0)
    spawn ch47scientists 0,0, 0,0, 50.0

    It wont matter what i do it keeps spawning at (0.0, 0.0, 0.0)
     
  16. Will have to research more how to spawn at coordinates or maybe someone else knows.

    Yeah... I can't find a way to spawn it above ground either. Insists on spawning it under ground no matter how I add the coordinates after it.

    TimedExecute can't seem to be able to do heli.call and supply.call. Probably same reason those commands don't work from RCON. And the spawn ch47scientists is a nogo... only works from F1.
    The best way imo would be to have a dedicated plugin for all three events now. We have plugins like HeliControl and EasyAirdrop.
     
    Last edited by a moderator: Apr 9, 2018
  17. Are you in noclip mode? If so, go out and try it again. I had that problem until I was out of noclip.
     
  18. We are trying to do it from RCON or through a plugin (TimedExecute Plugin). It spawns at 0, 0, 0 every time.
    Usually, I have no problems with spawning it on the ground where I look on noclip. There have been few cases where they don't end up dropping a crate for some reason and just fly away eventually.
    Problem is that this command "spawn ch47scientists" refuses to accept custom coordinates. Even inside F1 console, I can put coordinate and it still spawns where I look on the terrain.

    It would be nice if someone could tell how to trigger an event more directly. I know plugins can do that. I don't need any special features. Just server.events False and then trigger them if and when I want.
    P.S. btw server.events false does disable chinook too as far as I tested. But it disables heli and supply too. Those, however, can be activated from existing plugins separately. You can add it to command line +server.events false to disable on restart.
     
  19. We might have a fix.

    HeliControl
    Code:
    1.2.9
    -Added support for various Chinook (CH47) features:-Added config option: "Spawning - Disable CH47 default spawns"
    -Added config option: "Spawning - Automatically call CH47 between min seconds"
    -Added config option: "Spawning - Automatically call helicopter between max seconds"
    -Added config option: "Spawning - Automatically call CH47 if one is already flying"-Added chat/console command: "killch47" (requires permission helicontrol.killch47)
    -Added chat/console command: "callch47" (does not use the same cooldown & limit features as callheli, only requires permission helicontrol.callch47 and can be used freely)
    -Added chat/console command: "dropcrate" (drops ch47's crate, requires permission helicontrol.dropcrate)-Added "ch47" argument to "tpheli" chat/console command (requires permission helicontrol.tpch47, can be used as: /tpheli ch47)
    -Added "ch47" and "all" argument to "unlockcrates" chat/console command, to unlock CH47 crates (only) and all crates, respectively. If used with no argument, it will unlock only non-CH47 crates.
    I will have to test it tho.