> For the complete documentation index, see [llms.txt](https://wiki.metados.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.metados.com/economy/cosmetics-collectibles.md). # Cosmetics Collectibles MetaDOS Cosmetics are items that can be acquired to further customize the player's experience. Cosmetics are items that can be acquired to further customize the player's experience. As the name suggests, these items are entirely cosmetic and do not grant any competitive advantage. They can be acquired through the use of various types of currency. ## Form of Collectibles Collectibles can be acquired through the Battle Pass or bought in the In-Game Store using the various in-game currencies. ## Types of Cosmetics ### Skin

Skins change the appearance of or the **weapons** the skin has been assigned to. Up to eight skins can be equipped for each Legend and weapon, which cycle through every time the player connects to the Lobby. ### Takedowns Takedowns change the way a Hunter can kill an enemy while the latter is Knockdown. Only one Takedown can be equipped at any given time. ### Skydive

Skydive Emotes are short animations a Hunter can perform, either to show off to squadmates or to taunt enemies, during a match. However, they can only be played while dropping into the arena. They can be equipped to their own Skydive Emote Wheel, and up to eight of them can be equipped at the same time. ### Emotes --- # 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.metados.com/economy/cosmetics-collectibles.md?ask=&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.