Talk:Tactical AI - Revision history

Hobbes: /* Byte 22 */

2012-03-21T18:26:57Z

Byte 22

← Older revision		Revision as of 18:26, 21 March 2012
Line 8:		Line 8:
	Byte 0x16 used as boolean field so no matter what value you put in (zero/non-zero only matter). It used only in one waypoint function which called from patrol function. And work only when it's Base Defence mission.		Byte 0x16 used as boolean field so no matter what value you put in (zero/non-zero only matter). It used only in one waypoint function which called from patrol function. And work only when it's Base Defence mission.
	--[[User:Volutar\|Volutar]] 09:24, 21 March 2012 (EDT)		--[[User:Volutar\|Volutar]] 09:24, 21 March 2012 (EDT)
			:Regarding byte 0x15 (or 21) there's a bit of empirical evidence that 'something' is being used by the AI to know which specific locations to guard (UFO bridges, etc.). When I'm designing new maps I also set the byte on some nodes to 'attract' the aliens to those locations and it does have an effect on their actions.
			:Regarding byte 0x16 I think I activated that function during a Terror Site mission once although I haven't been able yet to repeat it. Me and Bomb Bloke have been discussing this byte and testing on StrategyCore, you can read it at this [[http://www.strategycore.co.uk/forums/Question-to-all-EU-veterans-t9598.html\|thread]]. Can you explain what the function does exactly? [[User:Hobbes\|Hobbes]] 14:26, 21 March 2012 (EDT)

Volutar: /* Byte 22 */

2012-03-21T13:24:52Z

Byte 22

← Older revision		Revision as of 13:24, 21 March 2012
Line 7:		Line 7:
	According original game code, byte 0x15 doesn't mean anything. You can put in it whatever you want, and nothing will happen.		According original game code, byte 0x15 doesn't mean anything. You can put in it whatever you want, and nothing will happen.
	Byte 0x16 used as boolean field so no matter what value you put in (zero/non-zero only matter). It used only in one waypoint function which called from patrol function. And work only when it's Base Defence mission.		Byte 0x16 used as boolean field so no matter what value you put in (zero/non-zero only matter). It used only in one waypoint function which called from patrol function. And work only when it's Base Defence mission.
	----		--[[User:Volutar\|Volutar]] 09:24, 21 March 2012 (EDT)

Volutar at 13:24, 21 March 2012

2012-03-21T13:24:29Z

← Older revision		Revision as of 13:24, 21 March 2012
Line 4:		Line 4:

	Scratch the firepoint theory. Aliens simply won't try to destroy terrain to take out base modules. Plus, some reading concerning line of fire made me think that most likely the alien is checking for LOF when the AI displays the function 'Fire Point'. However, that still leaves the question of why do the same values appear on TFTD for byte 22 on the XCom Bases terrain. Could both values be related since the value of byte 21 and 22 seem to always be the same? Questions, questions... [[User:Hobbes\|Hobbes]] 13:07, 19 March 2012 (EDT)		Scratch the firepoint theory. Aliens simply won't try to destroy terrain to take out base modules. Plus, some reading concerning line of fire made me think that most likely the alien is checking for LOF when the AI displays the function 'Fire Point'. However, that still leaves the question of why do the same values appear on TFTD for byte 22 on the XCom Bases terrain. Could both values be related since the value of byte 21 and 22 seem to always be the same? Questions, questions... [[User:Hobbes\|Hobbes]] 13:07, 19 March 2012 (EDT)

			According original game code, byte 0x15 doesn't mean anything. You can put in it whatever you want, and nothing will happen.
			Byte 0x16 used as boolean field so no matter what value you put in (zero/non-zero only matter). It used only in one waypoint function which called from patrol function. And work only when it's Base Defence mission.
			----

Hobbes at 17:07, 19 March 2012

2012-03-19T17:07:09Z

← Older revision		Revision as of 17:07, 19 March 2012
Line 2:		Line 2:

	Using an hex editor I've changed the setting of the byte both for 5 and 10 in different route nodes and then used it first on the beta with the debug function and afterwards on the DOS version. On the DOS version I even armed some aliens with blaster launchers to see what would happened. With the debug function it looked that the AI considered more the option 'Firing Point' while evaluating the options for each unit, but in both cases the aliens didn't try to destroy the terrain underneath the nodes. I'm still not certain to have personally seen actual cases of that event happening - need to confirm. [[User:Hobbes\|Hobbes]] 23:23, 18 March 2012 (EDT)		Using an hex editor I've changed the setting of the byte both for 5 and 10 in different route nodes and then used it first on the beta with the debug function and afterwards on the DOS version. On the DOS version I even armed some aliens with blaster launchers to see what would happened. With the debug function it looked that the AI considered more the option 'Firing Point' while evaluating the options for each unit, but in both cases the aliens didn't try to destroy the terrain underneath the nodes. I'm still not certain to have personally seen actual cases of that event happening - need to confirm. [[User:Hobbes\|Hobbes]] 23:23, 18 March 2012 (EDT)

			Scratch the firepoint theory. Aliens simply won't try to destroy terrain to take out base modules. Plus, some reading concerning line of fire made me think that most likely the alien is checking for LOF when the AI displays the function 'Fire Point'. However, that still leaves the question of why do the same values appear on TFTD for byte 22 on the XCom Bases terrain. Could both values be related since the value of byte 21 and 22 seem to always be the same? Questions, questions... [[User:Hobbes\|Hobbes]] 13:07, 19 March 2012 (EDT)

Hobbes: Created page with "==Byte 22== Using an hex editor I've changed the setting of the byte both for 5 and 10 in different route nodes and then used it first on the beta with the debug function and af..."

2012-03-19T03:23:06Z

Created page with "==Byte 22== Using an hex editor I've changed the setting of the byte both for 5 and 10 in different route nodes and then used it first on the beta with the debug function and af..."

New page

==Byte 22==

Using an hex editor I've changed the setting of the byte both for 5 and 10 in different route nodes and then used it first on the beta with the debug function and afterwards on the DOS version. On the DOS version I even armed some aliens with blaster launchers to see what would happened. With the debug function it looked that the AI considered more the option 'Firing Point' while evaluating the options for each unit, but in both cases the aliens didn't try to destroy the terrain underneath the nodes. I'm still not certain to have personally seen actual cases of that event happening - need to confirm. [[User:Hobbes|Hobbes]] 23:23, 18 March 2012 (EDT)