Text(X,Y,sub(NTH,1))

By the way I edited the NTH routine to make a correction.

The Data command needs the r modifier after each entry if you're using pointers since each entry needs to be 2 bytes large.  But there is a more memory efficient way to store the text, which is to just have each entry right after each other like this:

:"Text1"[00]->Str1
:"Text2"[00]
:"More Text"[00]
:.etc

And then to get the Nth string, just write a routine that starts at Str1 and scans until it has read N-1 zeros

:Lbl NTH
:Str1->r2
:While r1
: While {r2}
:  r2++
: End
: r2++
: r1--
:End
:Return r2


Too bad there's no options for versions above 0.5.3

There were also several unofficial versions that some people may have lying around becasue they requested to beta test new features, but I doubt anyone still uses those.  They had version numbers like "0.2.B" or "0.3.A" for instance.

That was already fixed as part of my revamping of buffer drawing commands.

That's already been around since I first added the EndIf, you can always use them in for loops

Speaking of For( loops, I don't know if this has already been asked, but why isn't a 4 parameter allowed?  Even if it's just a constant increment or decrement, that would be really helpful

The main reason is that the increment code has already been written by the 2nd argument so it would be hard to make that happen on the 4th argument.  I would have to do some really weird and difficult out of order parsing for that to work, and I don't want to make it the 2nd argument because that would be extremely confusing.

Also, I will probably be adding a new loop structure which unlike "Repeat" is literally a "Repeat".  The syntax is a one argument for loop For(Times):Code:End where it just does the loop however many times without using extra variables and is highly optimized (more so than Runer-style loops).  The only thing blocking me right now is those AWFUL "Goto" statements.  I now see why so many languages ban them, they make it really difficult to optimize since you can't use the stack in any loop that has a goto, otherwise you get memory leaks.  I am therefore banning the Goto instruction inside this new loop structure and possibly for-loops if it leads to an optimization there.  I mean you shouldn't be abusing gotos that way anyway so I'm hoping there won't be any compatibility issues with this.

And just to let developers know, I already added code to allow Axioms to hijack existing routines so they can call or jump into any routine at any entry point.  Beware when using this on native Axe commands though as some of them could change from version to version as new optimizations are found.  Speaking of which I've already found a few major optimizations with all sprite and pixel commands that should shed quite a few bytes off of programs, especially larger ones.

I think the Bitmap() command is perfect for that, except it doesn't work if you have part of the image off screen, but as long as these stay fully on screen, this would be the easiest way for sure.

push hl
sbc hl,de
ret z
pop hl
This could be disastrous!  If you return after you pushed hl, the top of the stack contains the number hl instead of the return address so the program will jump to some random place in memory.  You should only return after the stack is back to where it was before:

push hl
sbc hl,de
pop hl
ret z