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

# API versions

The API version number, the SDK in the scripts folder and the change history.

Quick uses the version number to tell which SDK a script was built for. The number is stored in `Script.API_VERSION`: the compiler writes it into the script at build time, and Quick compares it with its own. The current version is `28`.

The version goes up when something is added to or changed in the API. A script built for an older SDK almost always works as is. Quick recompiles the sources against its own `script-api.jar` anyway, so an old number has no effect. Only things that were actually removed or renamed will break, and you will see that as a compile error in the console.

## SDK in the scripts folder

On every start Quick overwrites `scripts\.api\`: `script-api.jar`, `script-api-sources.jar`, `README.txt`. There is no point in editing them. If your IDE shows different methods from the ones Quick compiles with, the project is using an old copy of the SDK. Add the library again from `.api/`.

## Checking

Type `.script check` in chat: the command compares the script API with the SDK and tells you exactly what does not match. It also lists the events your Quick version knows.

## Changes

| Version | What                                                                                    |
| ------- | --------------------------------------------------------------------------------------- |
| 28      | mixins and hooks: `hook(...)`, `Hooks`, `Hook`; `control().motion(x, y, z)`; MCP server |
| 27      | first version with jar bundles: `java/` and `resources/` in one file, hot swapping      |


---

# 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.quickclient.cc/en/extras/api-versions.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.