There are 2^8*8=18,446,744,073,709,551,616 unique monochrome 8*8 sprites.

Now it gets more interesting if you say a sprite only like rotated 90° is the same one as the one before.

but that won't do the whole trick, like there are ones like an X which are unique, and when tilted they are still the same sprite

Very few compared to the ones that look like random junk.

Also could Omnimaga write a program that will make all of them, index them and have the hex code foreach? Obviously it would be huge, duh. But that would be cool to be the only site in the world with all 18,7446,44,073,709,551,615 monochrome 8x8 sprites possible.

Are you CRAZY? I asked wolframalpha. You need 37.49 exabytes of data to store those images for 18 quintillion 744 quadrillion 644 trillion 73 billion 709 million 551 thousand 615 8-byte sprites. And that's the smallest part. You need 16 characters for every hex. In ASCII, every character is 1 byte. So that brings the total size per sprite to 24 bytes.
24 bytes * 18,7446,44,073,709,551,615 = 449.9 exabytes.

An exabyte, FYI, is 10 000 000 terabytes.
So unless you want to host the list, have the money, space, and power supply,
No.


EDIT: Because I feel like doing a What-If? XKCD style thing here, I'll put some more things here.

Assuming that Randall's approximation of Google's storage capacity (what-if #63) which he gauges at about 15 exabytes is correct, this means you'll need almost 30 and a half Googles to store all this information. If you wanted to put all the information on 1TB hard drive disks (measuring 2x18x10 cm, totally guesstimated that), you would need 449900000 drives. That would take up a volume of 161964m^3, or 43 olympic swimming pools (size: 50mx25mx3m)

I could go on, this is fun, but that's it.

I made a tool to do this a while ago:
http://merthsoft.com/binsprite.html
And, of course, TokenIDE can do it, and countless other tools.

Quote from: willrandship on April 28, 2014, 07:21:09 pm

Actually it's 8 bytes per sprite, not two.

We wouldn't need to store them all. We could generate them on the fly extremely easily, since it's just a 64-bit number. Pass the 64 bit number and a small javascript program could generate it using a small canvas element.

Yes, I know you don't have to store them all. But that's what OP is implying when he says "generates all of them". And I wanted to do some big number crushing

Are you sure? That seems awfully large... plus i said that
"will make all of them, index them and have the hex code for each?"
Not generate. Simply spits them out, perhaps on paper... oh wait, thats would probably be the whole redwood tree forest right?