> For the complete documentation index, see [llms.txt](https://documentation.rcore.cz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.rcore.cz/paid-resources/rcore_shortcuts/limits.md).

# Limits

#### Shortcuts Limits

You could define default limit for shortcuts It's also possible to set specific limit to specific user by their identifier Identifier should match your selected LicenseType in config.lua Use prefix if you have `Config.LicenseWithoutPrefix = false` in config.lua

ShortcutsLimit should be always higher than 0

```lua
Config.ShortcutsLimit = 10

Config.ShortcutsPerPlayerLimit = {
    b111fbae111a1111a111e916bf8ebc0664229cbf = 15,
}
```

#### Native Shortcuts Limits

You could define default limit for native shortcuts (shortcuts usable ingame without UI opened). It's also possible to set specific limit to specific user by their identifier Identifier should match your selected LicenseType in config.lua Use prefix if you have `Config.LicenseWithoutPrefix = false` in config.lua

```lua
Config.NativeShortcutsLimit = 5
Config.NativeShortcutsPerPlayerLimit = {
    b111fbae111a1111a111e916bf8ebc0664229cbf = 5,
}
```

If you want to disable this limit set limit to `nil`

```lua
Config.NativeShortcutsLimit = nil
Config.NativeShortcutsPerPlayerLimit = {}
```

#### Blocked Actions

In config.lua you could define which actions should not be allowed in shortcuts

```lua
Config.BlockedShortcutActions = {
    'revive',
    'teleport',
}
```


---

# 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://documentation.rcore.cz/paid-resources/rcore_shortcuts/limits.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.