TiTSEd for Cold Korgonne Restore

AsterionPrimus

New Member
Dec 3, 2019
3
1
34
So I recently discovered that Eitan existed, and the only way to access him was to have saved the Cold Korgonne in the cave on Uveto. I didn't know this 4 weeks ago and left her to freeze, thereby removing her from the game.

I was told using TitSEd could possibly revert her encounter flags, but I don't know which flags to modify or to what.

I tried changing the ULA_TALKED, ULA_LEAVE_TIMER, and ULA_MET values from 1 to 0, but it didn't reset that event. My ULA_CAVE has a "UVIP R36" next to it, and someone who rescued her says theirs has "UVIP J18"

If someone knows what I need to do to get her back in so I can have access to that beautiful Eitan, please help me out!
 

TheShepard256

Well-Known Member
I think the proper way would be to set almost all of Ula's flags to undefined (i.e. delete the values and leave them blank), which should reset her in-game state and make her available again. The only flag you don't have to do this with is ULA_CAVE, which specifies which cave Ula was in when you found her (though you can set it to undefined if you wish). I haven't tested this myself, but based on what I've read in the code, it should work.

To be precise, ULA_LEAVE_TIMER, ULA_SAVED and ULA_CAVE are the flags which determine Ula's condition:
  • If ULA_SAVED is defined, then Ula has been saved and Korg'ii Hold is accessible.
  • If ULA_CAVE is undefined, she has a 20% chance to appear in any eligible cave upon entering, setting ULA_CAVE to your current location.
  • If ULA_CAVE is defined but both other flags are undefined, then Ula can be approached, or left alone without risk of her being removed from the game. Once you approach her, ULA_LEAVE_TIMER will be set to the game's timestamp (a value that says how long it's been in in-game minutes since the start of Steele's adventure).
  • ULA_SAVED will be set to 1 if you give her a Heat Belt or Arctic Warfare Belt, and to 2 if you give her an Insulated Coat.
  • If the game's timestamp exceeds ULA_LEAVE_TIMER + 5*24*60 and ULA_SAVED is undefined (i.e. you go 5 days after talking with her without rescuing her), then Ula and the rest of Korg'ii Hold's content are inaccessible.

Also remember to take the "Middle" option at the end of the Siege of Korg'ii Hold; otherwise, Eitan's post-Siege content won't be available.
 
  • Like
Reactions: Senera2000

AsterionPrimus

New Member
Dec 3, 2019
3
1
34
I think the proper way would be to set almost all of Ula's flags to undefined (i.e. delete the values and leave them blank), which should reset her in-game state and make her available again. The only flag you don't have to do this with is ULA_CAVE, which specifies which cave Ula was in when you found her (though you can set it to undefined if you wish). I haven't tested this myself, but based on what I've read in the code, it should work.

To be precise, ULA_LEAVE_TIMER, ULA_SAVED and ULA_CAVE are the flags which determine Ula's condition:
  • If ULA_SAVED is defined, then Ula has been saved and Korg'ii Hold is accessible.
  • If ULA_CAVE is undefined, she has a 20% chance to appear in any eligible cave upon entering, setting ULA_CAVE to your current location.
  • If ULA_CAVE is defined but both other flags are undefined, then Ula can be approached, or left alone without risk of her being removed from the game. Once you approach her, ULA_LEAVE_TIMER will be set to the game's timestamp (a value that says how long it's been in in-game minutes since the start of Steele's adventure).
  • ULA_SAVED will be set to 1 if you give her a Heat Belt or Arctic Warfare Belt, and to 2 if you give her an Insulated Coat.
  • If the game's timestamp exceeds ULA_LEAVE_TIMER + 5*24*60 and ULA_SAVED is undefined (i.e. you go 5 days after talking with her without rescuing her), then Ula and the rest of Korg'ii Hold's content are inaccessible.

Also remember to take the "Middle" option at the end of the Siege of Korg'ii Hold; otherwise, Eitan's post-Siege content won't be available.


So I attempted to set those Ula values to undefined by leaving them blank, and also realized that what I thought was ULA_MET/ULA_TALKED were actually for Una, so I set those back to the 1s they were originally. However, it seems these changes may have disrupted the game's ability to read my file as it seems to just be stuck on this "Got file, verifying..." message when I attempt to load it in. After that, I tried setting it back to the original cave I found her in (UVIP R36) and when I went there, it still showed me the message that she's gone forever.

On a side note, each attempt I make at this seems to set me back from Uveto to Tavros with a full inventory of stuff I've found and sold previously that I have to go through all over again. Not sure why that is..?
 
  • Like
Reactions: Senera2000

TheShepard256

Well-Known Member
On a side note, each attempt I make at this seems to set me back from Uveto to Tavros with a full inventory of stuff I've found and sold previously that I have to go through all over again. Not sure why that is..?
The only way I think this could happen is if the file you're editing is actually an earlier one than you think it is. As for the rest of it, I've no idea, since I'm not an expert on save file editing. I've used TiTsEd for cosmetic changes, but loading the edited file didn't seem to be any different than loading a non-edited file.
Maybe try again using an unedited save? If that doesn't work, then I'm sorry, but I can't help you any further.
 

AsterionPrimus

New Member
Dec 3, 2019
3
1
34
I forgot to come back and reply to this. I managed to solve the issue by simply setting the flags to having saved Ula without actually encountering her. I was concerned if I didn't encounter her properly myself, the Siege quest wouldn't activate, but that seems to not matter. Now I just have to make sure I can get through the damn siege in one piece! Thanks for the help!