I don't think we should judge people too fast, but of course we need to be realistic about what the calc can accomplish:

15 MHz Zilog 80 CPU
24 KB of RAM (21 on CSE models)
480-1530 KB of Flash storage memory (3500 on CSE models)
No graphic card/accelerator
And TI-BASIC is far slower than Axe and Assembly.

It's possible to make an FPS in BASIC, but it will look like this:



Minecraft could theoretically be possible too, but you would only be able to look up at 90° angle and down the same way, and turning around would look like the screenshot above. Plus the game would take ridiculous amounts of RAM. For example, a matrix based map that is 10x10x9 would take 8111 bytes of RAM. Also you wouldn't be able to see more than 9 blocks at once.

On a CSE calc, this is probably the best graphics and frame rate that you could pull from pure BASIC without using a single pic variable (the following animated GIF is fake, so it could actually be even slower, especially if you only coded TI-BASIC for less than 10 years, but it shows a small idea of how jumping in such minecraft game would be):

If you want to program games, i really reccomend to learn a language other than basic, like axe, grammer or assembly. If you really want to use basic however, you might also want to look into libraries like xlib (included in the doorsCS shell)

And if you are awesome you'll even be able to do greyscale (though that is pretty advanced due to lack of speed)

DJ made it in Reuben Quest but again, DJ's the god of BASIC.

but axe doesn't have lbls like you use 'em currently so you'll have to learn loops which i would recommend anyways

Axe haz labels. They're actually better than loops if you think of it from an ASM point of view.

erm, don't you mean functions, that they just use the lbl token? functions!=lables, functions are faaaaaaaaaaaar more epic

Aren't lbls in Axe like jumps in Z80 ASM?

Aren't lbls in Axe like jumps in Z80 ASM?

The lbls in axe are basically pointers to certain pieces of code. And just like in z80 asm, you can either call them, or jump to them.
Because of this, axe lbl's are handled only by the compiler, and are thus 0 bytes large in the compiled program. The goto's or calls(subs) do take space and use CPU cycles, however.

If you wanted to make an FPS i would suggest raycasting as opposed to 3D.

That being said, an fps is not the type of project to tackle when you're only starting out programming wise. The things id learn first are dealing with program flow, sprites, data structures and of course, the inner-workings of the calc and OS itself.

Still keep the fps goal, but maybe make it a long term one? .

Out of curiosity, have you seen Gemini or other calc fps's?