> For the complete documentation index, see [llms.txt](https://docs.launchboard.app/cxd/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.launchboard.app/cxd/video-game/project-challenge.md).

# Project Challenge

## How do we create video games that people want to play?

During this project, the entire class represents a video game company that will be divided into teams. Each team will design and develop its own video game concept. The teams will help improve each other’s games through feedback and playtesting.

At the conclusion of the project, all teams will present their video games at a public game convention.

![](https://728828027-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LDgX-RykK9XCDxfIhX_%2F-LDgX7Ifr9nc11ubI925%2F-LDgX8XE4TmFUR4fVhOX%2Fphaser.png?generation=1527608054460302\&alt=media)

## Design Constraints

* Browser-based game created using [Phaser JS game engine](http://phaser.io/)
* 2D game world
* Single player game (or multi-player game using single computer)
* Single level game (or single level of multi-level game)

## Design Criteria

* **Innovative**: Game is unique (could be unique remix of existing game concepts).
* **Engaging**: Game is fun and motivating to play (based on targeted gaming motivations).
* **Functional**: Game is functional and has no major problems (such as loopholes in rules that provide unintended advantage, dead ends that prevent player from progressing, etc.).
* **Usable**: Game provides clear feedback to player and is easy for new player to understand (such as learning game's controls, rules, objectives, etc.).
* **Balanced**: Game mechanics are fine-tuned to produce desired gameplay experience (such as balancing success vs. failure, risk vs. reward, skill vs. chance, etc.).

## Design Team Roles

Each team member will be a **Game Designer**, contributing to the ideas, decisions, and work related to the design of their team's game.

In addition, each team member will have at least one other specialized role:

* **Programming Lead**: leads programming of game
* **Art Lead**: leads creation of art and sound for game
* **Research Lead**: leads playtesting and marketing of game
* **Project Manager**: leads team to ensure work is high-quality and completed on time

The recommended team size is 2-4 people. Your teacher will determine how many people each team must have:

* **Teams of 2 people** need to have separate people acting as Programming Lead and Art Lead.  Each person will also take on one of the other remaining roles. It is recommended to have the Programming Lead also act as the Project Manager and to have the Art Lead also act as the Research Lead.
* **Teams of 3 people** need to have separate people acting as Programming Lead, Art Lead, and Research Lead.  One person will also act as the Project Manager. It is recommended to have the Research Lead also act as the Project Manager.
* **Teams of 4 people** will have separate people acting in each of the four roles.

Each team member is responsible for contributing meaningfully at all times to the team project. Each team member must be willing and able to help work on **any task at any time** when needed. One of the responsibilities of the Project Manager is to ensure the team is working and collaborating effectively.

**IMPORTANT:** Each lead person is responsible for planning and delegating the tasks for their speciality area. However, this does not mean that only one person completes that type of work. At certain times, multiple team members will be working together on the same task, while at other times, they may be working in parallel on different tasks.

## Final Team Deliverables

* **Video Game** that is published online and ready to play
* **Marketing Website** for game, which includes a gameplay demo video and a link to play game
* **Poster** for final presentation that highlights key features of game and key steps in creating game
* **Presentation** at public game convention to demonstrate game and explain how it was designed, built, and tested


---

# 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://docs.launchboard.app/cxd/video-game/project-challenge.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.
