GEODATA.DAT - Revision history

Hobbes at 04:39, 23 July 2013

2013-07-23T04:39:38Z

← Older revision		Revision as of 04:39, 23 July 2013
Line 131:		Line 131:
	* [[Battlescape Map Generation]]		* [[Battlescape Map Generation]]
	[[Category:Game Files]]		[[Category:Game Files]]
			[[Category:Enemy Unknown/UFO Defense]]

Bomb Bloke: Table too wide for 1024x768 users

2011-03-17T12:14:15Z

Table too wide for 1024x768 users

← Older revision		Revision as of 12:14, 17 March 2011
Line 66:		Line 66:
	9: Mars 9: Artefact Site Stage 1		9: Mars 9: Artefact Site Stage 1
	10: Artefact Site Stage 2		10: Artefact Site Stage 2
	11: Cargo Ship Stage 1 & 2 (Check [[MISDATA.DAT#20-21\|MISDATA[20-21]]] ~~for which)~~		11: Cargo Ship Stage 1 & 2 (Check [[MISDATA.DAT#20-21\|MISDATA[20-21]]]
	12: Port Attack		12: Port Attack for which)
	13: Island Attack		13: Island Attack
	14: Colony Stage 2		14: Colony Stage 2

Bomb Bloke: Table

2011-03-04T00:09:41Z

Table

Show changes

Bomb Bloke: /* Structure */ Clean up & corrections - one offset left undocumented!

2010-06-28T06:21:10Z

Structure: Clean up & corrections - one offset left undocumented!

← Older revision		Revision as of 06:21, 28 June 2010
Line 60:		Line 60:
	21: Colony Stage 1		21: Colony Stage 1

	<b>12-~~<i>~~XX~~</i>~~/0C-~~<i>~~XX~~</i>~~:</b> ~~The next~~ [0-1]*[2-3] ~~bytes list~~ the [[MAPS_Terrain\|map modules]] used to build the battlescape. Reads in order from west to east, north to south. For example, in the case of the largest map (~~50x50~~), this list would be 25 bytes.		<b>12-''XX''/0C-''XX'':</b> A byte list of length [0-1]*[2-3], which details the [[MAPS_Terrain\|map modules]] used to [[Battlescape Map Generation\|build the battlescape]]. Reads in order from west to east, north to south. For example, in the case of the largest map (60x60), this list would be 36 bytes (offsets 12 through to 47).

	Values of 253/254/255 mean that the a module does not need to be placed in that area because a large 2x2 module (eg. An X-Com hangar) has already covered it.		Values of 253/254/255 mean that the a module does not need to be placed in that area because a large 2x2 module (eg. An X-Com hangar) has already covered it.

	<i>I'~~ve often observed~~ the ~~Tactical engine partly generating~~ it's own ~~maps~~, ~~so there must~~ be ~~a way~~ to ~~have some - or~~ all ~~- of these values ignored~~.		<b>48-''XX''/30-''XX'':</b> A byte list of length [0-1]*[2-3], one for each map module to be loaded by the game during [[Battlescape Map Generation]] (as detailed at offset 12). A byte here will be set to 1 if the [[ROUTES\|RMP file]] for that module is to be loaded, or 0 if it is not. This is determined by whether X-COM/alien craft exist within the modules - those modules with craft will not have their own RMP files loaded (instead, the craft route nodes will be added to the [[ROUTES.DAT\|combined table]] once all other nodes are in there).

	~~- [[User:Bomb Bloke\|Bomb Bloke]] 19:21, 6 February 2008 (PST)</i>~~		In the case of the largest maps (60x60), this list will be 36 bytes long (offsets 48 through to 83).

	~~...~~

	~~<b>37-83/25-53:</b> These values are currently unknown, but they all seem to flag as either 0 or 1.~~

	~~<i>I thought one of them might determine if victim UFOs had been shot down or not, but I can't seem to see any consistant values that would indicate that.~~

	~~Some might have something to do with~~ the ~~units present - Although this wouldn't account for all values, I can't think~~ of ~~anything else at the moment.~~

	~~- [[User:Bomb Bloke\|Bomb Bloke]] 19:21, 6 February 2008 (PST)</i>~~

	~~This is~~ the ~~RMP~~ (~~or LZ depending on how you look at it~~) ~~flag. It says if the craft or ground RMP file is used. --[[User:BladeFireLight\|BladeFireLight]] 18:45~~, ~~14 March 2010~~ (~~EDT~~)

	...

	<b>84/54:</b> Amount of craft to be placed on the map.		<b>84/54:</b> Amount of craft to be placed on the map.

Bomb Bloke at 08:03, 27 June 2010

2010-06-27T08:03:35Z

← Older revision		Revision as of 08:03, 27 June 2010
Line 1:		Line 1:
	Created in the MissDat folder when you start a battlescape mission, also copied to the savegame folder of choice when saving mid-mission. Primarily used for [[Battlescape Map Generation]] and to determine which [[~~TERRAIN~~\|MCD files]] to load.		Created in the MissDat folder when you start a battlescape mission, also copied to the savegame folder of choice when saving mid-mission. Primarily used for [[Battlescape Map Generation]] and to determine which [[MCD\|MCD files]] to load.

	File is 92 bytes long for both UFO and TFTD. Values are presented according to byte offset (0 to 91) followed by the equivalent hex offset (00 to 5B) in <b>bold</b>.		File is 92 bytes long for both UFO and TFTD. Values are presented according to byte offset (0 to 91) followed by the equivalent hex offset (00 to 5B) in <b>bold</b>.

BladeFireLight: /* Structure */ Flags Array explained.

2010-03-14T22:45:44Z

Structure: Flags Array explained.

← Older revision		Revision as of 22:45, 14 March 2010
Line 77:		Line 77:

	- [[User:Bomb Bloke\|Bomb Bloke]] 19:21, 6 February 2008 (PST)</i>		- [[User:Bomb Bloke\|Bomb Bloke]] 19:21, 6 February 2008 (PST)</i>

			This is the RMP (or LZ depending on how you look at it) flag. It says if the craft or ground RMP file is used. --[[User:BladeFireLight\|BladeFireLight]] 18:45, 14 March 2010 (EDT)

	...		...

BladeFireLight: /* Structure */ Validate Asumption

2010-01-06T02:33:18Z

Structure: Validate Asumption

← Older revision		Revision as of 02:33, 6 January 2010
Line 30:		Line 30:
	<i>*1 Requires maps "Interc" and "Fires". These don't exist normally, though XcomUtil adds versions similar to the SkyRanger and Lightning.</i>		<i>*1 Requires maps "Interc" and "Fires". These don't exist normally, though XcomUtil adds versions similar to the SkyRanger and Lightning.</i>

	<i>*2 Requires maps "Barracud" and "Manta". These don't exist normally, though XcomUtil adds versions similar to the ~~??? and ??? (~~Triton and Hammerhead ~~I assume, but I haven't tested).~~</i>		<i>*2 Requires maps "Barracud" and "Manta". These don't exist normally, though XcomUtil adds versions similar to the Triton and Hammerhead </i>

	<b>8-9/08-09:</b> Alien craft type (ignore this if not a UFO mission). Uses the above values.		<b>8-9/08-09:</b> Alien craft type (ignore this if not a UFO mission). Uses the above values.

Bomb Bloke at 02:51, 2 October 2008

2008-10-02T02:51:59Z

← Older revision		Revision as of 02:51, 2 October 2008
Line 37:		Line 37:

	<b>UFO</b> <b>TFTD</b>		<b>UFO</b> <b>TFTD</b>
	0: Jungle 0: Seabed ~~Trash~~		0: Jungle 0: Seabed
	1: Farm 1: Pipes		1: Farm 1: Pipes
	2: Forest 2: Crashed Plane		2: Forest 2: Crashed Plane

Bomb Bloke: TFTD Craft Types

2008-02-12T02:12:03Z

TFTD Craft Types

← Older revision		Revision as of 02:12, 12 February 2008
Line 12:		Line 12:

	<b>6-7/06-07:</b> X-Com craft type (ignore this if a base mission):		<b>6-7/06-07:</b> X-Com craft type (ignore this if a base mission):
	~~0 - SkyRanger~~
	~~1 - Lightning~~
	~~2 - Avenger~~
	3 - Interceptor *
	4 - Firestorm *
	~~5 - Small Scout~~
	~~6 - Medium Scout~~
	~~7 - Large Scout~~
	~~8 - Harvestor~~
	~~9 - Abductor~~
	~~10 - Terror Ship~~
	~~11 - Battleship~~
	~~12 - Supply Ship~~

	<i>* Requires maps "Interc" and "Fires". These don't exist normally, though XcomUtil adds versions similar to the SkyRanger and Lightning.</i>		<b>UFO</b> <b>TFTD</b>
			0: SkyRanger 0: Triton
			1: Lightning 1: Hammerhead
			2: Avenger 2: Leviathan
			3: Interceptor 1 3: Barracuda 2
			4: Firestorm 1 4: Manta 2
			5: Small Scout 5: Survey Ship
			6: Medium Scout 6: Escort
			7: Large Scout 7: Cruiser
			8: Harvestor 8: Heavy Cruiser
			9: Abductor 9: Hunter
			10: Terror Ship 10: Battleship
			11: Battleship 11: Dreadnought
			12: Supply Ship 12: Fleet Supply Cruiser

			<i>*1 Requires maps "Interc" and "Fires". These don't exist normally, though XcomUtil adds versions similar to the SkyRanger and Lightning.</i>

			<i>*2 Requires maps "Barracud" and "Manta". These don't exist normally, though XcomUtil adds versions similar to the ??? and ??? (Triton and Hammerhead I assume, but I haven't tested).</i>

	<b>8-9/08-09:</b> Alien craft type (ignore this if not a UFO mission). Uses the above values.		<b>8-9/08-09:</b> Alien craft type (ignore this if not a UFO mission). Uses the above values.
Line 32:		Line 36:
	<b>10-11/0A-0B:</b> Terrain type. Typically depends on the mission [[Missions\|type]] and [[WORLD.DAT\|location]].		<b>10-11/0A-0B:</b> Terrain type. Typically depends on the mission [[Missions\|type]] and [[WORLD.DAT\|location]].

	<b>UFO</b> <b>TFTD</b>		<b>UFO</b> <b>TFTD</b>
	0: Jungle 0: Seabed Trash		0: Jungle 0: Seabed Trash
	1: Farm 1: Pipes		1: Farm 1: Pipes
	2: Forest 2: Crashed Plane		2: Forest 2: Crashed Plane
	3: X-Com Base 3: Atlantis		3: X-Com Base 3: Atlantis
	4: Alien Base 4: Mu		4: Alien Base 4: Mu
	5: Urban 5: Sunken Galleon		5: Urban 5: Sunken Galleon
	6: Desert 6: Sunken Liner		6: Desert 6: Sunken Liner
	7: Mountains 7: Volcanic		7: Mountains 7: Volcanic
	8: Polar 8: Coral		8: Polar 8: Coral
	9: Mars 9: Artefact Site Stage 1		9: Mars 9: Artefact Site Stage 1
	10: Artefact Site Stage 2		10: Artefact Site Stage 2
	11: Cargo Ship Stage 1 & 2 (Check [[MISDATA.DAT]][20-21] for which)		11: Cargo Ship Stage 1 & 2 (Check [[MISDATA.DAT]][20-21] for which)

Bomb Bloke at 01:04, 9 February 2008

2008-02-09T01:04:46Z

← Older revision		Revision as of 01:04, 9 February 2008
Line 1:		Line 1:
	Created in the MissDat folder when you start a battlescape mission, also copied to the savegame folder of choice when saving mid-mission. Primarily used ~~to generate a new map at the beginning of combat~~ and to determine which [[TERRAIN\|MCD files]] to load.		Created in the MissDat folder when you start a battlescape mission, also copied to the savegame folder of choice when saving mid-mission. Primarily used for [[Battlescape Map Generation]] and to determine which [[TERRAIN\|MCD files]] to load.

	File is 92 bytes long for both UFO and TFTD. Values are presented according to byte offset (0 to 91) followed by the equivalent hex offset (00 to 5B) in <b>bold</b>.		File is 92 bytes long for both UFO and TFTD. Values are presented according to byte offset (0 to 91) followed by the equivalent hex offset (00 to 5B) in <b>bold</b>.