Speaking of updates... I put together a spread sheet (It uses OpenOffice) that has been a real help with my programming. It pretty much eliminates the need to calculate addresses. For that reason, I have optimized the code a bit, but there really are still only two things it can do at the moment.

yeah, my only goal in the spread sheet was to make it take all of my code and put it all together. It was designed for my uses, but anybody is welcome to use it.
Column A is the name
Column B is the size of the code in bytes
Column C is 1 if it is to be included in the final code, 0 if not
Column D converts Column B to hex
Column E is the start address of the code
Column F is the hex code
Column G is whatever F is if C is 1
Column H is all of the code in column G
Column I is the address as it is used in hex (1234→3412)
Column J is the length of the hex code (uses !!! if it doesn't match B)
Column K is the cumulative size of the code to be used

Okay, I have a new update... I have finally added the Disp command to the list. Apparently I didn't have a bug, but I guess it is always safer to be, well, safe. Also, I forgot to mention that I have not compressed the program. I will start doing that after the next command, though.

The next command I plan to use Line(a,b,x,y,t where it makes rectangles. For now I am going to use the OS routines, but I think I will make my own routines at another date.

Sounds good! Definetely make your own routines! This seems pretty useful to be one of the libraries for KOS, by eliminating any TIOS routines it should be KOS compatible already (albeit you should inform Sir about that...)

Okay, my latest update now has the Line( command which is used to draw rectangles. I actually made the example program prgmB do something this time and I have the compressed version of the program called prgmRECODE.

At the moment, you can comment on your code without a problem unless you use commands. The problem is, every byte gets read by the interpreter and this can slow down your code. I was thinking about using "." to start a comment and have it skip to the next line to save speed, but if anybody has a better idea for starting a comment, I can easily change it.

Also, the example program has a pause just about every other line, so it isn't slow, it's just taking a pause so you can actually read the words

Finally, this is as far as my original version got. Now I get to be a little more inventive. I am going to take it slow and easy, but if there are any ideas, I would be happy to read them. I do not plan to do anything major like a tile-mapping routine yet, but simpler things are okay.

Oh, yeah, sorry about that. I was just using variables, not coordinate logic. Should I just change the order to Disp Y,X or do you want the code changed (it is only 2 bytes to change)?

Does the pause have to be right in the middle? O.o I'm not sure if I understand the code. Nice to see it is still progressing, though.

So basically that 33 is used in both the Pause command as well as the 4th argument in Line(), as a way to save space, right?