Bridgekeeper Pitfalls and Progress

Coming back to a project I haven’t touched in six months was almost like looking at someone else’s code for the first time.  But after a some strategic archaeology, I was able to uncover the general idea of how everything was supposed to work, and remember my original basic plan.  While the app did run (somehow) there were a few major corrections to start off the resurrection.

• The Player was walking in fast-forward speed  – The animation code was running in two places..
• The Player sometimes continued to walk in place when it reached its destination time – the animation would only stop if the endpoint was an even pixel number.
• The Player attacking animation wouldn’t repeat – the stop event was firing every frame the Player wasn’t in motion.

Bridgekeeper Introduction

Bridgekeeper was the first android app that I started working from scratch early in 2011.  This is a game based on the original Bridgekeeper game I developed with GameMaker which had two major releases begining in 2001.  It was a minigame based on an MMORPG called NexusTK.  Between a 2002 a  game graphics patch and better programming skills, a second version was in order.  Exactly ten years later I rediscovered this game in an archive folder, and decided to try and build it once more on a mobile platform.  This proved to be a little more challenging than I expected, so it sat on the back-burner which allowed me to release my first app (Lexx Soundboard) to be completed(?) and released into the Android market.