CustomMissions.pdf

(88 KB) Pobierz
Creating Custom Campaigns and Patrols
By Jackson Clouse
Outline
Creating Custom Patrols
Edit index.pkg
Add label in localization.txt
Create CGN file for newly defined patrol set
Create corresponding folder with EMS files in it.
Creating Custom Campaigns
Edit index.pkg
Create CGN file for newly defined campaign set
Create corresponding folder with EMS files in it
Creating Custom Patrols
Edit index.pkg
Index.pkg is a text file that can be found under the ‘missions’ directory of
your Enigma installation (i.e. C:\Enigma\missions\index.pkg). You may edit it
using Notepad or any other program that reads and writes text-only files. Each
line in the file follows the following basic format:
[Token]
[Data]
[Data]
[Etc]
Each token has its own unique set of data that it reads in, and each member of a
token set must be separated by a single tab. When editing this file, make sure
there is always a single tab in between each member. The tokens we will need
to change to add an additional set of patrol missions are ‘N’ and ‘P’.
The ‘N’ token is the header for the file. Its format is:
N [id] [package name] [number of patrol sets] [number of campaign mission sets]
A ‘P’ token is a patrols token. There is one token for every set of patrol missions
(one for Training, Combat, Random, etc.). The format for the ‘P’ token is:
P [campaign set index] [mission set index] [set name]
To add a new set of patrol missions, increase the number of patrols sets by one
on the ‘N’ token line and add a ‘P’ token line for your new set of patrol missions.
An example would be:
N
1
Single Player Package
4
6
P
0
0
TrainingPatrols
P
0
1
CombatPatrols
P
0
2
RandomPatrols
P
0
3
CustomPatrols
C
1
1
Retail_USA_Submarine
C
1
2
Retail_USA_Surface
C
1
3
Retail_IGN_Submarine
C
1
4
Retail_IGN_Surface
C
1
5
Retail_LFN_Submarine
C
1
6
Retail_LFN_Surface
Please note that in all ‘P’ token lines, the campaign set index must always be 0
for patrol mission sets.
Add label to localization.txt
In this step you will define the text that will appear in the Missions
dropdown box in the Patrols menu. First, open localization.txt, which is located in
your installation directory (i.e. C:\Enigma\localization.txt). Localization.txt follows
the following format for each line:
[tag] text
Each tag corresponds to some text in the game. Note that there must be a single
space between each tag and its corresponding text. In this case we are only
concerned with the following tags:
PATROL_LABEL_0_TOGGLE Training
PATROL_LABEL_1_TOGGLE Combat
PATROL_LABEL_2_TOGGLE Tactical
If you are using notepad, you may easily locate these tags by using the find tool
(Edit->Find… or Ctrl+F).
These tags follow the following format:
PATROL_LABEL_[mission set index]_TOGGLE [text label]
The mission set index in the tag corresponds to the one specified in index.pkg.
So, for example, if you defined
P
0
3
CustomPatrols
in index.pkg, then in localization.txt you would add the tag
PATROL_LABEL_3_TOGGLE Custom
Create CGN file for newly defined patrol set
In this step you will create a campaign (CGN) file that will correspond to
the name of the patrol set you specified in index.pkg. If the name of the patrol
set is CustomPatrols, then the corresponding CGN file will be named
CustomPatrols.cgn. To create the file, open the missions folder (i.e.
C:\Enigma\missions), right-click and select new->text document, and then give
the file the appropriate name (i.e. CustomPatrols.cgn). Next, you will need to edit
the file using notepad, or some other text-editing application.
A CGN file for a set of patrol missions uses tokens with tab delimited data
just like index.pkg. The tokens you will be using here are ‘P’ (file header), and
‘ML’ (mission line). The ‘P’ token follows the format:
P [campaign set index] [mission set index] [set name] [number of missions]
In this file the campaign set index, mission set index, and set name should be
identical to those specified in index.pkg. So, for example, if in index.pkg you
specified
P
0
3
CustomPatrols
then in CustomPatrols.cgn, the header would read
P
0
3
CustomPatrols
[X number of missions]
The header will then be followed by ‘ML’ tokens that correspond to the number of
missions specified in the header. ‘ML’ tokens follow the format:
ML
[mission index]
[mission name]
[mission description]
So, for example, if you specified four missions in the header, then the rest of the
CGN file would read:
ML
1
Custom Mission 1
Custom Mission 1 Description
ML
2
Custom Mission 2
Custom Mission 2 Description
ML
3
Custom Mission 3
Custom Mission 3 Description
ML
4
Custom Mission 4
Custom Mission 4 Description
This mission name is what will appear in the list of missions on the patrols select
screen. The mission description is intended to make the CGN file easier to read,
and it does not appear anywhere in the game.
Here is an example of a complete CGN file for a patrols campaign:
P
0
3
CustomPatrols
4
ML
1
Custom Mission 1
Custom Mission 1 Description
ML
2
Custom Mission 2
Custom Mission 2 Description
ML
3
Custom Mission 3
Custom Mission 3 Description
ML
4
Custom Mission 4
Custom Mission 4 Description
Create corresponding folder with EMS files in it
In this step you will simply create a folder in the ‘missions’ directory (i.e.
C:\Enigma\missions) with a name that corresponds to the name of the campaign
that you specified in index.pkg. So, for example, if you specified CustomPatrols
as the set name, then you would create a folder named ‘CustomPatrols’ inside
the missions folder (i.e. C:\Enigma\missions\CustomPatrols). This folder will
contain all the EMS files that you have created for the campaign according to the
missions file format document (‘MISSIONS FORMAT.doc’). All EMS files in the
folder must be named ‘mission-1.ems, mission-2.ems… etc), where the number
in the name corresponds to the mission index specified in the CGN file.
Creating Custom Campaigns
Edit index.pkg
This will follow mostly the same process as was done in creating the
custom patrols. In index.pkg, after the ‘P’ (patrol) tokens, you will find the ‘C’
(campaign) tokens. ‘C’ tokens follow the format:
C [campaign set index] [mission set index] [set name]
To add custom campaigns, you will not only have to add some C token lines, but
you will also have to specify a corresponding ‘CN’ (campaign name) token line.
The CN token line specifies that name of the campaign that will appear on the
popup menu that appears after selecting ‘Campaigns’ from the main menu. Note
that the popup will not appear unless more that one CN token exists, where the
first campaign is always the 1937 Enigma Campaign that ships with the game.
The CN token follows the format:
CN
[campaign set index] [name of campaign]
Also note, that when adding the C token lines that the mission set index can only
be numbered 1~6, where 1 and 2 are reserved for the USA faction, 3 and 4 for
IGN, and 5 and 6 for LFN. The mission set index you specify will correspond to
the different areas of the campaign select screen. Also, the campaign set index
must be 2 or higher because 0 is reserved for patrols and 1 is used for the 1937
Enigma Campaign that ships with the game.
So, an example of how you might modify index.pkg for campaigns would be:
N
1
Single Player Package
4
9
P
0
0
TrainingPatrols
P
0
1
CombatPatrols
P
0
2
RandomPatrols
P
0
3
CustomPatrols
C
1
1
Retail_USA_Submarine
C
1
2
Retail_USA_Surface
C
1
3
Retail_IGN_Submarine
C
1
4
Retail_IGN_Surface
C
1
5
Retail_LFN_Submarine
C
1
6
Retail_LFN_Surface
C
2
1
Custom_USA_Submarine
C
2
4
Custom_IGN_Surface
C
2
5
Custom_LFN_Submarine
CN
1
1937 Enigma Campaign
CN
2
Custom Campaign
Here, a new set of campaigns has been defined. ‘Custom Campaigns’ is the text
that will appear on the popup after clicking on ‘Campaigns’ from the main menu,
and from there the campaign select screen will have enabled the lower half of the
USA screen, the upper half of the IGN screen, and the lower half of the LFN
screen. Note that the numbers 1 ~ 6 simply tell the engine which part of the GUI
will correspond to which set of missions. Usually 1, 3, and 5 correspond to
submarine missions while 2, 4, and 6 correspond to surface missions. Also note
that in this example, the custom set does not define campaigns for 2, 3, and 6,
and therefore those corresponding areas on the campaign select screen will be
disabled. Since we have just added three campaigns to index.pkg, the total
number of campaigns must be increased from 6 to 9 in the header token line.
Create CGN file for newly defined campaign set
Creating the CGN file for custom campaigns follows the same process as
creating the file for custom patrols, however the content of the CGN file for
campaigns in quite different and contains much more information. Below is a list
of all the tokens and what they do. At the end of this section, there is an example
of a complete CGN file for campaigns.
‘C’ (Header)
Format:
C [campaign set index][mission set index][campaign name][number of missions]
Example:
C
2
2
USA Custom Submarine Campaign
19
This tells the engine that this file defines the missions for campaign set 2,
mission set 2, and there are 19 missions. The text ‘USA Custom Submarine
Campaign is just to make the CGN file easier to read, and does not appear in the
game anywhere.

Plik z chomika:

Inne pliki z tego folderu:

Inne foldery tego chomika:

Zgłoś jeśli naruszono regulamin