> 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-outline/1-1-determine-gamer-motivation-profile.md).

# 1-1 Determine Gamer Motivation Profile

## What types of video games do you like to play?

Just as people like different types of books or movies, people like different types of video games. If you're going to design a video game, you'll need to know more about what motivates people to play certain games.

You'll start by taking a survey to determine your own Gamer Motivation Profile. Later in the project, each team will decide what gamer motivations their game will target.

[Quantic Foundry](http://quanticfoundry.com/) is a game analytics consulting company that has gathered data from over 300,000 video game players to construct a scientific model that describes different types of gamer motivations.

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

This model identified 12 motivations that clustered into 6 pair groups: Action, Social, Mastery, Achievement, Immersion, and Creativity. For example, *Challenge* and *Strategy* are motivations that belong to the *Mastery* group.

**VIDEO:** This gamer motivation model was constructed using a statistical method called factor analysis. If you're interested, Quantic Foundry has a [video explaining how this model was built](https://www.youtube.com/embed/YZwiQd-0xqQ?start=0\&end=380) using survey data collected from thousands of video game players.

## YOUR TASK

1. [Take the online survey](https://apps.quanticfoundry.com/surveys/start/gamerprofile/) to determine your Gamer Motivation Profile. The survey takes about 5-7 minutes.
2. Record your results in [this assignment document](https://drive.google.com/open?id=1QtWFyRvM4sgI5W1iHRpx-60IMaf7P4drH122iJjbMoc).
3. Discuss and compare your results with others in the class.

## Assignment Templates

Some of the assignments in this project guidebook include links to Google Drive templates (document, spreadsheet, slide presentation, drawing, etc.). All the templates are shared as "**View Only**." Students must create a **copy** of the template in order to modify it. (Students should **not** request edit access, as the file is a master template for all students.)

{% hint style="info" %}
**MAKE A COPY:** To use a Google template, be sure you're logged in to your Google Account. From the **File** menu of the template, select **Make a copy**. Save the copy to your shared team folder in Google Drive. The copied file can now be modified.
{% endhint %}


---

# 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-outline/1-1-determine-gamer-motivation-profile.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.