> For the complete documentation index, see [llms.txt](https://docs.hoppersgame.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hoppersgame.io/about/ownership-change/how-it-happened.md). # How it Happened The metapep team were discussing the history of Avalanche, the current state of it, and working to identify a way to lift up and potentially unite the community around something really positive. We knew that Hoppers had been discontinued but that many people still held them and had really loved that project. So, we reached out - through a mutual friend - to PM Studios to start a dialogue to see if they might be receptive to a new team taking over the project. From there, we scheduled a call to discuss our intentions and why we felt we were the right people for the job. After that, we submitted our intentions in writing, which was then accepted and the formal process of handing over the project began. metapep did not purchase this project from PM studios. They gave it to us because they believe - as do we - that we are the right people to lead Hoppers into the future. --- # 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.hoppersgame.io/about/ownership-change/how-it-happened.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.