Talk:UNITREF.DAT - Revision history

Zombie: /* Offset 0x4A (74) */

2015-05-30T05:12:56Z

Offset 0x4A (74)

← Older revision		Revision as of 05:12, 30 May 2015
Line 189:		Line 189:
	:Definitely a great find. Having 5 AI modes makes sense and looking at the other text I think it lists actions/moves/options for each mode: Patrol (Set Patrol Point, Finding Route, Moving), Combat (Attack Attempt, Find Fire Point, Select Target, Firing, Find Cover), Sniper (Evaluating Mode, Final Facing), Escape (Moving, GoUfo, etc.) and Guard.		:Definitely a great find. Having 5 AI modes makes sense and looking at the other text I think it lists actions/moves/options for each mode: Patrol (Set Patrol Point, Finding Route, Moving), Combat (Attack Attempt, Find Fire Point, Select Target, Firing, Find Cover), Sniper (Evaluating Mode, Final Facing), Escape (Moving, GoUfo, etc.) and Guard.
	::I'm trying to correlate this info with the /ROUTES files, especially the entry called 'flag' - I remember a post a long time ago that those values determined the rank of the aliens that could use them. What I'm wondering is if there's a relation between the map location (and node 'flag' value) and the value found on UNITREF.DAT[[User:Hobbes\|Hobbes]] 10:47, 26 January 2012 (EST)		::I'm trying to correlate this info with the /ROUTES files, especially the entry called 'flag' - I remember a post a long time ago that those values determined the rank of the aliens that could use them. What I'm wondering is if there's a relation between the map location (and node 'flag' value) and the value found on UNITREF.DAT[[User:Hobbes\|Hobbes]] 10:47, 26 January 2012 (EST)
			:::The values and modes are this: 0=patrol,1=sniper,2=attacking,3=escaping,4=guard,5=returning to UFO. At least that's what I'm coming up with. --[[User:Zombie\|Zombie]] ([[User talk:Zombie\|talk]]) 01:12, 30 May 2015 (EDT)

	== Offset 0x6F ==		== Offset 0x6F ==

Morgan525: /* Offset 0x2B (43) */

2013-03-19T08:25:15Z

Offset 0x2B (43)

← Older revision		Revision as of 08:25, 19 March 2013
Line 387:		Line 387:
	:.text:0041F180 mov [edi-0Eh], edx		:.text:0041F180 mov [edi-0Eh], edx

	Since the alien is marked as disabled, it is skipped in the routine to apply explosion damage to victims. Since its items are still assigned to it in OBPOS, they are skip by the item destruction routine. [[User:Morgan525\|Tycho]] 12:27, 18 March 2013 (EDT)		Since the alien is marked as disabled, it is skipped in the routine to apply explosion damage to victims. Since its items are still assigned to it in OBPOS, they are skip by the item destruction routine. ESI is either set to 6 as determined by the value of 2Bh or will increment up along another pathway. [[User:Morgan525\|Tycho]] 12:27, 18 March 2013 (EDT)

Morgan525: /* Offset 0x2B (43) */

2013-03-19T08:21:28Z

Offset 0x2B (43)

← Older revision		Revision as of 08:21, 19 March 2013
Line 371:		Line 371:
	:::Yeah, someone mentioned something about that a long time ago on the xcomufo.com forums. Certain aliens are 'flagged' for something at the beginning. But this can be merely a way for the engine to ensure that certain aliens remain outside, and not related to the AI.[[User:Hobbes\|Hobbes]] 18:20, 8 January 2012 (EST)		:::Yeah, someone mentioned something about that a long time ago on the xcomufo.com forums. Certain aliens are 'flagged' for something at the beginning. But this can be merely a way for the engine to ensure that certain aliens remain outside, and not related to the AI.[[User:Hobbes\|Hobbes]] 18:20, 8 January 2012 (EST)

	~~When~~ this byte is set, which is determined by comparing the value of ~~byte~~ 5 of the ~~alien~~ loadout ~~matrix~~ against a random %, the alien cannot be killed by a UPS explosion, if within the blast radius of one.		From what I have been able to uncover about this offset: when this byte is set, which is determined by comparing the value of offset 5 of the loadout table against a random % number, the alien cannot be killed by a UPS explosion, if within the blast radius of one.
	.text:0041F0E0 mov al, [ebp+2Bh] ; set by alien		:.text:0041F0E0 mov al, [ebp+2Bh] ; set by alien loadout byte 5 vs random %, ebp=current alien unitref offset
	~~.text:0041F0E0 ;~~ loadout byte 5 vx random %		:<s>.text:0041F0E3 mov word ptr [esp+3Ch+var_28], cx </s>
	.text:0041F0E3 mov word ptr [esp+3Ch+var_28], cx		:.text:0041F0E8 test al, al
	.text:0041F0E8 test al, al		:.text:0041F0EA jz short loc_41F0F5
	.text:0041F0EA jz short loc_41F0F5		:<s>.text:0041F0EC mov [esp+3Ch+var_28], ebx</s>
	.text:0041F0EC mov [esp+3Ch+var_28], ebx		:.text:0041F0F0 mov esi, 6
	.text:0041F0F0 mov esi, 6

	.text:0041F16E cmp si, 6		:.text:0041F16E cmp si, 6
	.text:0041F172 jnz short loc_41F19E		:.text:0041F172 jnz short loc_41F19E
	.text:0041F174 mov edx, [edi-0Eh] //edi=~~Unit#2~~ in OBPOS byte 0Ah		:.text:0041F174 mov edx, [edi-0Eh] ;edi=next unit in OBPOS byte 0Ah after the one being evaluated
	.text:0041F177 mov eax, 0FFFFFFFDh		:.text:0041F177 mov eax, 0FFFFFFFDh
	.text:0041F17C and edx, eax //this sets bit 2 of the unit's 0A byte to 0		:.text:0041F17C and edx, eax ;this sets bit 2 of the unit's 0A byte to 0
	.text:0041F17E mov cl, dl		:.text:0041F17E mov cl, dl
	.text:0041F180 mov [edi-0Eh], edx		:.text:0041F180 mov [edi-0Eh], edx

	Since the alien is marked as disabled, it is skipped in the routine to apply explosion damage to victims. Since its items are still assigned to it in OBPOS, they are skip by the item destruction routine. [[User:Morgan525\|Tycho]] 12:27, 18 March 2013 (EDT)		Since the alien is marked as disabled, it is skipped in the routine to apply explosion damage to victims. Since its items are still assigned to it in OBPOS, they are skip by the item destruction routine. [[User:Morgan525\|Tycho]] 12:27, 18 March 2013 (EDT)

Morgan525: /* Offset 0x2B (43) */

2013-03-18T16:27:35Z

Offset 0x2B (43)

← Older revision		Revision as of 16:27, 18 March 2013
Line 370:		Line 370:
	::You say it is also used for choosing AI patrol path. Does it mean that once a unit is assigned as a "scout" it will keep patrolling only on scout ranked nodes for the rest of his life? Does it also work the other way around, if a unit is not marked with this flag, it is not allowed to patrol on scout nodes? --[[User:Daiky\|Daiky]] 05:56, 6 January 2012 (EST)		::You say it is also used for choosing AI patrol path. Does it mean that once a unit is assigned as a "scout" it will keep patrolling only on scout ranked nodes for the rest of his life? Does it also work the other way around, if a unit is not marked with this flag, it is not allowed to patrol on scout nodes? --[[User:Daiky\|Daiky]] 05:56, 6 January 2012 (EST)
	:::Yeah, someone mentioned something about that a long time ago on the xcomufo.com forums. Certain aliens are 'flagged' for something at the beginning. But this can be merely a way for the engine to ensure that certain aliens remain outside, and not related to the AI.[[User:Hobbes\|Hobbes]] 18:20, 8 January 2012 (EST)		:::Yeah, someone mentioned something about that a long time ago on the xcomufo.com forums. Certain aliens are 'flagged' for something at the beginning. But this can be merely a way for the engine to ensure that certain aliens remain outside, and not related to the AI.[[User:Hobbes\|Hobbes]] 18:20, 8 January 2012 (EST)

			When this byte is set, which is determined by comparing the value of byte 5 of the alien loadout matrix against a random %, the alien cannot be killed by a UPS explosion, if within the blast radius of one.
			.text:0041F0E0 mov al, [ebp+2Bh] ; set by alien
			.text:0041F0E0 ; loadout byte 5 vx random %
			.text:0041F0E3 mov word ptr [esp+3Ch+var_28], cx
			.text:0041F0E8 test al, al
			.text:0041F0EA jz short loc_41F0F5
			.text:0041F0EC mov [esp+3Ch+var_28], ebx
			.text:0041F0F0 mov esi, 6

			.text:0041F16E cmp si, 6
			.text:0041F172 jnz short loc_41F19E
			.text:0041F174 mov edx, [edi-0Eh] //edi=Unit#2 in OBPOS byte 0Ah
			.text:0041F177 mov eax, 0FFFFFFFDh
			.text:0041F17C and edx, eax //this sets bit 2 of the unit's 0A byte to 0
			.text:0041F17E mov cl, dl
			.text:0041F180 mov [edi-0Eh], edx

			Since the alien is marked as disabled, it is skipped in the routine to apply explosion damage to victims. Since its items are still assigned to it in OBPOS, they are skip by the item destruction routine. [[User:Morgan525\|Tycho]] 12:27, 18 March 2013 (EDT)

Hobbes: /* Offset 0x4A (74) */

2012-01-26T17:51:03Z

Offset 0x4A (74)

← Older revision		Revision as of 17:51, 26 January 2012
Line 187:		Line 187:

	That's a great find, BBloke. I never looked at the demo exe. While the debug fonction was deleted in the release, it permits to locate the basic AI fonctions in the code. So we have: AI_patrol_mode (0x4A = 0) at 0x0407D60, AI_Sniper_mode (0x4A = 1) at 0x04081A0, AI_combat_mode (0x4A = 2) at 0x0408430, AI_escape_mode (0x4A = 3) at 0x04067F0 and even the AI_evaluation_mode at 0x0408430, which fills offset 0x4A when it is equal to something else. Other functions can be found as well with the debug info. Fantastic. Now we could try to make AI take cover from time to time, instead of making a stupidly exposed target.--[[User:Kyrub\|Kyrub]] 06:02, 13 April 2011 (EDT)		That's a great find, BBloke. I never looked at the demo exe. While the debug fonction was deleted in the release, it permits to locate the basic AI fonctions in the code. So we have: AI_patrol_mode (0x4A = 0) at 0x0407D60, AI_Sniper_mode (0x4A = 1) at 0x04081A0, AI_combat_mode (0x4A = 2) at 0x0408430, AI_escape_mode (0x4A = 3) at 0x04067F0 and even the AI_evaluation_mode at 0x0408430, which fills offset 0x4A when it is equal to something else. Other functions can be found as well with the debug info. Fantastic. Now we could try to make AI take cover from time to time, instead of making a stupidly exposed target.--[[User:Kyrub\|Kyrub]] 06:02, 13 April 2011 (EDT)
	:Definitely a great find. Having 4 AI modes makes sense and looking at the other text I think it lists actions/moves/options for each mode: Patrol (~~Finding Route,~~ Set Patrol Point, Moving~~, Partial Cover~~), Combat (Attack Attempt, Find Fire Point, Select Target, Firing, Find Cover), Sniper (~~Guard~~, Final Facing) ~~and escape~~ (Moving, GoUfo, etc.) [[User:Hobbes\|Hobbes]] 10:47, 26 January 2012 (EST)		:Definitely a great find. Having 5 AI modes makes sense and looking at the other text I think it lists actions/moves/options for each mode: Patrol (Set Patrol Point, Finding Route, Moving), Combat (Attack Attempt, Find Fire Point, Select Target, Firing, Find Cover), Sniper (Evaluating Mode, Final Facing), Escape (Moving, GoUfo, etc.) and Guard.
			::I'm trying to correlate this info with the /ROUTES files, especially the entry called 'flag' - I remember a post a long time ago that those values determined the rank of the aliens that could use them. What I'm wondering is if there's a relation between the map location (and node 'flag' value) and the value found on UNITREF.DAT[[User:Hobbes\|Hobbes]] 10:47, 26 January 2012 (EST)

	== Offset 0x6F ==		== Offset 0x6F ==

Hobbes: /* Offset 0x4A (74) */

2012-01-26T15:47:39Z

Offset 0x4A (74)

← Older revision		Revision as of 15:47, 26 January 2012
Line 187:		Line 187:

	That's a great find, BBloke. I never looked at the demo exe. While the debug fonction was deleted in the release, it permits to locate the basic AI fonctions in the code. So we have: AI_patrol_mode (0x4A = 0) at 0x0407D60, AI_Sniper_mode (0x4A = 1) at 0x04081A0, AI_combat_mode (0x4A = 2) at 0x0408430, AI_escape_mode (0x4A = 3) at 0x04067F0 and even the AI_evaluation_mode at 0x0408430, which fills offset 0x4A when it is equal to something else. Other functions can be found as well with the debug info. Fantastic. Now we could try to make AI take cover from time to time, instead of making a stupidly exposed target.--[[User:Kyrub\|Kyrub]] 06:02, 13 April 2011 (EDT)		That's a great find, BBloke. I never looked at the demo exe. While the debug fonction was deleted in the release, it permits to locate the basic AI fonctions in the code. So we have: AI_patrol_mode (0x4A = 0) at 0x0407D60, AI_Sniper_mode (0x4A = 1) at 0x04081A0, AI_combat_mode (0x4A = 2) at 0x0408430, AI_escape_mode (0x4A = 3) at 0x04067F0 and even the AI_evaluation_mode at 0x0408430, which fills offset 0x4A when it is equal to something else. Other functions can be found as well with the debug info. Fantastic. Now we could try to make AI take cover from time to time, instead of making a stupidly exposed target.--[[User:Kyrub\|Kyrub]] 06:02, 13 April 2011 (EDT)
			:Definitely a great find. Having 4 AI modes makes sense and looking at the other text I think it lists actions/moves/options for each mode: Patrol (Finding Route, Set Patrol Point, Moving, Partial Cover), Combat (Attack Attempt, Find Fire Point, Select Target, Firing, Find Cover), Sniper (Guard, Final Facing) and escape (Moving, GoUfo, etc.) [[User:Hobbes\|Hobbes]] 10:47, 26 January 2012 (EST)

	== Offset 0x6F ==		== Offset 0x6F ==

Hobbes: /* Offset 0x2B (43) */

2012-01-08T23:20:12Z

Offset 0x2B (43)

← Older revision		Revision as of 23:20, 8 January 2012
Line 367:		Line 367:
	--[[User:Volutar\|Volutar]] 04:40, 26 September 2011 (EDT)		--[[User:Volutar\|Volutar]] 04:40, 26 September 2011 (EDT)
	::You say it is also used for choosing AI patrol path. Does it mean that once a unit is assigned as a "scout" it will keep patrolling only on scout ranked nodes for the rest of his life? Does it also work the other way around, if a unit is not marked with this flag, it is not allowed to patrol on scout nodes? --[[User:Daiky\|Daiky]] 05:56, 6 January 2012 (EST)		::You say it is also used for choosing AI patrol path. Does it mean that once a unit is assigned as a "scout" it will keep patrolling only on scout ranked nodes for the rest of his life? Does it also work the other way around, if a unit is not marked with this flag, it is not allowed to patrol on scout nodes? --[[User:Daiky\|Daiky]] 05:56, 6 January 2012 (EST)
			:::Yeah, someone mentioned something about that a long time ago on the xcomufo.com forums. Certain aliens are 'flagged' for something at the beginning. But this can be merely a way for the engine to ensure that certain aliens remain outside, and not related to the AI.[[User:Hobbes\|Hobbes]] 18:20, 8 January 2012 (EST)

Daiky: /* Offset 0x2B (43) */

2012-01-06T10:56:39Z

Offset 0x2B (43)

← Older revision		Revision as of 10:56, 6 January 2012
Line 366:		Line 366:
	Apparently it can be called "AI_Wanderer_Flag" or something like that.		Apparently it can be called "AI_Wanderer_Flag" or something like that.
	--[[User:Volutar\|Volutar]] 04:40, 26 September 2011 (EDT)		--[[User:Volutar\|Volutar]] 04:40, 26 September 2011 (EDT)
			::You say it is also used for choosing AI patrol path. Does it mean that once a unit is assigned as a "scout" it will keep patrolling only on scout ranked nodes for the rest of his life? Does it also work the other way around, if a unit is not marked with this flag, it is not allowed to patrol on scout nodes? --[[User:Daiky\|Daiky]] 05:56, 6 January 2012 (EST)

Volutar: /* Offset 0x2B (43) */

2011-09-26T08:53:00Z

Offset 0x2B (43)

← Older revision		Revision as of 08:53, 26 September 2011
Line 361:		Line 361:
	== Offset 0x2B (43) ==		== Offset 0x2B (43) ==

	This value is set for some % of alien units at map initialization ~~state~~ (depending on mission type, alien craft type, and alien rank). If this field set to 1, the unit is spawned at "zero" (scout) point, otherwize appropriate rank spawn points are used. Though, if all rank points being occupied - every next unit spawned at ~~this~~ "zero" point.		This value is set for some % of alien units at map initialization stage (depending on mission type, alien craft type, and alien rank). If this field set to 1, the unit is spawned at "zero" (scout) point, otherwize appropriate rank spawn points are used. Though, if all rank points being occupied - every next unit spawned at any "zero" point.
	This value also used for choosing AI patrol path.		This value also used for choosing AI patrol path.

	Apparently ~~this~~ can be called "~~AI_wanderer~~" or something like that.		Apparently it can be called "AI_Wanderer_Flag" or something like that.
	--[[User:Volutar\|Volutar]] 04:40, 26 September 2011 (EDT)		--[[User:Volutar\|Volutar]] 04:40, 26 September 2011 (EDT)

Volutar: /* Offset 0x2B (43) */

2011-09-26T08:41:22Z

Offset 0x2B (43)

← Older revision		Revision as of 08:41, 26 September 2011
Line 359:		Line 359:
	I'm guessing it's a 2 byte count at least, which would account for the 124 and 125 bytes. If I think of anything for the others, I'll let you know. [[User:Hatfarm\|Hatfarm]] 01:07, 13 June 2010 (EDT)		I'm guessing it's a 2 byte count at least, which would account for the 124 and 125 bytes. If I think of anything for the others, I'll let you know. [[User:Hatfarm\|Hatfarm]] 01:07, 13 June 2010 (EDT)

	== Offset ~~0x1B~~ (27) ==		== Offset 0x2B (43) ==

	This value is set for some % of alien units at map initialization state (depending on mission type, alien craft type, and alien rank). If this field set to 1, the unit is spawned at "zero" (scout) point, otherwize appropriate rank spawn points are used. Though, if all rank points being occupied - every next unit spawned at this "zero" point.		This value is set for some % of alien units at map initialization state (depending on mission type, alien craft type, and alien rank). If this field set to 1, the unit is spawned at "zero" (scout) point, otherwize appropriate rank spawn points are used. Though, if all rank points being occupied - every next unit spawned at this "zero" point.

← Older revision		Revision as of 23:20, 8 January 2012
Line 367:		Line 367:
	--[[User:Volutar\|Volutar]] 04:40, 26 September 2011 (EDT)		--[[User:Volutar\|Volutar]] 04:40, 26 September 2011 (EDT)
	::You say it is also used for choosing AI patrol path. Does it mean that once a unit is assigned as a "scout" it will keep patrolling only on scout ranked nodes for the rest of his life? Does it also work the other way around, if a unit is not marked with this flag, it is not allowed to patrol on scout nodes? --[[User:Daiky\|Daiky]] 05:56, 6 January 2012 (EST)		::You say it is also used for choosing AI patrol path. Does it mean that once a unit is assigned as a "scout" it will keep patrolling only on scout ranked nodes for the rest of his life? Does it also work the other way around, if a unit is not marked with this flag, it is not allowed to patrol on scout nodes? --[[User:Daiky\|Daiky]] 05:56, 6 January 2012 (EST)
			:::Yeah, someone mentioned something about that a long time ago on the xcomufo.com forums. Certain aliens are 'flagged' for something at the beginning. But this can be merely a way for the engine to ensure that certain aliens remain outside, and not related to the AI.[[User:Hobbes\|Hobbes]] 18:20, 8 January 2012 (EST)