I haven't seen any variable length integers in MMB files.

Yeah, the Division's approach is certainly something new. But you probably won't get far without looking at the game's disassembly, because most of the per-file info is encoded in a way that's very hard to deduce from looking at it in a hex editor or something like that.

Or you could challenge yourself and try to figure it out on your own!

Those are just Flash files with compression enabled, you can look at the file spec for SWF to see how to decompress them.

You can get the PDF with the swf spec here: http://www.adobe.com/devnet/swf.html.

The command header is uint8_t for the command, then uint32_t for the tick.

The first link parses the signon data, the second link skips the data (it does a relative seek for signon length bytes).

Dunno about the rest, protobuf wasn't used when I last looked at the demo format.

What's that supposed to be?

Names, offsets, sdfdata indices and all that are in the TOC file's zlib compressed chunk. That 0x140 bytes block is probably some signature or something like that.

There's no encryption/obfuscation going on in the TOC file.

The format of the encryption and signature data in the header comment changed (the 2kb or whatever less is that data). Also be aware that XXTEA isn't actually used.

7zip opens the decrypted files just fine for me.

Check the Evolve pak thread.

The key changed from the closed beta. Didn't hardcore/provide any keys to avoid potential problems.

http://sktest.aruarose.com/PakDecrypt_Evolve.7z

Fill RSAKeyData.bin with the key from the release version (should be 140 bytes).

The only thing I've seen encrypted in Frostbite games was the .toc files.

It's LZ4.

It's almost identical to Crysis 3.