Permissions & hierarchy
Understand who can run a command and what Blood needs to carry it out.
Check both sides
A command can require permissions from you and from Blood. The command reference lists the caller requirements. Blood also needs permission to perform the action in the target channel or server. A missing permission on either side can prevent a command from working.
Place the Blood role correctly
In Server Settings → Roles, place Blood above roles it should assign or moderate. Discord restricts actions against equal or higher roles and the server owner. Giving Administrator does not remove those hierarchy restrictions.
Review channel overrides
Check View Channel, Send Messages, and Embed Links in the channel where you use commands. Music additionally needs Connect and Speak in the voice channel. Logging and embed features can require Manage Webhooks. A channel override may differ from a server-wide role permission.
Owner-only actions are intentional
Some configuration commands are restricted to the server owner, even if another member is an administrator. For example, the prefix command and VoiceMaster setup list Server Owner as their requirement. Check the exact command instead of granting broader access to troubleshoot.
,help voicemaster setupCommand quick reference
Blood’s real command help cards, including syntax, examples, aliases, permissions, categories, cooldowns, and interactive paginator controls.
APPblood helpCommand: prefix
Shows or changes this server's command prefix
Syntax: prefix <new prefix>Example: prefix .
Server OwnerAPPblood helpCommand: antinuke admin
Toggles a member's ability to configure Antinuke
Syntax: antinuke admin (member)Example: antinuke admin @alexCommand: voicemaster setup
sets up or repairs VoiceMaster without duplicating resources
Syntax: voicemaster setupGroup Command: createembed
creates an embed, plain message, or static Components V2 layout
Syntax: createembed (code or Discohook JSON)Example: createembed {title: Welcome}{description: Hello there}