RE: Maintenance of ANW scenarios
Posted: Mon May 22, 2006 7:27 pm
Let me see if I understood.
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 everytime a new version of the DB they are based upon is realased. 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. Is this correct?
One last thing:
This is a new feature of the game to me, since I have only played Harpoon 3 up to 3.6.3. Where I can ask about technical question (both before and after the new edition is realased) if not on this forum?
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 everytime a new version of the DB they are based upon is realased. 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. Is this correct?
One last thing:
ORIGINAL: VCDH
Herman, you really should come and ask us about these things if you don't know ok?
This is a new feature of the game to me, since I have only played Harpoon 3 up to 3.6.3. Where I can ask about technical question (both before and after the new edition is realased) if not on this forum?