Section N: SektorInfo.txt
SektorInfo.txt is the editable text file used with csek.exeP
to create SektorInfo.sekL
. Since SektorInfo.txt is not used by the program or module directly, an absence of it has no affect on the function of the module. Creating it is necessary only if you want to include sector information in your module with SektorInfo.sekL
files (by far the most technical part of creating a module).Creating SektorInfo.txt
To create a blank SektorInfo.txt file, right-click any unused space in you .gim folder, select "New", and select "Text Document".
Rename your new text document "SektorInfo.txt". From here, I recommend creating SektorInfo.sekL
and using Sektor EditorM
** to set all the available settings for each sector on the map.Editing SektorInfo.txt
Some sector information cannot be added to SektorInfo.sekL
using Sektor EditorM
. In these cases, the information must be included by editing a current copy of SektorInfo.txt and converting it back to SektorInfo.sekL
. I will begin with what cannot be added using Sektor EditorM
, and continue with a map of the rest of the information in SektorInfo.txt. Before editing SektorInfo.txt, you should always use rsek.exeP
to create a current copy of SektorInfo.txt from SektorInfo.sekL
so that SektorInfo.txt will reflect all changes made to SektorInfo.sekL
using Sektor EditorM
Each sector in your module is represented by one line in SektorInfo.txt. Each line has different parts, used for different pieces of information. The first part of each line is a character string which functions as the sector's name that appears in ABattleMap's title bar when a user hovers the cursor over the sector on the map. Following the sector name is a colon, which is then followed by nine sets of eight digits each. Each 8-digit set is called a long, and they are labeled "long1" through "long9" left to right. Each long may contain separate numbers, labeled according to the number of digits used: each set of two digits in a long is called a byte, labeled b1-b4 left to right, and each single digit I will call a nyble, labeled n1-n8 left to right.
Note that all numbers in SektorInfo.txt must be written as hexadecimal valuesQ
. Refer to section Q
for an explanation of hexadecimal values.IPC Value display location:
Long2 and long3 in each line define the location of the sector's IPC value display when a user selects "IPC Values" in ABattleMap's "View" menu.
Long2 is the location's X-value, or horizontal distance in pixels from the left side of the image. Long3 is the location's Y-value, or vertical distance in pixels from the top of the image. To identify the X and Y values of a specific location on the map, open Map.bmpD
in Paint.NET. Hover your cursor over a location where you would like the IPC value of your sector to be. The bottom-right corner of the Paint.NET window shows the X and Y values (respectively) of that location separated by a comma.
Convert each value from decimal to hexadecimalQ
, and then type them into long2 and long3 of the pertaining sector. For example, if your "X, Y" value for sector 1 is "1137, 879", then long2 of sector 1 should be "00000471", and long3 should be "0000036f".Pseudo-sectors
can include some information that does not pertain to a specific sector. This information is not represented by space on the map, but does exist in a line of SektorInfo.txt as a pseudo-sector. Pseudo-sector lines are structured in the same way as all sectors with a string (name), colon, and 9 longs, but each long in a pseudo-sector contains different information than the corresponding longs in normal sectors.
One type of pseudo-sector (the only one I know of) is used for defining at-war status criteria (used for convoy disruption). In this pseudo-sector, long1 is "00000080". Long2:b4 is the number of the aggressing power. Long2:b3 is the number of the sector which must be controlled by any power for the aggressing power to be considered "at war" with (afflict convoy damage against) power 1. Long2:b2 is the number of the sector which must be controlled by any power for the aggressing power to be considered "at war" with (afflict convoy damage against) power 2. Long2:b1 is the same for power 3, long3:b4 is for power 4, long3:b3 for power 5, and so on. For example, in the "Pacific 1940 v3.1" module, someone must control sector 192 (or C0 in hexadecimal) for Japan (power 1) to do convoy disruption damage to UK (power 4) or ANZAC (power 5), and someone must control sector 161 (or A1 in hexadecimal) for Japan to do convoy disruption damage to the US (power 2). Japan cannot do convoy disruption damage to China (power 3). In the module's SektorInfo.txt, this is shown with the following line:
atWarStatus Japan: 00000080 00a10001 0000c0c0 00000000 00000000 00000000 00000000 00000000 00000000The Rest:
The following is a map of what each location (in order) of each line in SektorInfo.txt defines (for normal sectors). Named features are references to fields in Sektor EditorM
- String- This is the name of the sector. Any white space between the last visible character of the string and the colon is ignored.
- Colon- This separates the string from the numerical codes
- Long1:b1- "01" is for land, "00" is for water
- Long1:b2- IPC value of sector
- Long1:b3- original owner of sector
- Long1:b4- defines type of pseudo-sector*; always "00" for normal sectors
- Long2- X-value of IPC value display location
- Long3- Y-value of IPC value display location
- Long4:b1- always "00" (as far as I can tell)
- Long4:b2- corresponds to "Convoiroute - All"
- Long4:n5- always "0" (as far as I can tell)
- Long4:n6- corresponds to "Flags - Convoi" ("1" is checked, "0" is not)
- Long4:n7- always "0" (as far as I can tell)
- Long4:n8- corresponds to "Flags - Oil", "Flags - SIPC", "Flags - SCVR", and "Flags - OCVR"*. Value for "Oil" is 1, "SIPC" is 2, "SCVR" is 4, and "OCVR" is 8. If more than one of these are applicable, add their values together.
- Long5:b1- corresponds to "Convoiroute - Special 4"
- Long5:b2- corresponds to "Convoiroute - Special 3"
- Long5:b3- corresponds to "Convoiroute - Special 2"
- Long5:b4- corresponds to "Convoiroute - Special 1"
- Long6:b1- corresponds to "Convoiroute - Special 8"
- Long6:b2- corresponds to "Convoiroute - Special 7"
- Long6:b3- corresponds to "Convoiroute - Special 6"
- Long6:b4- corresponds to "Convoiroute - Special 5"
- Long7:n1- corresponds to "IPCs - Special 6" (for power 8)
- Long7:n2- corresponds to "IPCs - Special 8" (for power 7)
- Long7:n3- corresponds to "IPCs - Special 7" (for power 6)
- Long7:n4- corresponds to "IPCs - Special 5"
- Long7:n5- corresponds to "IPCs - Special 4"
- Long7:n6- corresponds to "IPCs - Special 3"
- Long7:n7- corresponds to "IPCs - Special 2"
- Long7:n8- corresponds to "IPCs - Special 1"
- Long8:b1- always "00"
- Long8:b2- always "00"
- Long8:b3- always "00"
- Long8:b4- correspond to "Unit"
- Long9- always "00000000"
*This feature is new in ABattleMap version 0.80+
**This feature is new in ABattleMap version 0.80