Okay, so I have added by request the factorial token. It pretty much means not(). I will explain in more detail later, but I have to go a few minutes ago . Ask yeong or suronome as they were the ones that requested it

later I will add the ability for While and Repeat

>.> Well, that is a pretty neat way of getting around it. I actually did something similar when I made a prime sieve using Grammer (because it is faster). However, there are actually display functions and you can transfer between OS vars and Grammer vars. Here are some examples:
.0:Asm(prgmGRAMMER
Repeat A=15
ClrDraw
Repeat A
getKey→A
End
Text('0,0,A         ;Use Text(' to display numbers
DispGraph
End
Stop
Or you could do:
Repeat A=15
0:Asm(prgmGRAMMER
Repeat A
getKey→A
End
A→iA               ;i is the imaginary i, here
Stop
Output(1,1,"      ;2 space here
Output(1,1,A
End


Okay, so I will try to add in that Screen→Particles command sometime soon, but for now I am having fun trying to code that game to be faster I currently have it going pretty fast (I haven't won the game yet), but it isn't complete

EDIT: Here is a screenie of what I currently have

For the latter bit, what programming language where you using? (just curious)

Okay, I added it It seems to have a different format after a certain point, though, and I could figure out why Also, I put it under general tutorials.

Hmm, okay, I can add that. Which token should I use?

@DJ: Okay, would it be okay if I instead posted the whole tutorial there and posted a link to it here?
@Suronome: Yeong has it correct
@Yeong: You are getting a pretty solid understanding of the language Thanks for helping folks out!

What do you mean? Like pictures and particle buffers and arrays? The answer for that is yes
For example, to create an appvar with two graph buffers:
Send(768*2,"UBuf→A
+768→B
Disp A
Now A and B contain the locations of the buffers and instead of the graph screen being used, the first buffer is used

Now aside from that, I have made several updates in the past few days! I finally added the Fill( and Fix tokens
So the Fix token is used to set modes. Currently there are two: Inverse text and inverse pixels. Inverse pixels is neat because it displays off pixels as on at the LCD. Inverse text just inverses the text.

The Fill( token has 14 different things it can do all dealing with the graph buffer, currently. They range from inverting the buffer to swapping two buffers to combining buffers using some logic.

Also, grayscale works very nicely on a real calc I made a grayscale drawing program (with 4 shades of gray to draw in). Unfortunately, I tried sending it to my computer and that didn't work and when I took out the batteries to charge them... it crashed

So yeah, if anybody wants to make one, it really does work! Just not so well in WabbitEmu

The gist of what I did was I made two buffers and stored their location to H and I. Then I used Disp to swap between buffers when drawing and I made an interrupt that looked like this:
.INT
DispGraphH
DispGraphI
End

I will try to remake it

I also changed the particle engine a little to delete any particles that went offscreen using an idea that Qwerty.55 gave me on IRC So now we can have infinite waterfall animations

Finally, I changed the code around to save a few hundred bytes, so even with all the new additions, the code is now 30 bytes smaller than the last version!  I had a certain 10 bytes of code that got used many times throughout the program, so i just made it a call saving 7 bytes each instance, but using a few more cycles.