Maybe there is a misconception. The Community scenarios are not the responsibility of the developers. They were all (all 400+ of them) developed by users and distributed. They didn't come with C:MANO. To blame the developers for some of them not working is unfair.
To get the ones that don't to work will probably require the developers of those scenarios to do a little work and then have a "pack" compiled and added to over time, just as the current one has been. I would expect that will start happening. Unfortunately some of the scenario authors have kind of vanished, as has been evident when questions or issues come up with previous C:MANO updates. Maybe someone will adopt those.
I think "CF" was way over the top considering the above, but you're entitled to your opinion.
Well, if they hadn't used the community scenario pack to advertise compatibility with CMO, and also if a staff member hadn't uploaded the contents of said pack into the CMO Steam Workshop w/o testing compatibility of same...I would have given them a pass, as you said I should have done.
They're going to fix it, so that's fine. Just noting why I didn't give them a pass on the community scenario pack stuff. Community scenarios not in the pack and/or not uploaded into CMO's section of Steam Workshop do fit the 'not responsible for' description you noted, IMO.
EDIT: For example, go pull Caribbean Fury 1 from the CMO Steam Workshop, and try to load it into CMO. Look who uploaded it.
Again, they're going to fix it, I'm just pointing out why I thought it was important to not just 'give them a pass' on them.
< Message edited by mavfin -- 11/15/2019 11:06:19 PM >