Why 5 appvars ?
You know you can store several bytes in one appvar, even several times the size of a variable, right ?

Well if you ask someone can help you out I imagine Axe just uses the OS's routines so saving more than one variable shouldn't be any more difficult than just saving one variable.

EDIT: This is looking really great, by the way. Movement is a little slow but i love the bars and the action and everything!

Well it's always RAM that you manipulate.
You can do 1→{L3} and 1→{L3}^r but also 1→{L3+1} or 1→{L3+2}^r.
Well the exact same way, after a GetCalc("appvNAME",X)→P, you can do 1→{P} and 1→{P}^r (if X>1) but also 1→{P+1} or 1→{P+2}^r.

Will it get stored back into the appvar after you close the program?

If you are storing it to a pointer, yes. So basically if you want to create a new appvar if one does not exist, and archive it at the end of the program, it would go something like this:
1->{L1}:1->{L1+1}     //some initialization, if appvar doesn't exist these will not change
If GetCalc("appvDATA",Y0)    //checks to see if appvar exists and is in archive
{Y0}->{L1}                             //store data from the appvar into some free RAM
{Y0+1}->{Y0+1}
End

...Program that manipulates data in {L1} and {L1+1}...

Unarchive "appvDATA"      //unarchives it, if it doesn't exist (still) it does nothing
GetCalc("appvDATA",2)->S    //overwrites the previous appvar that may or may not have existed
{L1}->{S}                             //store data into appvar
{L1+1}->{S+1}
Archive "appvDATA"           //archives it
Return                               //ends the program

If you run this code every time the program runs, it will store the initial values (1 and 1) to the data you need if the appvar did not previously exist (running for the first time) and gets the data from the appvar if returning to a saved game. And at the end it stores the values back into the appvar and archives it.

Just a question but why are you using Y0 and what is it?

As far as I know it's the only way in Axe to read data from the archive, if you wanted to unarchive the appvar first, you could store it to some pointer and access it from that. But otherwise if the data is only accessible from the archive with the Y tokens. (Y0-Y9)

[somebody correct if this is wrong]

Quote from: Omegaxis213 on November 18, 2014, 06:38:49 pm

Just a question but why are you using Y0 and what is it?

As far as I know it's the only way in Axe to read data from the archive, if you wanted to unarchive the appvar first, you could store it to some pointer and access it from that. But otherwise if the data is only accessible from the archive with the Y tokens. (Y0-Y9)

[somebody correct if this is wrong]

That is correct, the y-vars are the archive pointers. You can't do a lot with them, like only read data via like {Y0+2} or via Copy(

Is it my browser or is the gif freezing pretty soon and is corrupted?
Anyways, the title screen is looking nice (alli could see )