Dungeon Crawler Game, Part 3
Due: December 10, 8:30 AM
To work on the design and implementation of large, collaborative
For this stage of the assignment, you will be adding some new features to
your dungeon crawler. Your group will present the program during the final
exam period. Each team member will also turn in a report on the project
In addition to the requirements for part 2, your game should add the following
- You should add different types of items with different types of effects.
In addition to the weapon and armor items that you already have, you should add
two additional types of items. These can be whatever you want, but have to
have some kind of purpose (they must have some kind of an effect on the
gameplay). You can do this by making sub-classes of Item.
- You will have to provide class and method documentation for the code in
your project using Javadoc. You will turn this documentation in along with the
code for your project.
- You should add one additional feature of your choosing to the game. The
feature shouldn't be trivial, and should require some amount of code to
incorporate. Adding one more type of enemy that behaves the same as others
wouldn't be enough, for example. Let me know what you decide to add before
working on it, so I can tell you if it is sufficient.
During the class's final exam period, each group will present and demonstrate
their project for the class. In doing so you should include the following:
- The name of the project, and the name of your teammates
- The setting and loose plot of the game
- A demonstration of the game including starting the game, moving around, battling, getting items, etc.
Be sure to also demonstrate the types of items and the extra feature you chose to implement.
The presentation should take around 15 minutes or so.
Each team member will turn in an individual paper. The paper should include
- An introduction to the project
- The updated UML diagram for the design (this can be the same for everyone on the team)
- A discussion of this design. What aspects worked well? What could possibly be improved?
- Talk about how your group divided the work amongst yourselves. How did you work together?
- A discussion of the biggest challenges in working on this project.
The paper should be about two single-spaced pages (not including the diagram). The paper doesn't
need to refer to any sources.
To submit your program, email the GitHub link of your repository to email@example.com. In the email, include a
link to the site that is serving your Javadoc documentation.
Also submit your paper to me as a .pdf file
Ian Finlayson | Licensed under a Creative Commons Attribution 4.0 International License.