Their descriptions and functions. We want to learn the functions of all the campaign files and describe them as through as possible so we gain greater understanding of the campaign and how it works.

The following list is taken from SuperPAK v4.2 campaign/save/ directory.

atc.ini

attrit.pri

Auto Save.cam, .frc and .his

The default automatic saves of campaigns. These files should be deleted before new theater is released.

cas.pri not used AFAIK

AFAIK it “was” suppose to change to different priority according to how campaign goes, but wasn't done .

DEFAULT.idx

DEFAULT.wch

Defense.pri

not used AFAIK

AFAIK it “was” suppose to change to different priority according to how campaign goes, but wasn't done .

doctrine0.txt doctrine0 through 7

Element.b

Element.db

Element2.db

Emerganc.b

END.B

f0.ia f0 through f13

Falcon4.AII

MaxFlymissionNoThreat

Increasing this to 100 boosts up mission tasking.

FALCON4.RT

FALCON4.TT

FEATURE.B

FLEVENT.DB

Flight.db

FLIST.TXT

FORDEND.DB

FORDEVT.DB

FORDNCE.DB

FORDWEAP.DB

Header.b

header.db

Instant.cam

Instant action file, just the ground objects. No aircrafts or ground units.

Intdict.pri

This is the primary file of the three that only works (intdict , defense, atrit , cas. pri

AFAIK it “was” suppose to change to different priority according to how campaign goes, but wasn't done .

kneemap.gif

1024×1024 gif image of theater map. More details see Kneemap page.

<theater>.idx

Index numbers list of all the theaters objective names.

<theater>.NAM

<theater>.pak

The PAK area image, seen on campaign when prioritizing the PAK areas.

<theater>.tc

<theater>.THR

Created by PathMaker utility, it shows where the roads and features are.

<theater>.tm

<theater>.wch

Strings of the objective names, use WitchFix to convert into readable text format.

Loadout.b

LOADOUTH.B

m0.ia m0 through m4

mission.dat

MISSION.GBD

NoSquad.b

OBJECTIV.B

OFFENSE.PRI

PackHead.b

PElement.db

PHEADER.DB

Pilot.db

related.db

Results.db

RoE.b

save0.cam

Main campaign objectives, ground units, squadrons and misc datas file.

0 is the first campaign, ie top, considered to be thea easy one (but really depends on the file contents laid out by campaign creator, top most campaign slot don't necessarily mean its the most difficult one, but usuall is heh).

save0.tri

Trigger file for first campaign, controls all kinds of campaign flow and the final objectives how to achieve a victory.

save1.cam / tri

Second campaign, ie middle.

save2.cam / tri

Third campaign, ie bottom.

SITUATE.B

SQUAD.B

stations.dat

Controls the Tacan. For example:

# Kimpo - ex Kimpo (Gimpo) 
276 083 X 14 25 1 109.9 
--------------------------- 
-#: Name of the airbase
-276: CampID of the airbase (into Tacedit objectlist view)
-083 X: TACAN channel
-14:It is a sequential no. that you choose for each airbase and that is linked to the CampID via this file
-25: TACAN Range (Nm) 
-1: Emmitter Type (always 1) 
-109.9: ILS frequency

STEERPT.B

STEERPTH.B

Strings.idx

Index list for the campaign strings.

Strings.wch

Campaign strings, when using WitchFix to convert into text file, it can be edited to change Korea names to theater specific ones.

Support.b

taceng.db

TASK.GBD

teplanes.lst

List of all aircrafts and their ID's etc data. For TE only?

teunits.lst

te_new.tac

The Tactical Engagement file. Can have only two teams. No ground forces are saved to this file, this is the master TE file.

THREAT.B

Threats.b

tmp.frc

tmp.his

validac.act

Aircrafts available in campaign (also TE?), add 8888 value and then they are available.

voicerange.dat

Weather.b

*.dfs

Dogfight files?