You might want to wait for the 84-C, even.

Question, is the TI-Planet update of Tinycraft uploaded today a new version you just finished working on for release? Just wondering since it just appeared in the new files list there now but there was no new post here nor the other thread.

No, not at all. On the contrary, I noticed that I forgot to update the topic on Cemetech when I posted the last update here, and that I never uploaded it to TI Planet

Is there at all still progress on this or is it 'on hold'?

Well it is "on hold" until I get holidays to get back to work on this. I had time to work a bit on Pokemon as you may have seen but not much was done, and it was easy stuff. But then, when I wanted to get back to work on TinyCraft, I was like "dafuq is that supposed to do ?" so I really need a lot of time to work on this one.

Well the problem is that the source is already 18577 bytes large and I hate doing subprograms. But yeah, maybe I should put in a subprogram some "obvious routines" that I never edit so I can comment the code.
Also, there are some comments on the "real tricky parts" where I had optimization flashes or something. It is just that some parts that seemed obvious to me when I coded them are not so obvious now that I read them again.

In other words, we need a direct-to-archive editor, that Axe supports

That doesn't sound impossible to me....

I meant a text editor that loads parts of the files into RAM at a time (Specifically, the part you're looking at) and automatically writes back modifications either once a block is unloaded or when the alteration buffer is full.

Anyways zStart already has an archive editor (it copies to RAM then archives back when you quit). You just need enough RAM to open your code.

Well that is what we are talking about. Of course I use zStart. But the code already takes 18577 bytes, so adding comments may have it go further than the RAM allows.

(not sure about the grammar of the previous sentence)

but if you go with sub-programs won't axe need to load 'em all into ram when compiling anyways?

I don't think so because if it did, it could not compile Pokemon (the two main sub-programs are respectively 12047 bytes and 11466 bytes). And the only reason why I used sub-programs for this project was that I recycled code from another program I already made. Otherwise, I never do sub-programs.