he just moves slow because he is fat

Lol j/k though, yeah the map engine needs serious optimization

Steadily working on optimizing. I have a lot of code that I can "subroutinize" for space, plus I've got the grayscale to be way less flickery. I'm probably going to stick it into Sourcecoder and print it out so I can look at it all at once and organize it a bit better

Ouch, I'm running very tight on space now. Combined everything fits into the app with about 600 bytes left . must...optimize..more...lol. I think I'll return to the battle engine for a bit and optimize that because it has some chunky stuff in it too

Well, it seems like FinaleTI and Runer have figured out a potential workaround here so the workload might just have been cut by >9000% (if it works, which it appears to do). All I have to do now is move the tile data out of the map engine to an external appvar which will save me like 1200 bytes off the map engine, then I can use that space for the routine Runer gave in that thread

Cool to hear! Hopefully you can fit more stuff. Btw do you know how many maps there are in the game approximately? (based on 12x8 chunks)

5100 bytes? That's pretty good, considering you're doing 3lvl and smooth scrolling between tiles.

I'm at 2467 for Nostalgia. Of course, maps are 1536 bytes... I'm gonna have to see about RLE compression or something. It does support animated water tiles, though.

Yep, I redraw every frame... I'm gonna go request some better water tiles than what I've been testing with though.

As for my maps, they can be up to 96x64, support wall, floor and ceiling tiles, as well as the aforementioned water tiles. My maps are basically the equivalent of two pictures, the first is used to determine the tile: If the pixel is off, draw a floor tile; if the pixel is on and the one below it is off, draw a wall tile; if the pixel is on and the one below it is on, draw a ceiling tile. The second pic is used to determine if the tile is a water tile. If the pixel is on, draw a water tile at the current frame. Then OR both layers over each other so you can't walk through water, etc.
The current map layer is stored on the back-buffer, and the current screen is on the main buffer.

I'm working on NPCs too. I'm just unsure of how I want to handle them, like do I want them to walk around, do I want them to just turn around in place, or just stand still? Nice about that shops/inn thing. I'm thinking of styling my NPCs after the way you did yours.

12x8 chunks?
Not sure what you mean there, but I do know that I can have about 10 or 11 64x64 maps to make around a total of 42000 tiles. I also have the engine structured to support an indefinite amount of map appvars (currently I've set up 2 of them, but theoretically I could make as many as the archive could fit ) However, not all maps will be 64x64: a lot of places like shops and rooms will be 16x16 and places like castles and such will be 32x32, so there could be a lot of different maps and map sizes.

Oh and the map engine is down to 5100 bytes now and runs much faster , but there are some weird bugs that I have to fix first

Ah ok, well I mean, divide your maps in 12x8 pieces. How many of those would you have? Or maybe you could state it in bytes. Assuming in your maps, one tile = 1 byte, how many bytes of map do you plan to include?

As example, Illusiat 13 had about 65-70 KB of map data, but several maps were reused multiple times for different purposes (such as the desert area). Had I not done this, I would have about 80-100 KB of map data. Each map were 16x8 large, by the way.