Command styles
The default prefix in this build is
,. Server managers can change it with
,prefix set <new-prefix> or the equivalent configured-prefix form. A prefix
may be at most 10 characters. ,prefix self <new-prefix> sets a personal
prefix across servers without changing the server-wide value.
Five-minute setup
1
Confirm the bot can respond
Run
/ping. If Hedwig cannot respond, check that it has View Channel and Send Messages in the channel where you are testing.2
Choose a prefix
Run
,prefix to see the current value. Use ,prefix set ! to choose a
server prefix, ,prefix remove to restore the project default, or
,prefix self ? for a personal prefix.3
Create a safety net
Run
/logging setup, /automod setup, and ,antinuke enable from an
administrator-only channel. Read Permissions before
enabling protection. Antinuke enable is restricted to the server owner or
an extra owner.4
Set up the member experience
Pick the systems that fit your server:
/greet setup, /leveling setup, /ticket setup, /selfrole setup, or /giveaway start.5
Test each workflow
Use each feature’s
test, config, or status command where available. Test in a private channel before announcing it to members.A useful first-week stack
Small community
Greet & farewell, suggestions, feedback, reminders, polls, and music.
Growing community
Add leveling, self-roles, giveaways, tickets, tracking, and autoroles.
Public community
Add antinuke, automod, logging, staff applications, and a documented moderation process.
Creator or media server
Add autopost, social notifier, music, profile cards, and live leaderboards.
Find your next step
- Need the bot to stop raids or destructive actions? Read Security.
- Need to manage members and channels? Read Moderation.
- Need tickets, roles, levels, or welcomes? Read Community systems.
- Need to play music? Read Music.
- Need a quick utility or AI tool? Read Utility & extras.