[2.0.7 and 2.0.14] Scenario Containing Pre-2.0 Rails Fails To Load

[bob152637485]

Prior to updating my game to 2.0, I disabled all mods and created a fresh sandbox scenario. In this scenario, I placed all of my rail blueprints, so that I could use them as a visual guide for redesigning my new rail blueprint book for 2.0. I believe I had read that while the old rails would not be placeable in 2.0, the game would still maintain backwards compatibility for rails already placed. I then allowed my game to update to the latest 2.0.14, and attempted to open the scenario.

When I attempted to load the scenario, I got an error (see attachments). Thinking that perhaps the backwards compatibility period had already passed, I reverted the game back to 2.0.7 (the oldest 2.0 version available on Steam), and attempted the same thing again, with the same results.

I would have expected that upon loading the scenario, there would have been no errors. Furthermore, I expected that while I would be unable to place/build the old rails, they would have been allowed to exist and be fully functional having already been placed prior to 2.0.

This issue occurs every time without exception, and is fairly easy to reproduce. Simply try and load the attached scenario through the normal game interface, no mods enabled.

EDIT:
For completeness sake, I reverted the game back to 1.1.110 and attempted to reload the exact same scenario, no modifications made. This was able to work without any issue.

[Muche]

This is due to "Renamed `global` into `storage`" change in 2.0.

Updating scenario's sandbox.lua manually allows it to be loaded.

[bob152637485]

I just gave it a try, and your fix worked! Thank you very much!