CSCI 4070/6070 Game Programming

Final Exam Project Chronologies in 3D

http://en.wikipedia.org/wiki/Sequel#Chronologies

Creating chronologies of the original story are important in video game industry and serves as inspiration for the final exam.

The key idea of the final exam is the create a chronology of the previously assigned 2D project but now in 3D. Your project needs to be either a
(1) prequel,
(2) a sidequel, or parallel adaptation,
(3) a sequel, or
(4) a reboot or remake of a game of a project from project 2.
Be sure to look at the grade criteria and list of requirements below for more details.

Theme

Use a similar story line that you used in P2 (similar: prequel, sidequel, sequel, or a new adaptation, a reboot). Recall, in project 2 you immerse an image of yourself into the story line, but now you will implement the game as chronology in Unity.

Prequel: events precede those of the original story. Example: Star wars Prequel Trilogy.
Sidequel/Parallel Story: Focuses on different characters of the original story (in a similar or different setting).
Sequel: Events of the second work to directly follow the events of the first.
Reboot/Remake: A reboot is a retelling or new envisioning of a story.

Theme - Group of two

Group of two - you will need to merge your characters/themes into one cohesive game.

Group of two projects must demonstrate double effort (e.g., need to have multiple blender or Maya assets instead of a single object).

In the last HW were you create a design document for this project, make sure you list the division of tasks and also 1 or 2 milestones. In the final report reflect again on the division of labor.

Collaboration Policy - Read carefully you must work on this project individually (or in a group of 2), you may discuss this assignment with other students in the class and ask and provide help in useful ways, preferable over our email list so we can all benefit from your great ideas. You may consult (but not copy) any outside resources you including books, papers, web sites and people. If you use resources other than the class materials, indicate / cite what you used along with your answer.

Due Date & Demo

Day of Final: See schedule page. Final Submission. Your submission should include a video link of you demoing the project. You should explicitly denote you fulfilled the grade criteria outlined below in the video. The link to the video may be set to private. (email both the instructor and TA).

 

Objectives & Requirement

Your minimal requirements are 75 pts worth. Your submission must look different from project 4 (book tutorial).

Submission:

Video: YouTube Video demonstrating your game.

Code/Scripts: Game code, scripts submitted to nike.

Unity Web Player: Game code, and game packaged into Unity Web Player (baked) and available an online link.

(for the below you may change the extension .txt if not plain text e.g., .doc, .pdf)

GRADING.txt: A description on how you met the grading rubric (see below table). You may copy paste these from REPORT.txt. This is where you 'argue' you met the criteria (note each requirment met must be well crafted, and hand-crafted).

REPORT.txt (or .pdf or .doc) should include minimally:
A description of what you did, how it works, screenshots and discussion on results.

README.txt should include a list of files required to run your game, and how to get your code up and running.

As usual, if you do use any assets/anything that is not your own work or you have generate from the plain unity engine, or blender - you must cite those resources.

Grading Rubrics

Scores are amenable to quality of work (or well craftiness).

Requirements	Example / Required Features	Score/Points
Sprite, Main Player Dynamics	Falling (2), Jumping (4), Swimming (2), Flying (4), Climbing (4), and Swinging (4)	20
Friendly Sprites	Helps you (works well in Game)	5
Enemy Sprites	Static and Dynamic (works well in Game)	5
3 Types of Attack	3 for each attach, 1 pt for running well together.	10
Player Attributes	Number of lives, health attributes, look & feel (inventory in Unity)	10
Chronology to Original Game	Nice follow up on to the original 2D Game that you are following.	5
Uniqueness	No overlap with Survival Island, your game must be different from the Tutorial.	5
Documentation / Files	Readme file, grading.txt that describes how you fulfilled the rubrics, Grading,txt, Report,txt, Screenshots	5
Video	Video Quality: Video Highlighting of Features of the Game	5
3D Art Work	A Character in Game with player dynamics that you designed on your own.	5
Baseline subtotal	(note - each requirement met must be well crafted).	75
Embellishments	25 Points are Required
Path Planning	Use of A Star (see Arongranbergs Solution) (script/code must be submitted to your class grader account for credit).	10
Flocking Behavior	Include a Flock of Enemies (example) Can't be just simple gathering, or following the main player (script must be submitted to your class grader account for credit).	10
Inside/Outside	Create both "Inside" and "Outside" Environments (more extensive that inside the 'hut' in survival island).	10
Time Lapse	Include Dawn, Sunrise, Day, Sunset, Dusk, Night periodically	10
Proposal	You propose your own feature, need to be at the level of complexity (or effort) as above embellishments.	5-10
Level	Different Levels. Clear Distinct level.	10
		10
	Max (before deductions): Exam will be graded out of a 100	110/100
Deductions
Not Present at Final	Not Present at Final.	-50
Audience Requirements	Arriving more than 15 min late, or leaving more than 15 min before last person presents their project.	-30
No Video Link	No video or link demoing the features of your game	-30
**Web Player	Non Working Web Player (b/c we can't grade your projects without one). We may accept an alternate way of a 'player', we are open for suggestions on this.	-30