Talk:INTER.DAT - Revision history

Spike: /* Nice work */ new section

2011-10-13T09:24:59Z

Nice work: new section

← Older revision		Revision as of 09:24, 13 October 2011
Line 16:		Line 16:

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

Spike: New section: UFO vs UFO, Interceptor vs Interceptor

2010-03-15T00:03:01Z

New section: UFO vs UFO, Interceptor vs Interceptor

← Older revision		Revision as of 00:03, 15 March 2010
Line 6:		Line 6:

	cheers, [[User:Spike\|Spike]] 06:52, 5 July 2009 (EDT)		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)

Spike: Moving to main article

2010-02-17T22:39:21Z

Moving to main article

@@ Line 1: / Line 1: @@
 == Logging Interception status window messages to file? ==
 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)

Spike: Refining this info slowly

2010-02-17T22:38:01Z

Refining this info slowly

← Older revision		Revision as of 22:38, 17 February 2010
Line 5:		Line 5:

	Record structure:		Record structure:
	*0x00 (word): ??window ~~present / record~~ active??		*0x00 (word): active/inactive window:
	*0x02 (word): ?aircraft type or icon?		**0= active window (aircraft exists & is in intercept range)
	*0x04 (word): ?aircraft number to use as label on minimised window?		**1= no active window (aircraft does not exist or does exist but is not in intercept range now)
			*0x02 (word): ?aircraft type or icon? 3=Interceptor?
			*0x04 (word): ?aircraft number to use as label on minimised window? Or is 0x08 the aircraft#?
	*0x6/8 (words): 4-3 3-2 2-1 1-0. Some kind of previous/current/next window linked list?		*0x6/8 (words): 4-3 3-2 2-1 1-0. Some kind of previous/current/next window linked list?
	*0x0a (~~word~~): ~~eg '''08 00'''~~ window ~~dimensions~~?		*0x0a/c (words): window/icon type/status?
	*~~0x0c (word): eg '''04 00''' window dimensions?~~		** 0008 0004 is maximised. 0004 0000 is minimised. 0006 0001 is yellow cross on Geoscape.
	*0x0e (word): ?window open =1 minimised =0 ??		*0x0e (word): ?window open =1 minimised =0 ?? No, seems not...
	*0x12 (word): y position of window (accessed as a byte where I found it but it is most likely a word).		*0x12 (word): y position of window (accessed as a byte where I found it but it is most likely a word).
	*0x14 (word): x position of window (x position is accessed as a word)		*0x14 (word): x position of window (x position is accessed as a word)
	*0x16 (word): status message (starting at offset 0x397 in [[ENGLISH.DAT]])		*0x16 (word): status message (starting at offset 0x397 in [[ENGLISH.DAT]])
	*0x18 (word): count down before the status message is cleared		*0x18 (word): count down before the status message is cleared
	*0x1A (word): ~~firing~~ mode		*0x1A (word): attack mode 0=Standoff 1=Cautious 2=Standard 3=Aggressive
	*0x1C (word): ?current distance to target? (km x8) eg '''30 02''' = 560 = 70km (stand off)		*0x1C (word): ?current distance to target? (km x8) - can exceed standoff range (if 0x00 = 01)
	*0x1E (word): requested distance to target (km x8)		*0x1E (word): requested distance to target (km x8) eg '''30 02''' = 560 = 70km (stand off)
	*0x22 (word): air speed (current? max?) eg '''18 15''' = 5,400 = Avenger		*0x22 (word): air speed (current? max?) eg '''18 15''' = 5,400 = Avenger
	*0x24 (word): ?current damage sustained by this XCom craft?		*0x24 (word): ?current damage sustained by this XCom craft?
Line 25:		Line 27:
	*0x86 (dword): memory pointer to CRAFT.DAT entry of the attacked UFO		*0x86 (dword): memory pointer to CRAFT.DAT entry of the attacked UFO
	*0x8A (dword): memory pointer to attacked craft builtin stats		*0x8A (dword): memory pointer to attacked craft builtin stats

			It is difficult to get saved inter.dat files while air combat is happening. The Options shortcut key from UFOExtender helps somewhat. It seems to be easier to do if you have 4 aircraft engaged, vs just 1 or 2. Or maybe it's just easier if your aircraft are faster than the UFOs and can keep station with them effortlessly.

	== Logging Interception status window messages to file? ==		== Logging Interception status window messages to file? ==

Spike at 01:47, 17 February 2010

2010-02-17T01:47:45Z

← Older revision		Revision as of 01:47, 17 February 2010
Line 5:		Line 5:

	Record structure:		Record structure:
	*0x00 (word): ??~~damage~~?? ~~total guess~~		*0x00 (word): ??window present / record active??
	*0x02 (word): ~~eg '''02 00'''~~		*0x02 (word): ?aircraft type or icon?
	*0x04/6/8 (words): 3-4-3 2-3-2 1-2-1 1-1-0 ~~(hidden)~~. Some kind of previous/next window list~~? Window depth/tiling~~?		*0x04 (word): ?aircraft number to use as label on minimised window?
	*0x0a (word): eg '''08 00'''		*0x6/8 (words): 4-3 3-2 2-1 1-0. Some kind of previous/current/next window linked list?
	*0x0c (word): eg '''04 00'''		*0x0a (word): eg '''08 00''' window dimensions?
			*0x0c (word): eg '''04 00''' window dimensions?
			*0x0e (word): ?window open =1 minimised =0 ??
	*0x12 (word): y position of window (accessed as a byte where I found it but it is most likely a word).		*0x12 (word): y position of window (accessed as a byte where I found it but it is most likely a word).
	*0x14 (word): x position of window (x position is accessed as a word)		*0x14 (word): x position of window (x position is accessed as a word)
Line 18:		Line 20:
	*0x1E (word): requested distance to target (km x8)		*0x1E (word): requested distance to target (km x8)
	*0x22 (word): air speed (current? max?) eg '''18 15''' = 5,400 = Avenger		*0x22 (word): air speed (current? max?) eg '''18 15''' = 5,400 = Avenger
			*0x24 (word): ?current damage sustained by this XCom craft?
	*0x76 (dword): memory pointer to [[CRAFT.DAT]] entry of the attacking craft		*0x76 (dword): memory pointer to [[CRAFT.DAT]] entry of the attacking craft
	*0x7A (dword): memory pointer to attacking [[Talk:GEOSCAPE.EXE#Craft_type_data \| craft builtin stats]]		*0x7A (dword): memory pointer to attacking [[Talk:GEOSCAPE.EXE#Craft_type_data \| craft builtin stats]]

Spike: Additional offsets

2010-02-17T01:19:23Z

Additional offsets

← Older revision		Revision as of 01:19, 17 February 2010
Line 1:		Line 1:
	Just for reference before I forget. Not sure enough yet for main article page.		Just for reference before I forget. Not sure enough yet for main article page.
	*0x12 (word): y position of ~~the windows~~ (accessed as a byte where I found it but it is most likely a word. ~~x position is accessed as a word)~~
	*0x14 (word): x position(?)		File length 0x238 568 bytes
			4 records per interception window x Record length 0x8E 142 bytes

			Record structure:
			*0x00 (word): ??damage?? total guess
			*0x02 (word): eg '''02 00'''
			*0x04/6/8 (words): 3-4-3 2-3-2 1-2-1 1-1-0 (hidden). Some kind of previous/next window list? Window depth/tiling?
			*0x0a (word): eg '''08 00'''
			*0x0c (word): eg '''04 00'''
			*0x12 (word): y position of window (accessed as a byte where I found it but it is most likely a word).
			*0x14 (word): x position of window (x position is accessed as a word)
	*0x16 (word): status message (starting at offset 0x397 in [[ENGLISH.DAT]])		*0x16 (word): status message (starting at offset 0x397 in [[ENGLISH.DAT]])
	*0x18 (word): count down before the status message is cleared		*0x18 (word): count down before the status message is cleared
	*0x1A (word): firing mode		*0x1A (word): firing mode
	*0x1E (word): requested distance to target		*0x1C (word): ?current distance to target? (km x8) eg '''30 02''' = 560 = 70km (stand off)
			*0x1E (word): requested distance to target (km x8)
			*0x22 (word): air speed (current? max?) eg '''18 15''' = 5,400 = Avenger
	*0x76 (dword): memory pointer to [[CRAFT.DAT]] entry of the attacking craft		*0x76 (dword): memory pointer to [[CRAFT.DAT]] entry of the attacking craft
	*0x7A (dword): memory pointer to attacking [[Talk:GEOSCAPE.EXE#Craft_type_data \| craft builtin stats]]		*0x7A (dword): memory pointer to attacking [[Talk:GEOSCAPE.EXE#Craft_type_data \| craft builtin stats]]

Spike: format mistake

2009-07-05T10:53:11Z

format mistake

← Older revision		Revision as of 10:53, 5 July 2009
Line 13:		Line 13:
	== Logging Interception status window messages to file? ==		== Logging Interception status window messages to file? ==

	~~----~~
	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! :)		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)		cheers, [[User:Spike\|Spike]] 06:52, 5 July 2009 (EDT)

Spike: New section: Logging Interception status window messages to file?

2009-07-05T10:52:27Z

New section: Logging Interception status window messages to file?

← Older revision		Revision as of 10:52, 5 July 2009
Line 10:		Line 10:
	*0x86 (dword): memory pointer to CRAFT.DAT entry of the attacked UFO		*0x86 (dword): memory pointer to CRAFT.DAT entry of the attacked UFO
	*0x8A (dword): memory pointer to attacked craft builtin stats		*0x8A (dword): memory pointer to attacked craft builtin stats

			== Logging Interception status window messages to file? ==

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

Seb76 at 10:24, 5 July 2009

2009-07-05T10:24:22Z

← Older revision		Revision as of 10:24, 5 July 2009
Line 7:		Line 7:
	*0x1E (word): requested distance to target		*0x1E (word): requested distance to target
	*0x76 (dword): memory pointer to [[CRAFT.DAT]] entry of the attacking craft		*0x76 (dword): memory pointer to [[CRAFT.DAT]] entry of the attacking craft
			*0x7A (dword): memory pointer to attacking [[Talk:GEOSCAPE.EXE#Craft_type_data \| craft builtin stats]]
	*0x86 (dword): memory pointer to CRAFT.DAT entry of the attacked UFO		*0x86 (dword): memory pointer to CRAFT.DAT entry of the attacked UFO
			*0x8A (dword): memory pointer to attacked craft builtin stats

Seb76 at 22:47, 29 July 2008

2008-07-29T22:47:57Z

← Older revision		Revision as of 22:47, 29 July 2008
Line 4:		Line 4:
	*0x16 (word): status message (starting at offset 0x397 in [[ENGLISH.DAT]])		*0x16 (word): status message (starting at offset 0x397 in [[ENGLISH.DAT]])
	*0x18 (word): count down before the status message is cleared		*0x18 (word): count down before the status message is cleared
			*0x1A (word): firing mode
	*0x1E (word): requested distance to target		*0x1E (word): requested distance to target
	*0x76 (dword): memory pointer to [[CRAFT.DAT]] entry of the attacking craft		*0x76 (dword): memory pointer to [[CRAFT.DAT]] entry of the attacking craft
	*0x86 (dword): memory pointer to CRAFT.DAT entry of the attacked UFO		*0x86 (dword): memory pointer to CRAFT.DAT entry of the attacked UFO