OK. I think I'll post a tutorial about it, or just post here a little later.

Looking good! Have you considered allowing the character to move around, and interact with the ground somehow?

Yay! Even in the last month, I've noticed new Axe projects popping up all over the place. Wonderful!

Yeah, that's usually what's referred to.

For the longest time, I have wondered about Pt-Mask and how the heck to use it effectively, but after an IRC discussion with Runer112, I think I have it!
I hope this clears up something for someone else who might been in the same position I was.

Runer112   Pt-On() has two colors
Runer112   black and trasnparent
Runer112   Pt-Off() has two colors
Runer112   black and white
Runer112   Pt-Mask() has 4 colors
Runer112   transparent, white, gray, and black
Runer112   Pt-Mask()r has 3 colors (and a sort of color)
Runer112   transparent, white, black, and xor

Runer112   I don't know if I have any example sprites around here...
Runer112   but let's just do something simple
buttsfredkin   k
Runer112   [00000000FFFFFFFF][0000FFFF0000FFFF]
buttsfredkin   right
Runer112   that would draw a sprite
Runer112   first two rows are transparent
Runer112   next two rows are white
Runer112   next two are gray
Runer112   and last two are black

buttsfredkin   so correct me if I'm wrong here
buttsfredkin   00 = transparent
buttsfredkin   01 = white
buttsfredkin   10 = gray
buttsfredkin   11 = black
buttsfredkin   ?
Runer112   yup, that's how Pt-Mask() works

Runer112   and it draws it all in one call
buttsfredkin   and you give it a single pointer to a 16 byte sprite?
Runer112   instead of having to do two separate calls for drawing a normal grayscale sprite
Runer112   yup
Runer112   and that 16-byte sprite should be formatted as 2 8-byte sprites
buttsfredkin   right

buttsfredkin   what about Pt-Mask()r?
Runer112   although r normally denotes back buffer/grayscale
Runer112   in this case it means the opposite
Runer112   only because Pt-Mask() was added first
Runer112   so that works a lot like Pt-Mask() without the r
buttsfredkin   alright
Runer112   except it only draws to the main screen buffer, so only for black and white

Runer112   00 = transparent
Runer112   01 = black
Runer112   10 = white
Runer112   11 = xor

^^ this.

Yeah, the speed issue is just because I refresh the screen more to try and get better looking gray, but I'll probably have to end up sacrificing a wee bit to maintain good speed.

Thanks everyone, and as promised I present to you the scrolling background:



I'm still working out a coupla collions related bugs (see the little slices of land left behind there when you erase blocks), and I'm going to tinker around with interrupts to see if I can't get the gray to look nicer.