> For the complete documentation index, see [llms.txt](https://docs.pxlz.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pxlz.org/pxl-wars/skirmishes.md).

# Skirmishes

![](/files/GqUYArpoqKyNHYcHhkmR)

**PXL Skirmishes** are meant to help players test out strategies and practice their PvP skills without spending any ADA on forging. As a consequence, rewards for winning Skirmish battles will not be paid out in ADA but in **Skirmish Tickets**.

The Skirmishes provide a free entry point into the PXL Wars game for users who want to have a taste before fully committing.

{% hint style="info" %}
**PXL Skirmishes** is the free to play version of PXL Wars.
{% endhint %}

Skirmishes will require the user to spend Skirmish Tickets in order to participate but don’t worry! A bunch of these tickets are given for free upon creating a new account and are also purchasable from the in-game shop by using $DING.


---

# 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://docs.pxlz.org/pxl-wars/skirmishes.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.