> For the complete documentation index, see [llms.txt](https://plantmaster.gitbook.io/plantmaster-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://plantmaster.gitbook.io/plantmaster-whitepaper/appendices/disclaimer.md). # Disclaimer *PlantMaster is a Gamefi that utilizes blockchain technology to create a unique gaming experience. While playing PlantMaster can be a fun and exciting way to engage with the blockchain ecosystem, it is important to understand that participating in the game comes with inherent risks.* *Firstly, players should be aware that the value of in-game assets, such as NFTs or other tokens, can be volatile and subject to sudden changes. Players should only invest what they can afford to lose and undertake their own research before making any decisions.* *Secondly, PlantMaster is a decentralized game, which means that there is no central authority or institution controlling the market or providing guarantees. This means that players face risks such as hacking, fraud, and other malicious activities. Players should take appropriate measures to secure their accounts and only use reputable platforms and services.* *Finally, the regulatory landscape of blockchain gaming is still evolving, and laws and regulations vary across jurisdictions. Players should be aware of the legal and regulatory framework applicable to their activities and seek professional advice if necessary.* *In summary, PlantMaster offers a unique and exciting gaming experience, but it is important for players to understand the risks and uncertainties involved and make informed decisions based on their individual circumstances.* --- # 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://plantmaster.gitbook.io/plantmaster-whitepaper/appendices/disclaimer.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.