Difference between revisions of "Talk:INTER.DAT"
m (→Nice work: new section) |
|||
| (11 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| − | + | ||
| − | + | == Logging Interception status window messages to file? == | |
| − | + | ||
| − | + | (Spike to Seb76) | |
| − | + | Dude, if there is any way you could enable your Extender to log the status messages out to a log file that would really help me in figuring out the air combat mechanics. It's very difficult/impossible to reliably read the status messages off the screen. And there are not that many other options to be able to count when a craft hits or misses another craft. But then you are probably way ahead of me on figuring out the mechanics since you are decompiling the logic directly! :) | |
| − | + | ||
| + | cheers, [[User:Spike|Spike]] 06:52, 5 July 2009 (EDT) | ||
| + | |||
| + | == UFO vs UFO, Interceptor vs Interceptor == | ||
| + | |||
| + | I wonder how hard it would be to hack INTER.DAT to get a fight going between UFOs or between XCom aircraft? You would need to set the pointers in both directions between [[CRAFT.DAT]] and [[INTER.DAT]]. You might want to force [[LOC.DAT]] as well. If the target was a UFO, the game would know how to operate it, but if the attacker was a UFO would the intercept interface work? Would attack modes work for UFOs? If the game was running an XCom craft, would it know how to use the weapons, and would it handle them running out of ammo? | ||
| + | |||
| + | If this could be made to work, you could also get situations where 1 XCom craft fights multiple UFOs, i.e. the UFOs are the "attacker". | ||
| + | |||
| + | If the XCom craft was the "target", you might need to fudge things by giving the XCom craft stats for a built in weapon, if the AI doesn't know how to use weapons attached in weapons pods. | ||
| + | |||
| + | Maybe some of this could be tested by giving a UFO limited ammo in a regular game. Or trying to arm it with XCom weapons. [[User:Spike|Spike]] 20:03, 14 March 2010 (EDT) | ||
| + | |||
| + | == Nice work == | ||
| + | |||
| + | Thanks Volutar! [[User:Spike|Spike]] 05:24, 13 October 2011 (EDT) | ||
Latest revision as of 09:24, 13 October 2011
Logging Interception status window messages to file?
(Spike to Seb76) Dude, if there is any way you could enable your Extender to log the status messages out to a log file that would really help me in figuring out the air combat mechanics. It's very difficult/impossible to reliably read the status messages off the screen. And there are not that many other options to be able to count when a craft hits or misses another craft. But then you are probably way ahead of me on figuring out the mechanics since you are decompiling the logic directly! :)
cheers, Spike 06:52, 5 July 2009 (EDT)
UFO vs UFO, Interceptor vs Interceptor
I wonder how hard it would be to hack INTER.DAT to get a fight going between UFOs or between XCom aircraft? You would need to set the pointers in both directions between CRAFT.DAT and INTER.DAT. You might want to force LOC.DAT as well. If the target was a UFO, the game would know how to operate it, but if the attacker was a UFO would the intercept interface work? Would attack modes work for UFOs? If the game was running an XCom craft, would it know how to use the weapons, and would it handle them running out of ammo?
If this could be made to work, you could also get situations where 1 XCom craft fights multiple UFOs, i.e. the UFOs are the "attacker".
If the XCom craft was the "target", you might need to fudge things by giving the XCom craft stats for a built in weapon, if the AI doesn't know how to use weapons attached in weapons pods.
Maybe some of this could be tested by giving a UFO limited ammo in a regular game. Or trying to arm it with XCom weapons. Spike 20:03, 14 March 2010 (EDT)
Nice work
Thanks Volutar! Spike 05:24, 13 October 2011 (EDT)