Hornpipe2's Blog - It's Official!

[RSS Bot]

http://www.richard.hutchinson.dsl.pipex.com/new_page_6.htm

# 0E 0380 - 03BF Karate Master (Greg Kennedy)

 

Now to finish it! LOL.

 

I've got two main branches going on with my code right now and I'm stumped on both ends, which explains the lack of progress.

 

• On the menu front: The biggest issue I am having is that it is hard to justify the ~2k expense on an elaborate menu system if I only have two options on it - "one or two players" and "choose player color". Some more options would be a plus (I'm presently considering things like player handicap, etc) but I have not yet figured out how it would work. Suggestions for more menu options are welcome - as this also helps drive the feature set in the game!
   
  I think overall though I will be replacing some of the font (text) with something smaller and less "flourished" (i.e. more readable), cramming a few more options on the page, etc. Probably will make the "Record" display a highlighable option when the SaveKey is present, and clicking that takes you from a Top 1 to a full-screen Top 16 (3 bytes score + 1 byte color).
   
  I may also see about making use of that System Settings page on the SaveKey. Character heights are as high as I can get them, so PAL folks will be playing with shorter (and slower...?) fighters, but I may be able to make up the difference in lines through a little bit of letterboxing and enlarged background images. But how do I work this around players who don't have the SaveKey? Drat.
   
  
• On the gameplay front: How in the world am I going to tackle collision detection?! For the frames that are "dangerous" (i.e. should be checked for hits) I've defined a "dangerous point" corresponding to a fist or foot. But now how do I rig up the vulnerable locations on the opponent per-frame? I've considered adding up to three or four hitboxes to be checked, but don't know if that will be enough or not, and the space of that (2 bytes/coord * 2 coords/box * 4 boxes/frame * 42 frames = 672 bytes) what a waste!! This stopped me cold last time and I haven't figured a better solution yet.
   
  Thinking... perhaps I can get a collision handler that is capable of reading the gfx data. Since the info is already there it would be pixel-perfect and probably not so expensive.
  

 

http://www.atariage.com/forums/index.php?a...;showentry=5768