The way I would personally like it is simple one-line headers (something akin to MirageOS headers in Basic, but not exactly the same) and then options in the App to control other options and program output.  And i have seen games (such as factory theta for example) that do end in theta, so thats not an entirely foolproof method. 

Yep, even sometimes if the do want to learn, some people just have difficulties leraning programming/computer stuff ect...

Oooooh that sounds awesome!  So will there be watter between islands?  Or is it a space island?

Ok found the problem code, its when you multiply a value by data read from RAM

0->{L1}
8*{L1}->A
Gives a very weird happening.

Ok i'm getting this weird thing happening during compilation.  about 80% the way through each pass the message changes from '1st Pass' to '65534ass' and i have to press a key to make the counter advance O.o.  It does seem to compile fine though after it finishes.  Should i upload the source that was making it act weird?

L1 is not a list in the traditional sense that we think of lists in Basic.  In Asm, memory is memory, there is no difference between pictures, sprites, and strings.  L1 is not a list, because Asm deals only with memory. L1 is a pointer. What that means is that in the calculator, there are places of memory that are unused, and that are free to be used my you, an axe programmer.  Each list pointer hold the location of these 'safe' places, and allows you to write and read to them.  For example L1 points to the locations know to asm programmers as 'SaveScreen'.  All we need to know is that its a 714 byte space of free memory to use It has essentially 714 element, each holding a single byte.  So to write to the first element, you would do:

:#->{L1}

because L1 represents the 1st element of the 'SaveScreen' chunk of memory.  To write to other locations in the PlotScreen, you would just add a number to the location.  Like to store to the 3rd, you would add 2 to L1.

:#->{L1+2}

EDIT: Ninja'ed

Does that make more sense?  The pointers readme in the documentation might help a bit if you are still confused.  And if I am wrong Quigibo, please inform me!

Yeah it's always good to keep hames as efficient as possible.  For a while none of my friends knew how to archive games, so they could only have a few on at a time.