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

# information

## Welcome to Eternal Docs.

[**Eternal**](https://eternal-std.ru/) is a Minecraft development studio. We create high-quality, minimalistic, and ready-to-use server builds. Here you will find all the necessary documentation, installation guides and answers to questions.

## Notice.

{% hint style="info" %}

#### Prohibition of distribution.

We prohibit any illegal distribution of our goods - resale, exchange of goods, publication in the public domain or an attempt to profit from the sale of our goods. If such actions are detected, we will revoke your access to our products and terminate support.

In case of violation of the user agreement between the Customer and the Studio, we reserve the right to refuse further service.
{% endhint %}


---

# 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.eternal-std.ru/information.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.