My suggestion would be that you use one routine for each calculator speed. If the program is compiled to run at max speed, insert both routines and if the person runs the game on a 15 MHz calc, it will call the 15 MHz grayscale routine instead of the 6 MHz one. If the game is made to run at 6 MHz the entire time, then during compiling, just include the 6 MHz routine. It might increase file size in the former case, but It seems like it's the only real way to do it.

Quality-wise it was ok for me, altough I could understand that for complex games it might flicker way too much and be hard to keep in sync.

That said, nice to see a new update, though, altough I had 0.2.3 for a day or two, already (altough it wasn't finished yet)

Yeah I was talking about that draw routine too.

By never using both of them, do you imply that if we compile a 15 MHz game, that game will not run at all on a 6 MHz calc or vice versa? In that case, I guess authors will have to make sure to never forget to compile two copies of their games before release: one for 83+ users and one for SE users, for authors who want their game to run on all models but run at full 15 MHz speed on faster models

Well, sometimes, people want to make a 15 MHz game, but still allow people to play it on regular 83+ too, even if it means less enjoyable gameplay.

An example of this is Axe Tunnel, Super Mario Smash Dance, Metroid II: Evolution and to a lesser extent, Illusiat series. All those games run without crashing on a regular 83+. They just run about twice slower.

I prefer to keep my 15 MHz games cross-compatible, even if it means they run twice slower on older models.

Will the Dispgraph^r command still be useable in the future with the Full command? If not, then I am afraid I'M gonna have to stick to version 0.2.3 of Axe Parser for future development. That's unless in the future, you add a compiling option that allows the author to sacrify file size to include both routines and a check if their prog is ran on a 6 MHz calc and automatically run the 6 MHz gs routine rather than the 15 MHz one.

I guess it's your choice, though, considering Axe Parser is your very own project. But I'm afraid if future versions breaks cross-calc compatibility for compiled programs, I will no longer be able to participate into testing future versions and will be sticking to 0.2.3, the last cross-compatible version, to make games (it has pretty much everything I need now anyway).

Or is the 6 MHz command gonna be useable in "Full" mode too?

How about having a variable that tells the program what type of delay to do? I mean that for example the default state is 0 so that each time a grayscale is run, it uses the 6MHz delay. However, if you put 1 into it, then the grayscale commands will be using 15MHz delays. And maybe have it so that 2 different programs are compiled when the variable is modified.

Dunno if I made myself clear.   

This is the best option possible.  I think it would be like this:
If (Calc == 83+)
Then
0->A
Else
80->A  //I have no idea how much extra this should be, so I'll just use 80
End

This value would be stored somewhere and used later like this:

Grayscale_Pause //Like Pause, only it uses the value looked up at the beginning of the program to determine how long to pause

I do not like the idea of breaking cross compatibility.  If you do this, you will lose people.  Hopefully you can just store this value to a little chunk of Safe RAM and add 5 or so more bytes to the program size and keep cross compatibility.

Hmm...

What are the applications of such?
I only see redundancy as of right now.

Also, you can use it for general optimizing.

If you check the source of Starship, I was using a bunch of things like this: conj(A-3,B-3,4)
Which I changed to this: conj(A,B,4)^r  Since it doesn't have to do extra subtractions.

That would seem more troublesome than it would be helpful.
You must remember not everyone is smart like us.
People can screw that command up and break the entire program.

Well I figure as long as there is a short explanation saying something like the six is for 83+ calculators while 15 is for 83+SE/84+(SE). Then you could say that if you want to use the six on the higher calculators that it is more advanced stuff. I don't know. Just seems like a good idea to me though.