well I've only had my calc for about a year, and less time than I've had my calc than that programming, but I could imagine that happening.

Wow, just about this entire page has been off topic.
Randomness board/area/thread/thing, perhaps?
wow, I'm looking at the top and suddenly there's like five people here now.

again, red font is clarification.

Hmm... on a dull day I might look through the news archive.  Ticalc.org had some pretty amusing ones.
That's actually how I first heard of Axe Parser, when it was featured in June.

My turn to ask, "what do you mean?"
The bar already depletes.  Do you mean it should deplete faster?
As before, you can modify the source to deplete faster/slower, start with X fuel, and get X fuel from each bar.

EDIT...
Oh, you mean the bars you aim for.  That could be a possibility...
Or the ship can speed up...or both...
I guess I know what I'll be doing while the rest of the class learns how to use the school-issue 83+'s--[teacher speaking]"So this is the GRAPH key, class.  Does anybody know what it does?"
"yeah, you go to the right."

While cleaning out my calc's archive for the umpteenth time, I found something that actually works.
Remember Spacerun? Apparently, I got bored sometime in the early summer and spent some time on it.  I'm not sure if there are any bugs or whatnot, but I remember being kind of addicted to it myself, as I played it a lot.  I don't remember any problems.
There's a GIF in the zip file.
Controls are the same, though now you can use a more finger-friendly scheme of [Y=] and [GRAPH].
Oh, and the three buttons in between pause it.  And MODE.
Press the [^] key to disable the drawinv commands, thus making it run faster (and look weird).
As for the winning screen, just think of something cliché.
It runs a lot faster than in the screenshot.


Afterthought.
What's supposed to be added in axe version 1.0.0?

Haven't demoed much yet...
I'm waiting until I get a MSD8X adapter in the mail. The calc memory's too full
Great programs though.

I doubt it's an Axe bug.  It (enemy editing, not archiving/unarchiving) worked fine before.
The code.  That's close to what I did, but it has some extra details such as a level map if it's in RAM or it says "Level Archived" or "No Level".
I guess archiving/unarchiving can wait for V2.

I'm not sure what the rules are about helping with code...
Try reading through some of the old forums. Something like June, in the posts/critique thread someone said something that has really helped me.

Kind of confusing, reading two conversations at once.
Anyways, it wasn't frozen, it would just turn off after it recieved the legitimate password which wasn't the same as the corrupted password.
Problem solved.

Uhmm, back on topic...
I already have it storing it in appvars, such as WHGLVL1, WHGLVL2, etc.  Up to nine levels.
Notice--level editor.  Level's too hard?  Make it easier.  Done.