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

# Configuration and compatibility

Use the configuration files shipped with your resource version. This guide does not define universal Lime Scripts configuration keys.

## What to check

* Framework and version supported by the product listing.
* Required database connector and any SQL migrations.
* Inventory, targeting, notification or other integrations listed for that resource.
* Permissions, language, coordinates and gameplay settings exposed in its configuration.

Edit only files intended for customization. Some resource files are protected by Asset Escrow. Keep original copies and make one change at a time so you can identify the cause of an error.

Do not paste credentials into screenshots or public support messages. If a required integration is not listed, ask support rather than assuming it is supported.


---

# 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.limescripts.com/documentation/configuration-and-compatibility.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.