Jump to content

Talk:Tactical AI

From UFOpaedia
Revision as of 13:24, 21 March 2012 by Volutar (talk | contribs)

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. 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... 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.