On this page
Communication
Discord for Unreal Engine
Community servers with text and voice channels, forums, roles, and scheduled events.
It's ideal for player, tester, and modding communities. Keep internal studio work off the public server.
What it is
Discord organizes a community into servers with text and voice channels, roles, events, and moderation tools. Community mode lets administrators add forum, announcement, and Stage channels, plus Onboarding. Discovery has separate eligibility requirements.
A Discord server gives players and testers a place to ask questions, report bugs, and join scheduled playtests. Forum channels keep reports separate, while voice channels support live sessions.
It's ideal to keep confidential studio work in a separate workspace or server. Test public-server roles and channel overrides with a normal member account before sharing restricted content.
With Unreal Engine
Discord works for player support, playtests, modding groups, and team voice chat. Community forum channels keep each report in its own post. Ask for the build and platform in the guidelines, then use tags to organize reports.
Where it fits
Strengths
- Text and voice channels support persistent game communities.
- Roles and onboarding can route members into relevant channels.
- Community-enabled servers can use events and announcement channels for playtests, updates, and public sessions.
Tradeoffs
- Forum posts and chat still need triage when feedback becomes production work.
- Role and channel overrides are easy to misconfigure.
- Internal studio discussion and public community access need a firm permission boundary.
Choose it when
- The project needs a player, tester, creator, or modding community.
- Voice chat, live streams, forums, and scheduled events matter more than formal work tracking.
- The studio has staff and policy for moderation and public access.
Look elsewhere when
- The workspace contains confidential client or production material.
- The team needs auditable task ownership, file approval, or release reporting.
- Enterprise identity, retention, and compliance controls drive the communication choice.
How it works
- Servers, categories, and channels
- A server contains text and voice channels grouped into categories. Community mode unlocks forum, announcement, and Stage channel types. Permissions can come from roles, categories, channels, and member overrides. Test the result with a normal account because the administrator view hides permission mistakes.12347912
- Community mode, roles, and onboarding
- Enabling Community lets administrators create forum, announcement, and Stage channels and configure Community Onboarding. Onboarding can route new members to relevant roles and channels. Discovery also requires more than 1,000 members.137891112
- Forum channels
- Forum posts have guidelines and tags. You can require a tag before posting, but that setting does not require a complete set of platform, build, and issue-type fields. Ask for those details in the guidelines and check them during triage.313
In production
- 01
Separate public and internal spaces
Keep confidential production systems outside the public server. If the server has a restricted moderator area, deny access at the category level and test every bot there with a normal member account.
- 02
Route new members through onboarding
Ask what game, platform, language, or contribution type they care about and assign only the useful channels. Keep default channels small and readable so announcements and rules are visible on first entry.
- 03
Collect structured feedback in forums
Ask for the build, platform, reproduction steps, and a capture in the forum guidelines. Require a tag to help sort reports, then check missing details during triage. Create a task for a confirmed bug and link its forum post.
- 04
Run live community sessions
Schedule the playtest or question session. Use a voice channel when everyone can speak, or a Stage channel when moderators need to control the speakers. Go Live can show the build, but write down any accepted feedback after the stream ends.
- 05
Moderate with a written escalation path
Configure roles, AutoMod, slow mode, reports, and private moderator alerts. Define when a moderator warns, times out, bans, or escalates a safety issue. Keep administrative roles limited and review them regularly.
Best practices
- Community mode doesn't enable Discovery
- Community mode enables the server tools needed for onboarding and announcements. Discovery has its own requirements, including more than 1,000 members, so enabling Community does not make a server discoverable.17
- Build roles from least privilege
- Start with a small baseline for everyone, then grant moderators, event hosts, bots, and contributors only the channel and moderation access they need. Test every category with a normal member account.
- Keep onboarding choices useful
- Ask only the questions needed to place a member in useful roles and channels. Review the defaults as the server changes so a new member can still find rules, announcements, support, and the right feedback area.8
- Prepare for moderation incidents
- Enable Community features, onboarding, rules screening, AutoMod, and a private alert channel. Document raid response, evidence handling, escalation, and backup coverage before the community needs them.578
- Record decisions outside Discord
- Write accepted bugs, release decisions, and production commitments in the system that owns them. Discord remains the source link and public conversation, not the only durable project record.
Gotchas
- Channel overrides can break category policy
- A synced channel inherits category changes. An unsynced channel keeps its own overrides, so a later category fix may leave that channel exposed. Audit both the category and every unsynced child.4
- Administrator bypasses channel restrictions
- The Administrator permission grants every permission and bypasses channel-specific restrictions. Keep it away from routine moderator and bot roles, then test permissions without an administrator account.411
- Some privileged roles are exempt from AutoMod
- Administrators and members with Manage Server are exempt from AutoMod rules. A compromised staff or bot account can therefore post content that ordinary members cannot.5
- Forum posts don't track status
- Inactive posts can be reopened unless they are locked, and a forum channel supports only one pinned post. Use tags and a separate tracker to distinguish new, acknowledged, fixed, and released reports.3
- Server-installed apps bypass AutoMod
- AutoMod doesn't check messages from server-installed apps. Limit bot and webhook permissions and review their output separately.5
Adoption checklist
- Test every private category and bot with a normal member account.
- Use onboarding to expose only the channels relevant to each member.
- Write forum templates for bug reports and playtest feedback.
- Publish moderation rules and an internal escalation path.
- Limit administrative and integration roles to the permissions they need.
- Move accepted feedback into the studio tracker with a source link.
Related guides
Sources
Official sources checked .
- 1Discord community serversdocs.discord.com
- 2Game community guidedocs.discord.com
- 3Discord forum channelssupport.discord.com
- 4Discord permissionssupport.discord.com
- 5Discord AutoModsupport.discord.com
- 6Discord Go Livesupport.discord.com
- 7Enabling a Community serversupport.discord.com
- 8Community Onboardingsupport.discord.com
- 9Discord Stage channelssupport.discord.com
- 10Discord Scheduled Eventssupport.discord.com
- 11Discord roles and permissionssupport.discord.com
- 12Discord announcement channelssupport.discord.com
- 13Discord required-tag settingdocs.discord.com
Unreal Directive is free and ad-free.
If it saved you time, you can help keep it that way.

