Mmm units do not inherit WRA settings from other unit types, they inherit from groups, missions, or the general side WRA


Right. So what I'm saying is that in my giant scenario, when I set the WRA for 'do not use in self defense' for the artillery and MLRS units along the DMZ from the general ...

Okay, I think I know what's going on and that this may still be a bug.

I had run a small test scenario with North Korean artillery and MLRS along the DMZ within range of land units south of the DMZ. By clicking on 'do not fire in self defense' in the unit WRA, it worked just as mentioned in this ...

....so we're back to "wierd stuff that happens only on that gigantic scenario" ?


Lol. It appears so. Since the bug first appeared in 1676, for some reason I can't get this scenario to work right. I changed all the North Korean global WPA for the artillery and MLRS along the DMZ to do not use in ...

The case with the mortar is WAD. The mortar has self-defense set to max range, so that's why the weapon is firing. Change the self-defense range and it should respect the activation time. (At least it does on B1746)


I finally got home and was able to test my giant scenario as per your ...

And the case for the sub is also WAD, the (hostile) submarines are treated as opp targets regardless of the doctrine (that has been that way during at least 8 years now)


So regarding the scenario, check the WRA of the arty units, missiles, etc to make sure they are not firing in self-defense ...

Nikel wrote: Fri Oct 03, 2025 12:49 pm I think it is not.

Here is a small scenario that should demonstrate it?

Thanks Nikel. So it seems it's still a bug and I don't have to rebuild this monster scenario.

I heard that this is a scenario-specific issue. Is that your impression too ?


I think so. After the last patch, the bug that introduced ignored mission start times (1676) was fixed when I ran a test and played a different scenario. It only has persisted, as far as I know, in this one huge ...

If easy, can you check if this issue persists on the current public beta? (Build 1728.2)


Hi Dimitris. I finally got time to update to the new beta through Steam and try it (1728.2) and it's still not fixed.

However, like Nikel said, it appears that the missiles (Scuds, Nodongs etc.) located ...

Tred did not come back to comment.


Sorry. I've been busy. Thanks for looking into this.


So, is this a simulation issue or scenario design flaw ?


This is a (massive) scenario I built almost two years ago. But I never had any problem with enemy units not obeying their mission start times ...

I'll try changing it when I get time Nikel. Thanks.

But that was never an issue before, so if it is, I'd wonder what changed in 1676 and 1706. Never had this problem until now. :/

Anyone? Anyone? Lol.

Has anyone else had a chance to look at this monster scenario of mine and have any ideas what is going wrong in the latest update?

Thanks.

It is a monster of a scenario. One day I hope to actually be able to play it through. Lol. It runs slow, but never had this issue before.

I wondered if opportunity targeting was making the missions fire prior to mission start time. Doesn't seem to be it. That would be a different bug. But there are ...

Okay, I don't know what's going on here. Below is a very large scenario I created a long time ago with a little bit of everything in it and designed to play in my micro-managed style.

In the scenario you'll notice that North Korean missile strikes, ground incursion, artillery barrage etc. are not ...

Hi Blue. Did you mean that this was supposed to be fixed for 1706? Or the next official update? I recently upgraded to the 1706 beta but it's still happening to me on there.

Thanks.

Thank you for the prompt response Dimitris (and thank you for moving this to the general forum from tech form, where I should have posted it originally).

So before I get into trying to clarify my gripes, let me say that I love you guys, the work you do, and I love the game. I have since I bought ...

Hi Blu3s.

The latest bug in the newest update I've already posted in the tech forum and has been marked as fixed for the next update (Mission start times being ignored).

And all the previous annoying bugs with each new update for the last year have all been fixed when the next updates come out ...

Hi all.

I understand that every major new update is bound to include all new bugs and glitches. But is it possible to just have one build, focused on extensively, to get rid of all bugs and make it as glitch free as possible and keep it up so some of us can just stick with it instead of new ...

Thanks everyone. I looked at my big personal scenario and it appears other missions (A ground incursion I have set up and an artillery barrage) are also not waiting until their mission start times anymore either. I assume it's all the same bug.

Is nobody else seeing this problem? Makes me think I'm missing a new mission setting I don't know about or something.