Ah ok I see. Interesting, hopefully he can get the game to run faster now. In the worst case scenario, he could maybe remove grayscale.

There were quite a few, yes Which command or commands are messing up?

I looked at the ROL3 source, and the first thing that I noticed was that you used Lbl to find a label in another program... without supplying the program name.

Also, in the TILE subroutine, you don't need ClrDraw >.>

But the most important things that were going wrong was using unsupported tokens like ) and your math is kind of buggy. For example:
If H=4 *!(M+T'-W') *Y' *Y=4
I am surprised that worked in the old version o.o The faster and more optimised way (as well as the way that will work):
If (M+T'-W': and Y':! and Y=4: and H=4
Did it look like it was having bugs with wiggling back and forth and moving without a key being pressed? If so, after fixing up all of the math and logic, the ROL3 code worked for me.

Hmm it might be a good idea to not constantly change the syntax of Grammer commands too much every version, because with Axe there were usually little changes, just additions, and for people who don't update often, changes might turn them away since they have to update every version

Oh ok lol. I just remembered when Lua arrived on the Nspire and TI removed some important code like a function that allowed the usage of the serial port and its removal sparked some public outcry and broke compatibility with certain programs.

Yeah, spaces should only be used for arguments for commands. For example, Pxl-On(3*X +4*Y,11. Colons are best everywhere else.

Also, as a tip, if something will only ever evaluate to 1 or 0, you can use " and ", " or ", and " xor " almost like you would in BASIC. This is a lot faster than the trick of using * or +. For example:
If A=3: and B=4

Don't panic. You are a decent coder. I have faith that you'll have a demo ready by the deadline.