210 likes | 368 Views
BITPLOMACY. FALL 2013 - G#4. Wisam Al-Malack. Kyle Frank. Anthony Glitzner. Travis Moore. Joe Perks. BITPLOMACY Project Objective Tree. Last Semester Objectives. Reliable. User Interface. Data Storage. Host Privileges. Accurate Adjudication. User-Friendly Interface.
E N D
BITPLOMACY FALL 2013 - G#4 Wisam Al-Malack Kyle Frank Anthony Glitzner Travis Moore Joe Perks
BITPLOMACY Project Objective Tree Last Semester Objectives Reliable User Interface Data Storage Host Privileges Accurate Adjudication User-FriendlyInterface Archive Access to Current Simulation Overview of All Teams and Decisions Chrome, IE, and Firefox Availability Point-Click Method for Input of User Decisions Archive Access to Past Simulations Option for Manual Adjudication Username/ Password Accounts Post-Simulation Statistical Analysis of Results Override Option for Ending Simulation Easy Access to Current-State Map Representation BITPLOMACY
Game Overview Current Cycle Supply Centers (34) Fleet Army BITPLOMACY
Unit Commands “Defend” “Support” “Attack” “Move” “Convoy” BITPLOMACY
Build/Remove Commands “Build Fleet” “Disband” “Build Army” “Retreat” BITPLOMACY
Saving Capability BITPLOMACY
Loading an Unfinished Game BITPLOMACY
Select an Ally Generator • Generates when a country reaches 12 supply centers • For 2 countries Supply Center count to add together, they must select each other. BITPLOMACY
Simulation Ending BITPLOMACY
Improvements Old Version New Version BITPLOMACY
Advantages • Decision engine offers instantaneous adjudication • During class, adjudication can often take 20-30 minutes per cycle for manual adjudication. • Much easier to keep track of Supply Centers due to color-coding • Units can leave a supply center, but keeps ownership until another country claims that territory. • Simpler unit movement • Avoids resizing of units in PowerPoint, or mistakenly grabbing the backdrop due to precision clicking. BITPLOMACY
BITPLOMACY Project Objective Tree Objective Outcome Reliable User Interface Data Storage Host Privileges Accurate Adjudication User-FriendlyInterface Archive Access to Current Simulation Overview of All Teams and Decisions Chrome, IE, and Firefox Availability Point-Click Method for Input of User Decisions Archive Access to Past Simulations Option for Manual Adjudication Username/ Password Accounts Post-Simulation Statistical Analysis of Results Override Option for Ending Simulation Easy Access to Current-State Map Representation BITPLOMACY
Design Achievements • (3) Game Persistence • Save Games • ***Note: only one saved game is available as of now • Load unfinished games • Load finished games (for lecture purposes) • Designing the Game • Create a better looking map w/ individual images • Design a UI with those images • Build a fully functional adjudication engine • Cut down play time in half • (2) Put the Game Online • Implement Networking BITPLOMACY
Database Diagram BITPLOMACY
State Transition Diagram Recent Design specs hosted on senior design webspace: http://www.lcsee.wvu.edu/seniordesign/2013springee480-gp04/ Contains API for every class, method, and field used in the final game. Reference the Change Log on the Bitplomacy Github repository to see how the game developed over time. https://github.com/youngJeezy858/Bitplomacy/commits/master BITPLOMACY
Complete Source Code Listing • BITPLOMACY is housed on GitHub in a public repository. • Meaning anyone in the world could go to its URL and download the source code or upload changes. • Hopefully sparking some interest in BITPLOMACY for new Senior Design students, and encourage newcomers by giving them a place to start. BITPLOMACY
Testing The team would have liked to see the professor use the final version in class to see if: The professor could handle the interface and input orders easily. Students could interpret the representations of their teams on the interface. Students, with the rules sheet, can figure out what is and what isn’t a valid order more easily than when the professor uses the PowerPoint slide. How much play time is actually reduced by. BITPLOMACY
Safety Precautions • Some methods exist in the GameCanvas class that fire up to 60 times per second, which are used to update and draw the game to the screen. • During the team’s development, the game’s frame rate dropped from 60 FPS to 15 FPS. • CAUSE: Initialization of a new object in one of those GameCanvas methods. • RESULT:Used up every core the game was being run on, requiring a total restart of the machine. BITPLOMACY
Online BITPLOMACY BITPLOMACY
Final Demonstration BITPLOMACY
Any LAST Questions ? BITPLOMACY