[cbk1994]

Originally Posted by 12171217

There's no need to do all that, simply parse the file's contents out, byte for byte, and generate a hash, then compare hashes. Of course merely changing a pixel or adding some header information would **** you over, but whatever.

Alternatively, you could sample a certain coordinates for the head, like where it faces down, and store the RGBA values with a threshold to permit. Then compare a few pixels aganist each other, only 32x32x3 bytes to parse if you do them all anyway, wouldn't take that long.

Not worth it for our cause . The head checker was just added as a precaution because with the new uploader it's a hell of a lot easier to re-upload heads (click "Upload", click "heads" folder, then double click one).

Originally Posted by CharlieM

problem with auto checking is there could be something that someone took from there head and put on a friends head that took up maybe 50% of the head, so if it checked by pixel it would come up as stolen wouldnt it?

see below

Originally Posted by cbk1994

It's not quite that simple. The way it works is that it looks for heads with the exact same file size (down to the byte) from a list of corresponding head paths and file sizes. If it matches, it's most likely a duplicate. However, there are rare cases where there are two heads with the same file size, so it also compares the contents with a string check.

Changing this to actually load every file, parse it as a PNG/GIF/MNG, then compare each pixel would be nearly impossible and definitely not worth the effort (except maybe for experience in programming, I guess).