Closed MontyMole98 closed 6 months ago
What exactly do you mean by "remotely the same way"?
zlib compressed data has been forward and backward compatible for the almost thirty years of its existence. Perhaps your app is doing some other check to guard against modifications.
Figured out that there was a header in the game files that doesn't exist in the most recent version of ZLIB. Didn't notice in the first place, but now I did.
On Tue, Feb 6, 2024 at 4:17 PM Mark Adler @.***> wrote:
What exactly do you mean by "remotely the same way"?
zlib compressed data has been forward and backward compatible for the almost thirty years of its existence. Perhaps your app is doing some other check to guard against modification.
— Reply to this email directly, view it on GitHub https://github.com/madler/zlib/issues/929#issuecomment-1931005831, or unsubscribe https://github.com/notifications/unsubscribe-auth/AXX7CQGRPAHNUSXSAJVIUFDYSLB23AVCNFSM6AAAAABC42PNDWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMZRGAYDKOBTGE . You are receiving this because you authored the thread.Message ID: @.***>
I will assume then that you have resolved your issue.
There are some ZLIB-compressed files from games made in, like, 2015, which I wish to edit. While these files seem to be accurately decompress, I can't get them recompressed in remotely the same way. Games just crash using the latest versions of ZLIB. How should I compress using the older method used around that timeframe?
Thank you for helping in advance!