hello) i found strange bug) if i call Ch47 with default command - "server.ch47event", then the Chinook appears in the location specified in the plugin, flies to the guard drop-off location, and simply hovers above the ground, although it has nothing to do with the plugin, it doesn't have an OwnerID, but if you rename private void SpawnChinook() -> private void SpawnChinook123(), then this problem disappears)
BradleyGuards and default CH47Bug
Is this still a problem for you, i am not seeing this issue myself.
The problem is that this affects the default CH47 event, which should arrive from the end of the map, but it immediately appears at the Launch Site :(
I only use the Launch Site, so I don't know how the event behaves when using the plugin on multiple monuments.
Are you using a plugin like an event manager by any chance?
Merged post
Ok i see the issue you are facing, going to do some debugging to find what is going on get back to you soon.
Merged post
Ah, the problem is that command calls the chinook in at your location and 300m away. It will then try and find the closest landing spot which would be the drop off point for scientists at launch site. I would recommend either a plugin to manage spawning it in from the edge of the map like normal Rust events do to avoid this issue.
Merged post
You can also use the events console command to set the min and max duration for the event to start nativly if you need to override the vanilla spawn times.
print_server_eventsset_event_enabledset_event_min_delayset_event_max_delayIn fact, 300 meters is just information. I noticed that it appeared on the edge of the map, although the message about 300 meters was written. And with renaming the method in the plugin, everything seems to fall into place. The plugin works and default ch47 appears where it should appear.
and i dont using any plugin for this, absolutly default behavior events
Merged post
and I concluded that this command is executed at the start of the ch47 event, because initially I noticed a flying Chinook near the Launch Site, which simply followed the specified route from the plugin and hung in the air, since it was not called for the event, it was simply intercepted by the plugin, spawning in the plugin coordinates and giving it a route from the plugin
As mentioned, the command will call the Chinook to the nearest landing point, which in your case is the launch site, due to the landing zone being added via the plugin. As for pathing, that is controlled by Facepunch's base logic, not the plugin. Their system automatically selects the closest landing zone to where the Chinook spawns. I’ll need to look into a way to override or bypass this logic sometime this week.