Well, the most recent workable sources are all available on this thread.  When programming on the highly volatile platform combined with the highly dangerous language that is Axe on z80 calculators, I generally think it's a good idea to disseminate sources as much as possible to guard against RAM crashes.
I think getting somebody to rewrite the portion in assembly might be a last-resort kind of idea, but I'll definitely keep it in mind. 

[RANDOM THOUGHT]You should add the quote "I hope your project doesn't die" to your signature![/RANDOM THOUGHT]

At the very worst case you could always do it the Joltima way but have corners using triangle tiles instead of squares, or something like that.

Wait, what? 
*Music scratches to a halt

What would that do?

I did.  I'm working on deciphering Runer112's tilemap program, but I'm still not entirely sure how it works.

I think that's b/c it's crazy optimized.

Correct! I often struggle to decipher my optimized code, which is why I usually try to force myself to add more comments than I think I need so I can understand it at a later time. However, it looks like I didn't comment my tilemapper much. Want me to go back and comment it?

Quote from: Michael_Lee on November 12, 2010, 07:02:05 pm

I did.  I'm working on deciphering Runer112's tilemap program, but I'm still not entirely sure how it works.

Quote from: MRide on November 12, 2010, 07:02:56 pm

I think that's b/c it's crazy optimized.

Correct! I often struggle to decipher my optimized code, which is why I usually try to force myself to add more comments than I think I need so I can understand it at a later time. However, it looks like I didn't comment my tilemapper much. Want me to go back and comment it?

I appreciate the offer, but I think I've managed to understand the tilemap moving part well enough that comments really aren't necessary.  (The tilemap creation part, however, is... difficult to follow, but strictly speaking, I don't need it for my project).  If you have time though, making the guide to Axe optimization that you mentioned on the tilemap thread would be pretty cool, though (poke, poke).

Another trick can also be to split your game source in sub-routines. That can help making the code easier to read.

Well, there's BasicBuilder, but it's not very reliable. Programs run slower, lots of pic stuff need to be renamed, xLIB/DCS sprite/map/pic commands won't work with internal BB pics, there are no archived program support and it's limited to 1 page apps. Hence why none of my old games use it.

That is a nice increase. Very cool! =)

Woah that's a huge increase indeed! Does this means the project might be revived soon?