Command line .pack unpacker support for S2TW

[taw]

The code is here.

There seems to be extra 8 bytes in header, but wtf are they?

It's probably not a checksum or GUID, as they'd more likely use 128bit,
and these numbers are too similar.

32bit checksum + 32bit timestamp also doesn't make much sense.

My best guess was some sort of 64-bit timestamp as all values
seem to be 0x01CB_xxxx_xxxx_xxxx but no units I try make much sense.

It doesn't matter for unpacking but it might for creating good packs. Any ideas?

Oh by the way, everybody knows that the mysterious 4 bytes in ABCE/ABCF-type ESFs
that weren't present in ABCD (offset 8) are 32-bit Unix timestamp, right?

[The Hedge Knight]

I would [jokingly] guess at another attempt to mess modders over .

Anyway thanks Taw!

[zowrath]

I would [jokingly] guess at another attempt to mess modders over .

Conspiracy theorists unite! I must say I wonder about this some times as well. I've tried to enable other factions now that the real startpos.esf can be unpacked. I've gone through those files like crazy and I can't find out why it should not be able. I can disable/remove factions easily enough, but not add them in the reverse way. I've even tried to just copy the parameters around from an small faction to a major just in case there's some small hidden parameter that I can't see but that just has the same result.

So, my conspiracy theory is that there may be some modifications that are not able to be done until after they've decided what DLC's to release.