If you are stuck with 8x8 (and it depends on what type of game you are making) you probably would not end up using the full area of the sprite, just so you can keep the correct proportions of your character.  Like make it a 4x8 image but on an 8x8 sprite.  This for Army or somthing else?

Bwang how are you managing the clipping for the sprites?  Do you have a full z buffer or what?

Woot so i already have the entire engine finished, what was the dimnensions that you required?  Traditional 10 wide and about 15 hight?

I am for mandatory headers for people with many programs in your program menu, it would be a way to sort through them and have a cleaner list.  And i am against using the traditional :String header because then regular Basic MirageOS will show up in the Axe menu, and it could confuse some users.

EDIT: Ninja'd by Will_W with a good point

EDIT2: Ninja'd by Quigibo

EDIT3:

Thanks again Builderboy for the Logo.  I didn't end up using the whole thing, just the picture of the Axe, but it looks great.

Thanks ^^

By directions do you mean collision calls?  There needs to be 10 collision calls per frame for the main character (5 pixels per side across 2 sides) and probably 2 or 4 for boxes, a single for plasma balls.  What do you mean by saving the cycles?

Is this intentional?

5->{L1}->A

Now A does not hold 5, but rather the address of L1.  This just caused me a horrible debugging session until i figured it out

Hmmmm but then it becomes tricky to move any object by a single pixel, since your coordinate plane is not evenly divided.  I think i have a way to make it work however by storing the tile data in a different way.  It will take up a tiny bit more memory, but it should not be too bad.

EDIT: Okay 4x4 tiles is officialy not going to work.  After a quick conversion i realized that while the tiles are smaller, it actually leaves me less room to make maps, since corridor would need to be 2 tiles wide (since the character is 5 pixels wide, and it will not be changed).  SO that means that i will try to use Calc84's option, but i will have to write a separate collision sub for the portal gun, which needs to be able to move pixel by pixel.  With so many more objects being added, such as boxes, plasma balls, and other collision things, there is going to be a lot of collision, and therefore it needs to be as fast as possible.

Well, that piece of code that Quigibo posted is the heart of my tilemap detection.  It takes a coordinate on screen and finds the tile that it resides in.  Since its used in collision code, that means its called many times each frame, and all with unique values.