> ## Documentation Index
> Fetch the complete documentation index at: https://docs.dogebot.net/llms.txt
> Use this file to discover all available pages before exploring further.

# Common questions and how to fix them

> The problems people run into with Yapin bots, and exactly what to do.

Find your problem below and follow the steps in order. Most are fixed in under a minute.

## Bot and connection

> **My bot is offline**
>
> 1. Open your bot's **Dashboard** and press **Start** if it says Stopped. Free bots switch off after 24 hours with no activity.
> 2. Did you press **New token** on Yapin? The old token stops working. Paste the new one on **Settings → Bot token**.
> 3. Open **Error Logs** and look at the newest error, it usually says what's wrong.
> 4. Check [dogebot.net/status](https://dogebot.net/status). If **Yapin bot hosting** isn't green, it's on our side and we're on it.
> 5. Still offline after 2 minutes? Press **Restart** on the dashboard.

> **Yapin didn't accept the token**
>
> 1. Copy the token again from **Settings → Developer** on Yapin, with nothing before or after it.
> 2. Make sure it's a **bot** token, not your own account's.
> 3. If you just reset it, use the newest one: older tokens stop working straight away.

> **The bot is online but does nothing**
>
> 1. Check the bot is **in your server** (Settings shows its servers).
> 2. Commands and events must be **switched on**: look for the switch next to each one.
> 3. Events with a **server or channel filter** only run there. Click the trigger block and check the filters.
> 4. Messages from **other bots** never start events. Test with your own account.

> **The bot goes offline by itself**
>
> Free bots switch off after 24 hours with no activity (no commands, no events). Press **Start** to turn it back on, or get **Premium** and it stays on 24/7.

## Commands

> **My command doesn't show in the / menu**
>
> 1. Press **Save Command** again: saving is what sends it to Yapin.
> 2. The name must be 1 to 32 **lowercase** letters, numbers, `-` or `_`. No spaces or capitals.
> 3. A bot can have **100 commands** at most, including module commands. Switch off module commands you don't use.
> 4. On **Settings**, press **Send commands** to send the whole list again.
> 5. Reload Yapin (refresh the page or restart the app).

> **The command says I'm going too fast**
>
> That's the command's **cooldown**. Click the command block and change or remove it under **Cooldown**.

> **How do I use what people type after the command?**
>
> Everything after the name is `{yp_args}`, and each word is `{yp_arg1}` to `{yp_arg5}`. For `/give @Ada 50`, `{yp_arg1}` is Ada's mention and `{yp_arg2}` is `50`. See [Variables](https://docs.dogebot.net/yapin/variables.md).

> **Two bots answer the same command**
>
> If two bots have a command with the same name, people pick one with `/name @Bot`. Your bot stays quiet when they pick another bot. Rename your command if it clashes often.

## Messages, pictures and buttons

> **My picture doesn't show**
>
> Yapin only shows pictures from its own uploads and a list of sites. Upload the picture to **Imgur**, **Giphy** or **GitHub** and use that link. See the full list in [Messages and cards](https://docs.dogebot.net/yapin/messages-and-cards.md#pictures). `{yp_user_avatar}` always works.

> **Yapin says the message is too long**
>
> Text is 2,000 characters at most, and all embeds together 6,000. Shorten the text, split it into two messages, or move details into embed fields.

> **The button says the interaction failed**
>
> 1. Make sure there are blocks under the button in the builder: an empty button has nothing to do.
> 2. Use **Answer the click** as the first block under the button so Yapin gets an answer within 3 seconds.
> 3. Buttons on messages sent before you changed the command keep their old IDs. Send the message again.

> **My custom emoji shows as text**
>
> Write it as `<:name:id>` (or `<a:name:id>` when animated) with the emoji's Yapin ID, and make sure the emoji is from a server the bot is in.

> **\{variable} shows up as text instead of a value**
>
> 1. Check the spelling and the curly brackets: `{yp_user_mention}`, not `{yp user mention}`.
> 2. Some variables only exist in certain events. `{yp_custom_id}` is only there for button clicks, `{yp_emoji}` only for reactions.
> 3. Values from a block (like `{yp_member_roles}`) need that block to run **above** the message.

## Permissions and moderation

> **The bot can't ban, kick, time out or give a role**
>
> 1. On Yapin, give the **bot's role** the permission (Ban, Kick, Timeout, Manage roles…).
> 2. Drag the bot's role **above** the members and roles it should manage. A bot can't act on anyone with a higher role.
> 3. The server owner can never be banned, kicked or timed out.

> **Moderation says I'm not staff**
>
> Staff are people with a role that can **manage messages** (moderators) or **manage the server** (admins). Give your role that permission on Yapin, or add it under **Extra moderator roles** on the Moderation module page.

> **Purge doesn't delete anything**
>
> The bot needs **Manage messages** in that channel. Purge deletes up to 100 recent messages at a time.

## Modules

> **My module settings didn't save**
>
> Changes only count after you press **Save Changes** in the bar at the bottom. If you leave the page with the bar still showing, your changes are lost.

> **Channels and roles are empty in the module settings**
>
> Pick your **server** at the top of the module page first. If it says the bot isn't in a server, invite the bot on Yapin and reload.

> **I can't claim the Premium role**
>
> 1. Link your Yapin account on DogeBot: **Account → Yapin sign-in**.
> 2. Make sure one of your bots has active Premium.
> 3. Press **Claim Premium role** again. If Yapin is busy, wait a moment and try once more.

## Still stuck?

Open **Error Logs**: every failed block is listed with a plain explanation. Or ask in the DogeBot Yapin server: press **Get help** and our AI support answers from these docs, or ask for a person.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.