Oh I see what you mean now, the ball being your character

well I'm sure yours will also turn out well   good luck on it!

Well, my estimate for the size of this program overall is 40K.  It will have a 16K flash ap controller and a 20K engine program with crabcake

Does data count to a flash app's size?

That amount of memory consumption is out of the question for me.

Still in progress, but inching along as I'm taking on all my projects at once in full force

I was working on this during my break in lifeguarding today, and I finished level loading and editing.  I think I did pretty beast on my level compression techniques:

- there are many types of tiles in this game, and using byte indices would make the tilemap take up 180 bytes.  I made it compress to one bit per tile, using the state of the surrounding tiles to determine the current tile type.  Tha cuts it down to 22 bytes and an extra nibble, which I use to determine the "level" the current room is part of, which can determine changes in tile prediction as well.  I then run it through a limited 2DRLE co oression algorithm that uses 6 bits to determine length, 1 bit for direction and 1 bit for state.  It check beforehand to see if L2DRLE compression is nessicary or not, and stores compression state right after the beginning level determining nibble.  One detailed room I made was only 12 bytes in tile data total, as opposed to 180.

- Enemies, objects, etc. Take up about 80 bytes per room.  However, i made it so each unused slot starts data with a reset bit, which means to skip that bit and continue struct processing with a +1/8 offset and move to the next slot position.  A room with two boxes only uses 10 bytes and 3 licks (half nibbles) of data as opposed to 80 wasted bytes.

- Since the sizes of rooms vary so much, instead of holding all rooms in arrays of 260 byte structs, each level-room array and data-level array is begun with with a static vector table for quick reference to rooms.  The data-level array is an array of level-room arrays, and has an embedded and extended vector table after the heading VT that combines all elements of held arrays, and indices.

- A non-compressed level-room array is 5200 bytes.  Compressed ones are now at the very most 2160 bytes, but I'm sure the actual output will be closer to under 1000 bytes.  1000 bytes for an action packed hour level is pretty damn good

When are we gonna get another screen shot
I enjoy screenshots