|
hermanhum -> Clarification of Database changes for 3.7.2 (11/9/2006 10:41:45 PM)
|
quote:
ORIGINAL: VCDH HERE
Weapon Record Import/Export
The export feature will work as long as the DB version stays consistent. Should there be any changes to the mount/magazine/weapon records in the scenario then you’ll have to rebuild and then manually make your weapons changes again. Most of the time you’ll be able to get away with using your original import file because there is no changes to the weapon record ID. If there is however, you’ll have to start from scratch as the game engine will not rebuild due to discrepancy (part of the anti-slug protocol).
This affects scenarios more than databases but it is up to the DB author to ensure that the loadouts in ammo dumps are not corrupted. This can have a fatal effect in GE preformance if the scenarios and their weapon export files are not kept up to date.
[snip]
Rebuild All Your Scenarios
After you’ve made your DB changes, make sure to rebuild all your scenarios. There’s been several bugs fixed that require you to rebuild the scenario for the fixes to take effect.
In short, rebuild first, then make your changes, then rebuild again. Be sure to save your weapon export file to save the time and trouble of having to manually input ammo loadouts all over again.
Is it possible to elaborate further on these items?
Are there any allowable changes to the Mount/Magazine/Weapon Record entries that will not corrupt the Export Weapons Edit function?
For example, if we change the Rate of Fire on a Weapon Record, will this have disasterous consequences? Version number? Max Weapons possible? Actual Weapons carried?
quote:
but it is up to the DB author to ensure that the loadouts in ammo dumps are not corrupted
Again, what changes might corrupt ammo dumps? I can imagine that the presence of a weapon in one version of the DB and its absence in a later version could cause a problem. Is this the full extent of the possible corruption? Are there other factors which editors should be aware?
|
|
|
|
