|Interactive Media & Game Development
Worcester Polytechnic Institute
|Objective:||THIS PROJECT SHOULD BE DONE IN TEAMS OF TWO!
In this project, you will learn how to generate a labyrinth structure for use in the game "Jäger: The Hunt for Crazy Gert's Gold!"
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.
The aim of this preparation part is for you to get your feet wet in the Jaeger development framework, as
well as with C4.
You will download the Jaeger codebase, compile it on your system, and then execute it to see how it works.
Download the ZIP file from the "File Releases" tab of appropriate project on the WPI SourceForge Web site for this course. Copy it to the directory where you will be doing your work, and unzip it. There will be a whole source tree, with accompanying project files for building using visual studio.
Once you have built your code, run it, and press the tilde/grave key to bring up the command console. Then type "default" to launch Jaeger with a simple labyrinth. Hit tilde/grave again to dismiss the command console, and then hit the ESC key to allow movement.
Use the WASD keys to move around the default labyrinth, and the mouse to look around.
|This problem has less to do with C4 and more to do with coming up with a "good"
algorithm to generate a proper labyrinth. So, independent of C4, you should be able to come up with
code to do this. Start by looking at
A great place to start getting up to speed on the C4 stuff is on the C4 wiki. Start with something small, like the "Hello World" tutorial, and work up from there. 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.
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.
You will use the new Web-based "Turnin" facility to submit your work. Information about submitting can be found here:
Choose one of your team members to submit the document.
Your WPI user ID should be used to login, and you should be mailed emailed a password real soon now...
|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.|