Nemesis compression and decompression are now implemented.
QUOTE (flamewing @ Mar 6 2011, 10:59 AM)
QUOTE (FraGag @ Mar 4 2011, 10:15 PM)
However, flamewing didn't make an Enigma compressor and decompressor,
I think you mean saxman compressor/decompressor, as I have indeed done the Enigma compressor and decompressor (click here to go directly to it
Indeed, I meant Saxman (de)compressor, sorry. And for the record, I'm keeping an eye on the s2-ssedit repository with Commit Monitor
, so if you happen to find a way to improve the existing compressors or fix bugs, I'll know about it. :P Speaking of which...
QUOTE (FraGag @ Mar 4 2011, 08:15 PM)
(However, flamewing's code for Nemesis decompression didn't work right, so I had to change some things to make it work correctly.)
The way you're checking for codes (at "Find out if the data so far is a nibble code") doesn't make sense. During my tests, I use Green Hill Zone's first pattern set. Its header defines codes 000 and 001 (these are the shortest codes in the header). In your decompressor, as soon as one bit is read, it will match one of those codes, because you only consider the numeric value of the code. I used a binary tree instead, similar to the node class you use for encoding (and in fact, KENSSharp has 2 such classes, one used for encoding and the other used for decoding).
This post has been edited by FraGag: 12 March 2011 - 04:31 AM