> For the complete documentation index, see [llms.txt](https://bountytemple.gitbook.io/whitepaper-v1/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bountytemple.gitbook.io/whitepaper-v1/gameplay/guild-wars/culture-points.md).

# Culture Points

## What are Culture Points?

Culture Points (CP) is a system tied to a player's personal account, and will directly affect a player's GIA earning capabilities. A player can have Culture Points ranging from 1 to 10.

* **Above 5 CP:** Good
* **5 CP and below:** Bad

When a player has a "Bad" CP rating, they will experience a lower GIA minting rate, thus affecting their earning capabilities. Players with a "Good" CP rating will enjoy regular minting rates.

## How to earn Culture Points?

Players can earn Culture Points in a number of ways, including:

* **Joining events with no spend:** 0.5 CP
* **Spending a designated amount of GIA:** 2 CP
* **Burning a designated amount of GIA:** 2 CP

Culture Points reset every 2 weeks, therefore it is important for players to stay active and continue earning CP to maintain a "Good" CP rating.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://bountytemple.gitbook.io/whitepaper-v1/gameplay/guild-wars/culture-points.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.