> For the complete documentation index, see [llms.txt](https://docs.obsiverse.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.obsiverse.net/welcome.md).

# Welcome!

Welcome to the official Obsiverse documentation. Here, you’ll find all the information we believe you may need to have the best possible experience while playing on our server!

**What is Obsiverse?**

Obsiverse is a Minecraft server focused on offering players a custom and improved experience, while still keeping the vanilla essence of Minecraft.

That said, in the near future, we plan to expand the number of game modes available on the server, allowing us to offer players even more variety, gameplay, and content.

Most likely, these future game modes will be chosen mainly by our community members through our official [DISCORD](https://discord.gg/obsiverse), so don’t hesitate to join it.

With that being said, if you feel like playing on our server, feel free to join using our official IP:

For Java: **play.obsiverse.net**

For Bedrock: **bedrock.obsiverse.net**\
Port: **19132**


---

# 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.obsiverse.net/welcome.md?ask=<question>&goal=<user_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.