Well, with CPU emulators it's best to write one specifically for the CPU you're using, in Asm. That way, commands can be directly linked, like how AND functions virtually identically across instruction sets. In C, doing an AND command is much more than the single operation.

Yes, exactly. Emulating a CPU in assembly is a cakewalk because of that. The z80 is a very simple cpu that has structures that exist on almost all other newer CPUs. For example, loads, bit operations, and addition/subtraction are available on almost all CPUs and that is the brunt of the operations available on a z80. Emulating the hardware is the tough part, especially the link port (which is a little different on the Prizm, but this may be possible), the LCD, timers, and USB (which I probably won't even attempt). I hope to have enough time for this in the summer (but then again, I hope to be doing GSoC which will eat up a lot of my time).

Version 2.25.03.12
I have to rewrite the readme for this thing sometime, it is getting messy...

Updates:
I am going to have to rewrite this whole document because it is a mess with
inserting new commands everywhere. Anyways, here are useful additions since the
last update:
-The user can now use lowercase letters instead of, say, A'. This is the same
size, but looks cleaner.
-You can now store Ɵ' and Ans at the same time by defining both vars after →.
For example, R*P→aA will store the upper 16-bits of the multiplication in a and
the lower 16-bits in A.
-Output(2 is the Text( mode for drawing the fixed font to pixel coordinates
-Text( without arguments will return the coordinates as Ans=Y, Ɵ'=X
-For the coordinates in a Text( command, you can do relative placement. For
example, if you want text at 2 pixels below the last drawn text:
:Text(+2,,"2The +2 draws it down 2 pixel from the last location and the empty argument for X
means it uses the previous X coordinate. Useful for subscripts and super scripts
-You can set the Text( coordinates by using two arguments for Y and X. For
example:
:Text(56,0

Well, if you already have the tileset, why copy it twice? You could also store it in an appvar and package it with your program :)As for detecting if there is a save file, here is what I do, normally:
"USave→A          ;Name of the var. Save to a pointer because it'll be used a lot
Unarchive A       ;Unarchive the var. (A points to the name)
If !Get(A         ;Finds the var. Returns 0 if it doesn't exist.
Then
Send(4098,A       ;creates the var
iPart(Ans,16448   ;writes the first two bytes as 40h,40h which is the size of the map
End
Get(A→Z           ;Z points to the var


As for generating random maps, how do you want to generate it? You could do some crazy cool stuff using math to make regions of similar tiles (so you could have ponds, rock areas, and others).

Also, there is an Axe coder now doing something like this, too

I spent days on mine Then again, I hardly knew any Axe when I started

Ah, I see, yeah, I forgot that grayscale part You can OR the different layers together, then, maybe? (like the darker layer of the sprite and background and then the lighter layer of both). I don't know if that would work at all...

Nice I want to rewrite mine, now...

Thanks The scrolling was fun to do. I used some similar code to a maze program that I wrote, so the program source loads Pic2 as a map. Then it reads the pixels to figure out if it needs to plot a barrier or fruit

Wow That is fast and is a great intro screen (I like the animation). And you have grayscale

EDIT: Also, you have 11 fingers? Coool