Moderation
Troubleshooting and glossary
Symptoms with their cause, and the terms used across this manual.
Troubleshooting and glossary
Symptoms with their cause, and the terms used across this manual.
Troubleshooting
Symptom, cause, fix
| Symptom | Cause | Fix |
|---|---|---|
| The bot ignores the trigger word in a group | The group is not authorized | Send /authorize in the group as the owner, or authorize it from the dashboard Groups tab |
| The bot ignores the trigger without a slash but works with one | Slash Required For Generation is on | Turn it off in Settings → Features, or keep typing the / |
| A photo sent after tapping a preset produces nothing | The chat is not authorized | Authorize the chat |
| An edit caption is ignored | Slash Required For Generation is on — for edits it applies to the whole bot | Start the caption with /Edit |
| Only 3 of the images sent with an edit are used | An edit uses at most 3 reference images | Send three |
| Generation is slow | Starter shares one GPU across up to four projects | Upgrade to Heavy |
| Results miss the character | The dataset is too small or inconsistent across angles | Submit a revision with better images |
| One user is consuming the bot | No per-user cap is set | Add a Rate Limit in Management → User Limits |
| A generated image has no View On Website button | Image Captions is off for that chat | Turn Image Captions on. The image is on the gallery either way. |
| A profile change sent no confirmation DM | Profile edits send no notification | Check the bot in Telegram |
Mistakes that cost a run
- Cutting the background out of training images.
- Shooting only one side of the character.
- Training a Day Pass bot on a weak dataset — the pass includes exactly one run and refuses a second.
- Banning a heavy user instead of rate-limiting them.
- Expecting the bot to work in a group before it is authorized.
Glossary
Terms
| Term | Meaning |
|---|---|
| Allowlist | The set of chats a bot is authorized in |
/authorize | Adds the current chat to the allowlist when sent by the bot's owner or a Memescale admin |
| Block | A per-username restriction that removes the username's access to the bot |
| Day Pass | The $5 product: 24 hours of access from delivery, one training run, no revisions |
| Demo group | A group with a Demo badge in the dashboard. It receives no demo sends |
| DM authorization | A Telegram username pre-cleared for generations in its own DM with the bot. Cap 50 per bot |
| Filter | Another name for a custom command — a trigger and a saved response |
| Gallery site | The {character}.memescale.ai site created when a character's trained model is deployed |
/getid | Replies with the numeric chat id and lists the chat under Discovered Groups. Also authorizes the chat when sent by the owner or a Memescale admin |
| Grace period | The 24 hours a bot keeps running after a missed payment |
| Heavy | The $299/mo plan — 100% of a GPU, no sharing |
| Heavy+ | The $499/mo plan — an X agent plus a matching Telegram Heavy bot |
| LoRA | The trained model file that teaches the bot a character |
| Owner | The Telegram account bound to the bot, fixed by the owner's first /start |
| Rate limit | A per-username daily generation cap, minimum 1, default 50 |
| Starter | The $99/mo plan — one GPU shared across up to 4 projects |
| Transfer Bot Ownership | The permanent handover of a bot to another Telegram account, from Profile → Advanced Bot Settings |
| Trigger word | The word that starts a generation for one character, set in the Characters tab under Trigger: |
Custom commands and content policy
Custom commands work in any chat, authorized or not. Generation output is shaped by a per-character prompt prefix, not by a content filter.
Buy bot setup
The buy bot posts a message in a Telegram group every time someone buys the token it is configured for. Set it up inside Telegram or from the dashboard.