Yours has the benefit of being much smaller, though. My engine on its own is 646 bytes, almost 150 bytes bigger than yours o.o

EDIT: As an update, I just removed 24 more bytes of code from the left/right shifting. The only impact the code had was to remove 5056 t-states for each pixel shifted left/right (saving about .006741333... seconds at 6MHz, every time the map scrolls 8 pixels >.>)

@stevon8ter: That is smoothscrolling >.> I should post an example of "hard" scrolling at some point.

I updated my post with another screenie scrolling at two pixels at a time. Now comes the next step-- animated tiles

Wow, that is awesome o.o

+ collision detection is way easier and smaller...

So I think the movement will be like this? ok lol :p

And then all walkable tiles before non-walkable this and collision detection is based on if the number-of-map-tile your standing on, is smaller then the number-of-first-non-walkable tile...?

And i sugest tiles as following: sand, dirt, stone, grass, and some other .. all to walk on, and some fences as non walk-able and some other...

Yes, this is definitely the next important thing that will need to be figured out after the map engine is made. In my experience, it is always easiest to have walkable tiles as the first tiles in the set.

Yeah, that is one of the things I have to fix. When I finished adding in the blacksmith, I forgot to set Str1 back to the player name.

In other news, I have tomorrow and the following two days where I either have finals or work, then I have until the 20th to finish this up I don't think it will be finished, but I'll still submit it.

Yay, another update The blacksmith now is completely functioning. Before she would tell you what materials were needed and how much it would cost you, (and if you didn't have enough of something, there was a line struck through it). However, there was no way to actually obtain the item. Now, the blacksmith will take the money and material, work on it, then when the item is done, you can pick it back up (different items will take a different amounts of time to make) Time is measured in steps, by the way, not by a clock. In the original version, I used the built in clock on the 84+, but I know now that the 83+/SE doesn't have a clock .

Anyways, when you get your first weapon or some other equipment, an option will be available at the stats screen to change your equipment. You will be told what stats are affected, if any (Gold Dagger, for example, increases your base magic strength by 10 points). Also, I know have the built in sprite editor so that users can edit their sprites from the Miscellaneous menu. Oh, and because there are now two 16x16 sprites being drawn, I got rid of the BASIC routine and I am now using a small assembly opcode. Needless to say, sprites are drawn much more quickly now

Now that I am using so many assembly routines, I won't feel so bad about using a List→String assembly program to make saving much faster. I won't have to fret about the speed anymore and I can focus on the storyline

I'm pretty sure that I am forgetting something, but I hope this is a solid update! Oh, the program is now getting close to 11000 bytes On the plus side, I can't wait to abuse the assembly programs I have, now. I mean, I can now use the 16x16 sprite drawer to make tilemaps o.o I won't, though Maybe I will use it for spell animations.