Even with mathprint turned off the program editor was extremly glitchy with files of the size of like 12k. I lost tons of progress over that.

Do you mean Rainbow Dash Attack for the PRIZM? Because that's the only calc one I remember.

You don't know mine

As for people learning ASM then switching to Axe or vice-versa it's definitively due to how both languages allows you to edit RAM directly and use pointers in a similar way.

Yeah, Axe's way to handle "objects" is the same as ASM, and not the same as Basic. And I saw a lot of noobs asking how to use the list L1 while it is not a list -.-°

Axe has a more user-friendly, but more complex syntax, while ASM has a simpler, but potentially confusing (due to lack of English mnemonics) syntax.

I would not say that Axe's syntax is user friendly, but more that it can be user friendly for beginners, but there is a moment you must start writing nonsense Runer-mimic code (even if Runer can always make better)

Hayleia yous is amazing

I know. But what are you talking about ?

()

Rainbow Dash Attack

Ah ok. Yeah, I was planning to add highscore saving and such, but got lazy
Anyway, it is full playable so it doesn't matter a lot

Well in fact, I first wrote Pokemon in Basic (then discovered ASM and started rewriting it in ASM), then discovered Axe and started rewriting it in Axe. And once the tilemapper was done, the thing I did for the battle engine was code recycling
Of course, as you said, there were problems of coordinates as you said, and reading data was not in matrixes, among other problems, and I added things that Basic couldn't support at the time, but I still kept the original algorithmic scheme

edit "Hence why it is so unoptimised" would say some, but I couldn't really do another way, I only had 2 months of holidays so I did my best to finish it in time before school starts again, and code recycling was very time saving. And I didn't feel like recoding from scratch something that I already coded and took me one month to code.