Zippy Wall · Docs

Troubleshooting

Common problems and how to fix them. Email [email protected] if nothing here applies.

Bot isn't responding to anything

  • Confirm the bot is online in your member list (status indicator should be green).
  • In Discord, check Zippy Wall's role assignments: Server Settings → Roles → Zippy Wall. It should have View Channels + Send Messages + Manage Messages at minimum.
  • Check the bot's position in role hierarchy — drag Zippy Wall above the roles of users whose messages it should moderate.
  • Try /help in a channel. If the command doesn't appear in the slash menu, the bot probably wasn't granted applications.commands scope. Re-invite via the dashboard.

Slash commands don't appear in the / menu

  • Global slash commands can take up to 1 hour to propagate after a change. Wait, then refresh Discord (Ctrl+R).
  • If a fresh install: re-invite the bot to make sure applications.commands scope is granted.
  • If you don't have Manage Messages permission, Discord hides the commands from your view by design.

"Missing Permissions" error on /ban or /kick

Discord requires Zippy Wall's highest role to be above the target user's highest role for kick / ban / timeout / role-strip actions to succeed. Move Zippy Wall above your mod roles in Server Settings → Roles.

Also: the server owner cannot be moderated by any Discord bot. That's a Discord platform rule, not a Zippy Wall limit.

My admin got role-stripped by anti-nuke

Anti-nuke deliberately does NOT auto-exempt Administrator-permission users — that's the threat model it's designed for (compromised admin account). Legit admins doing high-volume cleanup will trip it.

  • Re-grant the role manually — it's a normal Discord action.
  • Add the admin's user ID to Exempt users, or their role to Exempt roles, in the dashboard.
  • If this happens often, consider switching anti-nuke to LOG_ONLY for a week to tune limits before re-enabling enforcement.

See Whitelist for setup.

Re-invite required after Zippy Wall update

When Zippy Wall ships features that need new Discord permissions, your existing install doesn't automatically gain them. Re-invite from the dashboard — Discord shows a "needs additional permissions" consent screen for the delta only. You don't lose your config.

Bot says "DM blocked"

When you /warn, /ban, /kick, or /mute a user, Zippy Wall tries to DM them with the reason. If their Discord privacy settings block bot DMs, the response shows (DM blocked.) but the action still happens. Not a bug — it's just informational.

Anti-raid isn't firing on member joins

Anti-raid needs Discord's Server Members Intent turned on for your bot. Go to Discord Developer Portal → Applications → your bot → Privileged Gateway Intents and toggle Server Members Intent ON.

Without it, Discord doesn't fire GuildMemberAdd events to the bot, so anti-raid can't see joins.

Stripe Checkout shows old price

If the Stripe payment page shows a different price than the landing page advertises, the deployed environment's STRIPE_PRICE_ID hasn't been updated. Email me — [email protected] — and I'll fix it.