UFOpaedia - User contributions [en]

Talk:Game Files

2011-08-24T14:13:32Z

Pjlasl:

BB, thanks for your continuing work on this. A question to make sure I'm understanding correctly: MISSDAT has copies of UNITREF from the beginning (UNIREF) and end (UNIREF2) of your latest combat, and they could be compared to see all changes from the combat, yes? Thanks! ---[[User:MikeTheRed|MikeTheRed]] 14:57, 16 June 2006 (PDT)

-------------

This is true, so long as the game was started from scratch. If the game was loaded from a save slot, then you'll need to use UNITREF.DAT from the slot in concern.

For example, if you started a combat, saved it, started another combat, saved it, loaded the first combat and completed it, the UNIREF file in the missdat folder would refer to the second combat, and the UNIREF2 file would refer to the first combat - two entirely different battles!

If you wiped the contents of your missdat folder and then loaded a save file, the UNIREF.DAT file won't turn up at all.

Hence, if you didn't save the first combat at the very beginning, the initial data would be lost. Does that make sense?

- [[User:Bomb_Bloke|Bomb Bloke]]

----

I'm watching my experience counters in UNITREF closely; I have a little util that shows their current values. It's resulted in additional nuances I've pointed out. Also of course I'm using the util for firing-squad training (getting specific soldiers to 3 exp. pts. when aliens are few or weak). Sometimes e.g. my last reaction shot kills the last alien, but I couldn't catch who made that last shot as combat ended. Now that I know a final copy of UNITREF is made, I can always consult it if I want. So, thanks for pointing that out! As for my original question, in truth I don't currently see a reason to compare beginning and ending UNITREF - but I figured the answer would make clear how to work with these files. And you pointed out important potential problems.

In any event. Here's something I do a fair amount, where this can help: I start a combat, save the game, quit X-COM. Later, reload that same savegame and finish the combat. You're saying that those two UNITREFs will be the beginning and end of that combat, no matter how much "real time" has passed. Cool. (As long as I don't start or end any other combats in between!) I gather that if I end a particular combat multiple times (for testing), it will have the initial pristine combat (UNIREF) and only the last ended combat (UNIREF2).

I have a "comparer" that compares one file to another to see changes, such as soldier stats before and after combat. Previously I've worked with individual save slots (one versus the other), but now I see I can cut to the chase and just compare these two UNITREFs, if I want. No more mucking about.

Along those lines though... there is no particular "before and after" for SOLDIER.DAT, right? I don't see two versions in the wiki's MISSDAT listing.

Thanks, as always! ---[[User:MikeTheRed|MikeTheRed]] 18:57, 16 June 2006 (PDT)

----

I hope no one minds, but I've never liked how the save-game files were artificially on a separate page from the main-game files. Us few hackers are interested in them all, as I see it. Conversely, folks not into hacking might be into the many tips on "Under the hood", but are not so likely to be ''only'' interested in main-game files (not save-game files). So, I've moved the main-game section here. However, "Saved Game Files" is no longer an appropriate name for this page. We could rename it (requires admin rights, yes?) or just refer to it as "Game Files" by <nowiki>[[Saved Game Files|Game Files]]</nowiki>. BB, I hope I didn't just collide with your edits.

---[[User:MikeTheRed|MikeTheRed]] 19:35, 16 June 2006 (PDT)

---------

You can complete as many battles as you wish without the uniref file being touched. You can also load battles without it being modified. Back it up if you need to.

I doubt that unit stats are updated by the tactical engine, so I'd assume that uniref and uniref2 won't show you any changes. I could be wrong, though. The experience counters should certainly change.

The missdat folder contains the files listed, as well as a geoscape savegame for the point when combat began. That includes a copy of soldier.dat, however, I doubt the tactical engine modifies this file in any way. It certainly doesn't create another copy.

- [[User:Bomb_Bloke|Bomb Bloke]]

== Reformat ==

What about moving most of this content to the [[:Category:Game Files]]? I'm thinking of making the Tactical and Geoscape save files a sub category in it. Also maybe we could use a template on these files to standardize them a bit, they all have a 'structure' that is generally in a table or a bulleted list, and of course a See Also section.

Hmm, I guess I could copy-paste stuff from here onto the Category page and leave this one alone. We can tweak it to how we like and then set this to redirect.

[[User:Pi Masta|Pi Masta]] 10:14, 4 March 2007 (PST)

----

I know what categorization does on the back end (it lets one make an automatic "see also" page), but not sure what you mean on the front end. I would want all these files here on one page because they relate to each other so directly, for anyone taking a wrench under the hood. Also known as, I say, don't put things on separate pages just because they easily fit mental categories; put things on separate pages if they truly are not likely to be jumped around within, by someone into that level of topic. I for one like seeing everything related to being under the hood, on one page. If you're modifying what a soldier is holding, you need both the EXE level OBJECT.DAT and the Battle level other file, whatever its name was. I can look it up on this one page, hehe. My two cents. - [[User:MikeTheRed|MikeTheRed]] 21:48, 9 March 2007 (PST)

----

Using category pages as article pages has various problems, the biggest of which is you can't format how the list appears. The tables on this page right now look good. However, to save yourself some trouble, rather than put a "See Also: Saved Game Files" section at the bottom of each individual file article, you could just rely on the category link at the bottom (and put "Main Article: Saved Game Files" right at the top of the category page).--[[User:Ethereal Cereal|Ethereal Cereal]] 00:38, 10 March 2007 (PST)

-----

I'd vote against the Saved Games Files section being divvied up. But if a categorization scheme is added purely as an extra that can be used in "See Also" sections, that'd be great. Maybe I'm misunderstanding.

BTW this page is, of course, inaccurately named - it's about saved games ''and'' static program-level files - and I'm to blame for that. Back when Eth re-designed the Main Page, he did a great service given the dozens of pages and hundreds of concepts, but somehow the two pages on "under the hood" got a little disconnected. Back then I was tired of flipping back and forth between the separate pages for Saved Game files and the EXE-level files, so I copied the EXE info (the smaller set) to this page, and unified them. I guess that's sort of my vote for having them on a combined page. What are your thoughts, Pi? - [[User:MikeTheRed|MikeTheRed]] 18:59, 16 March 2007 (PDT)

----

It's trivial to rename (move) pages. What's a better name for this page? Just "Game Files"?--[[User:Ethereal Cereal|Ethereal Cereal]] 22:33, 16 March 2007 (PDT)

----
Yeah, I think he mentioned in the comments above about naming it to game files. That's fine with me.

Poof, it's done.--[[User:Pi Masta|Pi Masta]] 22:47, 16 March 2007 (PDT)

== Data Files Summary ==

Hi folks. There are times when I need to edit a data file but forget the length of each record. I then have to look up the file page in the wiki and try to decode the wording to get the right length. Tis a real pain sometimes. Because of this I created a quick lookup table a while back and had it sitting on my hard drive. Today I added a bunch more entries to include all the saved game files. Eventually, I'd like to include everything to make it even easier. The best way to explain this is to show an example, so here it is:

<table {{StdCenterTable}} class="sortable">
<tr {{StdDescTable_Heading}}><th>File Name</th><th>Records</th><th>Bytes/Record</th><th>File Size</th></tr>
<tr><td align="left">[[ACTS.DAT]]</td><td>12</td><td>7</td><td>84</td></tr>
<tr><td align="left">[[AKNOW.DAT]]</td><td></td><td></td><td>495</td></tr>
<tr><td align="left">[[ALIEN.DAT]]</td><td>12</td><td>124</td><td>1488</td></tr>
<tr><td align="left">[[ASTORE.DAT]]</td><td>50</td><td>12</td><td>600</td></tr>
<tr><td align="left">[[BASE.DAT]]</td><td>8</td><td>292</td><td>2336</td></tr>
<tr><td align="left">[[BGLOB.DAT]]</td><td></td><td></td><td>2</td></tr>
<tr><td align="left">[[BPROD.DAT]]</td><td>8</td><td>350</td><td>2800</td></tr>
<tr><td align="left">[[CRAFT.DAT]]</td><td>50</td><td>104</td><td>5200</td></tr>
<tr><td align="left">[[DIPLOM.DAT]]</td><td>16</td><td>36</td><td>576</td></tr>
<tr><td align="left">[[FACIL.DAT]]</td><td>17</td><td>16</td><td>272</td></tr>
<tr><td align="left">[[GEODATA.DAT]]</td><td></td><td></td><td>92</td></tr>
<tr><td align="left">[[IGLOB.DAT]]</td><td></td><td></td><td>64</td></tr>
<tr><td align="left">[[INTER.DAT]]</td><td></td><td></td><td>568</td></tr>
<tr><td align="left">[[LEASE.DAT]]</td><td></td><td></td><td>180</td></tr>
<tr><td align="left">[[LIGLOB.DAT]]</td><td></td><td></td><td>148</td></tr>
<tr><td align="left">[[LOC.DAT]]</td><td>50</td><td>20</td><td>1000</td></tr>
<tr><td align="left">[[MAP.DAT]]</td><td>Varies</td><td>4</td><td>Varies</td></tr>
<tr><td align="left">[[MISDATA.DAT]]</td><td></td><td></td><td>170<br>172 for TFTD</td></tr>
<tr><td align="left">[[MISSIONS.DAT]]</td><td>84</td><td>8</td><td>672</td></tr>
<tr><td align="left">[[OBPOS.DAT]]</td><td>170<br>200 for TFTD</td><td>16</td><td>2720<br>3200 for TFTD</td></tr>
<tr><td align="left">[[PRODUCT.DAT]]</td><td>35</td><td>18</td><td>630</td></tr>
<tr><td align="left">[[PROJECT.DAT]]</td><td>8</td><td>288</td><td>2304</td></tr>
<tr><td align="left">[[PURCHASE.DAT]]</td><td>91</td><td>20</td><td>1820</td></tr>
<tr><td align="left">[[RESEARCH.DAT]]</td><td>96</td><td>22</td><td>2112</td></tr>
<tr><td align="left">[[ROUTES.DAT]]</td><td>Varies</td><td>24</td><td>Varies</td></tr>
<tr><td align="left">[[SAVEINFO.DAT]]</td><td></td><td></td><td>40</td></tr>
<tr><td align="left">[[SEEMAP.DAT]]</td><td></td><td></td><td>Varies</td></tr>
<tr><td align="left">[[SMOKBIT.DAT]]</td><td></td><td></td><td>Varies</td></tr>
<tr><td align="left">[[SMOKREF.DAT]]</td><td>400</td><td>9</td><td>3600</td></tr>
<tr><td align="left">[[SOLDIER.DAT]]</td><td>250</td><td>68</td><td>17000</td></tr>
<tr><td align="left">[[SOURCEMP.DAT]]</td><td></td><td></td><td>Varies</td></tr>
<tr><td align="left">[[TERMP.DAT]]</td><td></td><td></td><td>Varies</td></tr>
<tr><td align="left">[[TRANSFER.DAT]]</td><td>100</td><td>8</td><td>800</td></tr>
<tr><td align="left">[[UIGLOB.DAT]]</td><td></td><td></td><td>48</td></tr>
<tr><td align="left">[[UNITPOS.DAT]]</td><td>80</td><td>14</td><td>1120</td></tr>
<tr><td align="left">[[UNITREF.DAT]]</td><td>80</td><td>124<br>132 for TFTD</td><td>9920<br>10560 for TFTD</td></tr>
<tr><td align="left">[[UP.DAT]]</td><td>116</td><td>12</td><td>1392</td></tr>
<tr><td align="left">[[WGLOB.DAT]]</td><td>22</td><td>2</td><td>44</td></tr>
<tr><td align="left">[[XBASES.DAT]]</td><td></td><td></td><td>48</td></tr>
<tr><td align="left">[[XCOM.DAT]]</td><td>12</td><td>124</td><td>1488</td></tr>
<tr><td align="left">[[ZONAL.DAT]]</td><td></td><td></td><td>12</td></tr>
</table>

As you can see, it makes a handy reference for the most edited mission files. (The file size cells with "Varies" in it depend on map/ufo size or modules spawned which I have but didn't include here for the moment). There are still a few files which I can't figure out if there is a correct record size or length. If everyone could please look at the table and fill in the blanks it would be much appreciated. Obviously, those fields don't apply to some files so those can be filled in with DNA or something. Before doing this though if we can fill in what we know for a fact, it will save others (like myself) from reinventing the wheel every time something needs to be edited for testing.

Some of the data file pages are worded so cryptically that it makes it impossible to understand for a layperson. Why is that? Obviously, some files are harder to understand due to the subject, but the structure shouldn't one of them in my opinion.

- [[User:Zombie|Zombie]] 21:27, 18 December 2007 (PST)

---------

Never spotted this before...

I've made some tweaks to the table, I believe it should now be completely accurate as far as battlescape save files are concerned. Those files where the record tallies/sizes have been left blank use either single byte values or multiple types listed randomly (ei. They can't be summarised).

- [[User:Bomb Bloke|Bomb Bloke]] 20:46, 12 February 2008 (PST)

:Thanks BB. [[BGLOB.DAT]] is one of those files where it can't be broken down into records so I switched that as well. --[[User:Zombie|Zombie]] 23:03, 13 February 2008 (PST)

----
Did anyone else notice there is no way to delete existing saves, only by overwriting them? Deleting the folder's content from Windows will make the game complain about not finding the save.--[[User:Amitakartok|amitakartok]] 16:55, 10 October 2009 (EDT)

: I have never seen the game complain after wiping any of the saves. It may crash if the save directory doesn't exist - so you only want to be deleting the contents. - [[User:NKF|NKF]] 02:09, 11 October 2009 (EDT)

----
What file contains the zone your base is located in?
- [[User:Pjlasl|pjlasl]] August 24, 2011

Talk:BPROD.DAT

2011-08-08T18:07:04Z

Pjlasl:

The formula the game uses is:

((hours / engineers) / 24) * Qty = days/hours to produce

My example:

I have wanted to produce 2 laser pistols with 5 engineers. According to the [[Laser_Pistol|Laser Pistol]] page, one pistol takes 300 hours to produce. Plugging the numbers into the formula we get:

((300 / 5) / 24) * 2) = 5 days

The game displays '''4''' days '''/ 24''' hours

[[user:PJLASL|pjlasl]]

Talk:BPROD.DAT

2011-08-08T18:05:16Z

Pjlasl: Created page with "The formula the game uses is: ((hours / engineers) / 24) * Qty = days/hours to produce My example: I have wanted to produce 2 laser pistols with 5 engineers. According to the ..."

User:Pjlasl

2011-08-03T22:07:57Z

Pjlasl: Created page with "I am an avid fan of X-COM Enemy Unknown and Terror from the Deep. I am here to help in any way that I can."

I am an avid fan of X-COM Enemy Unknown and Terror from the Deep.

I am here to help in any way that I can.

Talk:TRANSFER.DAT

2011-08-03T22:03:47Z

Pjlasl:

The Item list displayed here is not correct. Transfer.dat uses the exact same rec# found in base.dat. The list on this page only goes to 82, but in reality it should go up to 95.

- [[User:PJLASL|pjlasl]] 03/08/2011

----

A correction to offsets 4-5 for crafts. The reference to GEODATA.dat is incorrect. It is a little more complicated to identify the craft. Here is how it works: in my game I transferred my SkyRanger from base1 to base2. the TRANSFER.dat file shows the value 01 at offset 0x04. If we go by the instructions on the page, 01 = lightning. You have to do some work before you can get the GEODATA.dat translation. Here is how you identify it as a skyranger correctly.

The transfer.dat shows 01. This value is a pointer to the 2nd record in the loc.dat file. Remember the loc.dat record is 20 bytes long so just use the formula (20 * xx) to find the correct offset. After we find the correct place in the loc.dat file the value 02 tells us this is a x-com ship record. according to loc.dat the next offset value (00) tells us the position in the craft.dat file. In the craft.dat file the first offset 0x00 tells us the craft type = SKYRANGER.

transfer.dat 0x04 = 01
:loc.dat (0x20 * 01) validates this is a x-com ship (02)
:loc.dat (0x20 * 01) + 1 = 00
::craft.dat (0x00 * 00) = 00
:::GEODATA.dat 00 = SKYRANGER

- [[User:PJLASL|pjlasl]] 03/08/2011

Talk:TRANSFER.DAT

2011-08-03T21:54:04Z

Pjlasl:

The Item list displayed here is not correct. Transfer.dat uses the exact same rec# found in base.dat. The list on this page only goes to 82, but in reality it should go up to 95.

- [[User:PJLASL|pjlasl]]

----

A correction to offsets 4-5 for crafts. The reference to GEODATA.dat is incorrect. It is a little more complicated to identify the craft. Here is how it works: in my game I transferred my SkyRanger from base1 to base2. the TRANSFER.dat file shows the value 01 at offset 0x04. If we go by the instructions on the page, 01 = lightning. You have to do some work before you can get the GEODATA.dat translation. Here is how you identify it as a skyranger correctly.

The transfer.dat shows 01. This value is a pointer to the 2nd record in the loc.dat file. Remember the loc.dat record is 20 bytes long so just use the formula (20 * xx) to find the correct offset. After we find the correct place in the loc.dat file the value 02 tells us this is a x-com ship record. according to loc.dat the next offset value (00) tells us the position in the craft.dat file. In the craft.dat file the first offset 0x00 tells us the craft type = SKYRANGER.

transfer.dat 0x04 = 01
:loc.dat (0x20 * 01) validates this is a x-com ship (02)
:loc.dat (0x20 * 01) + 1 = 00
::craft.dat (0x00 * 00) = 00
:::GEODATA.dat 00 = SKYRANGER

- [[User:PJLASL|pjlasl]]

Talk:TRANSFER.DAT

2011-08-03T16:22:40Z

Pjlasl:

Talk:TRANSFER.DAT

2011-08-03T16:22:00Z

Pjlasl: Created page with "The Item list displayed here is not correct. Transfer.dat uses the exact same rec# found in base.dat. This list only goes to 82, but in reality it goes up to 95. - [[User:PJLASL..."

The Item list displayed here is not correct. Transfer.dat uses the exact same rec# found in base.dat. This list only goes to 82, but in reality it goes up to 95.

- [[User:PJLASL|pjlasl]]

Talk:PROJECT.DAT

2011-08-02T20:51:42Z

Pjlasl: Created page with "<blockquote>''Each research project's scientist-days remaining is stored in a little-endian word (low-order byte first). For realistic cases, the difference between signed word a..."

<blockquote>''Each research project's scientist-days remaining is stored in a little-endian word (low-order byte first). For realistic cases, the difference between signed word and unsigned word is irrelevant. 96 words i.e. 192 bytes.''</blockquote>

Every reference to research is in hours (research.dat), therefore i took the value as literal. In my case: BB = 187 hours. So I started digging and found that the correct calculation to determine research time (in days) is: roundup((hours / scientist)). Every test case produced the expected result. Below are the test and results.

Motion Scanner: 187 hours | Scientists: 50
* roundup(187/50) = 4 (raw value is 3.7) Result: Research ended at the 23:59:55 hour of the 4th day.

Motion Scanner: 187 hours | Scientists: 100
* roundup(187/100) = 2 days (raw value is 1.8) Result: Research ended at the 23:59:55 of the second day.

Motion Scanner: 187 hours | Scientists: 200
* roundup(187/200) = 1 day (raw value is .9). The research ended at the 23:59:55 of the current day.

Laser Pistol: 19 hours | Scientists: 10
* roundup(19/10) = 3 day (raw value is 2.5). The research ended at the 23:59:55 of the current day.

I think that the above statement needs to be revised.

--[[User:Pjlasl|pjlasl]] 3:27PM 08/01/2011

Talk:Game Files

2011-07-26T22:05:16Z

Pjlasl: