Progress being made.  Mostly under-the-hood fixes, but the game will run noticeably faster due to re-worked collision detection and the editor is almost fully debugged and functioning with a sort-of shiny tile selector, just need to make/apply options and allow support for multiple levels. Expect a level differentiating system similar to Tio, as in DSLvl00 DSLvl01 DSLvl42 etc

Yeah, i was just wondering about the impact on the score...

Anyway, made a few screenies yesterday and today.
In order:

Object getting stuck inside a wall and exploding (didn't get map modifying done yet but it's coming).  Afterwards it returns to where it started.
The explosion is a bit drawn out, I might change it so it's a not as long.  Also I need to fix the camera shake, fsr it spends more time up than down 0.o
Also the screenie shows that when the person finds himself inside a solid block, he explodes as well.
Btw I was thinking of changing the object manipulating key from [MATH] to down, blockdude-style I guess but I kept doing it by reflex in the emulator so i was wondering what the forum opinion would be on that.
Another edit: the old bug that this had and Tio still has where the char goes into the side of the block and jumps up from there has been fixed by the collision reworking from a few days ago.  It's first demonstrated in this screenie.

Selector thing in the editor.  Top row is normal, bottom is inverted.  I might take out the bottom row just b/c the text on the bottom labels it clearly enough
There's a bug in the actual editor that I fixed last night, a somewhat boneheaded mistake regarding key detection.  So where it obviously bugs in the screenie, that's been fixed

The splash screen and main menu again.  This time, though, it's possible to skip straight to the menu from whatever part of the animation.  So yeah.

I plan on making an indestructible block (or making the default indestructible and creating a breakable block) so levels aren't a pushover.

I'm running into one problem after another when shifting and the object are combined...I'm thinking for the contest when one is enabled, disable the other so I'm not spending the rest of the time debugging things related to that

What's been slowing me down the most is trying to make monochrome, non-animated, 4*4 sprites that are distinct from each other...like, how do you sprite the point where the ball respawns?

Having three dimensions would be stressing the engine even more than it is now and even two dimensions would create plenty of challenge for the avarage person
Plus, 9-level grayscale or whatever it would be would be somewhat impractical, esp. for calcs with cheap lcd's...

I thought about it when I first started with the dimensions, but ultimately decided against it.

Development-wise, I'm changing the level appvar a bit (one byte in front instead of 2, there's now an object respawn tile so I just need to enable an option and search for it)
Also finished putting in both object respawn and explodable tiles in the editor.  Nvm that it took only like five lines and one condition each, it's done.

Under-the-hood fixes, random bugs regarding bitwise reading, fun stuff

Anyway, I'm just about done with the options.  Fsr the game doesn't detect when they're activated even though the exact same thing seems to work in small test programs...a la inData().
Not a hard transfer to bytes but still...why does this keep happening...

Darl when you drop the pack thingy when it's over a wall, does it bump out properly?