Reckall
Member
DB2000 is often subjected to “micro adjustments”, changes in the data which are not recognized by a new version number. To give you an example, the current “6.5.24” version actually covers three different set of files.
- One dated Feb, 6th 2005
- One dated Feb, 11th 2005
- One dated Mar, 10th 2005
By opening the .zips you can easily see that the size of many .dat files is different, even if the official version remains the same.
The reason why these changes are unannounced was discussed some time ago. Basically the rationale was that should the version go up for every small adjustment we'd be up to 6.100.100 by now.
However, be advised that changing the data within a .dat file COULD lead to problems with scenarios written using a different version of DB2000 – and this includes versions which do have the same version number, and so *only apparently* are the same database.
For example, if you download the Feb, 6th version of DB2000 6.5.24 and do build a scenario, and then pass the scenario to someone who downloaded the Mar, 10th version, the scenario, it is possible that crashes will occur, due to DB mismatches.
Generally speaking, scenarios found on HHQ are always adjusted for the latest version of DB2000. Anyway, just to avoid a possible point of confusion and to reduce the possible causes of crashes when investigating a scenario’s malfunctions, when someone reports a crash while checking/playing your scenario, always verify that you both are using the same version of DB2000 *down to the same date on the files*, just to be sure.
Nice Harpooning, and may the muse of imaginary wars always be with you!
Vince
[Edited on March, 11th 2005]
- One dated Feb, 6th 2005
- One dated Feb, 11th 2005
- One dated Mar, 10th 2005
By opening the .zips you can easily see that the size of many .dat files is different, even if the official version remains the same.
The reason why these changes are unannounced was discussed some time ago. Basically the rationale was that should the version go up for every small adjustment we'd be up to 6.100.100 by now.
However, be advised that changing the data within a .dat file COULD lead to problems with scenarios written using a different version of DB2000 – and this includes versions which do have the same version number, and so *only apparently* are the same database.
For example, if you download the Feb, 6th version of DB2000 6.5.24 and do build a scenario, and then pass the scenario to someone who downloaded the Mar, 10th version, the scenario, it is possible that crashes will occur, due to DB mismatches.
Generally speaking, scenarios found on HHQ are always adjusted for the latest version of DB2000. Anyway, just to avoid a possible point of confusion and to reduce the possible causes of crashes when investigating a scenario’s malfunctions, when someone reports a crash while checking/playing your scenario, always verify that you both are using the same version of DB2000 *down to the same date on the files*, just to be sure.
Nice Harpooning, and may the muse of imaginary wars always be with you!
Vince
[Edited on March, 11th 2005]
Last edited: