> For the complete documentation index, see [llms.txt](https://docs.coherence.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coherence.io/0.10/developer-portal/manage-worlds.md).

# Worlds

![Managing Worlds in the Developer Portal](/files/QT0LvyhQQZXi73uTTRc0)

### Creating Worlds

Click the *New World* button at the top right of the *Worlds* view in the Developer Portal.

![The New World form](/files/fYaDmgL8Yx6Pwp2qNZ1P)

To create a World:

* Enter a unique name
* (optional) choose an SDK version. The latest version is recommended, but this should match the SDK version installed for your project
* Enter tags separated by commas
* Choose which region the World should be started in
* Choose the size of the Replicator
* (optional) Choose the schema this World should start with. Usually, the latest schema uploaded is the preferred choice, and this is the default.
* (optional) Adjust the packet frequencies for sending and receiving data. It can be adjusted per project and is part of the *Advanced Config* section. Note that the adjustment of frequencies is accessible only for paid plans.


---

# 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.coherence.io/0.10/developer-portal/manage-worlds.md?ask=<question>&goal=<endgoal>
```

`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.