> For the complete documentation index, see [llms.txt](https://docs.lumiterra.net/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lumiterra.net/docs/the-economics/specialty/farming.md). # Farming

Each player has their own farm (of course, you can invite other players to farm with you! ) , where they can grow crops and feed monsters. Players can plant seeds, water and fertilize them, and wait for a certain amount of time to obtain the corresponding crops. These crops are the basic materials for many craft items. Seeds can be obtained by collecting resources or defeating monsters in the open world. The game has a wide variety of crops, and there are also many factors that affect their growth, such as the Agricultural Specialty Skill, fertilizers, and weather etc.

Monsters in the open world can be captured, but there are certain conditions to meet, such as learning the capturing skill and consuming items from the player's backpack. Each monster has different preferred items, and capturing them also requires the player's skill. The output of different monsters varies, and these outputs also have unique uses. --- # 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.lumiterra.net/docs/the-economics/specialty/farming.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.