Closed IceReaper closed 3 years ago
After some testing, it seems its not a good idea to make this value larger -> resulting mpqs are broken. Anyway, i wonder why War3Net generates a huge HashTable for newly created MPQ archives.
Okay, got it fixed by specifying a default hashtable size. It might be a good idea to use a Max.Min() with the maximum table size, where the filecount * 8 is used, so when having more then 0x1 << 13 files, this wont produce a crash.
Any reason this is limited to 0x1 << 16 ? When packing a larger MPQ archive, i exceed this amount quite quickly by having a bigger HashTable. Reading an mpq archive also reads it as int32.