Skip to main content
Hedwig’s community features are designed as small systems you can combine: welcome members, give them ways to participate, and route questions to the right people. Required permissions vary by feature; check the dedicated guide before setup. For example, Voicemaster requires Manage Channels, while most community setup commands require Manage Server. Use the dedicated guides for welcome and farewell, leveling, tickets, and tracking. The rest of the community systems are listed in the sidebar.

​
Onboarding and participation

Test welcome and farewell messages before inviting a large wave of members. The test commands let staff catch channel, variable, and formatting mistakes early.

​
Support and staff operations

​
Tickets

When a ticket is open, support staff can use:

​
Staff applications

Use /staff reset only when you intend to remove the current application configuration. The setup panel stores questions, an accepted role, a review channel, and a staff-manager role.

​
Automation

Use keyword automation for lightweight, predictable responses:

​
Voice and server activity

​
Voicemaster

/voicemaster setup creates the Join2Create flow for private voice channels. These commands require Manage Channels. Use /voicemaster config to inspect or update defaults and /voicemaster reset to remove the system.

​
Autopost and social notifications

​
Leveling and tracking

Hedwig can track invites, messages, and voice time. Use the tracking commands to inspect or administer stats. Daily leaderboards use the current UTC date, and weekly leaderboards use the computed UTC ISO week. There is no user-configurable reset-time command, and these leaderboards are not a substitute for a permanent moderation record. These tracking commands are message/prefix commands. Administrative adjustments include ,addinvites, ,removeinvites, ,clearinvites, ,addmessages, ,removemessages, ,clearmessages, ,addvctime, ,reducevctime, and ,clearvoice; they require Manage Server. Use them only with a documented moderation reason.