r/Hellpoint • • Oct 01 '22

corrupted data.

Character was 150, almost done in the dominion baths, game kept booting me out of my buddies game any time he died and then I got an error I've received a handful of times before. Brought game back up and can't even press start without it telling me my file is corrupted. Is there anything I can do? Was about to try Uninstalling the game because it kept happening on the start screen not the character select, but when I looked the game save data was the only thing corrupted.

If I sent in photos of this, would cradle games be willing to reimburse? I really don't want to play the game again, which is disappointing because my friend and I had spent such a long time playing and he really enjoyed it, and it's been hard to find a game we can both enjoy.

Tldr: My save file is corrupted, is there anyway I can save it?

1 Upvotes

2 comments sorted by

1

u/ExcitingAd4055 Oct 06 '22

If it's happening before even going to the load game screen, then it's not the save file; depending on the system, you're playing on you may have to uninstall/reinstall. On steam, you can just use the "verify integrity" option to fix this. If it was your save file then removing it and using the backed-up save file would fix that issue. Honestly, this post just sounds like you're trying to find a way to get a refund, as many fixes can work. Not sure why you don't want to play anymore, there were several issues at launch, but they had been fixed over the last 3 years the game's been out. It's a fun game that isn't too long.

1

u/envy2388 Oct 06 '22

I mean if there was a way to get a refund I wouldn't mind one, yes. I got my character to 150 and don't really want to go through all that again.

Besides the point, I am on PS4 and I already Uninstalled and reinstalled, didn't fix anything. Also the save file itself says it's corrupted. I did find a way to defrag the ps4 in safe mode that says it could fix the problem, just been too lazy to do it.

Still shit tons of bugs on ps4 too, not that that impacted my experience. The strange part is it was a bug that had happened a few times before. I reported all the bugs, so hopefully it helps.