Feature Request: Weapons FREE Only in Patrol Area

[ThunderCBR]

I'd like to request an additional drop down in the mission doctrine area. Rather than doing a bunch of LUA scripting per patrol area, and additional weapons ROE of something like "FREE only in patrol area, otherwise TIGHT". Reason being is with realistic sub comms enabled, you cant set any mission to weapons free while they are in transit otherwise you risk a friendly fire incident. I'd like to set up patrol boxes where the captain or flight leader can assume anything in their assigned sector is hostile and weapons are free.

[blu3s]

You can obtain a similar result using Exclusion Zones marking any contact in the patrol area has hostile

P.S: The way to submit request is through this thread, thank you!

[ThunderCBR]

You can obtain a similar result using Exclusion Zones marking any contact in the patrol area has hostile

P.S: The way to submit request is through this thread, thank you!

Wow thats a brilliant solution!! Great use of the exclusion zone. Thanks for the suggestion!

[thewood1]

I have typically found its better to ask the question first before putting in a new feature request. It avoids cluttering the request thread excessively, as is a tendency.

btw, I always play with realistic sub comms on. But it means very detailed planning and deconfliction with other subs and surface ships. And in certain circumstances you might want the sub to ID before shooting, especially in shipping lanes before any type of shipping and air exclusion zones are announced.

One method I have used it create a waypoint path to the patrol zone. The path has weapons tight and the mission has free. And I have a waypoint right before the zone that switches everything to free and activates the mission through an event. There are several ifs, ands, or buts in it, but that's the basic concept.

[ThunderCBR]

Good solutions. It was really only an issue when I was working on a Soviet NorLant breakout with 30-40 SSN's transiting the GIUK gap. I mistakenly had weapons free turned on, and when I had the starting position randomizer script run it put a couple too close so they detected the unknown goblin and started firing. For my needs the exclusion zone idea is fine AND I added a check to the LUA randomizer script to make sure the subs are spaced further apart.