> For the complete documentation index, see [llms.txt](https://raceonlife.gitbook.io/raceonlife/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://raceonlife.gitbook.io/raceonlife/additionally/partnerships.md). # Partnerships We are certainly planning to work hard on the development and updates of RaceOnLife over the next few years and are actively seeking supporters and developers who would like to join our team. If you too dream of becoming part of something truly new and innovative, join our community! In our game, we use the latest developments in blockchain and the newest version of Unreal Engine, which is perfect for our tropical island setting. Our goal is to show that NFT projects can be executed at the quality level of top AAA studios and still have real value for each player. By joining us, you will have the opportunity to become part of something big and be present in the place you rightfully deserve! --- # 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://raceonlife.gitbook.io/raceonlife/additionally/partnerships.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.