In the first post I had forgotten to add a line between the map and HUD, so I said if I forgot it in the next set that someone gets to hit me over the head with a stick.

It looks great

wow looks so great. Keep up the good work. I especially like the complexity shown in these screenies like how some floors makes you automatically move in certain directions

Thanks

I'm trying to pick levels that show the different floors/tiles (that's why I threw level 87 in).

More good news:
1) I'm finally done implementing all of the different tile effects.
2) The routine for determining the player's new direction has been reduced by 90 bytes (using a look-up table)
3) Sprites are done.  (Adding one extra row of pixels into deeph's boot sprites made a huge difference)

To-do list:
1) Implement the timer
2) Modify the HUD, which will be white-on-black to help distinguish the map from HUD (thanks to DJ Omnimaga for the suggestion )
3) Mask the player's sprite instead of just ORing it over the tile.
4) Add in tanks (the only enemies I'm sure I can handle), then possibly other enemies.
5) Optimize the hell out of everything.
6) Port more levels.
7) Repeat (5) & (6) a few dozen times with bug-fixing and adding features I've forgotten about scattered throughout.
8 ) Repeat (7), etc...

I've attached a screenshot of level 3 with the new sprites.  I also posted screenies of levels 6 and 7 in the other thread.

[edit]I forgot to add a few things in:
-Level hopping/switching
-Keep score
-Do more than just display "You Win/Lose"
-Figure out the algorithm for when you can skip a level after losing a bunch more times.
-Implement passwords.

Looks great!

Thanks guys

Hehe, it looks like my tracks were followed pretty closely ..I use a main engine program/levels/actions.

When I said "this mess" I was talking about the little code snippet at the bottom of the page, not how my programs are organized (not sure if you thought I meant routine or not).
At least this means I'm not messing up too much

Oh, and right now my programs are:
CHIP, ZBLOCK, ZD, ZITEM, ZLOSE, ZMOVE, ZWIN, then ZLV...  Eventually CHIP & ZD will be recombined, ZMOVE & ZBLOCK combined ZLOSE & ZWIN will be combined, so overall there will be the engine, movement processing and winning/losing/level hopping, plus the levels.

Wow, it looks great!  Is this asm or BASIC?

As for enemies, I'm still working on that.  The flying star-things, rockets and balls should be fairly simple (but still not in large numbers, since that might make the calculator explode ).  The star-things and rockets move in a straight line until they hit an object, then they turn right/left.  The bouncy balls move in a straight line but turn around when they hit something.  I'm planning on having a list with the locations and another with the directions of movement.  I'll add them together, but when the new location isn't walkable I'll alter the direction list component.  Then I'll just loop over and display them.  Since the calculations are done in one chunk I don't think having many should slow it down a lot, just the displaying part.

These are just the thoughts going through my head right now, so it could turn out to be something completely different.  And if it turns out that enemies slow it down too much I might just not have any, since there are a lot of levels without them and others could be modified to still be a challenge without enemies.