[WAD] WCS Bug in Kashmir Fire Shoreline Scenario

[FMBluecher]

I was playing Shoreline with the newest build today and noticed some odd behavior--my CAP weren't actually firing their missiles. The reason given for this was that WCS was set to Weapons HOLD. I thought that was odd, and then went to idiot-check myself. Sure enough, both the Side Doctrine and the Mission Doctrine were set to Weapons TIGHT against air targets, exactly as it should be.

But then I realized that ALL of my units were behaving as though they were on Weapons HOLD regardless of the side or mission doctrine. The only units that were firing at all were those on which I manually allocated weapons to targets.

I quit and started it again as a standalone scenario (in case my campaign save was bugged), and the issue was still present. A save is attached. Check it out--the F-16s in the air won't fire at air targets, and the missile batteries on the shore won't either, unless you manually allocate weapons to targets.

[thewood1]

If you look at the individual units inside the group, the ROE is set for HOLD. I hit the button to reset the doctrine to follow the inherited ROE and that fixed that group. I reopened your save and went to side doctrine and hit the inherit button. It set all the units to the side ROE of TIGHT.

I then opened up a fresh Shoreline and all ROEs were also set to HOLD. There's a chance the author wanted that. I didn't read the briefing, but one of the first things I do is check the ROEs of all units when building missions and setting up plans to make sure ROEs are set or inherited properly.

[FMBluecher]

Ah, thanks! I've just never encountered a scenario before where the units didn't immediately go onto their mission or side WCS. Not a bug, then!

[thewood1]

Again, might be by design or a mistake. If the designer wants to make sure no one fires early, they might have set it that way on purpose. Maybe there's an event that kicks off a lua task to change ROEs.