Limits and constraints

What the Lolka platform limits, what the bot itself limits, and what doesn't work on Lolka yet. The web panel won't save values over a limit; in chat the bot trims the excess.

Platform limits

Checked on Lolka on October 2, 2026. Over a limit Lolka doesn’t trim but refuses — the message isn’t sent at all, so the web panel won’t let you save more, and the bot trims whatever grew after placeholders.

Message text

Limit: 2000 characters
Where it matters: Message texts, a custom command without an embed, automations, a web panel reply. Longer — turn on the embed.

Embed: title

Limit: 256 characters
Where it matters: Panel texts, the welcome, custom commands.

Embed: description

Limit: 4096 characters
Where it matters: Including a custom command's reply with an embed.

Embed: author

Limit: 256 characters
Where it matters: —

Embed: footer

Limit: 2048 characters
Where it matters: —

Embed: field

Limit: 256 (name) / 1024 (value)
Where it matters: The bot splits long values into several fields.

Embed: fields

Limit: 25
Where it matters: The custom command list in /custom list is cut with a note.

Whole message

Limit: 6000 characters
Where it matters: The sum of all embeds: title, description, fields, footer, author (the message text isn't included). Each field can be within its own limit and still be more together: the bot first drops extra fields, then trims the footer and the description. The editor has a “Total in the message” counter at the bottom.

Embeds per message

Limit: 10
Where it matters: —

Buttons

Limit: 5 per row, 5 rows
Where it matters: Label — up to 80 characters.

Items (categories) in a panel

Limit: 25
Where it matters: A drop-down holds 25 items, an item label up to 100 characters; the list takes a whole row.

Channel name

Limit: 100 characters
Where it matters: The ticket channel name template.

Nickname in web panel replies

Limit: 1–80 characters
Where it matters: A staff member's own nickname; the “· from web” suffix fits within these 80.

Files in a web panel reply

Limit: up to 4, 8 MB each, 25 MB in total
Where it matters: The bot doesn't store them — it sends them straight to the ticket channel.

Form questions

Limit: 5
Where it matters: Fields in a modal.

Question label

Limit: 45 characters
Where it matters: The form field's label.

Short answer / long answer

Limit: 200 / 1000 characters
Where it matters: A form field; a question can have its own “from … to …” within these limits.

Channel permissions

Limit: 6 permissions
Where it matters: View the channel, send messages, manage messages, add reactions, voice messages, bypass slow mode. On Lolka files and links are part of “send”, history is part of “view”, pinning is part of “manage”: they can't be granted separately.

What	Limit	Where it matters
Message text	2000 characters	Message texts, a custom command without an embed, automations, a web panel reply. Longer — turn on the embed.
Embed: title	256 characters	Panel texts, the welcome, custom commands.
Embed: description	4096 characters	Including a custom command's reply with an embed.
Embed: author	256 characters	—
Embed: footer	2048 characters	—
Embed: field	256 (name) / 1024 (value)	The bot splits long values into several fields.
Embed: fields	25	The custom command list in /custom list is cut with a note.
Whole message	6000 characters	The sum of all embeds: title, description, fields, footer, author (the message text isn't included). Each field can be within its own limit and still be more together: the bot first drops extra fields, then trims the footer and the description. The editor has a “Total in the message” counter at the bottom.
Embeds per message	10	—
Buttons	5 per row, 5 rows	Label — up to 80 characters.
Items (categories) in a panel	25	A drop-down holds 25 items, an item label up to 100 characters; the list takes a whole row.
Channel name	100 characters	The ticket channel name template.
Nickname in web panel replies	1–80 characters	A staff member's own nickname; the “· from web” suffix fits within these 80.
Files in a web panel reply	up to 4, 8 MB each, 25 MB in total	The bot doesn't store them — it sends them straight to the ticket channel.
Form questions	5	Fields in a modal.
Question label	45 characters	The form field's label.
Short answer / long answer	200 / 1000 characters	A form field; a question can have its own “from … to …” within these limits.
Channel permissions	6 permissions	View the channel, send messages, manage messages, add reactions, voice messages, bypass slow mode. On Lolka files and links are part of “send”, history is part of “view”, pinning is part of “manage”: they can't be granted separately.

Bot limits

What	Limit
Panel / category name	100 characters
Custom command name	50 characters
Category description	100 characters — the second line in the pick list
Category welcome	4000 characters
Close reason	500 characters in the Lolka form, 1000 from the web panel
Custom command prefix	1 character
Custom command: calling again	once every 3 seconds per member — more often the bot silently doesn't reply
Command call pattern	200 characters; a word longer than 32 characters isn't checked against patterns. Nested repeats like (a+)+ and long chains of optional parts and alternatives like a?a?a?… aren't accepted: such a pattern could hang the bot
Tickets per period	a period from 1 minute to 30 days
Leading zeros in the number	0…20
Open tickets per user	on the server 0…100 (across the server), on a category 0…1000 (across its tickets); both apply, 0 = no limit
Total open in a category	up to 100,000, 0 = no limit
Auto-close	1…8760 hours
Auto-delete	up to 3650 days
Retention of closed tickets' conversations	1…365 days, 180 by default
Roles in the blacklist	50
Moving settings with a code	everything within the server limits (below); the code is valid for a day
Panels / categories / custom commands per server	25 / 100 / 100
Multi-panels per server	10
Automation rules per server	25
Blacklist entries	5000
The /dashboard token link	5 minutes, one-time
Web panel access	the decision is remembered for 20 seconds, role permissions — up to a minute
Web panel requests	600 per minute from one address
Admin lists	50 roles, 50 users
Public stats	1-minute cache, a 14-day chart

Paper BotBOTToday at 12:00

Support

Press the button below to open a ticket

🎫Open ticket

Alex used /

Paper BotBOTToday at 14:10

You already have open tickets: 1 of 1. Close old ones to open a new one.

Only you can see this message · Dismiss message

The refusal comes as a hidden message — only the person who pressed sees it, and no ticket channel is created. The texts are edited in “Texts and buttons”.

What doesn’t work on Lolka yet

These are platform limitations, not the bot’s. The settings for them already exist and will turn on when Lolka adds support.

Direct messages from the bot

State: Not supported
What instead: The “Transcript to DMs” toggle in the settings is inactive until Lolka supports it. Notifications about new replies in DMs aren't planned while there's no API.

A file attached to a button reply

State: Rejected by the API
What instead: The “Transcript” button first defers the reply and then sends the file as a hidden message — that's how Lolka accepts it.

Threads

State: None
What instead: Tickets are separate channels only.

Channel permissions beyond the six

State: None
What instead: The category's permission matrix shows only existing permissions; old settings of other permissions are kept and will come back when they appear.

Feature	State	What instead
Direct messages from the bot	Not supported	The “Transcript to DMs” toggle in the settings is inactive until Lolka supports it. Notifications about new replies in DMs aren't planned while there's no API.
A file attached to a button reply	Rejected by the API	The “Transcript” button first defers the reply and then sends the file as a hidden message — that's how Lolka accepts it.
Threads	None	Tickets are separate channels only.
Channel permissions beyond the six	None	The category's permission matrix shows only existing permissions; old settings of other permissions are kept and will come back when they appear.

If something from this list started working on your server and the bot still behaves the old way — let us know: it can be turned back on with one change.