> For the complete documentation index, see [llms.txt](https://docs.gamesense.biz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gamesense.biz/getting-started/runtime-limits.md).

# Runtime & Limits

Supported Lua libraries, permissions, and runtime limits.

Scripts run in an isolated Lua environment with memory and execution-time limits.

## Available libraries

`base`, `coroutine`, `table`, `string`, `math`, and `utf8` are supported.

The `os` library provides only `clock`, `time`, and `difftime`. The only supported `require` module is `ffi`:

```lua
local ffi = require("ffi")
```

The standard `io`, `debug`, and `package` libraries are unavailable. `dofile` and `loadfile` are disabled. `load` accepts text-only Lua chunks, not bytecode.

## Default limits

| Resource                |   Limit |
| ----------------------- | ------: |
| Memory per script       |  64 MiB |
| Script load time        | 1000 ms |
| Callback execution time |   50 ms |
| Lua file size           |   1 MiB |
| Registered callbacks    |     256 |
| Menu controls           |      64 |
| Single FFI buffer       |   1 MiB |

A script may be stopped if it encounters an error or exceeds its execution limit.

## Script files

Local scripts are stored in `Gamesense/Scripts`. Filenames must end in `.lua`. Nested directories are not supported.

## Unsafe scripts

The **Allow unsafe scripts** option enables restricted IL2CPP operations, including field modifications and method calls. Enable it only for trusted scripts.


---

# 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.gamesense.biz/getting-started/runtime-limits.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.