From: Oslo, Norway
I've edited your quote above to represent what's happening behind the scenes. It's been my experience as a beta tester that it's a relatively frequent occurance that a new version is incompatable with older versions. PBEM games among the beta testers have to be restarted as the old file moves to the new version when it's written to the hard disk using the new version. The old version can't read it, no matter the coersion. And to answer your question I just now created a .31 version file and the .21 version successfully read it. I would post a .31 version file for you to play with but I fear my NDA blocks such a move by me at this time. In this case you'll just have to "take it on faith" that what I'm saying has any accuracy at all. Which I'm deeming "the religious approach". I'm listening to "The Who" while I type this. Implicates me as an old guy.
Sure, it makes sense for saved PBEM games that both players will need to be on the same version because changes have been made to rules and gameplay.
But for scenarios this makes little or no sense, how could scenarios be opened in newer version at all if that was the case? A scenario designer would need to break every one of their scenarios into parts like above, then load into into the new version, then repost to forums etc ... on every update. Designers come and go, and they can't be expected to do this.
Are the stock scenarios rebuilt on every new patch?
BTW, I really doubt the NDA would block you from posting a *scenario* edited in a new version and post for other to load. What it would most likely block is you even revealing there's a new version being tested - but that deed's already done
But you tested with .21 and it opened there so that's sorted, the problem is loading a scenario created in an older version into a newer version.
< Message edited by Shadrach -- 8/4/2019 10:10:01 PM >