S2emu works in the same way that recent versions of
Y@nkse used to for S2. It requires all the normal component parts to decode the encrypted signal, i.e. mask tables, hash tables, keys, plus other bits to hold it all together like config files etc.
Up to and including S2emu V1.06, all this was compiled into the .dll file, so you didn't even see it. Now, with the release of V1.07, the developer has chosen to break them back out, a la
Y@ankse.
Th primary reason for doing this now (I guess) is that Sly chose to swap the hash table it was using for another (already known!) table.
This is good news for the developer, as he doesn't need to modify his executable every table change, but slightly more of a bummer for end users, as they have to keep track of all this stuff and keep it all up to date.
From a modelling/OO point of view, this is more text-book, but when you get right down to it, stuffing it all into one big brown bag is more practical (and hence I'm in the all-in-one camp, especially as the executable changes quite often anyway).
There are no instructions in this game. We're all just playing catch up.
Don't get me wrong, I'm not moaning one litle bit. In fact the sh!ttier and more difficult it gets, the more I love it. Just trying to explain.
STICK