Catch a Dragonfly
The goal of this project is to get used to Dragonfly, a text-based game engine. You will work through a tutorial that has you make a simple game using Dragonfly. This will help better understand a game engine by developing a game from a game programmer's perspective, providing the foundational knowledge needed for building your own Dragonfly game engine (project 2) and designing and developing your own game from scratch with it (project 3).
You will work alone for this project (and the next one). This will ensure you have the development skills needed even if your tasks in project 3 (making your own game) are more partitioned. While you can discuss the project with other students and even help each other debug code, you must write all code yourself.
The assignments is to:
Your assignment is to be submitted electronically via turnin by 11:59pm on the day due. You must hand in the following:
|Tutorial||40%||Doing the tutorial without any additional customization is worth about 1/2 the grade. While you will have learned a substantial amount about the Dragonfly game engine, you will not have demonstrated an in-depth understanding of the principles.|
|Customization||50%||Extending or modifying the tutorial game with custom work is worth 1/2 the grade. Doing so will begin to flex your technical muscles and show mastery of the basic concepts of the Dragonfly game engine. This is essential in moving forward.|
|Documentation||10%||Not to be overlooked is including the documentation provided and having that documentation be clear, readable and pertinent to the assignment. This includes the README described above as well as the GAME document. Having well-structured and commented code is part of Documentation, too. Getting in the habit of good documentation is important for large software projects, especially when done in teams (project 3).|
Below is a general grading rubric:
100-90. The submission clearly exceeds requirements. The tutorial game works without problems. The custom extensions exhibit an unusually high degree of effort, thoughtfulness, technical ability and insight. Documentation is thorough and clear.
89-80. The submission meets requirements. The tutorial game works without problems. The custom extensions exhibit substantial effort, thoughtfulness, technical ability and/or insight. Documentation is adequate.
79-70. The submission barely meets requirements. The tutorial game may operate erratically. The custom extensions exhibit marginal effort, thoughfulness, creativity and/or insight. Documentation is missing details needed to understand the contributions and/or to build the programs.
69-60. The project fails to meet requirements in some places. The tutorial game may crash occasionally. The custom extensions are of minor scope, or exhibit perfunctory effort, thoughfulness, technical ability and/or insight. Documentation is inadequate, missing key details needed to understand the contributions and/or to build the programs.
59-0. The project does not meet requirements. The tutorial game crashes consistently. The custom extensions exhibit little or no evidence of effort, thoughfulness, technical ability and/or insight. Documentation is woefully inadequate or missing.