> For the complete documentation index, see [llms.txt](https://wiki.gamee.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.gamee.com/gameplay/gamee-arc8-faqs/token-takeovers-and-partner-events.md).

# Token Takeovers and Partner Events

## What are Token Takeovers?

Token Takeovers are events where players can earn tokens in Arc8 by entering [Lucky Events](https://wiki.gamee.com/gameplay/gamee-arc8-faqs/luck-mining-and-lucky-events.md) sponsored by partners.

Players can also earn partner tokens by competing in the [Arc8 League](https://wiki.gamee.com/gameplay/gamee-arc8-faqs/arc8-league.md).

## What Token Takeovers have appeared in Arc8?

Every season introduces a new range of partner tokens in Lucky Events. \
\
Prior to the introduction of Lucky Events in June 2023, the following partner tokens were given away as rewards in Arc8:

* [TOWER](https://crazydefenseheroes.com/)
* [QUICK](https://quickswap.exchange/#/)
* [REVV](https://revvmotorsport.com/)
* [SAND](https://www.sandbox.game/en/about/sand/)
* [SPORT](https://lympo.io/)
* [MATIC](https://polygon.technology/)
* [QUIDD](https://www.quiddtoken.com/)
* [TCP](https://www.thecryptoprophecies.com/token)
* [MSU](https://metasoccer.com/)
* [ICE](https://ice.decentral.games/welcome/master)
* [IXT](https://planetix.com)

## What games have been made in partnership with other brands?

We have made games in partnership with:

* [Cool Cats](https://coolcatsnft.com)
* [Manchester City Football Club](https://www.mancity.com)&#x20;
* [ATARI](https://atari.com)
* [Mocaverse](https://www.mocaverse.xyz)

## What other partnerships has Arc8 had?

We have had other partnerships with:

* [Benji Bananas](https://benjibananas.com)
* [BoomLand](https://www.boomland.io)

## What are the upcoming Token Takeovers or Partner events?

New Token Takeovers and events are announced on the [GAMEE Medium](https://gamee.medium.com) page.&#x20;

Note that partner tokens can be [withdrawn](https://wiki.gamee.com/gameplay/gamee-arc8-faqs/wallets.md) to the player's personal wallet in the same way as [GMEE](https://wiki.gamee.com/whitepaper/gmee-token.md).

{% hint style="info" %}
**Disclaimer:**\
The content of this page is meant for general information purposes only. It is not to be construed as an invitation, inducement, recommendation, offer or solicitation to purchase or sell any crypto. The services and crypto described on this page are not available to users of, and this communication is not intended to be acted upon by users in, certain jurisdictions, including US, UK and sanctioned countries. GAMEE reserves the right to adopt technological solutions, including geo-blocking and KYC, to restrict access for users from restricted jurisdictions.
{% endhint %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://wiki.gamee.com/gameplay/gamee-arc8-faqs/token-takeovers-and-partner-events.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
