Deep rebuild question

[Mgellis]

Quick question...

Eventually, after a database has been updated enough, scenarios will require "deep rebuilds." The manual says that this resets platforms to their "pristine state" from the database. Does this mean that if you added aircraft and/or added stores to a magazine that these will be erased?

For example, in one scenario that I wrote the sub had torpedoes in the tubes, but its magazine for reloads was empty. It had room for about 12 more torpedoes. I added the torpedoes to the magazine, selecting one of the options already listed--as I recall, I had a choice of the Mod 0 or Mod 1 versions of the Mk 37 torpedo.

Okay, so if someone does a deep rebuild of that scenario in the future, will those torpedoes go "poof" and vanish (which would require someone playing the scenario to manually add them)? I'm hoping the answer is "no," that the contents of magazines will be safe from even deep rebuilds.

I suppose I could add notes in the scenario information about what was added to various magazines so players could rebuild them manually if they had to, but this seems terribly inefficient and tedious.

Thanks.

[Meroka37]

In that case you need to rebuild using a previously created delta INI file, it contains all deviation from DB including any change in magazines. Being still in former DB version you create the detal INI file, then you rebuild it to new DB version with use INI file option.

[Mgellis]

ORIGINAL: Meroka37

In that case you need to rebuild using a previously created delta INI file, it contains all deviation from DB including any change in magazines. Being still in former DB version you create the detal INI file, then you rebuild it to new DB version with use INI file option.

Quick clarification...

I can see if that if you added an entirely new magazine or weapon, a deep rebuild would erase those changes.

What if the only thing you have done is stock an existing magazine? To do this, I used the "Add Weapon Record" command. (For example, adding bombs, etc. to a carrier magazine so the aircraft have weapons available.) Or, in some cases, I merely changed the weapon count for a record that was already there (for instance, changing 0/12 torpedoes to 12/12 torpedoes). So I did not add a magazine or a mount, I just added or altered a weapon record. Do those go "poof" if you update the database?

Thanks.

[Meroka37]

In your example if you rebuild the scenario without INI file the torpedo magazine will go to 0/12, so that's why you need to use the Delta INI, there's not 7/12, 10/12 or  587/1000 magazines in the DB, so to be in the safe side I always use the delta file INI option during scenario rebuilding.

[Mgellis]

Okay, I think I understand. So every time I create a scenario, I should also create an .ini file with the Editor/SBR/Generate Delta Template command. Then add that to the zip file so people can rebuild the scenario if they have to?

Is there anything else that has to be done?

Thanks.

[Mgellis]

Related question...this means I can create all kinds of custom versions of platforms and SAVE them so that even with a deep rebuild, a player can still get to use them? They just need to rebuild with the ini file option? Am I getting this right?

Thanks. Sorry if these are kind of obvious questions...I'm not exactly an expert with databases.

[Mgellis]

Okay, I just want to say, assuming I am understanding what the Delta Template generator does...this is a freaking awesome game! There is definitely a learning curve here, but it's definitely worth it!

[Meroka37]

ORIGINAL: Mgellis

Related question...this means I can create all kinds of custom versions of platforms and SAVE them so that even with a deep rebuild, a player can still get to use them? They just need to rebuild with the ini file option? Am I getting this right?

Thanks. Sorry if these are kind of obvious questions...I'm not exactly an expert with databases.

Yes, if you rebuild with ini file you have your "own" platform playable with a any future DB, (as far as I know of course)

[smudge56]

[&:] man you completely lost me lol. It's amazing what you can do.

[Mgellis]

ORIGINAL: Blighty56

[&:] man you completely lost me lol. It's amazing what you can do.

Okay, if I'm understanding this right (someone please let me know if I'm wrong here)...

Command NOT ONLY lets you micromanage how many weapons are at air bases or on carriers, but...

it ALSO lets you tweak individual platforms by adding and deleting weapons and sensors, AND THEN (and this is the cool part)...

because these changes might be erased when you update the scenario to a new version of the database, it lets you save any changes you have made to a special .ini file (using the Editor/SBR/Generate Delta Template command) which will RESTORE the changes you made even after the updated scenario has been scrubbed by the new version of the database.

Is that cool or what?

[brassem]

As long as the assets are there, yes. The ini should restock them.

[smudge56]

Ah I see very cool.

[Dimitris]

ORIGINAL: Mgellis
Okay, if I'm understanding this right (someone please let me know if I'm wrong here)...

Command NOT ONLY lets you micromanage how many weapons are at air bases or on carriers, but...

it ALSO lets you tweak individual platforms by adding and deleting weapons and sensors, AND THEN (and this is the cool part)...

because these changes might be erased when you update the scenario to a new version of the database, it lets you save any changes you have made to a special .ini file (using the Editor/SBR/Generate Delta Template command) which will RESTORE the changes you made even after the updated scenario has been scrubbed by the new version of the database.

Yes, that is correct.

So next time you hear/read someone yammering "No DB editor! No DB editor!" when discussing Command, please bring this up.

Thanks!

[ExMachina]

Okay, if I'm understanding this right (someone please let me know if I'm wrong here)...

Command NOT ONLY lets you micromanage how many weapons are at air bases or on carriers, but...

it ALSO lets you tweak individual platforms by adding and deleting weapons and sensors, AND THEN (and this is the cool part)...

because these changes might be erased when you update the scenario to a new version of the database, it lets you save any changes you have made to a special .ini file (using the Editor/SBR/Generate Delta Template command) which will RESTORE the changes you made even after the updated scenario has been scrubbed by the new version of the database.

Is that cool or what?

It IS cool [8D] Thanks for summarizing it here.

This ability has allowed me to finally achieve an "historical" result in Sea of Fire scenario; removing the Sea Wolf reloads will prevent the Brits from instantaneously reloading their hex launchers.

[smudge56]

Noooo us poor brits.....[;)]