Looks pretty good so far I got a few ideas:

-For the dungeon walls, there seriously could be graphical enhancements if you are going to stick with certain colors. Just using a For loop and perhaps 1 list you could make the walls look more 3D. It would definitively make the game more attractive and increase its audience, without considerable gameplay slowdowns.






-You could add a battle background with those walls at the top?

The borders look great, if you can put those in it'd look much better

Cool to hear. I wonder if they are fast enough for your needs? From what I saw in the Zelda Sacred Pearls menu I made a while ago (the game never got past that) it didn't seem too bad but that wasn't full screen, so maybe full screen is slower. But I think it's worth the addition

Ah ok good to hear. Now you can have water/ice, fire, standard, dark, forest and golden dungeons. (although golden has some green in it and there are like two choices for fire dungeons)


For battles, if you are concerned about the border being too small at the top of the screen you could always just display every instance/color twice except the bottom black line so it's twice larger from battle perspective. But with the yellow line it would look weird.

Not bad so far, although they kinda look different for some reasons

Aah ok, I thought it might look better with larger borders, but I guess this looks ok as well (and much better than without borders).

Yeah I never understood why "M->Str1:Disp A doesn't work but "M->Str1 then Disp A on a separate line does. It's generally a better idea to keep your code on separate lines, but on a CSE that slows down scrolling through the code considerably (although DCSE fixes that issue). As it was said in the Cemetech thread, the TI-BASIC interpreter is extremely buggy. Another weird bug with strings is if you concatenate hundreds of them together or about 3-4 massive strings together, which results into an instant and massive RAM leak and program slowdown.  When I programmed Zelda in 2004 I once had a 8 KB memory leak from string concatenation. The slowdown also happened to me when using an If:Then:Else block inside a For loop where I forgot to close the parenthese at the end of the For instruction, but it was not as bad.