MEE6 Bot Maker modules run within a set of limits: how much a module can do each time it runs, how often it can run, what it can store, and more. This article lists all of them. New to Bot Maker? Start with How To Use MEE6 Bot Maker.
⚠️ These limits are accurate as of October 1, 2026. Bot Maker is in Beta, so they can change at any time. To see the current limits, open a module in Bot Maker, click the ? button on the right of the module's tabs, and select Limits.
All limits are enforced by MEE6, not by the module's code, so no module can go past them.
ℹ️ The ? menu has three tabs: Reference lists everything a module can technically do (triggers, messages, reactions, roles and moderation, XP and coins, storage and more), Limits lists the limits in this article, and Safety explains what a module can never do on your server, whatever its code says.
1. Per Run
A run is one trigger: a command, an event or a scheduled task. These limits start over with every run.
Limit | Per run |
Run time | 8 seconds (wall clock). A run that goes past it is stopped. |
Memory | 128 MB of heap (objects, arrays, strings), plus at most 64 MB of raw buffers. Heavy lifting such as pictures and storage goes through the SDK. |
Messages | 5 sent. Edits don't count. |
Message length | 2,000 characters. @everyone and @here are neutralized. |
Direct messages | 5 |
Reactions | 5 |
Role changes | 10 |
Moderation actions | 5 (kicks, bans, timeouts and nickname changes) |
Message reads | 5 |
Threads opened | 2 |
Threads closed | 5 |
Purges | 1, of up to 100 messages, none older than 14 days |
Schedule changes | 5 |
Pictures drawn | 3, and 3 boards |
SDK calls | 50, everything included |
2. Across Runs
These limits are counted over 10 minutes, 1 hour and 24 hours, in distinct members (or distinct messages, for message deletions). Each one applies per module and per server, and the server cap is twice the module cap.
When a cap is crossed, that kind of action is paused for the module, or for the whole server if the server's cap is the one crossed. It stays paused until a server admin resumes it from the module's Activity tab.
Action | Per module (10 min / 1 h / 24 h) | Per server (10 min / 1 h / 24 h) |
Kicks and bans | 5 / 15 / 40 | 10 / 30 / 80 |
Timeouts, nickname changes and unbans | 15 / 50 / 150 | 30 / 100 / 300 |
Role removals | 20 / 60 / 200 | 40 / 120 / 400 |
Role grants | 60 / 300 / 1,500 | 120 / 600 / 3,000 |
Message deletions | 100 / 400 / 1,500 | 200 / 800 / 3,000 |
Coin and XP deductions | 100 / 300 / 1,000 | 200 / 600 / 2,000 |
💡 A burst of kicks is far more likely to come from a bug or a wrong setting than from an intended rule. Check the module before you resume it.
3. Runs
How often modules run at all.
Limit | Value |
Running time per minute | 60 seconds per server, shared by every module on it. This is counted in time rather than in runs: what modules' code computes and what their calls to storage and images take. Waiting for Discord isn't counted. Events such as messages stop at 30 seconds, so commands, buttons, forms and schedules keep working. Triggers past that are dropped and noted in Activity. |
Runs per minute | 600 per server, whatever they cost. Events such as messages stop at 300. A module that only reacts to certain channels, words or attachments isn't started for other messages, so those don't count toward either limit. |
Runs answering another bot | 10 per minute per module. Runs past that are dropped silently. |
Runs at once | 1 per module. A trigger waits for the previous run to finish. Events wait their turn in the order they came, for up to 15 seconds and up to 10 waiting, and are dropped past that. |
4. Storage
What a module can remember.
Limit | Value |
Keys | 1,000 per module |
Member keys | 64 per member |
Value size | 16 KB per value |
Key length | 64 characters |
Expiry | 30 seconds to 1 year, when an expiry (TTL) is set |
5. Scheduling
Runs a module books for later.
Limit | Value |
Schedules | 25 per module. Booking the same key again replaces it. |
Delay | 30 seconds to 1 year |
Repeat | No more often than every 5 minutes |
Payload | 4 KB |
6. Direct Messages
DMs are sent under MEE6's own identity, so they are limited across every server.
Limit | Value |
Per server | 60 per hour |
Per recipient | 3 per minute, from all servers together |
7. Reading the Server
Limit | Value |
Channels listed | 200 |
Roles listed | 200 |
8. Workspace
Limit | Value |
Modules | 10 per server, with Premium |
Files | 10 per module, 24,000 characters each |
Pictures | 64 per module, 4 MB each |
Generated pictures | 300 per day, per server |
AI assistant | Limited per request, and per server each day and each month. The chat tells you when a limit is reached. |
FAQ
Where can I see the current limits?
In Bot Maker, open a module, click the ? button on the right of the module's tabs and select Limits. The numbers in this article are from October 1, 2026 and may have changed since.
Where can I see what a module can do, or what it's not allowed to do?
Click the ? button in a module and open Reference for everything a module can technically do, or Safety for what a module can never do on your server.
Can the AI Builder raise a limit for my module?
No. Limits are enforced by MEE6, not by your module's code, so no module can go past them.
Why did my module stop kicking, banning, changing roles or deleting messages?
It most likely crossed one of the limits in 2. Across Runs. That kind of action is then paused for the module (or for the whole server, if the server's cap was crossed) until a server admin resumes it from the module's Activity tab.
Why did my module skip some triggers?
Triggers are dropped when the server goes past its running time per minute (60 seconds, or 30 seconds for events such as messages), which is noted in Activity; when it goes past 600 runs per minute (300 for events); when more than 10 events are already waiting or one has waited more than 15 seconds; or when a module answers another bot more than 10 times in a minute, which is dropped silently.
If you have any questions about this, do not hesitate to join our Support Server✌️