Worldmaps.xls

This set of 2DAs is used to define world [map]s. See the [map tutorial] for more information.

worldmaps worksheet

Column	Type	Description
ID	int	A number that uniquely identifies the entry (unless creating an M2DA override). ID numbers are listed from smallest to highest within a given file but do not need to be consecutive.
Label	string	The name that will be given to this map layout in the "Map" property's dropdown menu in the Designer Toolkit.
NameStrRef	int
MAP	string	The TGA image file that's used when displaying this map. Standard map size is 1024 pixels by 768 pixels.
TargetWpTable	string	references a worksheet in this excel file with a "target_wps_" prefix that determines which pins lead to where.
TargetWpTableID	int
TripsCounterTable	string	A table to show which trips should have a random encounter and which should not. There is one global counter for the entire game

terrain_types worksheet

Column	Type	Description
ID	int	A number that uniquely identifies the entry (unless creating an M2DA override). ID numbers are listed from smallest to highest within a given file but do not need to be consecutive.
Label	string
RandTable	string
RandChance	int	The chance for triggering any encounter in this terrain
RepeatVar	string	the module variable being used to store if encounters from this table have triggered or not (32 bit field)

map_pin_images worksheet

Column	Type	Description
ID	int	A number that uniquely identifies the entry (unless creating an M2DA override). ID numbers are listed from smallest to highest within a given file but do not need to be consecutive.
Label	string
Icon	string	Icon Image Name
Symbol	string

target_wps_* worksheets

Each worksheet lists the [area] resources accessible from the given map along both rows and columns, to create a grid with cells for all possible trips between the areas. The source location is listed in rows, the destinations in columns. Within each cell of the table is the [waypoint] that the player will arrive at in the target area.

As a simple example, consider a group of four areas named area_1 through area_4. Each area has an "arrival" waypoint in it named a#_wp1 (with the # replaced with the area's number). To set up the map so that every trip arrives in the corresponding area's arrival waypoint, you'd use this array:

Dest →	area_1	area_2	area_3	area_4
Source ↓
area_1		a2_wp1	a3_wp1	a4_wp1
area_2	a1_wp1		a3_wp1	a4_wp1
area_3	a1_wp1	a2_wp1		a4_wp1
area_4	a1_wp1	a2_wp1	a3_wp1

One could use this to set up more complex patterns, for example a mountain pass that starts the player at a different waypoint depending on whether he's arriving there from areas on one side of the mountain range or on the other side of the mountain range.

This doesn't allow the creation of chokepoints, eg forcing the player to go through the mountain pass area if they want to reach areas that lie on the other side. This will have to be implemented by using a script to enable and disable the appropriate map pins depending on which world map area transition the player has passed through. So in this example, exiting the mountain pass through an area transition at the western end would enable the map pins to the west of the mountain range and disable the map pins to the east of the mountain range.