Setting Up a Shot Caller for Large Guild Raids on Discord

A shot caller only works if everyone can hear them. In a small group that's trivial — one channel, done. In a 50–100 player raid split across party channels, it's the hardest part of the whole setup, because Discord can't put one voice into several channels natively. This guide covers the comms structure that works at scale, and how to solve the "everyone hears the caller" problem with a voice relay.

The comms hierarchy that works at scale

Large guilds converge on the same two-layer structure:

• Main caller (shot caller). One voice, strategic calls only: targets, pushes, retreats, cooldown windows. Everyone in the raid hears this layer.
• Party leads. Micro-calls inside each party channel: focus targets, peel assignments, who needs a heal. Only that party hears them.

The failure mode is mixing the layers: either everyone sits in one channel (party chatter buries the calls) or parties sit separately and only the caller's own channel hears the calls. The fix is broadcasting the caller's voice into every party channel while the parties keep their own comms — which is what a voice relay does.

Channel layout on your Discord server

1. One caller channel. The shot caller (plus co-callers, if any) speak here. Keep it locked — anyone in this channel is broadcast to the whole raid.
2. One voice channel per party. Your normal party channels, exactly as the game's group structure dictates (most MMOs run parties of 4–12).
3. A relay bot in each party channel. The bot mirrors the caller's voice into that channel with under a second of latency.

Calling discipline that survives contact

• Short imperative calls: "swap north", "burn boss", "disengage". No narration.
• One voice on strategy. If two people call strategy, nobody follows either.
• Party leads repeat only what their party must act on, in their own channel.
• Do a 30-second comms check before the pull — every party confirms they hear the caller.

Making every party hear the caller

dcshot is a voice relay service for Discord, built for MMO raid callouts. The admin installs it once through a guided web flow; on raid night you assign relay bots to your party channels in two clicks, and the shot caller just talks. Facts that matter for this job:

Do you even need this yet?

Honest answer: with fewer than ~15 players, put everyone in one channel and skip the tooling. The two-layer setup starts mattering when parties genuinely need separate comms — raids, sieges, mass PvP, alliance operations.