Oh no, please don't make this game run at 15MHz, think of my poor 83+

Also, if you want to have more than 8k of executable, you can use both the CrabCake and my PageSwap axioms. The first one allows you to run programs up to 24k and the second one allows you to use subroutines you defined in an app (16k moar !). You can even use PageSwap with several apps, which is the number of apps times 16384 bytes of executable code !

For example, with CrabCake and one app, it's 40k of code that you can write.

But please don't use Fullrene, it only works on 84+

That will be very useful I forgot about your Axiom. I can start writing more optimised routines then and store them in an app! I could even add code so that if the user tries to run the app, it will start the main program instead

EDIT: And I was only showing 15MHz so that people could see what it looks like. It is about 1.75 times faster at scrolling on my actual calc.

Yes, the program would require an app, but to be realistic, this program will probably get really big anyways. There is no way we will fit it all into RAM, so why not fit some of it into an App that is already in archive that we can add highly specific and optimsed code? I am sure we could fill the whole 16KB of space and leave almost no wasted room.

You mean loading the appvars as programs? I did that with Grammer, so it is quite doable

Oh, okay. And I was thinking that using an app, I could write routines to directly access the data in archived appvars. This would help quite a bit with map data, tile data, and sprite data. I could maybe make a command to copy a sprite from archive to a location in RAM (that way it can be accessed by the main program).

If I have 16KB to work with, I could make routines that can work directly with archive and do it quickly >.> It would technically be slower, but it probably wouldn't be noticeable.

I'll take this conversation over to the Coding topic, since it will be important for others.

how about map designing? So just positioning stuff?