NES ASM Tips – Box Collision

One of the most important parts in any game, code wise, is to have some form of collision detection between sprites. This is Assembly Code snippet ( using NESASM3) should help you out when it comes to box to box collision and uses little space, so should be quite fast. We’re only using the A register AND 9 bits of RAM for simplicity.

Here we go, first with the variables being declared in Zero Page:

Next Up, The Function Itself, with an explanation of what we’re doing:

So, to use this effectively, simply set your sprite bits up appropriately, then Jump to the function (well, subroutine) by calling:

If there is a collision between the two points, spriteCollision Result should contain a value of 1, otherwise it’s just a 0

Hopefully, this has helped someone out there get past one of the stumbling blocks with NES ASM development.

Happy coding everyone!

Another week, a bit more NES Game Development Completed!

So, this week I managed to  add a bit more to Flap Happy. Some of it obvious, some…not so much.

Firstly, there’s now some semblance of a background, just some simple dungeon walls in a loop but it was more the journey to getting them working that proved the interesting / challenging part. Y’see, It’s all down to how I have the levels generated….

  1. Firstly we fill the room with spikes.
  2. Put some verticals up on either side
  3. Then generate paths from left to right with varying heights.
  4. Then, and only then, do I actually draw the blue dungeon blocks, where the plain black spaces were.

Which is kinda backwards really when I think about it but hey. It works, I’ll take that.

The next issue was that of filesize.. The ROM image is 8kb too large for an NROM256 cartridge which should comprise of the following:
a 16 byte header
2 x 16kb PRG-ROM banks (Where the games code appears)
1 x 8kb CHR-ROM bank (Our Background and sprite tiles)

That should total up to just over 40kb…But that ROM says it’s 49kb. That can’t be right!

After a bit of puzzling with the NESASM3 compiler and messing around with my code banks to no avail I decided to just load the ROM into a text editor to see what was going on and, sure enough, 8192 blank characters at the end of the ROM file, doing sod all.

A quick deletion of those and (fingers crossed)… The game still loads and runs just fine, 40kb (well plus 16 bytes of header)!

The next issue is that regarding the generation of platforms in-game. Sure, they’re all positioned nicely now but, they shouldn’t all be active at the start of the game.

Thankfully, I have a fair chunk of zeropage RAM available to me so I’m storing the screen positions in memory… in memory. Yeah, I know. So, this weekend I’ll hopefully have that side of things sorted and some more obstacles can be placed for next week!

In the mean while, here’s some initial box art I’m playing around with, it’ll change a lot through time I’m sure.


Right, back to the code!