I think he referred to versions updated to 1.00, the one with squashed thingy and the one fixed. So both would run correctly, no easy way to know which one you have. I really need to support him about version numbering. In open source world it's very disliked to overwrite new package with old version number. It creates confusion, it brakes distfiles servers etc (same filename, different checksum). I know there are no such problems here but still, imagine a person on dial-up (yes, they still exist) that downloaded a few MB fan mission around the time you updated it. No way to know which one you have. Minor version update is not a problem for a packager and it easily allows you to determine which version you have. Something like 1.0.1 update for 1.0. 1.0 -> 1.0.1 -> 1.0.2 - bugfixing 1.0 -> 1.1 -> 1.2 - new content/mission changes 1.0 -> 2.0 - redisigning bigger part of a mission That's only an example but it's really good habit to use such (or similar) scheme, even if it makes a life easier for just a few people. And of course big thanks for St. Lucia as a release for TDM 1.0, been waiting some time for this to replay this mission. For some reason I still remember it the most and as one of the best.