And another silly thing about the 9001-byte platformer: The code for movement (left/right) is written 3 times identically one after another for no reason at all.

well, I once tried to "Goto randInt(0,10"
and have labels from 0-10.
I was trying to save "If" Statements.

Seeing all this made me go back and play my first legit program BWORM. It was a worm game where the worm was 2x2 squares that moved 3 pixels per frame. The goal was a three pixel wide line. (notice a problem?) Since this game was made long before I knew what lists were, I used all the variables to store the coordinates of the points. But x and y for every point took way to much memory. So I changed it to x.y where y was a decimal and x was the whole part.

So I started playing it, it was holding at a steady 2 fps, and once I got to about 15 points on screen, it started moving faster. Eventually it was jumping 8 pixels per frame. Not only was it nearly impossible to hit the 1x3 goal, but it was such a big jump that the worm could cross itself.

After I made it, I realized it was so bad that I didn't even try to go optimize it.

One of my very first Basic games was Breakout.  But dont get excited because it was no good The physics was set up so that the ball always bounced off the paddle the same angle, meaning that every single game was exactly the same.  I also was trying to get around getkey's quick key repeat with timers and lots of variables, but it just made it hard to use and lables lables lables means lots of memory leaks! Yayyy!.


Although probably the game with the most leaks was my very early Basic Shift game After the 3 built in Levels it got a memory error

I made Brian Teaches Typing when I remembered Mario Teaches Typing from elementary school. I didn't know about strings, so I stored 1-26 to A-Z. You typed without spaces and then the calculator multiplied the whole 70 variable number together and matched it with the correct answer. It even gave words per minute.

1)My first game was a text RPG where every single line was either a menu or a Lbl.  Most of the menus only had two choices, and one always ended in death.
2)When I finally learned how to use the Disp command I would use spaces to format text.  I was scared of the multiple-argument Output( .

You were scared of Output( and yet you used Menu(? It wasn't until after I learned assembly that I tried to use Menu(. Catalog help just wasn't making any sense to me.

I had an hard time understanding menu(). When I got it, I was disappointed that it only allowed 7 choices >.>

Also, one thing I did as newbie for NPC convos in a RPG was using Pause "text" for long speeches. So to read the entire text you had to scroll left and right. That said, the idea may not have been that n00bish, though, and it actually looked cool and took very few space on the screen . But still remains the fact it was a really cheap way to display huge text and avoiding coding an entire text routine