CH47 Geting stuck on Deep Sea Boundary

Not sure if it is this plugin or one of the others on my server (we run 190 plugins), but this issue has popped up a couple times (and started today I believe, or I didn't notice it until today at least) where CH47s will get stuck on the boundary of the Deep Sea and do not despawn or move. It was a single chinook just a bit ago but there was a line of 5 of them earlier today. They seem to be the normal: spawn ch47scientists.entity that the server runs automatically. 

If i go in and use ent kill them, the Deep Sea closes immediately closes as if I ran the cmd to close it but the status shows open and players inside the Deep Sea can stay in the Deep Sea fine until they leave where they are then immediately killed upon exiting it (this has only happened once and I have not been able to recreate the scenario yet, so I dont know if it is related to this issue or a separate one).

• After using the Ent Kill cmd on the CH47, the Deep Sea disappears from the map and running the /Deepsea Status shows the Deep Sea still being open and the time remaining on it.
• Players in the Deep Sea are able to stay in there like normal until the Deep Sea closes like normal.
• Disconnecting from the server and reconnecting, shows the regular map without the Deep Sea. 
• On connecting with a secondary non-admin account, shows the regular map without the Deep Sea.
• Trying to cross the boundary to enter the Deep Sea does not do anything, the server acts like the Deep Sea is closed. 
• Attempting to reopen the Deepsea with either /deepsea open or force open, ends up with the status coming back as: "Busy=True" even after waiting 10-15 minutes. The only solution I have found to get the Deep Sea to open and close again has been a server restart. 

Hi

I have also noticed this... phenomenon.

I will investigate and let you know.

Regarding the deepsea not being accessible after ent kill - it looks like the ch47 are getting stuck in the deep sea portal. It is like a huge invisible box, so when you ran ent kill,  it targeted the box and removed it. 

Awesome thanks for the reply, I had a feeling it was something along those lines since as soon as i ran that command it immediately disappeared. I will run the CH47 despawn all command instead from here on out to hopefully avoid accidentally destroying the patrol box in the future. 

Changed Status from Pending to Work in Progress

@TritonianYeti  try the new .cs included in 1.0.3 update 

I installed the update and spawned 5 CH47s beyond the Deep Sea boundary.

The initial one I spawned beyond the portal boundary was removed by the CH47 fix with this in the RCON: "[DeepSeaCH47Fix] Killed CH47 + NPCs NetID=163881554"

The next 4 CH47s I spawned beyond the portal boundary all spawned correctly and then proceeded over the portal boundary without issue.

I think its ok, the idea is that they don't hit the magic invisible wall that's just past the point which teleports you to deep sea,  which in turns allow them to go through it, then that gets detected and triggers a kill on them. 

You will hopefully not see any more of them stuck as they spawn and fly off naturally over the coming day 

Here's a generated representation of what the deep sea portal is actually like, since the CH47 wasnt triggering entering the portal , it was just hitting the backing collider and gettin stuck there


In vanilla, that wouldnt be a problem, but in the plugin we drastically increase the height of the portal, to allow flying vehicles to get in (rather than getting killed for being outside map bounds)

Changed Status from Work in Progress to Closed

Changed Fixed In to 1.0.3