Ah here he is ^^

I think the main issue atm for Axe is the lack of external program/data support. Your game needs to fit in one RAM file, thus, it would be impossible to fit a large game like SAD into Axe memory constraints, especially if the file compiles larger.

Later it may be possible, though, to have parts of your game written in BASIC and the rest in Axe, though

As far as I know, Axe does not support large sprites, and the program has to be LOL.  But I could be wrong.

I'll definitely look at the update.

Sure, the manual is provided below as an attachment.  But this is just an early version I used to try to get people interested in helping out, so you'll find there's a lot of changes.  I'm making a new manual for both versions of S.A.D. 

The new Axe still doesn't support large sprites, altough it adds program naming support. I can't wait until large sprite support, though, as well as triple buffering.

Are you planning to have two manuals, one that is complete and another smaller one for the TL;DR people? Or maybe have a quick-start guide or something?

The turn-based version will only have one manual--a quick one.  It will tell you everything you need to know to play the game, or nothing more.

Aaah ok ^^

I guess if units are a bit similar, though, that they could maybe use the ASM version readme if they want more information on the background/story/etc

Perhaps, but it's my goal that the turn-based version of S.A.D. be finished by this summer.  The real-time one is not going to be done until at least next year, unless there's some kind of miracle.

Prophets, I think we'll be sticking with Ti-Basic and Xlib.

Wow looks awesome! Keep in mind, though, that in matrix form, this map will take 8111 bytes of RAM, so that's something to consider for memory management.

well, the trick would be to split each routines that need to run in a turn into more sub programs, that way there's always enough RAM to copy them into