I know about your other projects, but yeah, that was a surprise to see strings like this (LolzDecodePipe, LolzThreadDecoder, etc) - guess you used them as internal names as it was based on lolz
I also tested TARZ on that Memoriaplis game, but properly decompressed this time.
1705382191 mem-tarz.arc
1664803071 mem-lolz.arc
Alas, but when chained with xtool+srep tarz could not unpack the arc (it worked fine on decomp on smaller/simple samples). Tried both cls and tarz.exe d options.
Testing Memoriapolis_Data\globalgamemanagers (796500 bytes)
Testing Memoriapolis_Data\level0 (2696 bytes)
Testing Memoriapolis_Data\level1 (3552 bytes)
Testing Memoriapolis_Data\level10 (255960680 bytes)
ERROR! Decompression problem: unexpected end of file - or I/O error
How to address this?
Also, do you plan to expand threads to N/unlimited from current 16? That was the limit of lolz, ProFrager told then that there are not much non-server CPU which have more threads, but now 16t is already very popular with more threaded CPUs arriving every year.
I also noticed that TARZ is more stable when it comes to compression speed. Lolz can severely slow down close to the end of compression, while tarz stays relatively the same. But need more larger samples to confirm.