You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
OS: Windows 10 Pro 1909 Version: 20.05 Commit/Build:a137181
The check boxes in the scenario editor for industry opening/closing are inverse of their actual setting.
I noticed while playing an old favourite scenario of mine (involving delivering one million goods) that the central factory (and the only one on the map) decided to shut down. Soon after, a Steel Mill that I was actively servicing also shut down. I had modified the scenario prior to playing and double checked that the boxes for industry opening/closing were unchecked.
I opened the scenario in vanilla, and noticed both check boxes were checked. I unchecked them, saved, and opened the scenario in OpenLoco. Lo and behold, both boxes are now checked in OpenLoco.
Steps to reproduce:
Edit a scenario in OpenLoco, set industries to be able to close/open. Save scenario.
Open the same scenario in vanilla. Notice the check boxes for industry opening/closing are unchecked.
Is the issue reproducible in Locomotion (vanilla)?
No.
Screenshots / Video: Vanilla OpenLoco
The text was updated successfully, but these errors were encountered:
OS: Windows 10 Pro 1909
Version: 20.05
Commit/Build: a137181
The check boxes in the scenario editor for industry opening/closing are inverse of their actual setting.
I noticed while playing an old favourite scenario of mine (involving delivering one million goods) that the central factory (and the only one on the map) decided to shut down. Soon after, a Steel Mill that I was actively servicing also shut down. I had modified the scenario prior to playing and double checked that the boxes for industry opening/closing were unchecked.
I opened the scenario in vanilla, and noticed both check boxes were checked. I unchecked them, saved, and opened the scenario in OpenLoco. Lo and behold, both boxes are now checked in OpenLoco.
Steps to reproduce:
Is the issue reproducible in Locomotion (vanilla)?
No.
Screenshots / Video:
Vanilla
OpenLoco
The text was updated successfully, but these errors were encountered: