UNITREF.DAT - Revision history

Zombie: /* Structure */ Indeed, Zombies have their own DM category, also linking to the preferred DM page.

2016-08-04T04:52:32Z

Structure: Indeed, Zombies have their own DM category, also linking to the preferred DM page.

← Older revision		Revision as of 04:52, 4 August 2016
Line 355:		Line 355:
	!<span id="55"></span>55		!<span id="55"></span>55
	!<span id="0x37"></span>0x37		!<span id="0x37"></span>0x37
	\|[[Damage~~#Susceptible_to...~~\|Damage Modifier]] Category		\|[[Damage Modifiers\|Damage Modifier]] Category

	This field is simply a look-up table, or more directly, a way to categorize the units into similar groups. The actual modifiers are listed in the executable. A value of 1 indicates the first DM category, a value of 4 indicates the 4th, etc. The values of 2 and 3 are not seen in the alien stats as they refer to X-COM soldier armor info~~. I'm not sure about 13 as the Zombie's stats haven't been found yet, but I think there is a category in the DM's for it~~.		This field is simply a look-up table, or more directly, a way to categorize the units into similar groups. The actual modifiers are listed in the executable. A value of 1 indicates the first DM category, a value of 4 indicates the 4th, etc. The values of 2 and 3 are not seen in the alien stats as they refer to X-COM soldier armor info.

	'''Value''' '''Unit Type(s)'''		'''Value''' '''Unit Type(s)'''

Morgan525: /* Structure */

2015-12-26T02:13:21Z

Structure

← Older revision		Revision as of 02:13, 26 December 2015
Line 458:		Line 458:
	!<span id="74"></span>74		!<span id="74"></span>74
	!<span id="0x4A"></span>0x4A		!<span id="0x4A"></span>0x4A
	\|AI Mode. Zaimoni found [http://www.strategycore.co.uk/forums/UFO-AI-patch-t8908.html&st=20&start=20 Here] that the values are 0:PATROL, 1:SNIPER, 2:ATTACKING, 3:ESCAPING, 4:GUARD, 5:Returning to UFO. 255 (-1) ~~is also possible. Zaimoni tripped this by wounding a Floater in SNIPER~~ mode~~; it returned fire, then was taken down by another soldier. Snap guess is that this is a "recalculate" marker~~.		\|AI Mode. Zaimoni found [http://www.strategycore.co.uk/forums/UFO-AI-patch-t8908.html&st=20&start=20 Here] that the values are
			:::0:PATROL
			:::1:SNIPER
			:::2:ATTACKING
			:::3:ESCAPING
			:::4:GUARD
			:::5:Returning to UFO.
			:255 (-1): Makes the program recalculate the AI mode.
	\|- valign="top"		\|- valign="top"
	!<span id="75"></span>75		!<span id="75"></span>75

Morgan525: /* Structure */ more information on Byte 70.

2015-12-26T02:02:13Z

Structure: more information on Byte 70.

← Older revision		Revision as of 02:02, 26 December 2015
Line 441:		Line 441:
	::Byte 70 is the index of the node of the end of the planned move.		::Byte 70 is the index of the node of the end of the planned move.
	:Note that the move may be multi-turn, and byte 69 is not guaranteed to update during a multi-turn move. I think it will if the alien ends its move on a node, however. -- Zaimoni		:Note that the move may be multi-turn, and byte 69 is not guaranteed to update during a multi-turn move. I think it will if the alien ends its move on a node, however. -- Zaimoni
			:For AI mode 2:
			::Byte 70 is the UNITPOS reference number for this unit's target. - Tycho
	\|- valign="top"		\|- valign="top"
	!<span id="71"></span>71		!<span id="71"></span>71

Morgan525: /* Structure */

2015-06-25T16:45:17Z

Structure

← Older revision		Revision as of 16:45, 25 June 2015
Line 259:		Line 259:
	!<span id="0x2B"></span>0x2B		!<span id="0x2B"></span>0x2B
	\|Called "deployment" with values of 0 or 1 (0=normal, 1=special).		\|Called "deployment" with values of 0 or 1 (0=normal, 1=special).
	0: Only those locations specified for units of the appropriate rank are used. ~~(but~~		0: Only those locations specified for units of the appropriate rank, size, and flying ability are used.
	~~if none are available, the spawn points for civilians may be used.)~~		1: Civilian spawn points are used, ignoring a unit's rank, but still selected by the unit's size and flying ability.
	1: Civilian spawn points are used, ignoring a unit's rank.
	As result - Commanders/leaders can occasionally be spawned outside of the UFO craft (and ramble around the UFO) and not in the "control room", which has an exclusive commander spawn node.		As result - Commanders/leaders can occasionally be spawned outside of the UFO craft (and ramble around the UFO) and not in the "control room", which has an exclusive commander spawn node.
	\|- valign="top"		\|- valign="top"

Morgan525: /* Structure */

2015-06-25T16:21:03Z

Structure

← Older revision		Revision as of 16:21, 25 June 2015
Line 259:		Line 259:
	!<span id="0x2B"></span>0x2B		!<span id="0x2B"></span>0x2B
	\|Called "deployment" with values of 0 or 1 (0=normal, 1=special).		\|Called "deployment" with values of 0 or 1 (0=normal, 1=special).
	~~When it is zero, the routine to select a place to spawn the alien unit on the battlefield follows normal rules~~: Only ~~nodes~~ specified for ~~alien~~ units of the appropriate rank are ~~chosen~~. If none are available, ~~nodes~~ for civilians may be used.		0: Only those locations specified for units of the appropriate rank are used. (but
	~~When it is one, civilian/neutral-~~spawn-points are used, ignoring ~~the~~ unit's rank. As result - Commanders/leaders can occasionally be spawned outside of the UFO craft (and ramble around the UFO) and not in the "control room", which has an exclusive commander spawn node~~. The chance for this byte to be set is based on byte5 for the alien's rank in the alien equipment table~~.		if none are available, the spawn points for civilians may be used.)
			1: Civilian spawn points are used, ignoring a unit's rank.
			As result - Commanders/leaders can occasionally be spawned outside of the UFO craft (and ramble around the UFO) and not in the "control room", which has an exclusive commander spawn node.
	\|- valign="top"		\|- valign="top"
	!<span id="44"></span>44		!<span id="44"></span>44

Morgan525: /* Structure */

2015-06-25T11:33:11Z

Structure

← Older revision		Revision as of 11:33, 25 June 2015
Line 258:		Line 258:
	!<span id="43"></span>43		!<span id="43"></span>43
	!<span id="0x2B"></span>0x2B		!<span id="0x2B"></span>0x2B
	\|Called "deployment" with values of 0 or 1 (0=normal, 1=special). When ~~set to~~ zero, the routine to select a place to spawn the alien unit on the battlefield follows ~~the~~ normal ~~path~~: Only nodes specified for alien units of the appropriate rank are chosen ~~unless~~ none are available, ~~then~~ nodes for civilians may be used. When ~~set to~~ one, ~~the routine will search for a~~ civilian/neutral spawn ~~point to place the alien~~, ignoring rank. As result - Commanders/leaders can occasionally be spawned outside of the UFO craft (and ramble around the UFO) and not in the "control room", which has an exclusive commander spawn node. The chance for this to ~~occur~~ is based on ~~byte 5~~ for the alien's rank in the alien equipment table.		\|Called "deployment" with values of 0 or 1 (0=normal, 1=special).
			When it is zero, the routine to select a place to spawn the alien unit on the battlefield follows normal rules: Only nodes specified for alien units of the appropriate rank are chosen. If none are available, nodes for civilians may be used.
			When it is one, civilian/neutral-spawn-points are used, ignoring the unit's rank. As result - Commanders/leaders can occasionally be spawned outside of the UFO craft (and ramble around the UFO) and not in the "control room", which has an exclusive commander spawn node. The chance for this byte to be set is based on byte5 for the alien's rank in the alien equipment table.
	\|- valign="top"		\|- valign="top"
	!<span id="44"></span>44		!<span id="44"></span>44

Morgan525: /* Structure */ hopefully clarified this further

2015-06-24T15:05:31Z

Structure: hopefully clarified this further

← Older revision		Revision as of 15:05, 24 June 2015
Line 258:		Line 258:
	!<span id="43"></span>43		!<span id="43"></span>43
	!<span id="0x2B"></span>0x2B		!<span id="0x2B"></span>0x2B
	\|Called "deployment" with values of 0 or 1 (0=~~inside~~, 1=~~outside~~). When alien units are ~~generated for a battle~~, ~~there is a random chance~~ for ~~this byte to~~ be set~~. That unit is a "scout" and can be assigned~~ to one of the neutral spawn ~~points on the map without the need~~ to ~~fill up all~~ the alien ~~exclusive points first. In other words with "1" alien unit is spawned at exact random node marked as "civilian/scout"~~ ignoring ~~actual~~ rank ~~of unit~~. As result - ~~Commander~~ can occasionally be spawned outside of the UFO craft (and ramble around UFO), not in the "~~contol~~ room", which has exclusive commander spawn node.		\|Called "deployment" with values of 0 or 1 (0=normal, 1=special). When set to zero, the routine to select a place to spawn the alien unit on the battlefield follows the normal path: Only nodes specified for alien units of the appropriate rank are chosen unless none are available, then nodes for civilians may be used. When set to one, the routine will search for a civilian/neutral spawn point to place the alien, ignoring rank. As result - Commanders/leaders can occasionally be spawned outside of the UFO craft (and ramble around the UFO) and not in the "control room", which has an exclusive commander spawn node. The chance for this to occur is based on byte 5 for the alien's rank in the alien equipment table.
	\|- valign="top"		\|- valign="top"
	!<span id="44"></span>44		!<span id="44"></span>44

Volutar: /clarification / 0x77 +0x80/0x82

2015-06-24T08:38:25Z

clarification: 0x77 +0x80/0x82

← Older revision		Revision as of 08:38, 24 June 2015
Line 562:		Line 562:
	!<span id="119"></span>119		!<span id="119"></span>119
	!<span id="0x77"></span>0x77		!<span id="0x77"></span>0x77
	\|Movement related? Large unit related? Possible bitfield.		\|[Garbage unused by game] Movement related? Large unit related? Possible bitfield.
	''MTR:''		''MTR:''
	00000000 0 Chryssalid(2), Civilian(9), Ethereal(2), Floater(2), Muton,		00000000 0 Chryssalid(2), Civilian(9), Ethereal(2), Floater(2), Muton,
Line 614:		Line 614:
	!<span id="128-129"></span>128-129		!<span id="128-129"></span>128-129
	!<span id="0x80-0x81"></span>0x80-0x81		!<span id="0x80-0x81"></span>0x80-0x81
	\|TFTD ONLY - Bubble animation enable. (0=disable, 1=enable)		\|TFTD ONLY - Bubble animation enable. (0=disable, 1=enable) - [unused by game - taken from "underwater" flag]
	\|- valign="top"		\|- valign="top"
	!<span id="130-131"></span>130-131		!<span id="130-131"></span>130-131
	!<span id="0x82-0x83"></span>0x82-0x83		!<span id="0x82-0x83"></span>0x82-0x83
	\|TFTD ONLY - Called "floorabove" flag. Is there a floor above unit? (0=no, 1=yes)		\|TFTD ONLY - Called "floorabove" flag. Is there a floor above unit? (0=no, 1=yes) [unused by game - calculated on-fly]
	\|-		\|-
	\|}		\|}

Volutar: Undo revision 66004 by Volutar (talk)

2015-06-24T08:30:09Z

Undo revision 66004 by Volutar (talk)

← Older revision		Revision as of 08:30, 24 June 2015
Line 587:		Line 587:
	!<span id="120-123"></span>120-123		!<span id="120-123"></span>120-123
	!<span id="0x78-0x7B"></span>0x78-0x7B		!<span id="0x78-0x7B"></span>0x78-0x7B
	\|Unit bit flags (32bit ~~value~~), mainly re: mobility. They do NOT affect the soldier in inventory screen: ''(Mix of notes by BB and NKF)''		\|Unit bit flags (32bit), mainly re: mobility. They do NOT affect the soldier in inventory screen: ''(Mix of notes by BB and NKF)''
	( 1) 1: 1 = Unit moving.		( 1) 1: 1 = Unit moving.
	( 2) 2: 1 = Unit can fly.		( 2) 2: 1 = Unit can fly.
Line 649:		Line 649:
	What else? The more to look for, the easier it is...		What else? The more to look for, the easier it is...

	Know ~~111~~ values.		Know 119 values.
	Unknown values (13 in total):		Unknown values (5 in total):
	~~[[#34\|[034 / 0x22]]] - Always 0?~~
	~~[[#36\|[036 / 0x24]]] - Always 0?~~
	~~[[#43\|[043 / 0x2B]]] - Set to 1 on occasion, usually 0.~~
	~~[[#52\|[052 / 0x34]]] - Seems to be a mirror of 48 / 0x30, the LOFTemp index for the unit.~~
	~~[[#71\|[071 / 0x47]]] - Appears to relate to lighting caused by the unit, [[Talk:UNITREF.DAT#Offset_0x47\|discussion here]].~~
	~~[[#74\|[074 / 0x4A]]] - Appears to relate to the AI-mode used by the unit, [[Talk:UNITREF.DAT#Offset_0x4A_.2874.29\|discussion here]].~~
	[[#75\|[075 / 0x4B]]] - Always 0?		[[#75\|[075 / 0x4B]]] - Always 0?
	~~[[#112\|[112 / 0x70]]] - Set to 1 for some aliens, 0 otherwise.~~
	[[#119\|[119 / 0x77]]] - No idea, possible bitfield, could be anything.		[[#119\|[119 / 0x77]]] - No idea, possible bitfield, could be anything.
	~~[[#120\|[120 / 0x78]]] - Unit bit flags, mainly re: mobility. Only one bit not 100% identified.~~
	[[#121\|[121 / 0x79]]] - Second unit gets a value of 16. Everyone else gets 0. No obvious purpose.		[[#121\|[121 / 0x79]]] - Second unit gets a value of 16. Everyone else gets 0. No obvious purpose.
	[[#122\|[122 / 0x7A]]] - Always 0?		[[#122\|[122 / 0x7A]]] - Always 0?
	[[#123\|[123 / 0x7B]]] - Always 0?		[[#123\|[123 / 0x7B]]] - Always 0?

	~~Know 1 TFTD value.~~
	~~Unknown TFTD values (7 in total):~~
	~~[[#125\|[125]]] [[#126\|[126]]] [[#127\|[127]]] [[#128\|[128]]] [[#129\|[129]]] [[#130\|[130]]] [[#131\|[131]]]~~

	4) Hobbes posted a savegame with a TON of different aliens in it [http://www.xcomufo.com/forums/index.php?showtopic=8591 here] (message 6). Interesting for testing. But note it was made with XCOMUTIL and there may(?) be concerns over vailidity of unit info - see [[Talk:UNITREF.DAT]].		4) Hobbes posted a savegame with a TON of different aliens in it [http://www.xcomufo.com/forums/index.php?showtopic=8591 here] (message 6). Interesting for testing. But note it was made with XCOMUTIL and there may(?) be concerns over vailidity of unit info - see [[Talk:UNITREF.DAT]].

Volutar: /0x78-0x7b/ mobility is 32bit

2015-06-24T08:27:16Z

0x78-0x7b: mobility is 32bit

← Older revision		Revision as of 08:27, 24 June 2015
Line 585:		Line 585:
	11111110 254 Muton		11111110 254 Muton
	\|- valign="top"		\|- valign="top"
	!<span id="120"></span>120		!<span id="120-123"></span>120-123
	!<span id="0x78"></span>0x78		!<span id="0x78-0x7B"></span>0x78-0x7B
	\|Unit bit flags, mainly re: mobility. They do NOT affect the soldier in inventory screen: ''(Mix of notes by BB and NKF)''		\|Unit bit flags (32bit value), mainly re: mobility. They do NOT affect the soldier in inventory screen: ''(Mix of notes by BB and NKF)''
	( 1) 1: 1 = Unit moving.		( 1) 1: 1 = Unit moving.
	( 2) 2: 1 = Unit can fly.		( 2) 2: 1 = Unit can fly.
Line 603:		Line 603:

	What if a hovertank is half on the ground, half in the air? What about a treaded tank, or large alien unit? What about units in lifts?		What if a hovertank is half on the ground, half in the air? What about a treaded tank, or large alien unit? What about units in lifts?
	~~\|- valign="top"~~
	~~!<span id="121"></span>121~~
	~~!<span id="0x79"></span>0x79~~
	\|Possible Values: 0 or 16. All units in unitref.dat get a value of 0 except for the second unit in the list which gets 16. Doesn't matter if the second unit is a soldier, a tank, or an alien. It's always 16. Editing it to 0 doesn't crash the game or have any dire consequences.
	~~\|- valign="top"~~
	~~!<span id="122"></span>122~~
	~~!<span id="0x7A"></span>0x7A~~
	~~\|Always 0? Possible low byte of 123(0x7B)~~
	~~\|- valign="top"~~
	~~!<span id="123"></span>123~~
	~~!<span id="0x7B"></span>0x7B~~
	~~\|Always 0? Possible high byte for 122(0x7A).~~
	\|- valign="top"		\|- valign="top"
	!<span id="124-125"></span>124-125		!<span id="124-125"></span>124-125
Line 661:		Line 649:
	What else? The more to look for, the easier it is...		What else? The more to look for, the easier it is...

	Know ~~119~~ values.		Know 111 values.
	Unknown values (5 in total):		Unknown values (13 in total):
			[[#34\|[034 / 0x22]]] - Always 0?
			[[#36\|[036 / 0x24]]] - Always 0?
			[[#43\|[043 / 0x2B]]] - Set to 1 on occasion, usually 0.
			[[#52\|[052 / 0x34]]] - Seems to be a mirror of 48 / 0x30, the LOFTemp index for the unit.
			[[#71\|[071 / 0x47]]] - Appears to relate to lighting caused by the unit, [[Talk:UNITREF.DAT#Offset_0x47\|discussion here]].
			[[#74\|[074 / 0x4A]]] - Appears to relate to the AI-mode used by the unit, [[Talk:UNITREF.DAT#Offset_0x4A_.2874.29\|discussion here]].
	[[#75\|[075 / 0x4B]]] - Always 0?		[[#75\|[075 / 0x4B]]] - Always 0?
			[[#112\|[112 / 0x70]]] - Set to 1 for some aliens, 0 otherwise.
	[[#119\|[119 / 0x77]]] - No idea, possible bitfield, could be anything.		[[#119\|[119 / 0x77]]] - No idea, possible bitfield, could be anything.
			[[#120\|[120 / 0x78]]] - Unit bit flags, mainly re: mobility. Only one bit not 100% identified.
	[[#121\|[121 / 0x79]]] - Second unit gets a value of 16. Everyone else gets 0. No obvious purpose.		[[#121\|[121 / 0x79]]] - Second unit gets a value of 16. Everyone else gets 0. No obvious purpose.
	[[#122\|[122 / 0x7A]]] - Always 0?		[[#122\|[122 / 0x7A]]] - Always 0?
	[[#123\|[123 / 0x7B]]] - Always 0?		[[#123\|[123 / 0x7B]]] - Always 0?

			Know 1 TFTD value.
			Unknown TFTD values (7 in total):
			[[#125\|[125]]] [[#126\|[126]]] [[#127\|[127]]] [[#128\|[128]]] [[#129\|[129]]] [[#130\|[130]]] [[#131\|[131]]]

	4) Hobbes posted a savegame with a TON of different aliens in it [http://www.xcomufo.com/forums/index.php?showtopic=8591 here] (message 6). Interesting for testing. But note it was made with XCOMUTIL and there may(?) be concerns over vailidity of unit info - see [[Talk:UNITREF.DAT]].		4) Hobbes posted a savegame with a TON of different aliens in it [http://www.xcomufo.com/forums/index.php?showtopic=8591 here] (message 6). Interesting for testing. But note it was made with XCOMUTIL and there may(?) be concerns over vailidity of unit info - see [[Talk:UNITREF.DAT]].

UNITREF.DAT - Revision history

Zombie: /* Structure */ Indeed, Zombies have their own DM category, also linking to the preferred DM page.

Morgan525: /* Structure */

Morgan525: /* Structure */ more information on Byte 70.

Morgan525: /* Structure */

Morgan525: /* Structure */

Morgan525: /* Structure */

Morgan525: /* Structure */ hopefully clarified this further

Volutar: /*clarification */ 0x77 +0x80/0x82

Volutar: Undo revision 66004 by Volutar (talk)

Volutar: /*0x78-0x7b*/ mobility is 32bit

Volutar: /clarification / 0x77 +0x80/0x82

Volutar: /0x78-0x7b/ mobility is 32bit