Another development tool I made to help myself figure out bugs with Ash: Phoenix...It's a memory viewer! Allows you to look at every address (0000 through FFFF) of your calculator's RAM and their contents. (Like Calcsys' hex editor, but more Axe user friendly)

Controls:
Arrow keys; move cursor around
1-6: Jump to memory locations L1-L6
XT0N: Jump to variables A through theta
/:Jump backwards by $1000 (4096)
*:Jump forwards by $1000
-:jump backwards by $100 (256)
+:jump forwards by $100
GRAPH: Goto 2 byte memory address pointed to by the current selection
Clear: quit

The cursor highlights the value of the byte you are looking at in hex and in ASCII (like calcsys)
In the upper left hand corner the 8x8 sprite starting at your cursor position is displayed
In the lower left hand corner the memory address your cursor is at is displayed in 3 different formats: hex, decimal, and the form Ln+(something) (displays the variable you are looking at if you are looking at variables)
In the bottom part of the screen there are two numbers: the value of the byte in decimal, and the value of the two-byte number little-endian (aka normal) starting at your cursor position.

Run with Asm(). Post comments/feedback/possible feature requests 

My way is long and inefficient but works as long as you have enough ram to hold the new sized appvar (and that's it... So if you have a 12k appvar and you want to make it 14 k all you need is 14k of ram... Which is the same memory requirement as nemos

Actually, it lets you use practically 16384+ as much code as your archive can hold, except they all have to be divided into 8192 byte or less pieces. For example, you could have 5 programs that were 8192 bytes each in archive, then from the app you could copy each one to ram when you needed to and run it. That's like 56k of code O.0

Thanks.

Today, I finished up my makeover to the NPC engine; now it looks very nice. It has variable font spacing so the letters don't look as weird, and it *looks* like it has word wrapping (although it doesn't )
Of course, also I found *another* bug with the battle engine....I think it's fixed now but I'm not sure yet It occured after talking to NPCs whose conversations with you would exceed 50 characters O.o Programming this large of an RPG makes me see really how easy all those glitches in Pokemon Red were to overlook...

Awesomesauce? Is that regional? I know a girl who liked to use that a lot...

Not sure...Where (generally, and if you want to answer) do you live?

Btw, does wabbit not work on your computer

I bet Michael could get a huge speed boost if he only checked a limited radius...

Hey, the scrolling looks really good actually Nice job!