Can you make the check of versions optional? I was playing a 1.4 scenario and paused it to start a new experimental game. Now with 1.5 out I can not copy my stuff to continue the 1.4 game. The scenario in not updated yet and it is unknown when. So I have to wait and continue the 1.4 scenario wich does not have the new content of 1.5
@El_Globo Could you please try the file I attached here? I couldn't test it but I think it may solve your problem. You know what? It was my intention from the beginning to be more flexible. DAT and EPB files have specific version numbers in their header and I thought of using that instead of the game's version. But my tests show that the ENTS.DAT file (and other binary files) is always version 1 so this number doesn't change if Eleon implement something new. So I had to discard using file numbers and started to check the game's version. Now I'm not to sure it would be wise to let it open to users. What happens if a version drastically changes the EPB and DAT versions enough to break people's games? Some would complain that the tool corrupted their games, others will stop using it without reporting a bug. On the other hand, I cannot guarantee that stuff from a v1.5 saved game will work in v.1.8 right away, for instance. But at least, in cases like this, I can fix it because I must support newer versions and I play Empyrion too so it's easy to spot "forward changes". Now making a newer version writable to older versions would be kinda dangerous. If you have a suggestion for making the tool less strict on that I'm all ears, of course.
After reading all these, I have to agree with you. Safety goes first, for save files. After all the tool is made to maintain and carry progress, not break it.
Can you let the tool create backups of both savegames and only transfer them between the backups if two versions are too far apart?
I can think of something like that. The caveat is that a savegame may reach 100MBs in size and would need to be zipped. Also backing up everytime you copy a structure would take considerate time and space. There is a way and I'll try that. You mean between versions "v1.5.1" and "v1.5.2" or "v1.5.1" and "v1.6", for instance? The former would be safer.
No, not every single time. At least not while there are no problems arising. I indeed mean to use a backup if you want to transfer structures between two major versions like 1.5.1 and 1.6. And to not have to backup every single time when you copy a structure you could change the name of the backup savegame for example from "NewGame_0" to "NewGame_0_stt-backup". When your tool see the "stt-backup" then it would just proceed with the transfer. If it doesn't see the "stt-backup" when you try to copy between major releases then it would create the backup. Also only the target savegame would need to be backed up. I don't think there is a need to backup the source savegame as i do not think your tool changes anything in it.
No, one was experimental (for testing my ecf modding changes), the other created on V 1.5.1. 3384. But, before launching the savetool, I launched both games and checked that they were loading fine after the update on public 1.5. They worked fine each and when I quit each game, they were saved in V 1.5.1 3384 with the last update validation, so I guessed that they were good for savegame transfer. But it worked before, when I transfered a saved game in last V 1.4 to the first EXP 1.5 release, so I guessed it was just a version number ID problem.
Hi, By the way I was wondering if you could add other useful options in your savegametransfertool : 1) Could you check player(s) current credits/money bank deposit in the source game and enable it to be transferred into the new game bank account (not into player stuff) of the destination game ? It is easy to get past (via console or withdrawing all your bank account before transfert), but as the game stock amounts of credit by 50000, it could encumber your stuff if you have a lot of money. 2) Could you enable an option to transfer all the carried stuff including armor (and equipped boosters) from the previous game ? I always forgot to put it in a container before the transfert ! Again, thank you for your work, it is very useful.
@El_Globo Thanks for letting me know it's working for you now. About your suggestions, the tool just copies entities that belong to the player and does nothing about the player itself. I would have to create a different tool but it can be done, I guess. I need to see its usefulness right now because we can "give credit 102899" in the console. About the stuff the player carries, I have no idea how to get the same armor's state and attached boosts though. I'd have to research a bit.
@me777 Not at this time I'm afraid. I always play single player so I'm not sure how that would work. Maybe in the future but I can't promise anything right now.
1. According to this post seems that for scenarios with custom items, copying vessels with cargo containing them, between 1.4 and 1.5 poses issues. That means that the custom items can not be transferred between those two saves with the exact version. Is there anything you can do with your tool to update it in order to comply with similar cases? It seems that since ids are changed between 1.4 and 1.5 items get lost during copy. The vanilla items are unaffected, at least as much as I have tested. 2. I think I found a bug. I use the tool to copy a vessel from a save game created with v1.5.0 to a save game created with v1.5.3 and it won't let me.
Seeing something similar moving stuff from 1.4 to 1.5 in Reforged Galaxy. If I load the 1.4 save in the 1.5 client, all items/blocks are exactly what they should be. But if I use the tool to move bases and other things from a 1.4 save to new 1.5 save certain things added in Reforged get substituted with other things. For example, the long range CV radar turns into a poster. Edit: This is using the version in post#102.
Do inventory and remove scenario items only and then move the vanilla stuff from PE/RE scenarios from 1.4 to 1.5. Finally use im command to restore from items those from the scenarios that are missing.
Thanks, guys. I will take a look at all of the things posted here. It's weird that I didn't seem to get notified about the replies or maybe they expired and I didn't see them.
