• Name: Will Clark
• Position: Secondary Contact Manager
• Subgroup 2
• Responsibilities: Analyze gameplay rules and mechanics in order to improve, streamline, and (if necessary) remove aspects of the game as it now exists in order to create a better end product
• E-mail: wclark@ufl.edu or wclark@cise.ufl.edu
• Phone: 850.443.0757
• Projected for current week (12/3-12/9): This week will be spent removing the class "Mission" and replacing them with instances of the class "Invasion." Right now, they basically do the same thing, so this will reduce the total amount of code and simplify everything. I will also update the "recalcTravel()" method to utilize the speed of the slowest unit involved in the calculation of the turns it will take for an invasion.
• Summary of current week's work (12/3-12/9): The work that I actually wound up doing was quite different from what was initially assigned to me (that stuff turned out to be relatively easy and was quickly completed). Instead, I wrote new constructors in the classes "Invasion" and "MovingArmy" that accept values for "bombers" and "ships" rather than "infantry" and "tanks," and then use the new method "setAmount" to add the specified amount of bombers and ships to an Invasion object using the hash table and methods I wrote earlier. Finally, I used the new constructors in the Empire class to restructure "missions" to actually create Invasion objects with bombers/ships instead of infantry/tanks.
• Summary of last week's work (11/25-12/3): I have gone through every class in order to make sure that any travel time recalculations are done by the method "recalcTravel()" in the class "MovingArmy." This was done to centralize the function of calculating the variables "turnsLeft" and "totalTurns," so that any future changes to the travel time algorithm will be easy to implement. In the immediate future, this will be helpful when I implement a unit's speed as part of the time it takes to travel around the map. I have also updated the method "addUnit()" in the "Empire" class to store units in a hash table rather than in an array list.
• Weekly Schedule
• Timesheet (Details)
• Google Code Group
• 'Less Than Three' Group Site
• Yuku Discussion Forum