-
Notifications
You must be signed in to change notification settings - Fork 23
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
Assistance offer for the recent update #37
Comments
yeah, that might be helpful |
Great, should I put it up on google drive or something? I can do it midday tomorrow when I'm off work. |
You should be able to attach your save file (or a zipped version) directly to this comment chain, but a google drive link is also fine. Thanks. |
hi, i ll love to help too |
got it, thanks. |
Just in case it helps. This save has 4 Weapon , 2 Skin and 1 Resource OC :) |
3 weapon, 2 skin, 3 cosmetic.zip |
4 weapon, 1 cosmetic.zip |
Hi, I looked at all the above save files and it helped me find these patterns in the new file format. These are some notes I've taken and hopefully they lead to a fix. Further testing may be required, but this is what I've surmised so far: there are some values tracking the quantity of OCs. Inspecting the data with a hex editor shows where these values are. After SchematicSave (first occurrence)
After OwnedSchematics (first occurrence)
After OwnedSchematics (second occurrence)
Any of these values not meeting the format will result in the game resetting progress on the file. |
6561198021787201_Player_Slot_save_for_assistance.zip.zip 17 weapon, 4 cosmetic, been grinding since the new season came out. |
so, after doing ALOT of digging, the values identified by @wahlp are storing the size (in bytes) of various parts of the file relating to the number of forged/unforged ocs, I detail the specifics in the code of my fork. using this information, I believe I have fixed the issue, and my testing confirms this, I'll be creating a PR soon now the only thing this project is missing is some of the most recent weapons and the OCs for them (specifically the "Nishanka Boltshark X-80", but there may be others) |
done, #45 for rock and stone! |
This is great news!
I think the save file I put up has a lot of the new overclocks. I think
almost a dozen? I'm writing this via email, so I can't check.
Which hopefully helps in identifying.
…On Thu., Jun. 30, 2022, 21:44 Anthony Rubick, ***@***.***> wrote:
I'll be creating a PR soon
done, #45 <#45>
for rock and stone!
—
Reply to this email directly, view it on GitHub
<#37 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACIBQWBDVKI4AJDINHVCEXTVRZLRZANCNFSM5UXNOCHQ>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
yeah, I believe scout, engineer, and driller are missing their most recently added secondaries (the "Nishanka Boltshark X-80", "Shard Diffractor", and "Colette Wave Cooker" respectively) |
Hi, I saw in the python code that you were having trouble with implementing addition of overclock matrices since your test save only had 1 weapon and 1 cosmetic. At the moment, my save has 2 unforged weapon, 1 skin, and 2 accessories sitting in the forge. I haven't run a deep dive yet, so I don't have any blank cores. Would it be helpful for me to share my save file with you? I'd offer to help with the coding itself but I have absolutely zero programming experience, sorry.
The text was updated successfully, but these errors were encountered: