That actually sounds like a server-side error (which means it's definitely my fault). What did you do to trigger it?

Yes, seems there is a bug with the Runner sample sprite specifically. I'll try to fix that later tonight.

As for ORG, it looks like JavaScript isn't loading. It was a mistake on my end, and has been fixed now. Sorry about that!

Any idea why the sprite shifting/rotating/animate options are grayed out (and not working)?

I guess maybe he kept some features disabled for certain browsers

Also what would be cool is if it was possible to import BMP, GIF and PNG sprite sheets or making larger sprites then splitting them in 8x8 chunks.

Ah I see now, I thought you disabled Opera support or something . I hope you can add support for it in the future (although I heard that Opera is gonna move to Webkit at one point, so in long terms this might not be as useful)

Yeah I'm unsure if it's official but it would be nice if Opera used Webkit. I like its interface and features in general.

I have some feature requests...

I finally used this for the first time today and I really like it! I was trying to make masked sprites, but there aren't any options available. Instead, I used the 4-level gray option and toggled the pixels accordingly. Unfortunately, this makes it kind of tough to visualise the sprite to make sure I am setting the pixels properly, so it would be cool to have it as an option. There are two ways that I am familiar with (and I have used both, depending on the conditions) :

---

Method 1: AND - OR
First layer is used as an AND mask. This tells which pixels to erase/preserve on the current image. Alternatively, you can make it so that a pixel OFF on this layer corresponds to an OFF pixel in the sprite. In other words, you can start this as all black.
Second layer is used as an OR mask. These are all the pixels that are set by the sprite.

The cleanest way to display this is to have it so that an ON pixel in the AND mask is displayed as gray, an OFF pixel is displayed as white. Any pixels OFF in the OR mask do nothing, pixels ON show as black. If the user toggles a pixel off, it should turn the pixel off in both masks.

---

Method 2: OR - XOR
The other method, the first layer is an OR mask, turning on pixels, the second layer has set bits that turn pixels OFF.

A pixel ON in the XOR mask should also be ON in the OR mask. This makes a white pixel.
A pixel OFF in the XOR mask and ON in the OR mask makes a black pixel.
A pixel OFF in both masks won't change the background.

The visualisation for this would be gray if both pixels are off, black if only the XOR pixel is off, white if both pixels are ON.

---

The other request would be one of data output syntax. I don't know how popular it is, but I tend to store my gray and masked tiles such that the two layers are interleaved (for assembly, this is easier/faster for me). So for a ball, I might have:
;OR Mask
.db $3C,$7E,$FF,$FF,$FF,$FF,$7E,$3C
;XOR Mask
.db $00,$3C,$7E,$7E,$7E,$7E,$3C,$00
That will cause the pixels on the outside of the ball to be unchanged when it is drawn, the pixels inside get set to white, perimeter is black. The data as I store it:
;Interleaved
.db $3C,00,$7E,$3C,$FF,$7E,$FF,$7E,$FF,$7E,$FF,$7E,$7E,$3C,$3C,00

I hope this makes sense! I won't have much trouble converting it myself (I have a spreadsheet that I have had for a looong time to interleave data and do other manipulations )