Difference between revisions of "LOC.DAT"

From UFOpaedia
Jump to navigation Jump to search
Line 26: Line 26:
 
:'''NOTE''': The maximum and minimum values for the coordinates is assumed to be the same as [[WORLD.DAT]] (which makes sense). They haven't actually been tested. (''I'm too lazy for that --[[User:Pi Masta|Pi Masta]]'')
 
:'''NOTE''': The maximum and minimum values for the coordinates is assumed to be the same as [[WORLD.DAT]] (which makes sense). They haven't actually been tested. (''I'm too lazy for that --[[User:Pi Masta|Pi Masta]]'')
  
'''0A-0B:''' Appears to be the 'count suffix' of the item, eg: Skyranger-'''1''' or Crash Site-'''47'''. It appears to have no meaning for XCOM Bases, but for other types where it is set, the next byte (0B) always seems to be 0, and is probably the high byte but I've never gotten over 255 UFO's or crafts to test this. ''--[[User:Pi Masta|Pi Masta]]'' 
+
'''0A-0B:''' Count suffix of the item, eg: Skyranger-'''1''' or Crash Site-'''47'''. It appears to have no meaning for XCOM Bases, but for other types where it is set, 0B is the high byte for when you go over 255 UFO's or crafts, etc.  
 
 
This is indeed a two byte integer, as I edited these bytes to 00 10 and it said that I had Skyranger-'''256''', so that is how it works for sure.''--[[User:hatfarm|hatfarm]]''
 
  
 
'''0C-0F:''' NEED HELP
 
'''0C-0F:''' NEED HELP

Revision as of 16:48, 20 September 2009

LOC.DAT has a row width of 20 bytes. There are a total of 50 records (not all of them necessarily used) for a fixed file size of 1,000 bytes. Most of this info is from NKF (thanks a lot) and some was ripped from Hatfarm / Chris Voss's great pages

Structure

00: Object type:

   00 - Unused entry
   01 - Alien Ship
   02 - X-Com Ship
   03 - X-Com Base
   04 - Alien Base
   05 - Crash Site
   06 - Landed UFO
   07 - Waypoint
   08 - Terror Site

01: Object table reference - Possible values - 00 to FF - Just a reference. This just shows how many there are of this type on the geoscape. If the object is either a UFO (Alien Ship for TFTD) or X-COM craft, then this is the index into CRAFT.DAT. If the object is an X-Com base, then this is the index into BASE.DAT.

02-03: Horizontal starting coordinates (low bit then high bit respectively). 0 - 2880

04-05: Vertical starting coordinates (low bit then high bit respectively). -720 - 720

NOTE: Ships don't land on the exact place that the alien ship is, that's why there will be discrepancies between the alien and x-com ship destination info.

06-07: Horizontal destination coordinates (low bit then high bit respectively). 0 - 2880

08-09: Vertical destination coordinates (low bit then high bit respectively). -720 - 720

NOTE: The maximum and minimum values for the coordinates is assumed to be the same as WORLD.DAT (which makes sense). They haven't actually been tested. (I'm too lazy for that --Pi Masta)

0A-0B: Count suffix of the item, eg: Skyranger-1 or Crash Site-47. It appears to have no meaning for XCOM Bases, but for other types where it is set, 0B is the high byte for when you go over 255 UFO's or crafts, etc.

0C-0F: NEED HELP

10: Something to do with visibility, not really sure however.

Possible bit field? --Pi Masta 16:55, 13 March 2007 (PDT)
bit
2 (value 4) seen this change on alien crafts when I targeted it for the first time
1 (value 2) Alien craft always have this flagged, for Xcom craft 0 - At base or patrolling, 1 - Moving (moving bit field?)
0 (value 1) not visible/detected field, 0 - visible, 1 - not visible
For Alien Bases
1 (value 1) Base is freshly discovered and will be revealed on next month end.
--Darkfred 23:22, 11 June 2007 (PDT)

11-13: NEED HELP

NOTE: Other files (e.g., CRAFT.DAT) reference the entry number for the base. For example, if the value is 0A then that base is in entry 10 of this file.

See Also