1:30 You can also use Lists and Matrices. 3:04 I wouldn't put that ClrHome within the loop, it's simple, but not ideal for advanced programming. It'd be better if you displayed a white space on the space you want to clear. (You could do this by doing Output(A,B," "):Output(C,D," ") right before your first output commands ) 7:19 There's a faster, more advanced way to do the screen boundary check & button press check, I can share some code for it if you'd like. 9:45 it's not necessarily 'memory', it's the CPU that's super slow. Personally I wouldn't reuse a variable for a completely different purpose in the same program, it can make debugging a *pain* if your program doesn't work. The calculator has a decent amount of RAM, you don't need to be *that* reserved with it. :) 12:37 oooh I see now what you did, that's pretty nifty. I think I can give you some better optimized code than all those if statements. If you could give me the entire program, I'll do what I can to optimize it! 16:06 Nice tip. I know I was very nitpicky with you, but overall I thought you did a very nice job explaining the code as you went! How long have you been programming? Since 10 years ago? I look forward to future videos!
I believe that using List or Matrix variables having a slightly slower call time than the built in simple letters. The ClrHome certainly leads to a lot of noticeable flicker, but I figured it would be simpler to do a simple ClrHome rather than two Outputs. Honestly the two Outputs would not be much extra work and it wouldn't increase the size of the program by much. I'd love to see some of your better boundary checking and optimized logic. The full program is what is shown in this video. I wrote this code in my very first few weeks programming on the TI-83/84 series and it has held up as one of the better games I've written, I believe. The code has not evolved much since that time, though I've tried several variations of the core concept. I will try to get some more videos out that cover techniques such as Lists and Matrices for more variable storage, as well as String manipulation for graphics, Matrices for map data, String Spriting, Plot Spriting. What are other topics you think would be helpful to cover?
So I was having a lot of trouble with the whole score thing and I turns out that I accidentally didn't put a comma before my qoute so it threw off the whole score board
You probably forgot an If statement and have B+1->B somewhere in the loop being executed. If your AI logic happens before your player movement, the player input is overwritten. As TheLastMillennial noted, using the same variable for different purposes can lead to bugs that are tough to catch and fix. Double check that the line B+1->B has an If F=26 and B
I'm sorry, but getKey->K is the only way to use getKey, as K is short for [K]ey. Any other variable used with getKey should be disallowed. Change my mind.* Also, A,B and C,D are very odd representations of player and computer co-ordinates, as X and Y are typically used for player positioning (sometimes S and T, also, if you need a second set of X,Y co-ordinates for the player.) and A and B for COM position. Please note that I'm joking, but, using K to store the value of getKey DOES make more sense, mnemonically.
