Never heard of screen damage from strobes. In fact, the method for producing grayscale on monochrome displays strobes the pixels in a checkerboard pattern, and strobing is used to fix stuck pixels.

@fb39ca4: I'm not sure what you mean by that. Could you explain?
Anyways, I optimized a bit, made it harder, and slowed it down on student software. I cant promise it will work on 3.1 though because im not sure if platform.hw() works with 3.1. If not, just use the link at the top.

You can use timer.getMilliSecCounter to get the time in milliseconds, and from that calculate the time since the last frame. You can either have everything move proportional to the delta time, resulting in a variable framerate yet constant gameplay speed, or wait for the delta time to reach a certain amount, resulting in a constant framerate.

Eiyeron, have you ever experimented with raymarching GLSL shaders?

After transforming the coordinates so that the origin is at the center of the screen and r is the distance from the origin, x' = 0.5 * x * (r^2 + r) and y' = 0.5 * y * (r^2 + r) for all points where r < 0.5. Otherwise, the coordinates are unchanged.

Also, a suggestion for the demo: You should generate the LUT for the next scene in the background while the current one runs, so that there isn't a pause between scenes. After each frame is drawn, generate one line of the LUT.

But my favorite avatar has to be thepenguin77's:

I have spent way too much time watching that thing.

I wonder how hard it would be to add support for small HTML5 video clips as avatars. It is possible to hide the playback controls and make them play and loop automatically, so that they behave just like animated GIFs, but with a much smaller file size. Of course, sound should then be disabled.

You don't need to unpack anything. Just store a number from 1-64 which corresponds with the index of each pixel in the texture as if it was a 1-D array.

You'll only be able to do security through obscurity, since a player can look through and modify the source code.