[1567.6] NFZ Baltic 22 - Russia becomes hostile when loading saved game

[stolowski]

Hi,

I'm not sure if this is a bug: every time I load the attached savefile of Baltic 22 scenario the message log says "Russia is now HOSTILE to NATO" for no apparent reason (hostilities didn't occur when I was saving this game) and when unpaused, my units start firing. I found out that marking all Russian units as "unfriendly" before unpausing works around the problem.

I've a vague memory of somebody else reporting similar problem not long ago... Is this a bug, or a problem with the scenario?

[Stanley_The_Rolmate]

It's because the strike mission 'Baltic AP' has two Russian targets.

[Swant]

I hade the same problem with the NFZ scenarios. I think this happens in showcase Icebreaker aswell

[stolowski]

It's because the strike mission 'Baltic AP' has two Russian targets.

But that's odd. Nothing happened before saving. If after loading and unpausing I mark all Russian units as unfriendly then, it's all fine after unpausing. Saving the scenario again in this state and loading it brings the problem back. It's like the act of saving-loading changed posture.

[Stanley_The_Rolmate]

If you disable the 'Baltic AP' mission then save and load the posture will not change. If you have a unit added as a target to an active strike mission, command wil change the posture to the unit's side to 'hostile' when you load a save for some reason.

[Knightpawn]

The real question is, does the side that turns hostile for me, also starts to treat me as hostile? For example, I might want to schedule a strike mission with take off or ToT some time down the road. Would this cause the opponent to treat me as hostile from the moment the mission is set up while waiting for take off? Or the behavior of the other side is independent?