Yes it does. I used it after 1.10. If no changes are made in the database it will be useful as is for long time. Do not worry.
Bear in mind that if you use it for copying vessels for a scenario that has its own custom devices and blocks, various of them might be replaced with other types or even empty ones i.e. a new generator from v1.x of the scenario might be replaced with a heavy window on a save started with a v2.x of the same scenario.So in this case you might end with a missing generator in the target save game. Same goes for copying vessels between vanilla saves and scenarios' saves. Always do an inventory of the devices of your vessels as well as the cargo you might carry between the copy.
One thing I noticed but forgot to mention is that although the copied vessel might have the devices messed, if you spawn the same blueprint on the new save game you want to transfer then the devices seem to be in place. I have not tested thoroughly though. Maybe @byo13 have some idea why this happens...
v0.7.5 (07-22-2024) FIXED: Compatibility was broken with newer versions after core game file changes After a long time (I had to be away because of some family matters), and having to recover my latest source code, I'm back. Sorry for taking so long, guys!
Currently migrating the source code from Purebasic to pure C. Learning a lot of new Empyrion data shenanigans in the process. Yay! Let's see how it goes. It's already as fast as it can be from my tests.
I'd like to thank @byo13 for creating this tool. My Reforged Eden 2 single player save game became corrupted (something involving mis-use of the teleport and sector commands, I think), and I wanted to recover the exact inventory contents of my main CV. The last backup save I had was from dozens of playtime hours ago, and I didn't care about player inventory, research unlock points, mission progression, etc.—all of that can be fixed through the console, and I had recent blueprints of my important ships. But having to rebuild my inventory using itemmenu would have removed any sense of accomplishment and purpose from the stuff I had accumulated, and therefore likely eliminated any interest I had in continuing to play, especially since I was already using itemmenu selectively to reduce the grind here and there (i.e. pentaxid and combat CV ammo). One thing I will note for anyone else bringing in a ship and replacing the same ship in the new save: The CV I brought in from the corrupted save also existed in the last good backup save, and I chose to replace it. The one in the backup save had various SVs and HVs docked to it, and when I loaded the game, those SVs and HVs were still there in space, the old version of the CV I brought in was gone (as expected), and the new CV was there, a little off to the side. When I tried to move the SVs to the new instance of the CV I brought in using this tool, they seemed to be stuck in docked mode, but with no ship under them. This isn't a problem, since I can just blueprint them and re-create them right there in a flyable state, but I thought it was worth mentioning. Anyway, thank you again, @byo13!
There is a console command to un-dock vessels based on their ID. Next time try this if you have any issues like this and see if it helps.
