We shall call him... Linc!
And he shall be in the Legends of Zeda!

I am not an experienced Axe coder, but I do have a bit of experience with game methods. I am wondering if there is any way that it could be sped up just by changing the method to another (as opposed to having Runer come in to mangle the code up a bit ^_^ ). So, I am wondering, how are you doing collision detection? A few weeks ago, I had an epiphany on how to do a really fast and simple collision detection. It is by no means obscure and is an idea that has been around, but because I figured it out myself, I like to promote it

(Pretty much, you draw to another buffer that I call the collision buffer. You draw any area that is occupied by another piece, so all you have to do is pixel test that buffer, once. That is super fast in Axe.)

Ah, sorry to hear Good luck on your school projects!

Yes, kind of Remember, the custom font has been available for a while, I just haven't had a full font To access the variable font, do Output(1. I have the letters, numbers, and other miscellaneous parts done and built in to Grammer, so it is still mostly usable.

Hi folks, I have a problem... Currently, the variable sized Grammer font is incomplete (very much so) and I don't have the time or drive to finish it, so I am asking if folks could help me out.

What is needed:
-A font that is generally the same height for all characters (preferably >6 pixels tall) and with varying width.
-It should look good (not sure what I mean by that) and should have some variation in width (like a ! might be thinner than a W)
-It should map to the same chars as the TI-OS in the large font
-Any extra chars that are empty you can fill in with your own (I made little sprites for the 4x6 font)

To help you, I have made the attached on-calc tool (it has one slight update from the previous version of it).
Controls:

+ and - scroll through chars
arrows move the pen tool
6 makes the char wider
4 makes it thinner
2 makes it taller
8 makes it shorter
[Enter] will set a pixel
[Del] will delete a pixel
[2nd] will invert it
[Mode] will exit

Everything saves automatically when you press MODE or you cycle to another char!
When you have a font you like, upload the appvar here (and possibly a screenie) so we can check it out.

Thanks much!

Hmm, I'm not sure, but it does definitely help text graphics. Pretty much, the Text( command has its own section/chapter thing in the tutorial because it has soooo many things that can be done and so many manipulations.

I am also working on a third font option that will use 4x6 font, but it will draw to pixel coordinates. That way, you can combine the variable size font with the fixed font to get better math looking results. I was also thinking of letting the Text( command with no arguments return the current cursor position. I was thinking also of adding the ability to do something like →AB where B would be loaded with the results of Ans and A would be loaded with Theta'. That way, you could do Text(→XY to get the X and Y coordinates in X and Y and also get overflows into other vars. For example, 348*567→AB would load the upper 16-bits of the multiplication to A and the lower 16-bits to B. Finally, I was thinking of adding a new syntax where instead of using A', you can use lowercase A, as well to mean the same thing. That might also cause less clutter in the program editor, too, if you can do →a instead of →A'.

Also, I plan to add all this today.

EDIT: Displaying the small fixed size font at pixel coordinates is now able to be done. This outputs with OR logic as a warning. You will need to do Output(2 to access this method.
EDIT2: Text( without arguments now returns the coordinates as Ans=Y, Theta'=X
Also, you can now do things like →AB
EDIT3:→a is now a valid way to do →A' (Still not able to use lowercase anywhere else in place of primes)
EDIT4:Now you can do math with the lowercase letters instead of primes and use them as arguments

Ah, I see. Did you use turiq's map for the example you showed there of the bug?

Ah, I'll give it a go later Also, it stores each pixel the same way the TI calculators do where 1 byte is 8 pixels. It is more precisely .125 bytes per pixel I am glad this method is working so well for you, too Would you be able to show us a level in action by any chance?

EDIT: Time for class, but it is looking okay already
EDIT2: Apparently, I cannot go to class today

EDIT3: I could not stay focused long enough to finish !_! Still, this should give people an idea of how secret passages and whatnot could work Just make sure that you are drawing the player, then the region on top of the sprite in case of secret tunnels