@evilpaul_atebit It'd be cool if it showed you which level you're on while you're in the level? Unless that is somewhere and I'm missing it.

I only did the first 8 levels but doing World 2 level 4 in three instructions was very satisfying.

@jcreed @evilpaul_atebit Yeah, I'm still parsing yours. What I did was... for the stripes, since you need the 2 bit and the colors are 2 apart:

add r1,#1,r2
and r2,#2,r2
add r2,#5,r2 ; 5 or 7

Then center the x coordinate:

sub #31,r0,r0
sub.mi #-1,r0,r0

Triangularize the y coordinate:

sub #31,r1,r7
sub.mi #63,r1,r1

Stick them together and choose blue or stripes:

sub r0,r1,r0
mov.gt #1,r0
mov.le r2,r0

@jcreed I was thinking about this again recently, but I deliberately steered away from addressing modes other than register and direct because memory access "doesn't make sense" in my mental model of the hardware.

I can see how I could have pre-defined lookup tables (font, etc.) and something like `fetch index,dst` without breaking the model. Hmmm.. that could work

Maybe even a way (on later levels..) for the user to create the lookup tables

@evilpaul_atebit oh, one more little idea of an option for how "texture memory" might be handled: you could assign one of the registers to be the index into texture memory, and another be the "value", i.e. if r7 is the "index" and rtex is the "value", then maybe like

and #7, r0, r0
and #7, r1, r1
asl r1, #3, r1
add r0, r1, r7
add #3510, r7, r7 ; 3510 = 65 'A' * 64 pixels per character?
mov rtex, r0

would draw a screen full of 8x8 'A' characters?