Game Engines 2021W Project Guidelines - Revision history

Soma: /* Presentation */

2021-03-25T01:14:44Z

Presentation

← Older revision		Revision as of 01:14, 25 March 2021
Line 54:		Line 54:
	* 6 for challenges		* 6 for challenges
	* 2 for Godot perspective		* 2 for Godot perspective
	Your score in each category will be based on content and style, with more of an emphasis on content.		Your score in each category will be based on content and style, with more of an emphasis on content. Note the scoring should give you an idea of how to allocate your presentation time.

	==Final Report==		==Final Report==

Soma: /* Presentation */

2021-03-25T01:13:58Z

Presentation

← Older revision		Revision as of 01:13, 25 March 2021
Line 44:		Line 44:
	In these 10-15 minutes, you need to do the following:		In these 10-15 minutes, you need to do the following:
	* Describe at a high level what you built, and explain your motivations. Feel free to include information on your personal passions.		* Describe at a high level what you built, and explain your motivations. Feel free to include information on your personal passions.
	* Describe at least three technical challenges that you faced and explain how each was overcome. Be specific. Explain in the context of key Godot engine concepts. Consider using code excerpts.		* Describe at least three technical or design challenges that you faced and explain how each was overcome. Be specific. Explain in the context of key Godot engine concepts. Consider using code excerpts.
	* Give your perspective on Godot as a platform for implementing what you did. How did it support your work? How was it unhelpful? How did it get in the way? Make specific technical arguments please.		* Give your perspective on Godot as a platform for implementing what you did. How did it support your work? How was it unhelpful? How did it get in the way? Make specific technical arguments please.
	* If you have future plans to extend or modify what you did, please outline them.		* If you have future plans to extend or modify what you did, please outline them.
Line 52:		Line 52:
	Your presentation will be graded out of 10 as follows:		Your presentation will be graded out of 10 as follows:
	* 2 for description & motivation		* 2 for description & motivation
	* 6 for ~~technical~~ challenges		* 6 for challenges
	* 2 for Godot perspective		* 2 for Godot perspective
	Your score in each category will be based on content and style, with more of an emphasis on content.		Your score in each category will be based on content and style, with more of an emphasis on content.

Soma at 01:12, 25 March 2021

2021-03-25T01:12:55Z

← Older revision		Revision as of 01:12, 25 March 2021
Line 37:		Line 37:

	You may ask for no-penalty extensions.		You may ask for no-penalty extensions.

			==Presentation==

			You will have 10 minutes to present your game to the class. If you did your game with a partner, the two of your have 15 minutes to jointly present your work.

			In these 10-15 minutes, you need to do the following:
			* Describe at a high level what you built, and explain your motivations. Feel free to include information on your personal passions.
			* Describe at least three technical challenges that you faced and explain how each was overcome. Be specific. Explain in the context of key Godot engine concepts. Consider using code excerpts.
			* Give your perspective on Godot as a platform for implementing what you did. How did it support your work? How was it unhelpful? How did it get in the way? Make specific technical arguments please.
			* If you have future plans to extend or modify what you did, please outline them.

			For joint projects, you should each describe at least two technical challenges. Otherwise, your presentation may be as joint or as separate as you wish.

			Your presentation will be graded out of 10 as follows:
			* 2 for description & motivation
			* 6 for technical challenges
			* 2 for Godot perspective
			Your score in each category will be based on content and style, with more of an emphasis on content.

	==Final Report==		==Final Report==

Soma: /* Progress Report */

2021-03-04T14:42:37Z

Progress Report

← Older revision		Revision as of 14:42, 4 March 2021
Line 33:		Line 33:
	* This should be bringing together recent journal entries and organizing them, expanding them		* This should be bringing together recent journal entries and organizing them, expanding them
	** Maybe a lot of expansion if your progress reports have all been short		** Maybe a lot of expansion if your progress reports have all been short

			Grading will be based on the overall quality of the progress you've made versus the proposal.

			You may ask for no-penalty extensions.

	==Final Report==		==Final Report==

Soma: /* Progress Report */

2021-03-04T14:40:38Z

Progress Report

← Older revision		Revision as of 14:40, 4 March 2021
Line 31:		Line 31:
	** No need to repeat things from the proposal.		** No need to repeat things from the proposal.
	** However, you may want to present revised parts of your proposal if your plans have changed		** However, you may want to present revised parts of your proposal if your plans have changed
			* This should be bringing together recent journal entries and organizing them, expanding them
			** Maybe a lot of expansion if your progress reports have all been short

	==Final Report==		==Final Report==

Soma: /* Progress Report */

2021-03-04T14:39:49Z

Progress Report

← Older revision		Revision as of 14:39, 4 March 2021
Line 29:		Line 29:
	* Explain how your progress compares to what you originally proposed.		* Explain how your progress compares to what you originally proposed.
	* Provide drafts of what you can for the final report.		* Provide drafts of what you can for the final report.
			** No need to repeat things from the proposal.
			** However, you may want to present revised parts of your proposal if your plans have changed

	==Final Report==		==Final Report==

Soma at 14:38, 4 March 2021

2021-03-04T14:38:22Z

← Older revision		Revision as of 14:38, 4 March 2021
Line 35:		Line 35:

	* Introduction/Overview		* Introduction/Overview
			** what did you do?
	* Inspirations/Background		* Inspirations/Background
			** What led to what you did?
			** inspiring games, articles, daydreams, whatever
			** make sure to cite inspirations where feasible
	* Design		* Design
			** high-level description of what you built
	* Implementation		* Implementation
			** details, how it exists in Godot
			** ideally explain object hierarchies & scenes, code structure
			** enough detail that someone who looks at your code will have a basic idea of what is going on, how to find bits they are interested in
			** if chunks of your implementation came from outside sources, just give a high level summary of it and cite the source
	* Iteration/Evaluation		* Iteration/Evaluation
			** organize what you wrote in your journal, what was the process?
			** how close did you get to what you wanted to do?
			** what are the major issues remaining?
			** report on any playtesting or other testing you did
			** cite resources that helped you along the way
	* Lessons Learned		* Lessons Learned
			** what do you know now that you didn't know at the start of the term?
	* Conclusion		* Conclusion

Soma at 13:20, 4 March 2021

2021-03-04T13:20:43Z

← Older revision		Revision as of 13:20, 4 March 2021
Line 23:		Line 23:

	Note that part of technical scope is whether what you propose is doable within the time you have. So, if you propose something very ambitious you should have a lot of preliminary work completed.		Note that part of technical scope is whether what you propose is doable within the time you have. So, if you propose something very ambitious you should have a lot of preliminary work completed.

			==Progress Report==

			* Discuss what you've done since the proposal.
			* Explain how your progress compares to what you originally proposed.
			* Provide drafts of what you can for the final report.

			==Final Report==

			Your report should have the following sections:

			* Introduction/Overview
			* Inspirations/Background
			* Design
			* Implementation
			* Iteration/Evaluation
			* Lessons Learned
			* Conclusion

			Grading will be based on:
			* 30% Writing & presentation quality (organization, grammar, flow)
			* 30% Technical scope
			* 20% Creativity
			* 20% Evaluation/Process

			Again, the weighing may be changed.

Soma: Created page with "This page contains guidelines on the class project. This page will be updated based on questions and feedback. ==Project Proposal== Your project proposal should be a relati..."

2021-01-26T01:29:35Z

Created page with "This page contains guidelines on the class project. This page will be updated based on questions and feedback. ==Project Proposal== Your project proposal should be a relati..."

New page

This page contains guidelines on the class project. This page will be updated based on questions and feedback.

==Project Proposal==

Your project proposal should be a relatively short document describing what you plan to do for your project. You should propose to make an original game, mechanics demonstration, or engine extension/modification.

Your proposal should:
* Have a title and your name
* List collaborators and explain how the collaboration will work
* Explain your motivation for what you are doing
* Describe what you plan to do
* Present what preliminary work you've done
* Outline your development plan, including milestones and dates
** Be sure to include what you hope to have done by the preliminary report
** Leave enough time to write your final report

Your proposal will be graded based on the following criteria:
* 40% Writing & presentation quality (organization, grammar, flow)
* 40% Technical scope
* 20% Creativity

I may change the relative weights of the categories, but only if it results in a better grade (i.e., a project that is really creative but not so technically demanding might get 40% creativity, 20% technical scope).

Note that part of technical scope is whether what you propose is doable within the time you have. So, if you propose something very ambitious you should have a lot of preliminary work completed.