> 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/quests.md). # Quests & Tasks Villagers with problems, and a board that always wants something.
The quest journal
## Quests Twenty-four of them, written by hand, given by the nine villagers. Each one teaches a trade by needing something done. Rowan wants timber and gives you an axe. Wren wants a line in the water and gives you her old rod. Bram wants the pass cleared and gives you a pickaxe. Follow them. They are what opens the roads out of the valley, and they hand you nearly every tool you need on the way. Your quest progress is yours. Another player finishing one does not open anything for you. ## The Delivery Center
The delivery board
A board of standing orders at the town hall. There is nothing to accept and nothing to track. If you are carrying what one asks for, hand it over and get paid. It pays better than selling the same goods, and one order is always something a brand new farm can fill. The board refreshes, so there is always something new on it. --- # 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/quests.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.