

			*******************************
			**                           **
			**     UNIT UPDATER2 FOR     **
			**      CALL TO POWER 2      **
			**                           **
			*******************************




The unit Updater2 is a new version by Peter Triggs (with some ideas borrowed from Pedrunn) of his original unit Updater designed for the Cradle Mod.




I - INSTALLATION
    ------------


1) Copy the following files in the C:\Program Files\Activision\Call To Power2\ctp2_data\default\gamedata (you should back up the original files):

Units.txt
Updater2.slc


2) The following file must be copied in the language folder you use (C:\Program Files\Activision\Call To Power 2\ctp2_data\###language###\gamedata):

Updater2_str.txt (either the German, English or French one)

WARNING: if you play CtP2 in a language other than English, German or French, you have to copy either the English, German or French version of Updater2_str.txt into your language folder.

3) Open the file script.slc in the C:\Program Files\Activision\Call To Power2\ctp2_data\default\gamedata folder and add the following line at the end of the text:

#include "Updater2.slc"

4) Open the file Strings.txt located in your language folder (C:\Program Files\Activision\Call To Power 2\ctp2_data\LANGUAGE\gamedata) and add the following line at the end of the text:

import "Updater2_str.txt"




II - PLAYTEST VERSION UPDATE
     -----------------------

Each time you install a new ctp2_playtest version some files are overwritten in the process, you should thus open the script.slc (default\gamedata folder) and Strings.txt (LANGUAGE\gamedata folder) files and check if the lines #include "Updater2.slc" (script.slc file) and import "Updater2_str.txt" (Strings.txt file) are still at the end of the text. If not, add them again.




III - HOW TO USE THE UPDATER2
      -----------------------

Using the updater is very easy:

1 - When your great nation discovers a new advance allowing you to update your units a message is displayed, just follow the instructions in the message boxes.

2 - In the turns following this discovery you can still update your units individually by clicking on the sleep button. Select your unit (if the units to update are part of an army, it is better to ungroup them all in order to select them one by one, don't forget to group them again as soon as you have finished), click on the Sleep button, a self explanatory message is then displayed...



III - ADAPTING THE UPDATER2
      ---------------------

I have included in this zip the two worksheets I have used to prepare the conversion, this will ease your task if you want to adapt the Updater2 to another mod or change the update paths if they don't suit your taste or your needs (or both).

Changing an update path is really easy, edit the APOL_updater.slc and change the DATA ARRAYS. If you add a new update path, be careful to give your arrays numbers which are not used by another one (as the number 3 and 4 in the example).

If you want to change an update path, suppress an array if you don't agree with an update path or a part of the said update path :


Example :

In the following update path (Machine Gunner>Marine>Hover Infantry), suppress the four lines of the array number 4 if you don't want the Marine to upgrade to Hover Infantry

enadv[3]=AdvanceDB(ADVANCE_ADV_INFANTRY_TACTICS); 
OLD_UNIT_TYPE[3]=UnitDB(UNIT_MACHINE_GUNNER);
NEW_UNIT_TYPE[3]=UnitDB(UNIT_MARINE);
PER_UNIT_UPDATE_COST[3]=1000;

enadv[4]=AdvanceDB(ADVANCE_CHAOS_THEORY); 
OLD_UNIT_TYPE[4]=UnitDB(UNIT_MARINE);
NEW_UNIT_TYPE[4]=UnitDB(UNIT_HOVER_INFANTRY);
PER_UNIT_UPDATE_COST[4]=2500;


If you prefer the Machine Gunner to be updated to the Paratrooper, change the number 3 array like this:

enadv[3]=AdvanceDB(ADVANCE_ADV_INFANTRY_TACTICS); 
OLD_UNIT_TYPE[3]=UnitDB(UNIT_MACHINE_GUNNER);
NEW_UNIT_TYPE[3]=UnitDB(UNIT_PARATROOPER);
PER_UNIT_UPDATE_COST[3]=1400;

Remember to change the name of the new unit, the name of the advance triggering the update (which is not useful in our case as Paratrooper and Marine are both available with the same advance) and the cost of the update.


The Upgrade Paths I have chosen are detailed in the Updater2_UpdatePathWorksheet.TXT file included in this zip (the "Dead End" units are the units which have not been included into an update path because of their specificity or their lack of similarity with another family of units).

You can find all the units along with their cost, their code name and the code name of the advance enabling them in the file named Updater2_UnitWorksheet.txt in this zip.




Have fun!

Tamerlin/Jeff