Jump to content
  • entries
    4,932
  • comments
    2,716
  • views
    1,807,356

13 or 16 obstacles


atari2600land

212 views

So I am doing math now. A page has 255 bytes. Subtract the code for placing bytes and I'm guessing I have about, let's say 200 bytes. For there to be 5 tracks, each track would have to have about 13 obstacles. For there to be 13 obstacles would take up 39 bytes of code the way I've set it up, and 39*5=195. Or if I felt that 13 obstacles wasn't long enough, I could have there just be 4 tracks, each with 16 obstacles. (16*3)*5=192 bytes. Either way, I'll probably have enough room in one page to have all the track data plus the code that gets the track data and puts it where it needs to be. And I've put the beginning of a page right where the track data begins.

 

What I did do was took out the title screen music. I replaced it with a countdown timer. It counts down from 3 to 1 and then you hear a gun fire which signals the beginning of timing. I saved some room this way. Right now I'm at 1,200 or so bytes used up. Add another page to that and I'll have used up about 1,600 or so bytes of an allotted 2,048 in a 2k cartridge. So having an Excitebike-type game in just 2k should be possible.

 

And also remember too, I could lengthen the tracks by adding the lap numbers needed to get done. I'll start at 3 laps needed once I get track 1 designed and go from there. But what I've done in a week's time looks promising.

0 Comments


Recommended Comments

There are no comments to display.

Guest
Add a comment...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...