> For the complete documentation index, see [llms.txt](https://penguin-wars.gitbook.io/penguin-wars/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://penguin-wars.gitbook.io/penguin-wars/token-economy/token-utility.md).

# Token Utility

$ICED can be used to make in-game purchases such as a wide range of cosmetics ranging from penguin skins to custom UIs and HUDs, taunts and celebrations, sound effects, stickers, profile frames, emotes, arenas, and more. These purchases and assets are purely cosmetic, and do not affect or disbalance the gameplay in a tangible way.

Numerous different boosts and power-ups are also available via the in-game store to enhance earnings and empower players’ penguins. While some of these multipliers apply to PvP games, they’re tuned to affect rewards first, single-player performance second, and most importantly, to prevent affecting the outcomes of PvP games to a Pay-to-Win scenario.

Tournaments are the most straightforward way to win large amounts of $ICED, however, the aforementioned rewards need to come from somewhere. Thus, as both a means of funding tournaments and as a means of expanding $ICED’s utility, $ICED is the currency with which tournament entries are ensured.

Various factors bring players together within their clans, but loyalty and contribution are often expressed through a fundamental asset: $ICED. This asset is necessary for upgrading clans, purchasing clan-related power-ups and cosmetics, and entering clan-based competitions. Contributions from individual members will also be tracked, ensuring that dedicated players receive recognition, while those who do not contribute are identified.

<br>


---

# 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://penguin-wars.gitbook.io/penguin-wars/token-economy/token-utility.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.