Progress Report (10/02/2010)

Until this week, I was firmly convinced that the only way to make real progress on this project was to have a large, contiguous block of hours.  While I'm still convinced that long, uninterrupted time is the ideal scenario, I've accomplished quite a bit this week just working a few minutes at a time throughout the whole week. Lesson learned:  Take what you can get and make the best of it!

There is some troubling news on the horizon, however.  My grad school class requires me to complete two games in the next month and a half.  It's likely that TLC will be put on hold.  I sincerely hope I can keep things moving in spite of the opposition.

Accomplishments:

• Created TLCScreenBase class which provides support for common screen elements, such as the title banner and the status bar.  TLCScreenBase is a subclass of MHScreen, of course, so it also comes with the same capabilities built into all screens managed by the engine.
• Tested the game setup process for several player modes.  So far, all modes need some modification, but it's mostly insignificant.
• Fixed the "connected to null" problem.  The IP address of the server is now correctly displayed in the status bar.
• Started work on the team configuration screen -- the second most complex screen in the entire project. 
• Optimized MHImageFont class to make it more versatile and efficient.  We need to decide on a set of clean, readable fonts that fit the feel of the game.

Known Issues:

• Server IP address needs to be prominently displayed on the game host's screen, along with instructions to tell the other players of the address.  Perhaps as a scrolling marquee.
• Player modes need to be tested for UI, functionality and server registration.
• Single Player mode should not have a lobby screen since there is no one to chat with or "signal ready" to.  Instead, the player should be sent straight into the team configuration screen after team creation.
• Spectator modes should not have a team creation screen since spectators are not players.  They should go straight from the login screen to the lobby, or to the game screen if a match is already in progress.
• Need to test team color registration for multiple clients.  I think the server may be failing to remove used colors from the list of available choices.
• The standalone server app is treating the user as a player instead of a spectator.

Next Steps:
High Priority:

• Add buttons to lobby screen
• Create isometric wall tile converter
• Enhance client list display
• Redo team creation screen with custom components.
• Display IP prominently on host's screen
• Test and fix team color registration
• Test and fix player modes

Medium Priority:

• Analyze and re-evaluate client architecture.
• Begin building the game state.
• Create command line interface for server app so it can be launched and configured remotely.
• Create custom TLC input dialog screen
• Create team configuration screen
• Replace boring buttons with image buttons.

Low Priority:

• Add sound capability to MHGUIButton class.
• Change layout of main menu.  Put in placeholder for skyline backdrop.
• Lay out the HUD
• Consider designs for an effective test level.
• Write a level design guide.
• Implement player descriptor system.