Interactive Media & Game Development Worcester Polytechnic Institute	IMGD

Objective:	THIS PROJECT SHOULD BE DONE IN YOUR PROJECT TEAMS! In this project, you will add new game-play elements to the game "Jäger: The Hunt for Crazy Gert's Gold!" You will implement Ghoulie movement. You will implement a Heads-Up Display (HUD) showing the current state of Hedi. There are two parts to this project: a "Preparation" part, and a "New Stuff" part.
Preparation:	Create a code base from the ones you created for Project 2. You can either choose one person's code, or combine code from multiple team members.
New Stuff:	You will implement Ghoulie movement, during regular play, good-mushroom play, and bad-mushroom play. Read the original project description for what these mean. You will implement code to appease a given Ghoulie by hitting it with thrown jellybeans in the proper color sequence. You will implement code to have Ghoulies steal and redistribute gold when they collide with Hedi after the count down. You will create a user interface to display Hedi's state to the user. You need to include elements showing: Gold he is carrying, Mushroom time/type, Which RGB jellybeans you need to throw when a given Ghoulie appears, Status messages.
Attacking the Problem:	A good place to start looking for things is on the C4 wiki. Also, look at the Guide as a source info. Next, read through the C4 Forums on the things that you are stuck on. They know you are coming, so please post to the "Beginners" forum with your questions! Of course, read through older posts before submitting.
Documentation:	You must create adequate documentation, both internal and external, along with your project. The best way to produce internal documentation is by including inline comments. The preferred way to do this is to write the comments as you code. Get in the habit of writing comments as you type in your code. A good rule of thumb is that all code that does something non-trivial should have comments describing what you are doing. This is as much for others who might have to maintain your code, as for you (imagine you have to go back and maintain code you have not looked at for six months -- this WILL happen to you in the future!). I use these file and function (method) headers, in my code. Please adopt these (or the official CS ones) for all your projects. The file header should be used for both ".h" and ".cpp" (or ".c") files. Create external documentation for your program and submit it along with the project. The documentation does not have to be unnecessarily long, but should explain briefly how you altered the source files, and which art assets you created.
Submission:	All documents are to be submitted electronically via turnin by 11:59 pm on the day the assignment is due. Make sure to include a README file as well, listing the names of your team members, and a short description of what each person did. When you are ready to submit, zip everything up into a single archive file. Name the file LastnameFirstname_proj3.zip. You will use the new Web-based "Turnin" facility to submit your work. Information about submitting can be found here: http://web.cs.wpi.edu/~kfisler/turnin.html. Choose one of your team members to submit the document. Your WPI user ID should be used to login, and you should have been emailed a password. The Turnin assignment ID is proj3.
Academic Honesty:	Remember the policy on Academic Honesty: You may discuss the project with others, but you are to do your own work. The official WPI statement for Academic Honesty can be accessed HERE.