> For the complete documentation index, see [llms.txt](https://gilmour.online/compsci/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gilmour.online/compsci/2d-game-design/game-7-final-project.md).

# Game 6: Final Project

{% file src="/files/YCIONvO0vD2QowbILJgg" %}

Please turn in the planning sheet answers by filling them out in a google doc and sharing it with me or by handing a printed sheet to me at the start of class.

## Places to find sprite and tile assets

{% embed url="<https://www.gameart2d.com>" %}

{% embed url="<https://craftpix.net/freebies/>" %}

{% embed url="<https://opengameart.org/>" %}

{% embed url="<https://graphicriver.net/graphics-with-sprite-in-game-assets>" %}

## Assignment

#### All games need to:

* Have a strong theme or genre. (2 points)
* Run smoothly and as intended. (8 points)
* Have at least three animated multi-frame sprites. (3 points)
* Use 5 rooms (or utilize a procedurally generated room.) (5 points)
* Get progressively more difficult. (2 points)
* Be winnable and losable by the player. (2 points)
* Use variables to control aspects of dynamic game play (i.e.; parts of your game should change in some way throughout the game. Power-ups, Getting new inventory/ materials, or level gain are examples of this.) (3 points)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://gilmour.online/compsci/2d-game-design/game-7-final-project.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.