> For the complete documentation index, see [llms.txt](https://docs.bloomshire.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bloomshire.xyz/playing/character.md). # Your Character Two bodies, six colours, and no hats.
The character creator
Pick a body and colour your skin, hair, eyes, shirt, trousers and shoes. There are no hats and no armour. Your farmer is one character animated properly in every direction, swinging every tool, rather than a stack of clothing layers. The tool you carry is drawn in its own colours, so an upgrade shows in your hands as well as in your bag. The villagers are built exactly the same way. ## Founding Farmers look different The planned [Founding Farmers](/nfts-and-token/founding-farmers.md) collection is the one place with real hats, hairstyles and accessories. Those farmers are fixed: their look comes with them and cannot be recoloured. None of that is live yet. --- # 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://docs.bloomshire.xyz/playing/character.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.