> For the complete documentation index, see [llms.txt](https://docs.dreamlandgenesis.com/dreamland/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dreamlandgenesis.com/dreamland/dreamland-utility/dreamland-partners/ghost-town-showdown.md).

# Ghost Town Showdown

                                                

![](/files/iWfNvxytx3NsEa5d2gdT)

Ghost Town Showdown combines the meticulous planning of a deck builder with the real-time tactical decision making of a battlefield strategy game. Cast powerful spells from your folio and command your Wranglers to disable the opposing Marshal. The objective is simple: take down your opponent's Marshal before they take down yours.

* All 10K dreamers will be integrated into the GTS game, thus allowing holders entry into their ecosystem free of charge! Community held events within GTS will be prevalent in their game as well whereby dreamers can go against other projects in a tournament.


---

# 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.dreamlandgenesis.com/dreamland/dreamland-utility/dreamland-partners/ghost-town-showdown.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.