What I mean is instead of Pt-Mask only looking 8 bytes forward, you would be able to tell it where the second sprite is.

Ok, how about this...
Two (sort of, more like 4) requests

1) a signed Disp, so numbers >32768 would display the respective negative number.  Ie instead of 65472 it would print  -   64 , prolly requiring six spaces to work in instead of the normal five.  Or maybe even have the negative sign next to the topmost digit, if it's smaller code-wise
1a) something similar for Text()
1b) support for one-byte numbers, maybe check the syntax at compile-time?

2) a Disp that advances only as many digits as the number needs

They would all be optional, so the existing commands aren't changed.

E: changed "bit" to "byte" >.<

Why not adding in the Commands.html the size of each routine and the size of each routine call ?

That actually might be a pretty good idea, since people always ask about this information and it's nowhere to be found. Perhaps speed data could be added as well? My only concern is that theses would complicate the otherwise fairly clean and simple command list.

Maybe add that programs compiled to Axe Fusion won't crash when axe isn't installed. E. g. let it return to homescreen when the axe app can't be found.

No, it only wasn't the latest version of axe on that calc and he accidentally ran an axe fusion program.

I am quoting what I asked in the wrong topic so my feature request is actually in the Features Wishlist.

Would it be possible to have equates ?
I mean that for example if I write this
   test equ {V+17}
each time the parser hits the word "test", it replaces it with "{V+17}" before translating it into asm.

(note that here, V+17→°test would not work since V+17 is not constant)

EDIT: Oh, I see, that way if FOO translated to {V+17}, you could do something like 23→FOO and FOO→X and both would be valid statements.

It would still be no different than using {V+17} everywhere though, since FOO wouldn't actually exist. It'd be more like a macro than anything.

Yes that's it. It would not save space in any way. It is just so I can easily see who is who in my appvar. Because I have wood, stone and apples (among others) and having this
   {V+17}^^r equ wood
   {V+19}^^r equ stone
   {V+21}^^r equ apple
would be of a great help for me to understand my code easier. So would it be possible ?

Could the UnArchive command be modified to return the address of the unarchived var if it was successful, and 0 if unsuccessful?

How about a larger app max compile size