That speed needs some improvement but that enemy sprite is awesome :O

very cool, it looks great! Are you going to add Y axis scrolling, cause that would be boss.

Also, do you have the link for the tilemap compression thingamajig?

Oh yeah, sorry I forgot about that. I'll try and get that to you later today. And for pxl based collisions, you can go ahead and use the engine I wrote for Seeker if you want to.

Yeah I still need to know how the jumping part works

Those variables are confusing me...and the 256 is just so it's more accurate right?

Oh you're right, I get screwed up sometimes with the Y coordinates

Saintrunner, fix that inequality and I forgot to add that it needs to do
0->V->W->A->B
After it.
(edited the post)

And 256 is for accuracy.
I'm using variables for Location, velocity, and acceleration, which I think works nicely.

Can you explain how that works?

So I have two subroutines, MoveX and MoveY. Each of these moves the character as far as the [velocity variables] dictate, stopping the character and zeroing the [velocity variables] if there's a pixel in the way.

Basically, I have a loop set up that loops from 1 to however large the [velocity variable] is (negative values of the [velocity variable] made things a little complicated, but it wasn't too bad). Inside this loop is another loop that goes from [zero] to the [height of the sprite] minus one, doing a buttload of pxl-test commands to see if there's anything in the way. If there's anything in the way, stop the MoveX or MoveY routine, and move the character position as far as they can (up to a point) without hitting something.

It looks kinda like this: assuming X is the X_COORDINATE and D is the X_VELOCITY. Pretend that X_VELOCITY is positive (so the character moves down). Assume there's no inflation, and X_VELOCITY (D) is 3, so the character can potentially move 3 pixels in the downward direction, and this is written out in non-loop form (which is highly impractical but demonstrates the concept fairly well).

1. Look to see if there's any filled in pixels in the 8-pixel-wide row directly beneath the character (assume a rectangular character).
2. If there's none, move the character one pixel down, and repeat step 1 until you've already gone as far as you had the potential to go (You don't want to go fifteen pixels, you want to go three, because X_VELOCITY is three, and X_VELOCITY is the maximum number of pixels your character can move in a frame.
3. If there are any, stop moving the character. Return from the subroutine, get on with the rest of the game logic and whatnot.

That probably didn't make much sense. But hopefully that^^, coupled with studying the source code of my engine, will help you.