> For the complete documentation index, see [llms.txt](https://doc.archloot.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.archloot.com/gameplay/parts.md). # Parts Monster parts, which are all NFTs, come in five kinds: torso, head, upper limb, lower limb, and accessory. The torso is essential, and the rest are simply attached. You can stretch, scale, and place these parts anywhere on the torso in the evolution interface, and can edit your monsters anytime. Parts of monsters are divided into four levels according to their rarity — **common, rare, epic, and legendary** — corresponding to 1, 2, 3, and 4 attributes respectively. Some of these parts also have separate special skills. ### **Strengthening** Players can strengthen monster parts and improve their attribute values by consuming corresponding materials. (For epic and legendary parts, you need to consume parts of the same level to strengthen.) ### Recombination Players can genetically recombine monster parts to increase the rarity of parts from common to rare, and also to add an additional attribute. ### Special skills Some parts have special skills in addition to their basic attributes. Each monster can have any number of skills through parts, but you can only choose to activate up to three of them during battle. You can freely combine skills and match your own attributes to win battles. The parts can be attached as rewards from purchasing hunting licenses, and also be acquired through direct purchase from the marketplace, and dungeon quests. --- # 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://doc.archloot.com/gameplay/parts.md?ask=&goal= ``` `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.