For the PK3 checksums like Q3 uses you need to correctly hash the CRC-32 checksums (they may even have included something more like timestamp, file name, etc) not really worth even considering, but you can get a pretty good hash by creating a MD5 checksuming out of all the CRC-32 checksums and it is fast (only need a header scan).
That is one 128bit hash per PK3, somewhat bigger than the 32bit checksum that I believe Q3 currently uses, then again all depends on trusting the client and it is hard to trust an OSS unfortunately.
Sometimes I wonder why I do those utterly pointless posts.. ohh well too late wondering once you've typed it. |
_
|