DIRECT.DAT: Difference between revisions
Appearance
m →See Also: Category |
Bomb Bloke (talk | contribs) Clarifications |
||
| Line 1: | Line 1: | ||
A single 9 byte/null terminated string, that is the path to the save slot the battlescape game was loaded from. | |||
This file | This file is only used if indicated by the [[SAVEINFO.DAT]] file in the missdat folder. Otherwise, the battle is a new one, and a new tactical map is generated from the seeder files also in the missdat folder. | ||
<i>(Note to self - since the map isn't saved to the harddrive unless a savegame is made, how is terrain stock collection stored at the end of battle? Alloys, Alien Navigation, etc...)</i> | |||
< | |||
(Note to self - since the map isn't saved to the harddrive unless a savegame is made, how is terrain stock collection stored at the end of battle? Alloys, Alien Navigation, etc...) | |||
==See Also== | ==See Also== | ||
* [[Saved Game Files]] | * [[Saved Game Files]] | ||
* [[Saved_Game_Files#Missdat_Files|Missdat Files]] | * [[Saved_Game_Files#Missdat_Files|Missdat Files]] | ||
Revision as of 04:20, 17 June 2006
A single 9 byte/null terminated string, that is the path to the save slot the battlescape game was loaded from.
This file is only used if indicated by the SAVEINFO.DAT file in the missdat folder. Otherwise, the battle is a new one, and a new tactical map is generated from the seeder files also in the missdat folder.
(Note to self - since the map isn't saved to the harddrive unless a savegame is made, how is terrain stock collection stored at the end of battle? Alloys, Alien Navigation, etc...)