How to Run a Draft Night in Your Discord Server

Updated 2026-07-13

How do you run a draft night in your Discord server?

You run a draft night in your Discord server by gathering ten players in a voice channel, screen-sharing the live pick board so everyone can watch the picks land, and posting the final result link back to the server when it's done. The format turns a random 5v5 into something people show up for on purpose, because the picking itself is entertainment — watching who gets chosen, and when, is half the fun.

This draft night Discord server playbook works at any scale, from a small friend group's private server to a larger Dota 2 Discord community with dozens of members rotating through draft nights.

How do you get ten players into the voice channel?

Pin a message in your draft-night channel with the time and a simple reaction or thread for people to confirm, and set a reminder ping 30 minutes before start. Discord's built-in Events feature also works well for a recurring weekly slot — members can RSVP ahead of time instead of scrambling in the channel that afternoon.

Once ten confirmed players are in the voice channel, add them to DOTA DRAFT. Pasting Steam IDs pulls each player's rank medal, best positions, and win rate from OpenDota so the pick board shows real information, not just names — useful in a server where not everyone knows every other member's skill level yet.

How do you run the live draft during the call?

Have one person screen share DOTA DRAFT in the voice channel so the whole server watches the same pick board in real time — this is the part that makes draft night feel like an event instead of a chore. Pick captains manually, by random wheel, or by auto-selecting the two highest-MMR players in the pool, then let them alternate picks in snake order (A, B, B, A, A, B, B, A) with the 30-second timer running on screen for everyone to see.

The shared screen does the work a text channel can't: everyone sees the same pick land at the same moment, so there's no confusion about who called dibs on the captain who mains a hero like Pudge, and no argument later about the order things happened in.

How do you share the result back to the server?

When the draft finishes, use the Share to Discord button to copy a link straight into your clipboard, then paste it into the server so the final rosters and balance score are visible to anyone who missed the live call. This matters for a Discord community specifically — not every member is in voice every week, and a posted result link lets the rest of the server see who ended up where without asking around.

Pinning the result link in your draft-night channel also builds a running history: over several weeks it becomes obvious which captains draft well and which teams tend to run close, which is exactly the kind of small detail that keeps a community coming back.

The result link also settles the kind of dispute that tends to flare up an hour after the game ends — whether a specific pick happened before or after the timer ran out, or which captain actually had the higher balance score that week. Since the link records the finished draft exactly as it happened, there's no need to rely on anyone's memory of a call that took place in a busy voice channel.

How do you turn this into a weekly ritual instead of a one-off?

Keep the format identical every week — same channel, same time slot, same draft process — and rotate who gets to be captain so the same two people aren't always in charge. Consistency is what turns a random Tuesday game into something members plan their evening around.

A server that runs the same draft night format for a few months in a row also starts building its own culture around it — inside jokes about a captain's habit of drafting the same core five players, a running tally of whose teams tend to win, or the server's dedicated Techies main who somehow always goes in the final pick round. None of that happens if draft night is a one-off; it happens because the ritual repeats often enough for members to notice patterns.

• Use the same pinned message format for every announcement so members know exactly what to expect.
• Rotate captains between weeks, either manually or with the random wheel, so the role spreads across the community.
• Keep the 30-second pick timer on so slow weeks don't discourage people from coming back.
• Post the result link every time, even for lopsided games, so the ritual stays consistent rather than selective.

Frequently asked questions