> For the complete documentation index, see [llms.txt](https://27rogi.gitbook.io/server-toolbox/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://27rogi.gitbook.io/server-toolbox/master.md).

# Introduction

Welcome to the Server Toolbox documentation.

Let's start from the purpose of this mod: It was developed with expandability in mind and to give server admins with players more advanced commands (and more) that are mostly present in plugins, but not on Fabric.

{% hint style="warning" %}
This project is still in early stages of coding and some features are not tested completely, but you can help me with that by using this mod and reporting issues! :heart:
{% endhint %}

### Requirements

* Fabric API
* LuckPerms (optional, yet recommended)

### Used Libraries

It's too uneffective to write many lines of boilerplate code, so I'm trying to use libraries to make development easier and less overcomplicated\~\~*, also because I'm lazy.*\~\~ There are few awesome libraries used in this mod:

| Name                    |    Authors    |
| ----------------------- | :-----------: |
| Fabric API              | FabricMC Team |
| CompleteConfig          |    Lortseam   |
| TextPlaceholderAPI      |     Patbox    |
| Silk                    |  SilkMC Team  |
| Server Translations API |               |


---

# 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://27rogi.gitbook.io/server-toolbox/master.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.