Bug, bug, buggity bug

There’s a bug.. two in fact, one in the server side part of the highscore management code (which was kludged, then broke again when i tried to improve it and finally works correctly now) and the other in the game itself that doesn’t reset the chain counter when the player dies (due to an assumption i made when dealing with killing the player’s craft). Both are repaired, although only i’m playing with the corrected game code right now. Depending on the feedback the beta testers give me, that should pretty much make this the final version of the code… unless someone manages to thrash the server.

The huge irony of course is that it was me who found the things after passing the beta out for testing!

Share and Enjoy:
  • Digg
  • Sphinn
  • del.icio.us
  • Facebook
  • Mixx
  • Google Bookmarks
  • Twitter

Tags: , , , , , ,

4 Responses to “Bug, bug, buggity bug”

  1. Shaun C says:

    Cooly wooly! Great dose of ‘just one more go’ fun.

  2. Jason says:

    Yeah, and look who just pwned the online score table too! =-)

  3. Shaun C says:

    heheh. This damn thing is too addictive. It’s totally destroying my attempts to meet my work deadlines. >:(

  4. Jason says:

    Tell me about it, getting the code ready has me all caught up as well! The WordPress sidebar widget now highlights scores added on the same date as the server’s clock says it is in red and i’ve tweaked a few other things in the highscore system…

Leave a Reply