> For the complete documentation index, see [llms.txt](https://mytheria.gitbook.io/mytheria/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mytheria.gitbook.io/mytheria/pro-tips/2-color-deck-tips.md).

# 2-COLOR-DECK TIPS

### ![🔍](https://static.xx.fbcdn.net/images/emoji.php/v9/t1a/1.5/16/1f50d.png)SOME FACTS YOU NEED TO KNOW WHEN CREATING A DUO-COLOR-DECK IN MYTHERIA!

In this article,we would like to introduce a duo-color Custom Deck. A Duo-color Custom Deck shows player's creativity which it creates more diverse battles in the Mytheria world.

#### Pros and cons of the duo-color custom deck:

**Pros (+)**: A duo-color custom deck converges strong cards of two different colors.+ A duo-color custom deck creates a new style of play, which will make it harder for your opponent to predict your next moves.

**Cons (-):** You need to accumulate enough Shards to be able to summon cards of each color.

#### Steps to create a duo-color custom deck:&#x20;

First, you need to identify the "Main God" and the "Subsidiary God" of this custom deck.

The Main God will often need more accumulated Shards, so the amount Main God's card's color should be dominating in the duo-color custom deck.

You should only prioritize choosing cards that require 2 Shards for the Subsidiary God's card's color. Thus, players can optimize 2 skills of the Subsidiary God as well as ensure the Shards requirements for other summoned cards.


---

# 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://mytheria.gitbook.io/mytheria/pro-tips/2-color-deck-tips.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.
