> For the complete documentation index, see [llms.txt](https://know.atrollcity.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://know.atrollcity.com/of-games/lets-play/trollet-dash.md).

# Trollet Dash

## Description

Players choose a battle deck of 1 Avatar + 5 Trollets to for a race against another.&#x20;

The race track is broken up into 5 sections at random. Each section can be a Fire, Water or Earth track.  The element of the trollet determines how fast they complete that section.\
For example, \
🍍 A Fire trollet on a Water track runs 50% slower\
🍍 A Fire trollet on a Eater track runs 50% faster\
🍍 A fire trollet on a Fire track runs at normal speed\
\
Each game is no more than 2-minutes and is fully auto-battled once the lineup is set.&#x20;

#### Winning Conditions

Who ever completes the race first wins.

#### Entry Fee

5000 PINES.

#### **Win Rewards**

8000 Pines.


---

# 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://know.atrollcity.com/of-games/lets-play/trollet-dash.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.
