I have hit a variable limit and was wondering if there was anything to get around that. I know in Ti-BASIC you can just create a list and store things to that, but I do not know how to to such things while using axe parser.
Can I get some help please? Thanks.

I am refering to A-Z and ø. Now what do I use...

What squidgetx said. Look at the Commands.html, find a RAM area that none of your lines of code will corrupt (for example, don't use L5 if you use ClrHomes in your code), then create new variables like this:
  L5→°Var1
  L5+2→°Var2
  L5+4→°TheGame
Now, Var1, Var2 and TheGame are legit variables, like A, B and so on, you can do 1→Var1, etc.
(note that TheGame has a name length above 5 so it will only work on 1.2.0 and higher).

Im afraid i don't fully understand...

What didn't you understand ?

If you only need 6 more variables, you can press VARS, go right to Y-VARS, Polar..., and then you can use R1 through R6 just like you would any other variable.
If you need more, this tutorial is what I used to understand how to use Arrays to store variables (it's pretty much like a list). It's best explained by this link, but it'll be confusing at first (was for me at first): http://ourl.ca/9288
Also, if you want to run it in MirageOS or any other OS, make sure to only use L1, not L2 or others or it will not work.

Variables in Axe are two bytes large, and you only allocated FOO and BAR to be one byte apart. The second byte of FOO overlaps the first byte of BAR.

Two solutions:

• Allocate your custom variables two bytes apart instead of one. The standard solution.
• If you know your variables will fit in one byte each, you can keep them allocated one byte apart. All uses of the variables only allocated one byte should then be followed with a superscript r, like FOO^r.

How does this compile? It looks like you are defining labels at runtime, even though labels are usually resolved to constants at compile time.