Writing IF A == B || C THEN is apparently wrong no matter what, but writing IF A == B || A == C THEN results in an ugly inconceivably wall of text due to a rather long array name of A. Is there a way to keep it tidy aside from shortening variable names further?

@Nicole: Thanks for the recommendation. I just started SmileBasic so the number of "Instructions" i can make use of (or even know of) is still pretty limited. I had to read a bit further into "DEF" to understand its purpose, but it seems fairly useful. Though i have to evaluate rewriting my current code or keeping it as is. Might not be worth the hassle, as it serves its purpose.

First thing first: Can i call multiple sub-routines in succession? E.g. in sub-routine @X i call sub-routine @Y in which i then call sub-routine @Z. The upcomming RETURN will return to @Y, the next RETURN returns to @X, and the next RETURN returns to the inital caller? Second: How to execute multiple commands after THEN or ELSE (aside from GOTO)?

@Hanzo: Thanks that's very helpful. If i understand your explanation to "Fourth" correctly, then C and D are executed IF B. So i deduce the following are synonymic. IF A THEN B:C IF A THEN B C ENDIF Are the following possible? 1) IF A AND B THEN C 2) IF A OR B THEN C 3) IF A AND (B OR C) THEN D 4) IF (A AND B) OR C THEN D

Third: Will RETURN do anything if i go to a @Label with GOTO (so i can use @Labels with GOTO and GOSUB as fit)? Fourth: Any general advice for how to write multi condition heavy and branch heavy code?

Slow but steadily i´m making progress (in "learning"). I had a hard time grasping "Arrays". I´m still not very confident in using them. I´m also currently working on my first very simple game (not shown in the screenshot btw).

This programm speaks for itself. Rating: ★★★★☆ (Because coding on 3DS keyboard isn´t really that fancy.) Still love this. Even though it will probably take a while before i can create anything meaningful (learning Basic feels like... "learning")