-
-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add ability to extract save file without processing game files #102
Comments
Excellent idea, I added (3f8d179) a way to do that. Unreleased version here... |
Wasn't expecting such a quick reaction. Stellar job, thank you! Tested b296 on the same save file as b295 by doing the same operation (Export As Text). Compared the output. Only diffs were various missing comments referencing ID-s to human-readable strings (e.g. I further confirmed this with b296 by utilizing the same exact steps as described in the original post (resulting in the processed game files getting re-imported into decaGUI) and arriving at an identical result to the original one (i.e. export including the human-readable comments) Appending the _tmp to the working directory is also a nice touch for separation of which files were exported with or without processed game files. Looks very solid to me, closing this issue. Thanks again! |
You are correct, the missing hashid to equipment info and/or string mapping is because the archives were not processed. However, fixing that may not too complicated ... #103 |
As per this guide it is currently required to have Generation Zero game files processed and loaded into decaGUI in order to operate on the save file ("savegame") even though it is loaded via "Add external.." (and not part of the core game files).
This is inconvenient in a scenario where the interest is only for decrypting/uncompressing the save file and not operating on the the game files themselves (processing game files is a very time and disk intensive operation and should be avoided in such simplistic use cases if possible).
Proposing to investigate removing the need to fulfill steps 2 and 3 below for this described workflow (if possible):
The text was updated successfully, but these errors were encountered: