XBASES.DAT - Revision history

Hobbes at 04:37, 23 July 2013

2013-07-23T04:37:04Z

← Older revision		Revision as of 04:37, 23 July 2013
Line 21:		Line 21:
	==See Also==		==See Also==
	[[Category:Game Files]]		[[Category:Game Files]]
			[[Category:Enemy Unknown/UFO Defense]]

Zaimoni at 19:22, 22 December 2009

2009-12-22T19:22:30Z

← Older revision		Revision as of 19:22, 22 December 2009
Line 9:		Line 9:
	'''2-3''': LOC.DAT reference of base to be targeted.		'''2-3''': LOC.DAT reference of base to be targeted.

	A successful base defense sets ~~both coordinates~~ to 0.		A successful base defense sets at least the first coordinate to 0.

	<i>Following may belong in Talk...not sure -- [[User:Zaimoni\|Zaimoni]]</i>		<i>Following may belong in Talk...not sure -- [[User:Zaimoni\|Zaimoni]]</i>
	If both horizontal and vertical offset are 0, no conversion happens.		* If both horizontal and vertical offset are 0, no conversion happens.
	If both horizontal and vertical offset are 1 (detected, LOC.DAT index is Skyranger-1), the resulting Battleship hovers directly over the X-COM base. No base attack occurs just from editing this file.		* If both horizontal and vertical offset are 1 (detected, LOC.DAT index is Skyranger-1), the resulting Battleship hovers directly over the X-COM base. No base attack occurs just from editing this file.
	If the horizontal offset is 1 while the vertical offset is 0 (detected, LOC.DAT index right), a base attack happens when the Battleship arrives.		* If the horizontal offset is 1 while the vertical offset is 0 (detected, LOC.DAT index right), a base attack happens when the Battleship arrives.
	If the horizontal offset is 0 while the vertical offset is 1 (not detected, but bogus LOC.DAT entry pointing to Skyranger-1), a weird buggy UFO flies in, likely missing the X-COM base.		* If the horizontal offset is 0 while the vertical offset is 1 (not detected, but bogus LOC.DAT entry pointing to Skyranger-1), a weird buggy UFO flies in, likely missing the X-COM base.

	The base coordinates (0x64, 0xc8ff) were also tried. The Battleship headed for at coordinates (0xcb, 0x8c), but had destination (0x47, 0x600).		The base coordinates (0x64, 0xc8ff) were also tried. The Battleship headed for at coordinates (0xcb, 0x8c), but had destination (0x47, 0x600).

Zaimoni at 19:19, 22 December 2009

2009-12-22T19:19:24Z

← Older revision		Revision as of 19:19, 22 December 2009
Line 1:		Line 1:
	This file ~~likely~~ records whether an X-COM base has been targeted for alien retaliation purposes. Total file size is 48 bytes and since the number of bases is limited to 8, this would suggest that each record is 6 bytes long (most likely 3 2-byte entries per record). Darkfred claims each record is only 4 bytes in length but that seems rather strange considering the base cap.		This file records whether an X-COM base has been targeted for alien retaliation purposes.

	~~'''0-1''' Unknown. Have seen~~ a ~~value of 4 here. Possible pointer into~~ [[~~LOC~~.DAT]]?		In experimental testing, this file was found capable of converting a Retaliation mission from the type indicated from [[MISSIONS.DAT]], to a Battleship that headed straight for an X-COM base in the region.

	~~'''2-3''' Unknown.~~		For a single base in North Africa, bytes 20-23 controlled the offset from the base where the Battleship headed straight to. This suggests a layout of 12 records of 4 bytes, one for each geographical region in canonical order.

	~~'''4-5''' Flag for alien retaliation~~ in ~~progress.~~

	~~=== Alternate Reading ===~~

	~~In experimental testing~~, ~~this file was found capable of converting a Retaliation mission~~ from the ~~type indicated from [[MISSIONS.DAT]], to a~~ Battleship ~~that~~ headed straight for ~~an X-COM base~~ in ~~the region~~.

	~~For~~ a ~~single base in North Africa, bytes 20-23 controlled the offset from the~~ base ~~where the Battleship headed straight to~~. ~~This suggests a layout of 12 records of 4 bytes, one for each geographical region in canonical order:~~		'''0-1''': nonzero if and only if a base is detected.

	'''0-1''': ~~longitude/horizontal offset(?)~~		'''2-3''': LOC.DAT reference of base to be targeted.

	~~'''2-3''': latitude/vertical offset(?)~~		A successful base defense sets both coordinates to 0.

			<i>Following may belong in Talk...not sure -- [[User:Zaimoni\|Zaimoni]]</i>
	If both horizontal and vertical offset are 0, no conversion happens.		If both horizontal and vertical offset are 0, no conversion happens.
	If both horizontal and vertical offset are 1, the resulting Battleship hovers directly over the X-COM base. No base attack occurs just from editing this file.		If both horizontal and vertical offset are 1 (detected, LOC.DAT index is Skyranger-1), the resulting Battleship hovers directly over the X-COM base. No base attack occurs just from editing this file.
	If the horizontal offset is 1 while the vertical offset is 0, a base attack happens when the Battleship arrives.		If the horizontal offset is 1 while the vertical offset is 0 (detected, LOC.DAT index right), a base attack happens when the Battleship arrives.
	If the horizontal offset is 0 while the vertical offset is 1, a weird buggy UFO flies in, likely missing the X-COM base.		If the horizontal offset is 0 while the vertical offset is 1 (not detected, but bogus LOC.DAT entry pointing to Skyranger-1), a weird buggy UFO flies in, likely missing the X-COM base.

	~~In any case~~, ~~a successful base defense sets both~~ coordinates ~~to 0~~.		The base coordinates (0x64, 0xc8ff) were also tried. The Battleship headed for at coordinates (0xcb, 0x8c), but had destination (0x47, 0x600).

	==See Also==		==See Also==
	[[Category:Game Files]]		[[Category:Game Files]]

Zaimoni at 12:18, 22 December 2009

2009-12-22T12:18:54Z

← Older revision		Revision as of 12:18, 22 December 2009
Line 13:		Line 13:
	For a single base in North Africa, bytes 20-23 controlled the offset from the base where the Battleship headed straight to. This suggests a layout of 12 records of 4 bytes, one for each geographical region in canonical order:		For a single base in North Africa, bytes 20-23 controlled the offset from the base where the Battleship headed straight to. This suggests a layout of 12 records of 4 bytes, one for each geographical region in canonical order:

	'''0-1''': longitude/horizontal offset		'''0-1''': longitude/horizontal offset(?)

	'''2-3''': latitude/vertical offset		'''2-3''': latitude/vertical offset(?)

	If both horizontal and vertical offset are 0, no conversion happens.		If both horizontal and vertical offset are 0, no conversion happens.
Line 21:		Line 21:
	If the horizontal offset is 1 while the vertical offset is 0, a base attack happens when the Battleship arrives.		If the horizontal offset is 1 while the vertical offset is 0, a base attack happens when the Battleship arrives.
	If the horizontal offset is 0 while the vertical offset is 1, a weird buggy UFO flies in, likely missing the X-COM base.		If the horizontal offset is 0 while the vertical offset is 1, a weird buggy UFO flies in, likely missing the X-COM base.

			In any case, a successful base defense sets both coordinates to 0.

	==See Also==		==See Also==
	[[Category:Game Files]]		[[Category:Game Files]]

Zaimoni at 10:14, 19 December 2009

2009-12-19T10:14:40Z

@@ Line 6: / Line 6: @@
 '''4-5''' Flag for alien retaliation in progress.
 ==See Also==
 [[Category:Game Files]]

Zombie: Linking.

2009-01-02T05:17:32Z

Linking.

← Older revision		Revision as of 05:17, 2 January 2009
Line 1:		Line 1:
	This file likely records whether an X-COM base has been targeted for alien retaliation purposes. Total file size is 48 bytes and since the number of bases is limited to 8, this would suggest that each record is 6 bytes long (most likely 3 2-byte entries per record). Darkfred claims each record is only 4 bytes in length but that seems rather strange considering the base cap.		This file likely records whether an X-COM base has been targeted for alien retaliation purposes. Total file size is 48 bytes and since the number of bases is limited to 8, this would suggest that each record is 6 bytes long (most likely 3 2-byte entries per record). Darkfred claims each record is only 4 bytes in length but that seems rather strange considering the base cap.

	'''0-1''' Unknown. Have seen a value of 4 here. Possible pointer into LOC.DAT?		'''0-1''' Unknown. Have seen a value of 4 here. Possible pointer into [[LOC.DAT]]?

	'''2-3''' Unknown.		'''2-3''' Unknown.

Zombie: Added See Also, categorized.

2008-12-29T04:51:09Z

Added See Also, categorized.

← Older revision		Revision as of 04:51, 29 December 2008
Line 6:		Line 6:

	'''4-5''' Flag for alien retaliation in progress.		'''4-5''' Flag for alien retaliation in progress.

			==See Also==
			[[Category:Game Files]]

Zombie: Not quite correct AQ, this file deals with retaliation against X-COM bases.

2008-10-04T03:40:08Z

Not quite correct AQ, this file deals with retaliation against X-COM bases.

← Older revision		Revision as of 03:40, 4 October 2008
Line 1:		Line 1:
	This file records ~~the location of any Alien Bases on the Geoscape, and likely~~ whether X-COM has ~~found them yet~~. It is ~~unclear if destroyed~~ bases ~~are removed from~~ the ~~record~~.		This file likely records whether an X-COM base has been targeted for alien retaliation purposes. Total file size is 48 bytes and since the number of bases is limited to 8, this would suggest that each record is 6 bytes long (most likely 3 2-byte entries per record). Darkfred claims each record is only 4 bytes in length but that seems rather strange considering the base cap.

			'''0-1''' Unknown. Have seen a value of 4 here. Possible pointer into LOC.DAT?

			'''2-3''' Unknown.

			'''4-5''' Flag for alien retaliation in progress.

Arrow Quivershaft: Placeholder. I'm cleaning up dead links tonight.

2008-10-03T03:37:22Z

Placeholder. I'm cleaning up dead links tonight.

New page

This file records the location of any Alien Bases on the Geoscape, and likely whether X-COM has found them yet. It is unclear if destroyed bases are removed from the record.