- Joined
- Nov 18, 2017
- Messages
- 666
- Reaction score
- 1,246
- Trophies
- 0
- Location
- Melbourne, Victoria
- XP
- 2,781
- Country

The SHA256 of the patched file is to confirm that it was patched correctly, there are numerous factors which could cause a bad patch.Why is the sha256 of the patched file in the metadata? It's not like the same patch suddenly does something different if the source-file is confirmed to be the correct one.
Also having an human-readable patch-format wouldn't be that hard and makes combining patches much less painful.
Imo just including the old value (and a bit of the values around that, like gnu-patch does it) and then only applying if that matches would be much better since it would allow you to apply multiple patches to a game while still making sure that the patch isn't applied to an incompatible elf.
Also pretty much anything other than vb would have been better because vb is strictly windows-only so porting your tool essentially means a full rewrite.
I even experienced one myself, turns out I ran out of disk space on my C: drive, therefore the file was incomplete and hashed to a different value.
Also, VB can be transpiled to C# natively, so in my opinion, it's a non-issue.
Last edited by SimonMKWii,







