> For the complete documentation index, see [llms.txt](https://rules.gatcg.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://rules.gatcg.com/general-rules/general-rules-parts-of-a-card/parts-of-a-card-element.md).

# Parts of a Card - Element

General Rules:

1. All cards have an element denoted in the top right of the card.
   1. If a card or object is not specified to have an element, it is Norm by default.
2. The element specified on the card must be enabled for a player for that player to play that card.
   1. The norm element is unlocked innately for all players.
   2. Champion cards are not bound by element restrictions when materializing.
3. Non-norm elements are unlocked innately depending on the elements of champion cards within the lineage (see [Lineage](/glossary/game-terms.md#lineage-term)); non-champion cards do not unlock elements.

{% hint style="success" %}
E.g., A player has a lineage containing a Spirit of Water, norm champions, and an arcane champion; that player may play or activate norm, water, and arcane cards.
{% endhint %}

{% hint style="success" %}
E.g. a player may materialize a Level 3 champion with the crux element type without previously having the crux element enabled as long as the other rules for leveling up that champion are followed.
{% endhint %}

4. Basic elements are Fire, Water, and Wind elements; Advanced elements are any elements that are not Fire, Water, Wind, or Norm. Exalted is a [special advanced element](/game-mechanics/game-mechanics-special-elements.md) that is unlocked by default as long as you have a champion that enables another advanced element.


---

# 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://rules.gatcg.com/general-rules/general-rules-parts-of-a-card/parts-of-a-card-element.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.