Game AI, Summer 2016:
Capstone options
Due: Day before scheduled final exam period at 11:55pm
You will be given until 11:55pm the night before the final exam period. Note that for grading the non-report option, I expect thorough documentation of both the evolution of your design as well as technical decisions, so keep good notes as you go along. The following are the options:
- REPORT, undergraduate only: Write a 5-page report (12pt font, 1-inch margins, single spaced) to address the different ways in which AI could be used in a hypothetical game. The instructor describes a game from the design perspective. The report will discuss which AI techniques would be needed to implement the design vision, and the particular pros and cons of different alternatives.
- Capstone 1, open ended: This project is designed to allow students to delve deeper into Game AI development by designing a game that has AI as a core aesthetic component (e.g. Nero, Spy Party, Black and White, etc.). Being creative about how to employ AI in games so that it is not simply used to provide intelligent opponents but becomes an intrinsic part of the game mechanics is a difficult task.
- Capstone 2, squad companions: In tactical 1st/3rd person shooters such as Gears of War, progress through a level requires coordinated movements of a squad of teammates. Implement a game in which NPCs must coordinate with the human player to progress through a battlefield against suppressing fire. Implement natural language generation so that NPCs can "bark" their state and intentions.
- Capstone 3, MOBA Map Generation: In this project, you will look at run-time PCG to create MOBA maps, using the Python game engine from earlier assignments. You must design a system that uses AI optimization to design maps for different players.
Non-Report Writeups
Note that for grading, I expect thorough documentation of both the evolution of your design as well as technical decisions, so keep good notes as you go along. In your submission, include a .doc or .txt file that describes the following:
- Exact instructions for how to run your game (if these are not included, you may receive an F).
- The algorithmic approach you used.
- The major challenges you met during the project and how you overcame them.
- Make clear what your goal was in creating your algorithms, why that goal was a reasonable one, and how well you achieved it.
- Thorough documentation of both the evolution of your design as well as technical decisions.
Suggested Milestones
The following are strongly suggested (and partially enforced) milestones:
- By [7/6 Wednesday]: Pick your team; this will be self-organized on Piazza. When your team is assembled, put it on the wiki page called "Final project team list" with each team member's first and last name, and the team name. Any unteamed class members should randomly form groups after 11:55pm on Wednesday night, 7/6. You can use the "Search for Teammates!" note to help in this process.
- By [7/11 Monday]: Choose your game, or have the design of your own game finished. At this point you MUST understand, and be able to tell everyone, how your AI functions as a core aesthetic component that is a key element in the gaming experience. Have a completion plan for your work, including what algorithms you will use, and be ready to do a 2-minute "pitch" to me (firm 5 min limit) on Tuesday. I'd also like a half page writeup.
- By [7/18 Monday]: If you haven't even set up your environment and began coding by now, you are in trouble. If you are making your own game from scratch, the non AI elements should be complete. If your game doesn't run by now, even with massive bugs or somewhat naive AI, you're probably going to fail. Your target should be to have all the AI-related code (structure) in place, but possibly needing to be refactored and extended. You should be able to do a rough, runnable demo in class on Thursday 7/21.
- By [7/25 Monday]: Your implementation is finished. You're only changing code to add polish (and squashing occasional, minor bugs).
- By [11:55pm night before scheduled final exam period]: Turned in. Recall that no late submissions will be accepted.
Submission
Submit via T-Square. For non-reports, this includes everything needed to run your game, and your writeup.
Grading
This project is worth 25% of your final grade. Non-report capstones will be demoed live during the final exam period.