^This. I remember one year ago I IM'ed him about Pyoro and how I liked the game and he said he would update it, then he brought up Axe. However, back then I was still not confident because I saw so many projects like that failing due to the author's ambitions surpassing their coding skills. I told Quigibo to start with the rudimentary stuff at first that you saw in 0.0.1. Then he signed up here, shortly after joining Revsoft, to post about Pyoro. He asked me what would be the best places to announce Axe. I told him to wait a bit until he has a good enough amount of stuff done, because I was convinced people would not take the project seriously if the first version could only ClrDraw. Then on Feb 1st he announced it with version 0.0.1 and during the first month the Axe board already had 700 posts. Activity skyrocketed even more after sprites support was added.

Nonetheless, Axe came a long way since its creation and I am glad finally a language that answers everyone's wishes had success in creation. Now we have plenty of good ports of popular Flash games and a big upsurge in new releases, especially since the end of the contest.

Thank you a lot, Quigibo!

By save grayscale, do you mean while playing the game in one go, or between gameplays?  Either way, I can think of 2 methods.
If the scene changes, could first create an appvar, copy over both L6 and L3 to the appvar (L6 is the buffer, L3 is the backbuffer), compress it perhaps, then archive if you want.  You would do the reverse when opening it.
If the scene doesn't change, you could just redraw the screen by reusing the data you used to draw it in the first place.

For non-8x8 sprites - if the dimensions are less then 8x8, then just draw whatever you need to, then use Pt-On or Pt-Mask.  Both leave blank cells transparent.
If it's larger then 8x8, then you might have to end up using the existing sprite routine then making your own.

Yes. You could store both layers for each screen image consecutively.
So, the first scene could be accessed like:
GetCalc("appvMOVIE")->P
Copy(P,L6,768)
Copy(P+768,L3,768)
Then you could just call DispGraph^rr or DispGraph^r in a loop or something to display the scene for a little.
If you wanted to cycle through a few scenes, you could try something like this:
GetCalc("appvMOVIE")->Q
For(Z,0,3)
Z*1536+Q->P
Copy(P,L6,768)
Copy(P+768,L3,768)
Repeat getKey(54)
DispGraphr
End
End
For simplicity's sake, this just waits till you press 2nd before moving onto the second scene.

Now, if you're asking how to create the appvar:
GetCalc("appvMOVIE",number of frames * 1536)->P
...
Data for frames
Maybe they're in imported pics, or something
...

If you were gonna put the first scene into the appvar, then something like this:

Copy(pointer to front layer of first scene,P,768)
Copy(pointer to back layer of first scene,P+768,768)

Adding other scenes would follow the same pattern, just keep adding 768 to the appvar pointer.


You can draw the picture in Paint or something on the computer, then run the picture through SourceCoder.

For image conversion, make sure it's a .bmp/.png/.gif file (one you made with Paint, for example).

Oh, the error is when compiling with Axe? Might be because you need to surround the hex with [] brackets.

By the way, is asking for this kind of help on IRC discouraged?

Not at all.  That's one of the reasons the chat is there.   Good luck.

Quick question:
If
Elif/Else-if
Else


In Axe? Thanks.