|
JWE -> RE: DaBigBabes Release (11/22/2010 12:36:35 PM)
|
quote:
ORIGINAL: Bliztk
Do you have a file with a changelog ? Ok more or less everything, but something especific [;)]
I think we are going to start a DaBigBabes scen 28, and need to familiarize myself with the changes from stock
No changelog. There's literally thousands of changes. But this is the basis statement.
BabesLite Scen026 is standard Scen001 - BabesLite Scen027 is standard Scen006 but with:
Classes and Ships Many additions to historical OOB (both sides). More and different kinds of ARDs, tenders, transports, auxiliary trawlers, yard oilers, sea trucks, lots of smaller one-of-a-kind ships. Arrival dates and arrival locations vetted and adjusted. Submarines all have the split-tube model for more accurate combat results.
Devices Naval Guns, DP Guns, and ship borne AA Guns, vetted and data (Acc, Pen, Eff, Rng) adjusted for uniformity, relative comparability, and better fit (ioho) to the different combat algorithms. Load Costs adjusted for torps and mines to give better reload flexibility.
Everything else Aircraft Airgroups Locations Leaders Pilots AI/Production, is same as in stock.
DaBigBabes;
Classes and Ships Includes all BabesLite, but with many more additions to historical OOB (both sides), particularly late-war arrivals of warships, transports, landing craft, etc, suitable for Zipper, Buccaneer, Downfall, etc. File contents have been compacted and moved around. Additional carriers and their airgroups are included. Using DBB Class and Ship files REQUIRES use of the corresponding Airgroup (wpgxxx.dat) files. Inputs provided by Don Bowen, Harald Velemans, Kereguelen, Buck Beach, Andrew Brown, Central Blue, Kitakami, mikemike, and many others (apologies for forgetting names Im old, and my memory is
what?).
Devices Includes all BabesLite, plus: Beyond the support infrastructure and TO&E tweaks, BigBabes uses some code allowable stuff to redefine things according to our vision of reality; it has two expressions, Type = Engineer and switch = Shore Party.
(1) Naval devices All data elements vetted and data adjusted for uniformity, relative comparability, and better fit (ioho) to the SurfCom, AACom, SubCom, ASWCom, combat algorithms.
(2) Land devices (a) Many new Eng types and NavSup types (both sides) to support the new TO&E paradigm. (b) Changes to LC and firepower of Squad-type devices to support the new TO&E paradigm. (c) Changes to LC and firepower of Vehicle and AFV-type devices to support the new TO&E paradigm.
(3) Engineers An Eng unit can always build, but if it has Anti-Armor <1, it cannot reduce forts. If it has Anti-Soft <9, it cannot AV. If it is named construction labor, but is a Type = 23 squad, with no a-a , or a-s, it wont do squat. There is a 7-way matrix of different Eng squads that represent a mix of abilities; build stuff, reduce forts, able to AV, some of the above, none of the above. DaBigBabes uses this matrix (according to our appreciation as to how it falls out) to help limit in-game tempo, by limiting in-game infrastructure.
(4) Shore Party Shore Party is a sub-set of NavSup. Currently NavSup does many things that are not appropriate to the stock devices. Shore Party devices, and a skoosh of code that lets them give an unload bonus, assist in loading/unloading but do not assist in repairing or rearming, thereby allowing the amount of NavSup to be dramatically reduced and limited to its more normal functions.
Airgroups Basically as in stock, but with additions/changes to conform to the added/relocated Classes/Ships. Vetted by Timtom. DBB Airgroup file is necessary with use of DBB Class and Ship files.
Locations.
(1) TO&Es Many changes made in order to subsume the Device changes and to adapt the unit totals to the requirements of island stacking limitations and transport ship loading/carrying capacity considerations.
(2) OOB The basic combat OOB is unchanged, however many Allied units are aggregated and moved (which is why the AI wont work for the Allies) in order to make room for several hundreds of changed/additional units. The changes involve a major paradigm shift with respect to how Base Forces, AvSup, NavSup, Engs, are handled. Basic Japanese OOB substantially unchanged, but has significant TO&E tweaks and many additions.
(3) Base Forces Completely redefined. Many (most) have been removed but are buildable from their component Eng and Port/Base Maintenance Bns. Capabilities depend on relative mix of NavSup/AvSup/Shore Party/Eng/Labor devices.
(4) Aviation Support Both the number of units and the amount of AvSup in a unit have been dramatically reduced. At least 50-60% reduction in amount of AvSup for both sides.
|
|
|
|
