The Game Developer Playbook, Part One: Getting Started on Discord (opens in new tab)
Discord’s playtest community should be created early in development to build relationships with players, gather feedback, and develop trusted advocates. The article recommends keeping the server focused on testing and feedback, with a clear structure separating information, discussion, staff communication, and playtest voice channels. A simple server template can evolve as the game and community grow. ## Getting Started - New server owners should understand Discord basics, including: - Creating and setting up a server - Managing permissions and roles - Sharing screens - Starting early gives developers more time to nurture a small but valuable group of engaged players. ## Playtest Community Basics - The primary goals should be to: - Make it easy for players to test the game - Give testers clear ways to provide feedback - Keep the community’s scope focused - Developers can begin with Discord’s recommended server template and expand it over time. ## Categories and Server Organization - Organize channels into clear groups: - Read-only information - Two-way discussions - Staff-only communication - Individual voice channels for voice chat, video, and screen sharing - Keep important information—such as rules, announcements, and updates—at the top. - Games with many classes, heroes, kits, or complex mechanics may benefit from dedicated forum or discussion channels. ## Roles and Permissions - Use two primary roles: - `@admin`, later renamed for the studio - `@playtest`, assigned to testers - Studio members should access every channel, while testers should see everything except the admin-only category. - Remove permissions from `@everyone` so unassigned users see an empty server, even if they enter through an unauthorized invite. - Use Discord’s **View Server As** feature to verify what each role can access. ## Community Features - Enabling Discord’s **Community** features can help larger servers manage growth. - Useful options include: - **Announcement Channels** for publishing updates that other servers can follow - **Server Insights** for engagement and retention data once the server reaches 500 members - **Community Onboarding** for self-assigned roles and rule acceptance - These features do not need to be enabled immediately; developers can adopt them as the community expands. ## Channel Design - Every channel should have a clearly defined purpose and a descriptive name. - Read-only channels should use consistent formatting, emojis, and Markdown to make important information easy to scan. - Suggested channels include: - `#rules-and-info` for server rules and guidelines - `#announcements` for game and playtest news - `#patch-notes` for updates and release details - `#game-discussion` for broader conversation A successful game playtest server should start small, organized, and purpose-driven. Establish clear permissions, separate information from discussion, and add features or channels only when they support the testing process and the community’s growth.