I know you have been posting in the Grammer threads, too, so I will explain how to do it in Grammer (and probably Axe/Asm) and see if you can do it on the NXT:

First, can you draw or pixel test on other buffers? If so, for what I have been doing today. For each enemy, I have two sprites. One to be displayed and the other contains the hit as pixels on. For example, I draw this sprite to the viewing buffer:


Then on the other buffer, I draw this hitbox at the same location:


There is no need to make it like this, either. You can have a huge hitbox for enemies with some kind of aura or things like that. Anyways, then all I need to do is whenever I move, I just pixel test the location I am moving to. If there is a pixel on, it means it is in the hitbox. so you just don't move there.

The nice thing is, you can have several buffers for other things. For example, one buffer for collision, one buffer for killzones, et cetera.

Again, this all relies on the ability to pixel-test other buffers. I don't know if this helped clarify things or not

I am not sure about the NXT, but in Grammer, yes (and in Axe/Asm)

When I say buffer, I mean, in this case, that if you were to display it, you would see all the hitboxes.

Exactly I was going to call it a layer, but I decided not to to avoid some confusion. But yes, that is how I think of it I think of them as layers of the screen and you are just pixel testing what is underneath.

Eh, I think of tilemaps as just being able to get detailed pixels and showing the detail by blowing it up in scale. When you are still checking a tilemap, you are just "pixel testing" it, but getting more than a 1 or 0 result.

Are you applying the same acceleration to the enemies? Also, do you have FP support, or just integers?

Ah, okay, try starting both you and the enemies at a half pixel location. That is the way I solved it before