So, to get factual regarding scenario maintenance...

[Vincenzo_Beretta]

OK; since this is technical info, and for some reason the old thread got deleted, I'll repost it:

In the past, up to H3 3.6.3, there was a chronic problem with third-parties DB: if someone modified his own DB but failed to warn the community about the changes, an unsuspecting guy loading a scenario (both one downloaded from the net or even one he was working on) could meet any sort of problems without having a clue about their origin - this because the DB mis-match was not registered by the game and warnings were not given.

So, to prevent this, a safety feature has now been added: if there is even the slightest discrepancy between the DB originally used and the one now loaded, no matter if it is only a single character in a ship's name. This warning is given both if the altered platform(s) are used by the scenario *and* if they are not used. OK, I can understand this - and I'm happy with it, since it is a way to prevent some of the DB accidents that happened in the past.

This, however, will basically force all the DB and scenario designers to update their scenarios every time a new version of the DB they are based upon is released. If you are also the designer of the DB you will do it "at home", while if you are using the DB written by another player you must first download the new version and then update your scenarios and re-upload them on the hosting sites - doing this routine once in a month if DBs are updated once in a month, once every week if a guy decides to update his DB once a week.

I think that this should go in the technical FAQ. [:)]

[Anonymous]

[Deleted by Admins]