You can be active in the TI-BASIC subforum, it has some discussion or you can start one.
I don't go too much into Axe Parser discussion, sometimes I help with some asm stuff...

I liked the "Dragon Tavern: Boss Hunter" idea. It would be cool to reveal the coolest bosses to defeat that you can find in RPGs in PC or consoles.

oh yeah those. I don't know for the garbage ones but for the 3x3 squares one that is like 256 characters large, I heard it was the calc trying to display empty flash memory content. Dr.Dnar told this on IRC a while ago. Despite the token being 256 chars long (taking two screens), it's still just a 2-byte token.

That was a nice token hack. ^^

I think I tried to see what the program displayed with a 2 byte token started by DD (hexadecimal). It displayed a ? that changed to ?RESET RAM?. See http://tibasicdev.wikidot.com/miscellaneous-tokens.
By the way, one time my TI-BASIC program had some ? randomly through every 3 lines or so. I managed to reconstitute the code, hopefully, but it seems like my calculator RAM was changed in some way that affected the TI-BASIC programs. I ram cleared and deleted things for precaution. Maybe I run some assembly program with a bug or I ungrouped some odd corrupt group.

And I believe, the xtrachar.8xp misses only the hidden DDDF (hex) token. Which is like the transposition matrix but displayed a little down.

I hex edited some TI-BASIC programs to find some hidden tokens seen in TI|BD token tables.
I found that some unused tokens show in program editor as a ? and when you "scroll" it changes to ?RESET RAM?
I used Calcsys, although nothing bad happened to me, test at your own risk.

how would i implement gravity in axe? it doesn't have to be realistic, i just want to manage getting a sprite to jump up and down.
i could easily implement this with some flag variables, but i'm really looking for a routine that only uses a few variables. Even just a starting point or hint would be helpful. So far, i can get a sprite to jump up, but it won't come back down.

If you don't need realistic simulation simply reduce by some value (test for one that makes the desired effect) velocity in y coordinate each frame and that is it.
I think for gravity simulation you need at minimal 2 variables: Y position and velocity in Y coordinate.

Pseudo code:
Lbl A
// code
V-9->V
Y+V->Y
// code
Goto A
//Y has now the coordinate

Mind that V velocity will be negative, so when adding V to Y it will be actually subtracted.

We reached 20000, close to the middle of the year. We can believe in the 40000 mark in one year.

Yeah, I hope this activity revitalises other forums as well. The key is coders show progress on new projects and keep interest in coding talk exchange. Basically is what happens here in Omnimaga with a complete team of coders and Cemetech mainly with Kerm works and discussion about important z80 and BASIC issues.

That feature was unexpected to me. It is a nice game for a TI-81 but I never imagined it could be feature when TI-81 is a rare calculator, someday museum calculator only.

Congratulations, if you are the only feature in the TI-81, you know what it means.
WIll you port it over to Nspire OS 1.7?

I use the 2 setups you are discussing. It just depends on the program I use. The conversion on Y for the -62->Ymin:0->Ymax  is just -Y.
For the other you do something like 62-Y.

And in movement/physics things you have the change the code accordingly to the setup.

Thanks, that is a great support.

I have a few ideas to speed up things like caching graphics on Pictures. And I might abuse unrolling code if I need. Hard code some lists in variables, anything that helps speed.