> 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/technical-overview.md).
# Technical Overview
High-level 101
The Otherside Development Kit (or ODK) is a platform built for the Yuga community to build and share experiences within the Otherside community.
The ODK is built on top of the World Builder platform. World Builder documentation is available [here](https://docs.otherside.xyz/platform-documentation/). The World Builder is built on top of a Blueprint only version of Epic's Unreal Engine, and is architected to allow quick iteration on content, while also providing unparalleled player number and quick and easy travel between worlds.
It's highly recommend that if you intend to develop for the ODK that you familiarize yourself with the basics of the World Builder platform. In particular, sections that are useful to read are:
* [Morpheus networking](https://docs.otherside.xyz/platform-documentation/creation/unreal-development/getting-started/networking)
* [Difference from native Unreal](https://docs.otherside.xyz/platform-documentation/creation/unreal-development/getting-started/differences-in-unreal-development-workflow)
* [Actor pooling](https://docs.otherside.xyz/platform-documentation/creation/unreal-development/features-and-tutorials/actor-pooling)
The ODK also provides a host of Otherside related content built on top of the World Builder. The majority of the functionality is provided within [ODK plugin](/odk-docs/odk-plugin.md), which is located within the engine plugins of your ODK Unreal installation
ODK Plugin Content
Please peruse the provided content, and use the [Template Projects](/odk-docs/odk-templates.md) as means to explore what's available within the ODK.
---
# 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/technical-overview.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.
