Figure out exactly how the algorithm in blz.zig work.

[Hejsil]

I couldn't find any specification of what kind of algorithm CUE's blz implementation uses. I don't know if it's a well known "compression" algorithm or some closed source Nintendo thing. This makes it hard to debug, refactor and optimize the code, as I don't understand it at all.

We have two options:

• Either we need to understand and then refactor the code in blz.zig. This might be the easier short term solution, but I don't think it's the best because:
• Get a better understanding of the spec of the nds encryption and look into how systems that seem to follow the spec have implemented this. Desmume have, what seems to be, a solid implementation of these.

The blz.zig works for the games I've tested, so it's gonna stay for now. This issue is for the future, when perfection of the code in the randomizer becomes more important.

[Hejsil]

23 was fixed by removing the blz.encode from nds.Rom.writeToFile (as roms can be loaded without and encoded arm9).

If we are to ever use the blz.encode, then it has to be faster, because omg it's slow.