> For the complete documentation index, see [llms.txt](https://docs.otherside.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.otherside.xyz/odk-docs/readme/getting-setup-with-odk-development.md). # Getting setup with ODK development Quick-start guide on how to download the ODK and start developing! Access the[ Dashboard](https://otherside.m2worlds.io/dashboard?download\&project=open-roses-send-489062) download page and click "Install the Launcher". 1. The ODK Launcher should open and start downloading the ODK. 2. When the download is complete, the template selection window should open with the option to load an existing project or create a new project from the ODK template:

3. If this is your first time developing for the ODK, we recommend you use the "ODK Boneyard Template" as the starting template. Click on the template to create a project from it 4. Give your project a name, and click "Create New Project". The template will download and open automatically.

5. Once open, you're able to use Play-in-Editor to test and develop your experiences! ### Creating an online world It only takes a quick few steps to create a deployment from your project content that others can join. 1. Click the "Upload Content" button within the editor dashboard

2. Give your world a description, and ensure that the `Boneyard` map is selected. Then click the "Upload" button

3. Your project will then be cooked, packaged and uploaded to the Otherside dashboard. In future uploads, this process will be quicker as not all content will need to be recooked. Once complete, click the "View upload in dashboard" button

4. That will take you to the ODK dashboard, which will display your world's uploads. You can then click "Launch World" to create a deployment from your uploaded content, and share that with others to join

--- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.otherside.xyz/odk-docs/readme/getting-setup-with-odk-development.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.