> For the complete documentation index, see [llms.txt](https://hashguardians-2.gitbook.io/whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hashguardians-2.gitbook.io/whitepaper/directory/species.md). # Species There are eight unique HashGuardian species, each with its own level of rarity. In the final HashGuardians game, there will be different planets that HashGuardians can travel between, and each HashGuardian species will have its own home planet. When playing on their home planet, each species will have special abilities and receive a farming bonus multiplier. This will increase the player’s chance of earning NFTs as they complete quests and adventures. For example: Western Guardians will have an NFT farming bonus on the Western planet, while Fantasy Guardians will have an advantage on the Fantasy planet. This will be true of each species on their native planet. The NFT farming multiplier bonus for home planet species will be up to 8%. Beyond farming utility and the general collectability value of the species, HashGuardian NFTs also come equipped with unique early adopter weapons, shields, and gadgets. Rare species will often be equipped with rare items. **Along with the species trait, these rare items have special utility in the HashGuardians Universe.** --- # 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://hashguardians-2.gitbook.io/whitepaper/directory/species.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.