From: Melbourne, Australia
Thanks guys. Maybe I need a another coffee, but Dave where is the "load/menu screen"? I am not familiar with that one. But anyway, is Steam still on 1.00.11158? Based on the picture above that appears to be the case. I guess the real question is what version should we be designing and testing scenarios for the Community on? The Steam version, if it is 1.00.11158, is ancient history given the numerous fixes the past several weeks. Ideally, we would design off of official builds not betas. But CMO is so new, maybe that is not the best way to design at the moment. Maybe I am wrong, but it appears a player's experience with a scenario will depend highly on which version of CMO that have installed. At least in the early days. A year from now, not so much of an issue.
The good news is that it doesn't really matter what game version you design a scenario on, at least not at the scale of changes we have seen since CMO release day. If the scenario is totally dependent on a particular mechanic that is changed it could upset balance, but the scenario itself will run fine--and when I say a mechanic that is changed, I mean something like the introduction of the CoW features or a large and pivotal new feature, not bug fixes and tweaks.
As an example, I develop scenarios on a bunch of different versions of CMO/CMANO from PE to betas to retail to Steam to CMANO for GameBoy(TM). So far the only issues have been due to me making mistakes, not mixing versions of the programs.
The only real constraint is that scenarios created in CMO cannot be loaded into CMANO.
DB updates have far more impact, but that again is mitigated by the system of manually upgrading scenarios to the latest DB, which allows you to roll back if there's issues.