yes, that's true.
but if you want to use ur asm prog within a BASIC prog, than it's easy to store some settings in a list, or in Ans.
BTW, In BASCI you cán edit the AppVars, when you convert them to a program (just one or two bytes different). But I assume that will not happen very often. And perhaps u sometimes just want to be able to check your game loading system, so then it is just usefull that lists or whatever can be accessed, i think...

My opinion: AppVars are usefull for game saves, and lists/Ans are/is usefull for settings to use in tour asm prog.

So.
Program Writeback to AppVars.
It must be done.

nice, good idea, it should actually guide people in what project (or parts of projects) to work on and which one to wait before starting working on so they wait for upcoming Axe releases to make their task easier. That's of course for less patient people, though, so these people will probably use or modify the premade ressources like those by SirCmpwn to get these features early

I really like the if counter idea, because it will make it much easier to create animations and the like

well they are included in html format with each Axe downloads. Check the documentation.html file.

The user made routines I do not officially endorse because many of them will be added as built-in features in future versions.

Probably those will come packaged with the parser when its completed either as a separate app or a submenu in the parser.  But right now, if anyone authors a useful helper program to make axe programming easier, feel free to submit it to me and I'll include it in future versions.  Its also a plus if you can write a short readme to go with the program.  Include proper credits to yourself as well.

EDIT: This includes help manuals and tutorials too!

can someone please explain how a counter statement will work?
perhaps I'll understand it when i see an example, but right now i don't know what it exactly will be.
Something like a for loop with multiple vars