I just thought about a solution for the battery bill issue:
Since Axe Parser now supports the storage of data inside appvars and sub-programs, this means if someone created a map editor in Axe to store the map data into an appvar one map after each other, he could simply store his map data inside such program file. Since archiving over and over can lead to fragmented Flash memory (and possibly a lot of annoying Garbage Collects), why not do the same thing TI-BASIC programmers do with ASM libs? Simply make an hybrid Axe Parser game that abuses some TI-BASIC as well as Iambian's XCOPY program to grant yourself the ability to copy archived programs into temporary RAM programs:
http://www.omnimaga.org/index.php?action=downloads;sa=downfile&id=522Basically, split your Axe game into multiple archived sub-programs, and make your game launcher a TI-BASIC program where the ASM lib by Iambian is used to copy those sub-programs in RAM only when needed. This might save Quigibo some time and he said implementing this directly in axe may actually increase the size considerably, not to mention the speed loss wouldn't be that bad considering the loading would occur during parts of the game where it doesn't need speed.
The only two issues I can see is that idk if such program would have to be uploaded in TI-83 Plus Assembly games or BASIC games and your game would no longer be pure-Axe (and disqualify it from a possible eventual Axe Parser contest)
