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

# Introduction

## Are you someone who knows nothing about programming and just want to use OneConfig? Check out our website [here](https://polyfrost.org/projects/oneconfig/)!

Welcome to the OneConfig documentation for developers and designers. If you're confused about how to integrate your mod with OneConfig, or just what something does, there's a good chance the answer is here.

Keep in mind though, that these docs aren't perfect, so if something is wrong, feel free to [fix it yourself](https://github.com/Polyfrost/OneConfig-Documentation/), before we even notice.

## Contributions

If you encounter any errors or bugs in OneConfig, feel free to [make an issue](https://github.com/Polyfrost/OneConfig/issues) or [pull request.](https://github.com/Polyfrost/OneConfig/pulls) If you're still stuck, join our [Discord](https://polyfrost.cc/discord) server and create a ticket!

## Licensing

The OneConfig Docs are licensed under the GNU Free Documentation License, version 1.3 or later.

Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3, or any later version published by the Free Software Foundation; with the Invariant Sections just being "Introduction" with no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled "[**Documentation License**](/oneconfig/documentation-license.md)".


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.polyfrost.org/oneconfig/readme.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 `build a script that syncs our docs to a CMS` 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.