Support

Almost always the consent gate. Until you accept the current Terms of Service and Privacy Policy, every user-initiated command returns the consent card instead of running. That check is server-side, so clearing cookies or using a slash command does not bypass it.

Open the consent center, accept both documents, then run the command again.

Mention the bot directly. A bare mention, or a mention with help, start, or support, always replies with the server's current prefix. A mention is never itself a command, so it works even when commands are locked.

Several commands need a configured system channel or role before they can do anything: the muted role for mute, a destination channel for welcome and Goodbye delivery, an audit log channel for logging.

Set them with setchannel and setrole. The serverconfig command prints what is currently set without revealing anything sensitive.

Run bot-permissions in the affected channel. It reports what Panindigan currently has and exactly what a given feature still needs.

The usual causes are channel-level overrides. A role that is allowed to manage messages at the server level can still be denied it on one channel.

Some capabilities are genuinely plan-gated, and the response names the feature, your current plan, and the minimum plan that includes it. Other messages mean the underlying service is temporarily unavailable — for example music while no audio node is healthy. Those are different problems with the same shape of message, and the message tells you which one it is.

Check the Notifications pages for that type under your server's Community section. The Delivery panel shows the destination channel, the bot's permission health there, the filters that were evaluated, and the state of every attempt: sent, retrying, failed, skipped, or duplicate-suppressed.

A delivery is only marked sent after Discord confirms it. If it failed, the reason is recorded and the retry policy is bounded, so a broken configuration will not hammer Discord.