-
Notifications
You must be signed in to change notification settings - Fork 8
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
Can't edit chips #7
Comments
Interesting. I don't really have time to look at it right now, but if you could upload the files somewhere it'd be greatly appreciated when I'll have the time. |
Hey, not the same guy but I have the same bug but I think in this case that it's savefile dependant, switching the savefiles names didn't seem to do much attached are the errors shown by the CMD and my savefiles. I'm looking at the code atm, I'm no expert but if I do find something I'll let you know |
Hey, just an update here, so I made some guesses from the code and tried the following: It should work now. Now for my guesses - the code checks for normal/expected Chips so I think if you tried to modify your chips using a memory editor or something (ex: Cheat Engine) like that you'll get the aforementioned error. I could be totally wrong though - not an expert, if you're willing to attempt to fix it that'll be nice if not then here's the current 'Solution' PS: Thanks a ton for this useful tool! |
Huh, seems to be working fine now, thanks :P In case the author wants to create any fix and analyze our savefiles, I've attached my savefile as well. |
Hi! So, I can't edit chips for SlotData_0.dat and SlotData_1.dat, but I can edit for SlotData_2.dat without any problem. First 2 saves are after finishing the game(60+h) and the third one is before (~40h).
What happens when I try to load first 2? That : http://prntscr.com/jk2ikg
If I try to change even the 2 chips that I can change, after reopening chips section they are still the same. If it could help, I can upload savefiles that don't work.
Thanks in advance for any help.
The text was updated successfully, but these errors were encountered: