# NoCap Bots: Add-ons that make Discord work for big guilds. Source: https://www.nocapbots.com/ > NoCap Bots builds Discord add-ons for gaming guilds. Start with Voice Relay: one caller's voice in every party channel at once, for raids, sieges and PvP. ## What every add-on shares - **Sign in with Discord.** No new password. We see your username, your server list and a verified email — never your messages. - **One dashboard, every server.** Every server where you have Manage Server, in one list. Set up an add-on, check it's live, switch servers in a click. - **Plans per server, per add-on.** Pay only for the add-ons a server uses, sized to how big it is. Every plan starts with seven days free. - **Share the work.** Invite your officers as managers and choose what each can change: configuration, billing or other managers. ## Add-ons - **Voice Relay** (beta) (https://www.nocapbots.com/voice-relay): Your shot caller talks in one channel and every party hears them, at the same moment, without leaving their own channel. Built for raids, sieges and large-scale PvP. - **Attendance** (beta) (https://www.nocapbots.com/attendance): Attendance notes who was in your voice channels during a fight and for how long, then saves a list you can export for payouts, regears and loot. It runs on its own or alongside Voice Relay. ## About NoCap Bots ### What is NoCap Bots? NoCap Bots makes add-ons for Discord: bots and a dashboard that give big communities what Discord doesn't do on its own. The first is [Voice Relay](https://www.nocapbots.com/voice-relay), which puts one caller's voice in every party channel at once. ### Which add-ons are there? Two, both in beta: [Voice Relay](https://www.nocapbots.com/voice-relay), one caller's voice in every party channel, and [Attendance](https://www.nocapbots.com/attendance), who was in voice for a fight and for how long. More are on the way, built with the guild leaders who use NoCap Bots — tell us in our Discord what your server needs next. ### Is NoCap Bots made by Discord? No. NoCap Bots is an independent service that works through Discord's official bot and sign-in features. It isn't affiliated with Discord Inc. ### Who can add NoCap Bots to a server? Anyone with Manage Server or Administrator on it in Discord. They can invite their officers as managers afterwards. See [who can set up a server](https://www.nocapbots.com/docs/permissions.md#who-can-set-up). ### How does billing work? Each add-on has its own plans, and a plan belongs to one Discord server. Every plan starts with seven days free and you can cancel any time. See [plans and billing](https://www.nocapbots.com/docs/billing.md). ### Do my members need to install anything? No. Add-ons run inside Discord, so members keep using Discord as normal. Only the people who set things up use the dashboard. # Voice Relay Source: https://www.nocapbots.com/voice-relay > Your shot caller talks in one channel and every party hears them, at the same moment, without leaving their own channel. Built for raids, sieges and large-scale PvP. ## Features - **No transcode, no drift.** A caller's Opus packets are forwarded exactly as their client encoded them, so every party hears the same audio at the same moment. Only when several people talk at once is anything mixed. More: https://www.nocapbots.com/docs/voice-relay/how-it-works.md - **Scales with your guild.** From four parties up to 24-channel alliances. Each party channel gets its own speaker bot, so your players stay in their party and talk like normal while the caller comes through on top. More: https://www.nocapbots.com/docs/voice-relay/speaker-bots.md - **Nothing to install.** It runs inside Discord. No overlay, no driver, no second voice client for your members to configure an hour before a siege. More: https://www.nocapbots.com/docs/voice-relay/getting-started.md - **Talk back.** Party leaders with Priority Speaker hold their priority key to reach the caller. Their normal key stays in their squad, and other squads never hear it. More: https://www.nocapbots.com/docs/voice-relay/talk-back.md - **Voice priority and teams.** Pick which roles get broadcast, with a backup caller. Voice teams run attack and defense at once, each side hearing only its own caller. More: https://www.nocapbots.com/docs/voice-relay/voice-teams.md - **Cross-server relay.** Link two servers with a single-use invite code. Your caller reaches speaker channels on both, and the allied server gets Guild Master free. More: https://www.nocapbots.com/docs/voice-relay/alliances.md Guilds use it in games like Throne and Liberty, Black Desert, World of Warcraft, Guild Wars 2, New World, Aion 2, Albion Online, Elder Scrolls Online, EVE Online, Where Winds Meet. ## Voice Relay plans Source: https://www.nocapbots.com/pricing | Plan | Speaker channels | Price | Cross-server | | --- | --- | --- | --- | | Squad Leader | 4 | $5/month | No | | Raid Commander | 8 | $8/month | No | | Guild Master | 12 | $15/month | No | | Alliance | 24 | $25/month | Yes: links a second server, which gets Guild Master free | Every plan includes voice priority filtering, talk back and voice teams, and starts with a 7-day free trial. Subscriptions are per Discord server and billed monthly through Whop. ## Voice Relay questions ### What does NoCap Bots do? It relays one caller's voice into several Discord voice channels at the same time. Your caller talks in a shot caller channel, and a speaker bot in each party channel plays it, so every squad hears the call without leaving its own channel. See [how it works](https://www.nocapbots.com/docs/voice-relay/how-it-works.md). ### Is Voice Relay a caller bot for guilds? Yes. A caller bot carries the shot caller's voice to everyone who needs it, and Voice Relay does it for gaming guilds: one bot listens in your callers' channel and a speaker bot in each party channel plays the call. See the layout and plan for your game in [Voice Relay by game](https://www.nocapbots.com/games). ### Why can't Discord do this on its own? Discord only sends your voice to the channel you are in, and a bot can hold one voice connection per server. Reaching six channels at once takes six speaker bots plus one bot listening to the callers, which is what NoCap Bots runs for you. ### Do my players need to install anything? No. Everything runs inside Discord. Players stay in their party channel and talk like normal; the caller comes through on top. Only party leaders who want to [talk back](https://www.nocapbots.com/docs/voice-relay/talk-back.md) need the Discord desktop app. ### How many channels can one caller reach? Up to 4 on Squad Leader, 8 on Raid Commander, 12 on Guild Master and 24 on Alliance, which can also link a second server. See [pricing](https://www.nocapbots.com/pricing). ### Is there a delay? About a tenth to three tenths of a second. Audio is forwarded without re-encoding whenever one person is talking, so there is no quality loss either. ### Can party leaders talk back to the caller? Yes. Give your party leader role Discord's Priority Speaker permission. A leader's priority push-to-talk key reaches their squad and the caller; their normal key stays in their squad. See [talk back](https://www.nocapbots.com/docs/voice-relay/talk-back.md). ### Can two callers run at the same time? Yes, with [voice teams](https://www.nocapbots.com/docs/voice-relay/voice-teams.md): for example one caller for attack and one for defense, each heard only by their own channels, while an overall commander on no team is heard everywhere. ### Does it work across two Discord servers? Yes. On the Alliance plan you link a second server with a single-use invite code, and `/start-cross-server` sends your caller to both servers' speaker channels. See [alliances](https://www.nocapbots.com/docs/voice-relay/alliances.md). ### Which games does it work with? Any game, because it works at the Discord level. Guilds use it for raids, sieges, node wars and large-scale PvP in games like Throne and Liberty, Black Desert, World of Warcraft, Guild Wars 2 and Albion Online. ### Is Voice Relay still in beta? Yes. Every feature on this page works today, and we are still tuning it with the guilds that use it, so expect small changes along the way. If something sounds off, [troubleshooting](https://www.nocapbots.com/docs/voice-relay/troubleshooting.md) covers the usual snags. ### Is there a free trial? Every plan starts with a 7-day free trial, and you can cancel from the Subscription page before it ends. See [billing](https://www.nocapbots.com/docs/billing.md). ### Is the subscription per server or per person? Per Discord server. The plan sets how many speaker channels that server can relay into at once, and everyone in the server benefits. ### What counts as a speaker channel? Each party voice channel the caller's voice is relayed into. The shot caller channel, where your callers talk, doesn't count. Each one has its own [speaker bot](https://www.nocapbots.com/docs/voice-relay/speaker-bots.md). ### What happens when the trial ends? The plan is billed monthly through Whop. Cancel before the trial ends and you aren't charged; cancel later and the relay keeps working until the end of the period. ### Can I change plans later? Yes, from the Subscription page. The old plan runs to the end of its period, so nobody pays twice. See [billing](https://www.nocapbots.com/docs/billing.md#manage). ### How does the Alliance plan's second server work? You send another server a single-use invite code. Once it joins, it gets Guild Master — 12 speaker channels — free, and either server can start a cross-server relay. See [alliances](https://www.nocapbots.com/docs/voice-relay/alliances.md). ### Can I move my plan to a different server? Yes. **Transfer subscription** in the server's side menu moves it to another server you run. See [moving to a new server](https://www.nocapbots.com/docs/billing.md#moving). # Attendance (beta) Source: https://www.nocapbots.com/attendance > Attendance notes who was in your voice channels during a fight and for how long, then saves a list you can export for payouts, regears and loot. It runs on its own or alongside Voice Relay. Free while in beta. ## How it works 1. **Start it.** Type `/attendance-start` before the fight, or let it start by itself when [Voice Relay](https://www.nocapbots.com/voice-relay) goes live. Everyone already in voice is counted from then. 2. **Fight.** Joins, leaves, party moves and deafens are noted as they happen. A Discord reconnect under two minutes doesn't cost anyone their time. 3. **Save and export.** `/attendance-stop` saves the fight. Open it on the dashboard and download the CSV for your payout, regear or loot sheet. ## What counts - **Counted after half the fight.** Or any share you pick, from 1% to 100%. Everyone who was in at all is still listed, with their minutes. - **Your channels, not the lounge.** Every voice channel but AFK, the channels you pick, or the relay's own channels when it follows Voice Relay. - **Deafened isn't present.** Deafened time is always shown, and you can leave it out of what counts. - **Members only.** Count only people with your member role, so visitors and allies stay off the list. - **Rules that don't move.** Each fight keeps the rules it was taken with, so a fight people were paid for never changes. - **Officers, not admins.** Give payout officers the Attendance permission and nothing else. ## Attendance questions ### What does beta mean for Attendance? It works, and it's free while we finish it with the guilds trying it. Counting rules and the dashboard may still change, and we'll say before it gets a price. Tell us what your payouts need — it shapes what Attendance becomes. ### Do I need Voice Relay? No. Attendance runs on its own with `/attendance-start` and `/attendance-stop`. If you do use [Voice Relay](https://www.nocapbots.com/voice-relay), it can start and stop with the relay and count the relay's channels. ### Does the bot join voice to take attendance? No. Discord already tells the Callout bot who joins, leaves and moves between voice channels, so it never joins a channel or hears anything for attendance. It needs no permissions beyond the [three it already asks for](https://www.nocapbots.com/docs/permissions.md). ### How does it decide who counts? Someone counts when they were in a counted channel for at least 50% of the fight, or the share you set. Short drops are bridged and party moves are one stretch — the details are in [how attendance counts](https://www.nocapbots.com/docs/attendance/counting-rules.md). ### Who can see the lists? The server's owner, and managers you give the Attendance permission — see [managers](https://www.nocapbots.com/docs/managers.md#permissions). Members can type `/attendance` to see their own time in the last fight. ### How long are fights kept? 90 days, then they're deleted. You can delete one fight, or all of them, from the dashboard any time. # Documentation ## Set up Voice Relay from an empty Discord server Source: https://www.nocapbots.com/docs/voice-relay/getting-started Last updated: 2026-11-07 > You need a Discord account, Manage Server on your server and at least two voice channels. Make a caller channel and one channel per party, invite the Callout bot, pick your roles and speaker channels on the dashboard, then type `/start` in any text channel. ### Before you start - A Discord account with **Manage Server** on the server you want to set up — see [who can set up a server](https://www.nocapbots.com/docs/permissions.md#who-can-set-up). - At least two voice channels: one for your callers and one per party. - A few minutes. Nothing to install, and no bot tokens to handle. ### Steps 1. **Make the channels.** Create one voice channel for your callers — call it command, officers, whatever fits; several callers in it is fine — and one voice channel per party: Alpha, Bravo, Charlie… Starting from an empty server? Copy the [gaming guild server template](https://www.nocapbots.com/templates/gaming-guild-discord-server), or the layout for [your game](https://www.nocapbots.com/games). 2. **Make a caller role.** In Server Settings → Roles, create a role for the people running comms, for example Shot Caller. Don't use @everyone or a general member role, or anyone can broadcast. 3. **Log in and pick a plan.** Open the [dashboard](https://www.nocapbots.com/dashboard) and log in with Discord. It lists the servers where you have Manage Server. Pick a plan by how many channels you need at once — see [pricing](https://www.nocapbots.com/pricing). Every plan starts with a 7-day free trial. 4. **Invite the bot, then check status.** Click **Invite bot** and authorise it. It asks for three permissions: View Channels, Connect and Speak. Back on the dashboard, click **Check status**; once it says connected you land on the configuration page. 5. **Set roles and the shot caller channel.** Pick the **starter role** (who can run /start and /stop), the **shot caller channel** and the **primary** and **backup** caller roles. The page saves by itself. Details in [configuration](https://www.nocapbots.com/docs/voice-relay/configuration.md). 6. **Add speaker bots.** Each speaker slot has its own **Invite bot** button. Invite them, hit **Refresh**, then pick a voice channel for each. See [speaker bots](https://www.nocapbots.com/docs/voice-relay/speaker-bots.md). 7. **Type /start.** In any text channel, type `/start`. The speaker bots join their channels; your caller talks in the shot caller channel and every party hears them. `/stop` sends the bots home. All commands are in the [command reference](https://www.nocapbots.com/docs/voice-relay/commands.md). ### What next - Let party leaders reach the caller with [talk back](https://www.nocapbots.com/docs/voice-relay/talk-back.md). - Run attack and defense calls at the same time with [voice teams](https://www.nocapbots.com/docs/voice-relay/voice-teams.md). - Link a second server with an [alliance](https://www.nocapbots.com/docs/voice-relay/alliances.md). - Something not working? Start at [troubleshooting](https://www.nocapbots.com/docs/voice-relay/troubleshooting.md). ### Related guides - [Configure roles, channels and voice priority](https://www.nocapbots.com/docs/voice-relay/configuration.md): The Voice Relay configuration page explained: starter role, shot caller channel, primary and backup caller roles, and the four things /start needs. - [Speaker bots: one bot per party channel](https://www.nocapbots.com/docs/voice-relay/speaker-bots.md): How the Callout speaker bots work: one slot per channel on your plan, an invite button each, picking channels, private channels and stage channels. - [Voice Relay slash commands](https://www.nocapbots.com/docs/voice-relay/commands.md): Every Callout slash command: /start, /stop, /status, /ping, /start-cross-server and /stop-cross-server, and who can use them. - [Troubleshooting Voice Relay](https://www.nocapbots.com/docs/voice-relay/troubleshooting.md): Fix common Voice Relay problems: /start won't run, nobody hears the caller, a bot can't access a channel, a full channel, an offline bot or a dead priority key. ## How Voice Relay carries Discord voice Source: https://www.nocapbots.com/docs/voice-relay/how-it-works Last updated: 2026-11-06 > Discord only sends your voice to the channel you are in, and a bot can hold one voice connection per server. So the Callout bot listens in your caller's channel and one speaker bot per party channel plays what it hears. Audio is forwarded without re-encoding, adding about 0.1–0.3 seconds. ### Why it takes bots Discord sends your voice only to the voice channel you are sitting in, and a bot account can hold exactly one voice connection per server. Reaching six party channels at once therefore takes six bots in voice, plus one more listening to the callers. On the hosted service those bots are ours; if you run it yourself, each is its own Discord application — see [self-hosting](https://www.nocapbots.com/docs/self-hosting.md#bots). - The **Callout bot** sits in the shot caller channel, undeafened, and listens to the callers. - One **speaker bot** per party channel plays whatever the callers say. - Players stay in their own party and talk like normal; the caller comes through on top. ### The audio path When one person is talking to a channel — the common case — their Opus audio packets are forwarded exactly as their Discord client encoded them. Nothing is decoded or re-encoded, so there is no quality loss and almost no processing. Only when several voices reach the same channel at once (two [voice teams](https://www.nocapbots.com/docs/voice-relay/voice-teams.md) callers, or several leaders using [talk back](https://www.nocapbots.com/docs/voice-relay/talk-back.md)) are they decoded, mixed and encoded once. A short jitter buffer smooths out Discord's bursty packet delivery so callouts don't stutter. ### Latency Expect about a tenth to three tenths of a second between the caller speaking and the parties hearing it. Over a second is not normal — see [troubleshooting](https://www.nocapbots.com/docs/voice-relay/troubleshooting.md). ### Who is heard where | Setting | Effect | | --- | --- | | Voice priority filtering | Only people with the primary or backup caller role are relayed; primaries pre-empt backups. | | Voice teams | A channel on a team hears that team's callers; a channel on no team hears every caller. | | Talk back | A party leader's priority key reaches the callers; other parties don't hear it. | | Cross-server | The starting server's callers reach the speaker channels of both allied servers. | ### Related guides - [Set up Voice Relay from an empty Discord server](https://www.nocapbots.com/docs/voice-relay/getting-started.md): Set up a Discord voice relay in about ten minutes: make the channels and a caller role, invite the bot, pick roles and speaker channels, then type /start. - [Configure roles, channels and voice priority](https://www.nocapbots.com/docs/voice-relay/configuration.md): The Voice Relay configuration page explained: starter role, shot caller channel, primary and backup caller roles, and the four things /start needs. - [Talk back: let party leaders reach the caller](https://www.nocapbots.com/docs/voice-relay/talk-back.md): Set up Discord Priority Speaker so party leaders can talk to the caller with a priority push-to-talk key while their normal key stays in their squad. - [Voice teams: run several callers at once](https://www.nocapbots.com/docs/voice-relay/voice-teams.md): Use Voice Relay's voice teams to run attack and defense callers at the same time, each heard only by their own speaker channels. ## Configure roles, channels and voice priority Source: https://www.nocapbots.com/docs/voice-relay/configuration Last updated: 2026-11-08 > The configuration page saves by itself. Set a starter role (who can run /start and /stop), the shot caller channel the bot listens to, and the primary and backup roles whose voices get broadcast. /start needs a shot caller channel, a speaker channel, a starter role and a caller role. ### Starter role Whoever has the starter role can control the bot with `/start` and `/stop`. People with Manage Server can always control it too. `/status` and `/ping` are open to everyone — see the [command reference](https://www.nocapbots.com/docs/voice-relay/commands.md). ### Shot caller channel The voice channel the Callout bot listens to. Your callers talk here, and more than one caller in it is fine. If the channel is private, give the bots' role View Channel, Connect and Speak there, as described in [speaker bots](https://www.nocapbots.com/docs/voice-relay/speaker-bots.md#private-channels). ### Voice priority filtering These are the roles that actually get broadcast. When someone with one of them talks in the shot caller channel, it goes out to your parties. You can pick two: - **Primary** — always relayed, and takes priority. - **Backup** — relayed while nobody with the primary role is talking. > **Note: If a caller isn't coming through, look here first.** Someone in the shot caller channel without the primary or backup role is not relayed. Don't use @everyone or a general member role, or anyone can broadcast. ### Saving and Refresh Everything saves by itself — there is no save button. If you add a role or channel in Discord and it isn't listed, hit **Refresh** at the top of the page. A running relay picks changes up within a few seconds: it joins new party channels, leaves removed ones, and applies [voice teams](https://www.nocapbots.com/docs/voice-relay/voice-teams.md) and caller roles straight away. [Cross-server relays](https://www.nocapbots.com/docs/voice-relay/alliances.md) are the exception — `/stop-cross-server` and start them again. ### What /start needs - A shot caller channel. - At least one speaker channel that is switched on. - A starter role. - A shot caller role (primary or backup). ### Related guides - [Speaker bots: one bot per party channel](https://www.nocapbots.com/docs/voice-relay/speaker-bots.md): How the Callout speaker bots work: one slot per channel on your plan, an invite button each, picking channels, private channels and stage channels. - [Voice teams: run several callers at once](https://www.nocapbots.com/docs/voice-relay/voice-teams.md): Use Voice Relay's voice teams to run attack and defense callers at the same time, each heard only by their own speaker channels. - [Voice Relay slash commands](https://www.nocapbots.com/docs/voice-relay/commands.md): Every Callout slash command: /start, /stop, /status, /ping, /start-cross-server and /stop-cross-server, and who can use them. - [Troubleshooting Voice Relay](https://www.nocapbots.com/docs/voice-relay/troubleshooting.md): Fix common Voice Relay problems: /start won't run, nobody hears the caller, a bot can't access a channel, a full channel, an offline bot or a dead priority key. ## Speaker bots: one bot per party channel Source: https://www.nocapbots.com/docs/voice-relay/speaker-bots Last updated: 2026-11-08 > You get one speaker slot for each channel on your plan. Invite each speaker bot from its own button, hit Refresh, then pick a normal voice channel for it. For private channels, give the bots a role with View Channel, Connect and Speak. ### One slot per channel Your plan sets how many speaker slots you get: 4 on Squad Leader, 8 on Raid Commander, 12 on Guild Master and 24 on Alliance — see [pricing](https://www.nocapbots.com/pricing). Each slot is its own bot, because a bot can be in only one voice channel per server — [how it works](https://www.nocapbots.com/docs/voice-relay/how-it-works.md#why-bots) explains why. ### Invite each bot 1. **Invite.** Slots that say **needs an invite** have their own **Invite bot** button. Authorise it, come back, and do the next one. You only do this once. 2. **Refresh.** Hit **Refresh** so the dashboard sees the new bots. 3. **Pick channels.** Pick a voice channel for each bot: this one's Alpha, this one's Bravo, and so on. ### Which channels work - Use normal voice channels, not stage channels. - Keep speakers away from channels your music bots use. - Each channel can have only one speaker bot. - If a channel has a user limit and it is full, the bot can't get in — raise the limit. ### Switching a speaker off The switch next to each speaker turns it off without losing its channel. A running relay picks the change up within a few seconds. ### Private channels Bots can't see private channels until you let them in. Make a role for the bots and give it to all of them. Then, on your private channels — or the whole category — allow **View Channel**, **Connect** and **Speak** for that role. Do the same on the [shot caller channel](https://www.nocapbots.com/docs/voice-relay/configuration.md#shot-caller-channel) if it is private. ### Related guides - [Configure roles, channels and voice priority](https://www.nocapbots.com/docs/voice-relay/configuration.md): The Voice Relay configuration page explained: starter role, shot caller channel, primary and backup caller roles, and the four things /start needs. - [Troubleshooting Voice Relay](https://www.nocapbots.com/docs/voice-relay/troubleshooting.md): Fix common Voice Relay problems: /start won't run, nobody hears the caller, a bot can't access a channel, a full channel, an offline bot or a dead priority key. - [Plans, billing and transfers](https://www.nocapbots.com/docs/billing.md): NoCap Bots plans and billing: free trial, upgrading, cancelling, payment details, moving a subscription to a new server and server transfer requests. - [How Voice Relay carries Discord voice](https://www.nocapbots.com/docs/voice-relay/how-it-works.md): Why Discord voice needs bots to reach several channels, how the speaker bots relay audio with no transcoding, and what latency to expect. ## Talk back: let party leaders reach the caller Source: https://www.nocapbots.com/docs/voice-relay/talk-back Last updated: 2026-11-06 > Talk back is already on. Give your party leader role Priority Speaker, and have each leader set up push-to-talk with two keybinds: normal goes to their squad, priority goes to their squad and the caller. It needs the Discord desktop app. ### Server setup There is nothing to set on the dashboard. In Server Settings → Roles, pick your party leader role and turn on **Priority Speaker**. To limit it to certain channels, leave the role alone and allow Priority Speaker for that role on those channels instead. ### Each leader's setup 1. **Push to talk.** In User Settings → Voice & Video, switch on push-to-talk and raise the release delay a little so their last word isn't cut off. 2. **Normal key.** In Keybinds, add **Push to Talk (Normal)** and record a key — for example mouse 4. 3. **Priority key.** Add **Push to Talk (Priority)** and record another key — for example mouse 5. Now the normal key goes to their squad, and the priority key goes to their squad **and** the caller. Other squads don't hear it. ### Several leaders at once If a few leaders press their priority key together, their voices are mixed so nobody gets cut off. If it is too loud for the caller, they can right-click the Callout bot and turn it down. With [voice teams](https://www.nocapbots.com/docs/voice-relay/voice-teams.md) on, every caller in the shot caller channel hears talk back. > **Tip: Desktop only.** Priority Speaker doesn't work on mobile, so leaders need the Discord desktop app. ### Related guides - [Voice teams: run several callers at once](https://www.nocapbots.com/docs/voice-relay/voice-teams.md): Use Voice Relay's voice teams to run attack and defense callers at the same time, each heard only by their own speaker channels. - [Troubleshooting Voice Relay](https://www.nocapbots.com/docs/voice-relay/troubleshooting.md): Fix common Voice Relay problems: /start won't run, nobody hears the caller, a bot can't access a channel, a full channel, an offline bot or a dead priority key. - [How Voice Relay carries Discord voice](https://www.nocapbots.com/docs/voice-relay/how-it-works.md): Why Discord voice needs bots to reach several channels, how the speaker bots relay audio with no transcoding, and what latency to expect. - [Configure roles, channels and voice priority](https://www.nocapbots.com/docs/voice-relay/configuration.md): The Voice Relay configuration page explained: starter role, shot caller channel, primary and backup caller roles, and the four things /start needs. ## Voice teams: run several callers at once Source: https://www.nocapbots.com/docs/voice-relay/voice-teams Last updated: 2026-11-08 > Voice teams let more than one caller run at the same time — say one calling attack and another defense — and each side hears only its own caller. A channel on no team hears every caller, and a caller on no team is heard everywhere. Changes reach a running relay straight away. ### Set up teams 1. **Speaker channels first.** Set up your [speaker bots](https://www.nocapbots.com/docs/voice-relay/speaker-bots.md) first, because teams pick from those channels. 2. **Add a team.** Switch on **Voice teams** and click **Add team**. Name it — Attack — and pick who calls it by role, and its channels. 3. **Repeat.** Do the same for Defense. A channel can only be on one team, and you get up to one team per speaker slot. ### Two rules to remember - A channel with no team hears every caller. - A caller with no team is heard by everyone — perfect for your overall commander. Callers stay together in the shot caller channel, so they can hear each other and coordinate. Callers still need a [voice priority role](https://www.nocapbots.com/docs/voice-relay/configuration.md#voice-priority-filtering) to be relayed at all, and [talk back](https://www.nocapbots.com/docs/voice-relay/talk-back.md) reaches every caller. > **Note: Changes apply while it runs.** Save a change and a running relay picks it up within a few seconds, callers mid-sentence included — no `/stop` and `/start`. Cross-server relays ignore teams — see [alliances](https://www.nocapbots.com/docs/voice-relay/alliances.md). ### Related guides - [Talk back: let party leaders reach the caller](https://www.nocapbots.com/docs/voice-relay/talk-back.md): Set up Discord Priority Speaker so party leaders can talk to the caller with a priority push-to-talk key while their normal key stays in their squad. - [Configure roles, channels and voice priority](https://www.nocapbots.com/docs/voice-relay/configuration.md): The Voice Relay configuration page explained: starter role, shot caller channel, primary and backup caller roles, and the four things /start needs. - [Alliances: relay across two Discord servers](https://www.nocapbots.com/docs/voice-relay/alliances.md): Link two Discord servers with a single-use invite code so one caller reaches the speaker channels of both. The allied server gets Guild Master free. - [Voice Relay slash commands](https://www.nocapbots.com/docs/voice-relay/commands.md): Every Callout slash command: /start, /stop, /status, /ping, /start-cross-server and /stop-cross-server, and who can use them. ## Alliances: relay across two Discord servers Source: https://www.nocapbots.com/docs/voice-relay/alliances Last updated: 2026-11-06 > On the Alliance plan you can link a second server. Create a single-use invite code, send it to the other admin, and they paste it in. Their server gets Guild Master — 12 speakers — free. Then /start-cross-server sends your caller to both servers' speaker channels. ### Link two servers 1. **Create a code.** On the Alliance page, click **Create invite code** and send it to the other server's admin. It only works once, so send it to someone you trust; if it gets out, **Regenerate code** or **Cancel invite**. 2. **Join.** The other admin logs in, picks their server, opens Alliance, clicks **I have an invite code** and pastes it in. 3. **Set up the ally.** They set their server up like any other — bots, roles, speaker channels. See [getting started](https://www.nocapbots.com/docs/voice-relay/getting-started.md). If the other server already pays for its own subscription, it has to cancel first, because the alliance covers it. See [billing](https://www.nocapbots.com/docs/billing.md). ### Cross-server relays When it's time for the big fight, type `/start-cross-server`. The caller in the server that starts it goes out to speaker channels on both servers, and party leaders on both can [talk back](https://www.nocapbots.com/docs/voice-relay/talk-back.md). Either server can start it; `/stop-cross-server` ends it. Cross-server ignores [voice teams](https://www.nocapbots.com/docs/voice-relay/voice-teams.md), so everyone hears the caller; your teams stay saved for normal relays. ### Ending an alliance The owner clicks **Disband alliance**, or the other server clicks **Leave alliance**. Either way the allied server loses the free plan. If the owner's Alliance plan lapses, the link pauses. ### Related guides - [Plans, billing and transfers](https://www.nocapbots.com/docs/billing.md): NoCap Bots plans and billing: free trial, upgrading, cancelling, payment details, moving a subscription to a new server and server transfer requests. - [Voice Relay slash commands](https://www.nocapbots.com/docs/voice-relay/commands.md): Every Callout slash command: /start, /stop, /status, /ping, /start-cross-server and /stop-cross-server, and who can use them. - [Voice teams: run several callers at once](https://www.nocapbots.com/docs/voice-relay/voice-teams.md): Use Voice Relay's voice teams to run attack and defense callers at the same time, each heard only by their own speaker channels. - [Managers: share the dashboard with your officers](https://www.nocapbots.com/docs/managers.md): Invite managers to a NoCap Bots server by email or Discord username and choose what they can touch: configuration, billing or other managers. ## Permissions and privacy: what NoCap Bots can access Source: https://www.nocapbots.com/docs/permissions Last updated: 2026-11-06 > Signing in shares your username, avatar, server list and verified email — never your messages. The bots need only View Channels, Connect and Speak. Anyone with Manage Server can set a server up, and you can take any of it back from Discord. ### Signing in with Discord You sign in on Discord's own page, so NoCap Bots never sees your password. Discord asks you to share three things: | Discord scope | What NoCap Bots uses it for | | --- | --- | | `identify` | Your username and avatar, to show who's signed in. | | `guilds` | The servers you're in and whether you can manage each, so the dashboard lists the right ones. | | `email` | Your verified email, only so a server owner can invite you as a [manager](https://www.nocapbots.com/docs/managers.md). | That's all. NoCap Bots can't read your messages or DMs, join servers for you, or post as you — it never asks for those. ### What the bots can do | Bot permission | Why | | --- | --- | | View Channels | To see the voice channels you pick. | | Connect | To join the callers' channel and your party channels. | | Speak | So the speaker bots can play the call into party channels. | Nothing else: no Administrator, no managing roles or members, no reading messages. The Callout bot's invite also adds its slash commands. For private channels, give the bots' role these three permissions there — see [private channels](https://www.nocapbots.com/docs/voice-relay/speaker-bots.md#private-channels). ### Who can set up a server - The server's owner, and anyone with **Manage Server** or **Administrator** in Discord, sees it on their dashboard. - Whoever sets it up first owns it on NoCap Bots. Another admin can [request a transfer](https://www.nocapbots.com/docs/billing.md#server-transfers). - Anyone else needs the owner to invite them as a [manager](https://www.nocapbots.com/docs/managers.md). > **Tip: Server not on your dashboard?.** You need Manage Server there. Once an admin gives it to you, the dashboard picks it up within a minute. ### Who can do what | Who | Can | | --- | --- | | Owner | Everything, including billing and managers. | | Manager | What the owner allows: configuration, billing or managers — see [manager permissions](https://www.nocapbots.com/docs/managers.md#permissions). | | Starter role | Run `/start` and `/stop`. | | Primary and backup caller roles | Be relayed to every party — see [voice priority](https://www.nocapbots.com/docs/voice-relay/configuration.md#voice-priority-filtering). | | Priority Speaker | Reach the callers with [talk back](https://www.nocapbots.com/docs/voice-relay/talk-back.md). | | Everyone | Run `/status` and `/ping`. | ### Taking it back 1. **Sign out.** From the menu under your avatar. That ends the session in this browser. 2. **Remove the app.** In Discord, User Settings → Authorized Apps, remove Callout. It can no longer read your profile or server list. 3. **Remove the bots.** Kick the Callout bot and its speaker bots from your server, or take the permissions away from their role. 4. **Delete your account.** Account → Delete account removes what NoCap Bots stores about you. Cancel any subscription first — see [your account](https://www.nocapbots.com/docs/billing.md#account). ### Related guides - [Managers: share the dashboard with your officers](https://www.nocapbots.com/docs/managers.md): Invite managers to a NoCap Bots server by email or Discord username and choose what they can touch: configuration, billing or other managers. - [Speaker bots: one bot per party channel](https://www.nocapbots.com/docs/voice-relay/speaker-bots.md): How the Callout speaker bots work: one slot per channel on your plan, an invite button each, picking channels, private channels and stage channels. - [Plans, billing and transfers](https://www.nocapbots.com/docs/billing.md): NoCap Bots plans and billing: free trial, upgrading, cancelling, payment details, moving a subscription to a new server and server transfer requests. - [Troubleshooting Voice Relay](https://www.nocapbots.com/docs/voice-relay/troubleshooting.md): Fix common Voice Relay problems: /start won't run, nobody hears the caller, a bot can't access a channel, a full channel, an offline bot or a dead priority key. ## Managers: share the dashboard with your officers Source: https://www.nocapbots.com/docs/managers Last updated: 2026-11-06 > Invite managers from the Members page by email or Discord username and pick what they can touch: configuration, billing, managing other managers, or attendance. They must have logged into NoCap Bots once. They show as pending until they accept on their dashboard. ### Invite a manager 1. **Have them log in once.** They need to have logged into NoCap Bots with Discord at least once, or it won't find them. 2. **Invite.** On the Members page, enter their email or Discord username and pick what they can touch. 3. **They accept.** They show up as pending and get a notification. Once they accept on their dashboard, they have access. ### Permissions | Permission | Lets them | | --- | --- | | Configuration | Change roles, channels, speaker bots, voice teams and the alliance, and start or stop the relay. | | Billing | Change plans, update payment details and cancel — see [billing](https://www.nocapbots.com/docs/billing.md). | | Managers | Invite, edit and remove managers who don't hold more than they do. | | Attendance | See and export fights, start and stop them, and change [attendance](https://www.nocapbots.com/docs/attendance/track-a-fight.md) settings. | ### Who owns a server Whoever first sets a server up on NoCap Bots owns it there. Another Discord admin can't take it over, but can request a transfer, which the owner approves or denies — see [server transfers](https://www.nocapbots.com/docs/billing.md#server-transfers). ### Related guides - [Plans, billing and transfers](https://www.nocapbots.com/docs/billing.md): NoCap Bots plans and billing: free trial, upgrading, cancelling, payment details, moving a subscription to a new server and server transfer requests. - [Configure roles, channels and voice priority](https://www.nocapbots.com/docs/voice-relay/configuration.md): The Voice Relay configuration page explained: starter role, shot caller channel, primary and backup caller roles, and the four things /start needs. - [Alliances: relay across two Discord servers](https://www.nocapbots.com/docs/voice-relay/alliances.md): Link two Discord servers with a single-use invite code so one caller reaches the speaker channels of both. The allied server gets Guild Master free. - [Set up Voice Relay from an empty Discord server](https://www.nocapbots.com/docs/voice-relay/getting-started.md): Set up a Discord voice relay in about ten minutes: make the channels and a caller role, invite the bot, pick roles and speaker channels, then type /start. ## Plans, billing and transfers Source: https://www.nocapbots.com/docs/billing Last updated: 2026-11-06 > Plans are per Discord server and priced by how many speaker channels you need: $5 for 4, $8 for 8, $15 for 12 and $25 for 24. Every plan starts with 7 days free. Payments go through Whop; you can change plan, cancel or resume, and move a subscription to a new server. ### Plans | Plan | Speaker channels | Price | | --- | --- | --- | | Squad Leader | 4 | $5 / month | | Raid Commander | 8 | $8 / month | | Guild Master | 12 | $15 / month | | Alliance | 24, plus a linked server | $25 / month | All plans get [voice teams](https://www.nocapbots.com/docs/voice-relay/voice-teams.md), [talk back](https://www.nocapbots.com/docs/voice-relay/talk-back.md) and everything else; the only question is how many channels you need at once. Compare them on the [pricing page](https://www.nocapbots.com/pricing). ### Managing a subscription - **Upgrade or downgrade** from the Subscription page. The old plan runs to the end of its period, so nobody pays twice. - **Change payment details** opens Whop's page for your membership. - **Cancel** keeps the relay working until the end of the period; **Resume** takes it back. - A failed payment stops the relay until the card is updated. The owner can do all of this, and so can [managers](https://www.nocapbots.com/docs/managers.md#permissions) given the billing permission. ### Moving to a new Discord server **Transfer subscription** in the side menu moves your plan to another server you run. The old server is left without one. ### Server transfers If someone else already has your server on NoCap Bots, request a transfer. They see it under **Server transfers** in their account settings and can approve or deny it. Their plan runs to the end of its period and then stops; you pick your own. ### Your account Your profile comes from Discord. In account settings you can set privacy preferences, request a copy of your data and delete your account — after cancelling any active subscriptions. ### Related guides - [Managers: share the dashboard with your officers](https://www.nocapbots.com/docs/managers.md): Invite managers to a NoCap Bots server by email or Discord username and choose what they can touch: configuration, billing or other managers. - [Alliances: relay across two Discord servers](https://www.nocapbots.com/docs/voice-relay/alliances.md): Link two Discord servers with a single-use invite code so one caller reaches the speaker channels of both. The allied server gets Guild Master free. - [Speaker bots: one bot per party channel](https://www.nocapbots.com/docs/voice-relay/speaker-bots.md): How the Callout speaker bots work: one slot per channel on your plan, an invite button each, picking channels, private channels and stage channels. - [Set up Voice Relay from an empty Discord server](https://www.nocapbots.com/docs/voice-relay/getting-started.md): Set up a Discord voice relay in about ten minutes: make the channels and a caller role, invite the bot, pick roles and speaker channels, then type /start. ## Voice Relay slash commands Source: https://www.nocapbots.com/docs/voice-relay/commands Last updated: 2026-11-06 > /start and /stop control the relay and need the starter role (or Manage Server). /status shows whether it's live and how many callers are speaking; /ping shows latency and your subscription — anyone can use those. /start-cross-server and /stop-cross-server run alliance relays. ### Commands | Command | Who | What it does | | --- | --- | --- | | `/start` | Starter role | Speaker bots join their channels and the relay goes live. | | `/stop` | Starter role | Every bot leaves. | | `/status` | Anyone | Whether it's live and how many callers are speaking. | | `/ping` | Anyone | Relay latency and the server's subscription. | | `/start-cross-server` | Starter role | Relay to the speaker channels of both [allied servers](https://www.nocapbots.com/docs/voice-relay/alliances.md). | | `/stop-cross-server` | Starter role | End the cross-server relay. | `/attendance-start`, `/attendance-stop` and `/attendance` belong to Attendance, in beta — see [tracking a fight](https://www.nocapbots.com/docs/attendance/track-a-fight.md#commands). ### What /start checks Before joining voice, `/start` checks the four requirements from [configuration](https://www.nocapbots.com/docs/voice-relay/configuration.md#requirements) and reports any channel a bot can't access or that is full. It won't start by itself — someone has to run it. ### Related guides - [Configure roles, channels and voice priority](https://www.nocapbots.com/docs/voice-relay/configuration.md): The Voice Relay configuration page explained: starter role, shot caller channel, primary and backup caller roles, and the four things /start needs. - [Troubleshooting Voice Relay](https://www.nocapbots.com/docs/voice-relay/troubleshooting.md): Fix common Voice Relay problems: /start won't run, nobody hears the caller, a bot can't access a channel, a full channel, an offline bot or a dead priority key. - [Alliances: relay across two Discord servers](https://www.nocapbots.com/docs/voice-relay/alliances.md): Link two Discord servers with a single-use invite code so one caller reaches the speaker channels of both. The allied server gets Guild Master free. - [Set up Voice Relay from an empty Discord server](https://www.nocapbots.com/docs/voice-relay/getting-started.md): Set up a Discord voice relay in about ten minutes: make the channels and a caller role, invite the bot, pick roles and speaker channels, then type /start. ## Troubleshooting Voice Relay Source: https://www.nocapbots.com/docs/voice-relay/troubleshooting Last updated: 2026-11-08 > Most problems are roles or permissions. Check the starter role for /start, the primary or backup caller role when nobody hears the caller, and View Channel, Connect and Speak when a bot can't get in. A delay of 0.1–0.3 seconds is normal. ### My server isn't on the dashboard You need Manage Server or Administrator on it in Discord, or an invite from its owner as a manager. See [who can set up a server](https://www.nocapbots.com/docs/permissions.md#who-can-set-up). ### It keeps asking me to sign in Your Discord sign-in lasts about a week. When it runs out, sign in again and you land back where you were. If you removed Callout under Authorized Apps in Discord, signing in adds it back — see [permissions](https://www.nocapbots.com/docs/permissions.md#revoke). ### /start won't run Check you have the [starter role](https://www.nocapbots.com/docs/voice-relay/configuration.md#starter-role), then the four things /start needs: a shot caller channel, a speaker channel, a starter role and a caller role. ### Nobody can hear the caller It's usually a role. Check the caller has the [primary or backup role](https://www.nocapbots.com/docs/voice-relay/configuration.md#voice-priority-filtering), they are actually in the shot caller channel, and the speaker channels are switched on. With [voice teams](https://www.nocapbots.com/docs/voice-relay/voice-teams.md) on, make sure the channel is on their team. ### /start says it can't access a channel The bot is missing Connect or Speak there. Go back to [private channels](https://www.nocapbots.com/docs/voice-relay/speaker-bots.md#private-channels). ### A party channel is full If a channel has a user limit and it is full, the bot can't get in. Raise the limit. ### The bot is offline Check it was invited, check your [subscription](https://www.nocapbots.com/docs/billing.md) is active, and try inviting it again from the dashboard. ### A leader's priority key does nothing Check they have Priority Speaker in that channel, they're on push-to-talk, they're using the priority keybind, and they're on the desktop app. See [talk back](https://www.nocapbots.com/docs/voice-relay/talk-back.md). ### Changes don't seem to work A running relay picks up saved changes within a few seconds. If it doesn't, check the change is complete: a relay with no shot caller channel or no party channel picked keeps running as it was. Cross-server relays keep their channels until you run `/stop-cross-server` and start them again. ### A party went quiet, or you heard a chime Discord sometimes drops a bot from voice. A speaker bot that drops rejoins its channel by itself, and the callers hear a falling chime when it drops and a rising one when it's back. If the Callout bot drops, every party channel hears the chime instead, because the callers can't be heard until it's back. Either way it keeps trying for about a minute; the dashboard and `/status` show what's rejoining. If it still can't get in, check it can see and join the channel, then run `/stop` and `/start`. ### It sounds delayed A tenth to three tenths of a second is normal. Over a second is not — come tell us in our Discord. More in [how it works](https://www.nocapbots.com/docs/voice-relay/how-it-works.md#latency). ### Related guides - [Configure roles, channels and voice priority](https://www.nocapbots.com/docs/voice-relay/configuration.md): The Voice Relay configuration page explained: starter role, shot caller channel, primary and backup caller roles, and the four things /start needs. - [Speaker bots: one bot per party channel](https://www.nocapbots.com/docs/voice-relay/speaker-bots.md): How the Callout speaker bots work: one slot per channel on your plan, an invite button each, picking channels, private channels and stage channels. - [Talk back: let party leaders reach the caller](https://www.nocapbots.com/docs/voice-relay/talk-back.md): Set up Discord Priority Speaker so party leaders can talk to the caller with a priority push-to-talk key while their normal key stays in their squad. - [Voice Relay slash commands](https://www.nocapbots.com/docs/voice-relay/commands.md): Every Callout slash command: /start, /stop, /status, /ping, /start-cross-server and /stop-cross-server, and who can use them. ## Self-host NoCap Bots Source: https://www.nocapbots.com/docs/self-hosting Last updated: 2026-11-06 > NoCap Bots is two processes: a Next.js dashboard and a relay engine that holds the Discord gateway and voice. Create one Discord application for the Callout bot and one per speaker slot, fill in .env.local, and run npm run bot and npm run dev. Whop billing is optional. ### Discord applications One bot account can hold one voice channel per server, so you need one application for the Callout bot plus one per speaker slot. In the Discord Developer Portal, create the main application, copy its client id, secret and bot token, and add `/api/auth/callback` as an OAuth2 redirect. Then create one more application per speaker slot and copy each bot token. ### Environment ``` DISCORD_CLIENT_ID=your_application_id DISCORD_CLIENT_SECRET=your_oauth_secret DISCORD_BOT_TOKEN=shotcaller_bot_token RELAY_BOT_TOKENS=speaker_token_1,speaker_token_2 AUTH_SECRET=run_openssl_rand_hex_32 CONTROL_SECRET=run_openssl_rand_hex_32 NEXT_PUBLIC_APP_URL=http://localhost:3000 ``` ### Run it ``` npm run bot # relay engine + control API on :8787 npm run dev # dashboard on :3000 ``` ### Billing with Whop Optional. Without Whop keys a plan is simply a setting. To charge, create four monthly plans with a 7-day trial in Whop, put their ids and your API key in the environment, point a webhook at `/api/billing/webhook`, and set `BILLING_REQUIRED=1`. How plans behave for your users is in [billing](https://www.nocapbots.com/docs/billing.md). ### Related guides - [How Voice Relay carries Discord voice](https://www.nocapbots.com/docs/voice-relay/how-it-works.md): Why Discord voice needs bots to reach several channels, how the speaker bots relay audio with no transcoding, and what latency to expect. - [Set up Voice Relay from an empty Discord server](https://www.nocapbots.com/docs/voice-relay/getting-started.md): Set up a Discord voice relay in about ten minutes: make the channels and a caller role, invite the bot, pick roles and speaker channels, then type /start. - [Plans, billing and transfers](https://www.nocapbots.com/docs/billing.md): NoCap Bots plans and billing: free trial, upgrading, cancelling, payment details, moving a subscription to a new server and server transfer requests. - [Voice Relay slash commands](https://www.nocapbots.com/docs/voice-relay/commands.md): Every Callout slash command: /start, /stop, /status, /ping, /start-cross-server and /stop-cross-server, and who can use them. ## Take attendance of a guild fight in Discord voice Source: https://www.nocapbots.com/docs/attendance/track-a-fight Last updated: 2026-11-08 > Run `/attendance-start` before the fight and `/attendance-stop` after it, or let attendance follow Voice Relay. Each fight is saved with everyone who was in voice and for how long, and downloads as a CSV for your payout sheet. Attendance is in beta and free. ### Track your first fight 1. **Invite the Callout bot.** Attendance listens through the same bot as Voice Relay, so if the relay works, you're set. It never joins voice for attendance and asks for no extra permissions — see [permissions](https://www.nocapbots.com/docs/permissions.md). 2. **Start before the fight.** Type `/attendance-start` in any text channel, with a name if you like: `/attendance-start name: Node war`. Everyone already in voice is counted from that moment. 3. **Fight.** Joins, leaves, party moves and deafens are noted as they happen. The Fights page on the dashboard fills in live. 4. **Stop and save.** Type `/attendance-stop`. The reply links to the saved fight, and everyone who can see attendance gets a notification. 5. **Export.** Open the fight on the dashboard and download the CSV: one row per member, with minutes, share of the fight and whether they counted. ### Let it follow Voice Relay With **Follow Voice Relay** on (it is by default), a fight starts when the relay goes live and stops when it does, counting the relay's own channels: the shot caller channel and every party channel. A relay that stops and starts again within two minutes carries on the same fight, and a party channel added to the running relay — see [configuration](https://www.nocapbots.com/docs/voice-relay/configuration.md) — counts from when it's added. A fight you started by hand is never ended by the relay. ### Commands | Command | Who | What it does | | --- | --- | --- | | `/attendance-start` | Starter role | Starts a fight, with an optional name. | | `/attendance-stop` | Starter role | Stops and saves it, and replies with a link to the list. | | `/attendance` | Anyone | The running or last fight, and your own time in it. The starter role also sees the totals. | The starter role is the one you picked for Voice Relay; Manage Server can always start and stop. The rest of the relay's commands are in [commands](https://www.nocapbots.com/docs/voice-relay/commands.md). ### On the dashboard - **Fights** shows the running fight, a button to start or stop one, and every saved fight. - **Members** adds up each member over the last 7, 30 or 90 days, with a CSV of that too. - **Settings** picks which channels and roles count and the share of the fight that counts — see [how attendance counts](https://www.nocapbots.com/docs/attendance/counting-rules.md). Officers who run payouts don't need access to anything else: give them the **Attendance** permission on the Members page — see [managers](https://www.nocapbots.com/docs/managers.md#permissions). ### If the bots restart mid-fight A running fight is saved every minute. If the engine stops during one, the fight ends at the last minute saved and is marked **cut short by a restart**. Start a new one to carry on. > **Tip: Name your fights.** The name shows in the list, in `/attendance` and in the CSV's file name, so "Node war" beats "Fight" when you add up payouts at the end of the month. You can rename a fight afterwards. ### Related guides - [How Attendance counts who was at a fight](https://www.nocapbots.com/docs/attendance/counting-rules.md): How Attendance decides who counts: share of the fight, short drops, party moves, deafened time, roles, channels and what is stored. - [Managers: share the dashboard with your officers](https://www.nocapbots.com/docs/managers.md): Invite managers to a NoCap Bots server by email or Discord username and choose what they can touch: configuration, billing or other managers. - [Voice Relay slash commands](https://www.nocapbots.com/docs/voice-relay/commands.md): Every Callout slash command: /start, /stop, /status, /ping, /start-cross-server and /stop-cross-server, and who can use them. ## How Attendance counts who was at a fight Source: https://www.nocapbots.com/docs/attendance/counting-rules Last updated: 2026-11-08 > Someone counts when they were in a counted voice channel for at least 50% of the fight; you can change the share. Drops under two minutes are bridged, moving between parties is one stretch, and bots and the AFK channel never count. Fights are kept for 90 days. ### The rule A member counts for a fight when they were in a counted voice channel for at least **50% of it**. Change the share in Settings, anywhere from 1% to 100%. Everyone who was in at all is still listed, with their minutes, so you can make your own call on the edge cases. ### Which channels count | The fight | Counts | | --- | --- | | Started by hand, no channels picked | Every voice channel except the server's AFK channel. | | Started by hand, channels picked | Only the channels picked in Settings. | | Following Voice Relay | The relay's shot caller channel and party channels in this server. | ### Drops, moves and late arrivals - **Drops under two minutes** — a Discord reconnect, a quick restart — don't break someone's time; the gap counts. - **Moving parties** is one stretch, and the list shows every channel they were in. - **Joining more than five minutes late** or **leaving more than five minutes early** gets a note with the time, in your own time zone. - **Bots** are never counted, including the Callout speaker bots. ### Deafened time Someone sitting deafened in the channel is usually away from the keyboard. Their deafened time is always shown; turn on **Leave out deafened time** to stop it counting. ### Only some roles Pick roles in Settings to count only members who hold one of them — your guild's member role, say — and leave visitors and allies out. A member is checked as they join a counted channel. ### Changing the rules Each fight keeps the rules it was taken with. Changing the share, the deafened setting or the roles applies from the next fight, so a fight people were already paid for never changes under you. ### The CSV | Column | What's in it | | --- | --- | | Member, Discord ID | Their display name at the time, and their ID, which never changes. | | Counted | Yes or no, by the fight's rule. | | Minutes, % of fight | Time that counts, and its share of the fight. | | Joined, Left | First and last time in a counted channel, in UTC. | | Channels | Every counted channel they were in. | | Deafened minutes | Time spent deafened while in a counted channel. | ### What's stored, and for how long For each fight: members' Discord IDs and display names, the counted channels' names, and when each person joined, left, moved or deafened. Nothing they say, and no messages. Fights are kept for **90 days**, then deleted; delete one, or all of them, from the dashboard any time. Only the owner and managers with the Attendance permission can see them. Start with [tracking a fight](https://www.nocapbots.com/docs/attendance/track-a-fight.md). ### Related guides - [Take attendance of a guild fight in Discord voice](https://www.nocapbots.com/docs/attendance/track-a-fight.md): Track who was in your Discord voice channels during a fight: start by hand or with Voice Relay, stop to save it, then export the list as a CSV. - [Managers: share the dashboard with your officers](https://www.nocapbots.com/docs/managers.md): Invite managers to a NoCap Bots server by email or Discord username and choose what they can touch: configuration, billing or other managers. # Voice Relay by game ## Discord voice comms for Albion Online ZvZ Source: https://www.nocapbots.com/games/albion-online Last updated: 2026-11-07 > Albion ZvZ fights are won on the shotcaller's timing and lost when half the zerg hears the bomb call late. Put your callers in one channel, keep every party in its own, and relay the call into all of them at once — party leads keep their own comms, and nobody misses the commit. ### The fights that need it - **ZvZ in the black zone** (Several parties a side). Alliances meet with a zerg on each side. The commit — when to bomb, when to reset — has to land in every party in the same second, or the fight is lost before it starts. - **Objective and territory fights** (The whole alliance). Timed objectives bring every guild in the alliance at once. Guilds that each run their own Discord can still follow one caller with a cross-server relay. - **Roams and smaller brawls** (One to four parties). A small-scale group with its own caller. The same setup works with fewer speaker channels, and a cheaper plan. ### A channel layout for Albion Online ``` COMMS 🔊 Command main caller, backup caller 🔊 Party 1 tanks and engage 🔊 Party 2 🔊 Party 3 🔊 Party 4 🔊 Party 5 🔊 Party 6 🔊 Party 7 healers 🔊 Scouts scouts report with their priority key ``` Every channel under Command gets a speaker bot. Scouts and party leads hold their Priority Speaker key to reach the callers; their normal key stays in their own channel. ### Recommended plan: Guild Master 12 speaker channels, $15/month, 7 days free. Seven parties and a scout channel is eight speaker channels, and alliance zergs grow past that fast. Guild Master covers twelve. Two guilds in separate Discords on the same call need the Alliance plan's cross-server relay. ### Calls that cut through a zerg Albion calls are short and absolute, because the caller is often reacting to the other zerg's movement rather than a plan. Keep them in the same order every time — who, what, when — so a party knows in one word whether the call is theirs. The structure is in [how to run voice comms for 100-player PvP](https://www.nocapbots.com/blog/voice-comms-for-large-scale-pvp.md). > Everyone, stack on me. Bomb on my call… bomb now. > > — The commit > Party 1, engage left. Healers, stay behind the tanks. > > — Splitting the zerg > Reset. Everyone back to the portal. > > — The call nobody can miss ### Name a backup caller Callers die first. Give a second officer the **backup caller** role: they are relayed only while the primary is quiet, so the hand-over doesn't need anyone to ask who's calling. See [voice priority filtering](https://www.nocapbots.com/docs/voice-relay/configuration.md#voice-priority-filtering). ### Scouts that reach the caller Make Scouts a speaker channel and give scouts Priority Speaker there. A scout holding their priority key is played into the callers' channel — “40+ coming from the east portal” — without the rest of the zerg hearing it. Setup is in [talk back](https://www.nocapbots.com/docs/voice-relay/talk-back.md). > **Tip: Healers on their own channel.** A dedicated healer channel lets the healers coordinate cooldowns among themselves and still hear every call from Command. ### Albion Online questions #### How many speaker channels does an Albion ZvZ need? One per party channel the call has to reach, plus one for scouts if they report in. The Command channel itself doesn't count. Most guild zergs land between eight and twelve — see [pricing](https://www.nocapbots.com/pricing). #### Can two guilds in an alliance follow one caller? Yes, even in separate Discord servers. Link them on the Alliance plan and start the fight with `/start-cross-server`: the caller reaches the party channels of both. See [alliances](https://www.nocapbots.com/docs/voice-relay/alliances.md). #### Can we run two fights at once? Yes. [Voice teams](https://www.nocapbots.com/docs/voice-relay/voice-teams.md) give each group its own caller and channels, while an overall caller on no team is heard everywhere. ## Node war and siege comms for Black Desert guilds Source: https://www.nocapbots.com/games/black-desert Last updated: 2026-11-08 > Node wars and sieges are won on calls the whole guild hears together: when to push the fort, when to fall back to defend. Keep each party of five in its own channel and relay the caller into all of them, so parties keep their own comms and the call lands everywhere at once. ### The fights that need it - **Capped node wars** (25 to 50 players). The lower tiers cap how many of your guild can join, which is five to ten parties of five. Every party has to hear the push call at the same moment. - **Uncapped node wars** (The whole guild). No cap means every party you can field, and usually a fort to hold while you attack someone else's. That is where split calls pay off. - **Siege wars** (Several guilds). The biggest fights in the game, often with allied guilds in their own Discord servers. A cross-server relay puts one caller in all of them. ### A channel layout for Black Desert ``` NODE WAR 🔊 Command caller, backup caller, officers 🔊 Attack 1 🔊 Attack 2 🔊 Attack 3 🔊 Attack 4 🔊 Attack 5 🔊 Attack 6 🔊 Defense 1 🔊 Defense 2 ``` One channel per party of five. Put the Attack and Defense channels on two voice teams, each with its own caller, and the overall commander on no team so everyone hears them. ### Recommended plan: Guild Master 12 speaker channels, $15/month, 7 days free. Guild Master's twelve speaker channels cover sixty players in parties of five, which handles capped tiers and most guilds in an uncapped war. A capped war of 25 to 40 fits Raid Commander's eight. For a siege with an allied guild in another Discord, the Alliance plan links the two. ### Attack and defense at the same time Node wars rarely give you one objective. While most of the guild pushes, a few parties hold your own fort. Give each side its own caller with [voice teams](https://www.nocapbots.com/docs/voice-relay/voice-teams.md): the attack caller is heard only in the attack channels, the defense caller only in defense, and the overall commander — on no team — reaches everyone. The full shape is in [running attack and defense calls at the same time](https://www.nocapbots.com/blog/attack-and-defense-callers.md). > Attack 1 to 3, push the fort now. Attack 4, cannons first. > > — Attack caller > Defense, they're on the west wall. Hold the command post. > > — Defense caller > Everyone — defense is collapsing. Attack 5 and 6, go back. > > — Overall commander ### Before the war starts 1. **Sort parties ten minutes early.** Everyone in their party channel. Party leaders confirm numbers in text. 2. **Start the relay.** Run `/start`, then `/status` to see it's live. Team changes you save reach a running relay straight away. 3. **Test every channel.** The caller asks each party to answer on their priority key. If a party can't hear, [troubleshooting](https://www.nocapbots.com/docs/voice-relay/troubleshooting.md) has the checklist. ### Black Desert questions #### Which plan fits a capped node war? Count your parties of five. A 25 to 40 player cap is five to eight parties, which fits Raid Commander. A 50 player cap is ten, which needs Guild Master. See [pricing](https://www.nocapbots.com/pricing). #### Can attack and defense hear different callers? Yes, that is what [voice teams](https://www.nocapbots.com/docs/voice-relay/voice-teams.md) are for. Each team has its own caller role and its own channels; a commander on no team is heard by everyone. #### Do my members need to install anything? No. Everything runs inside Discord. Only party leaders who want to [talk back](https://www.nocapbots.com/docs/voice-relay/talk-back.md) to the caller need the Discord desktop app and a priority key. ## Siege and guild war comms for Throne and Liberty Source: https://www.nocapbots.com/games/throne-and-liberty Last updated: 2026-11-07 > A Throne and Liberty guild holds up to 70 players, and parties hold six, so a full guild is about a dozen party channels. Relay your caller into all twelve: each party keeps its own comms, and the call reaches the whole guild at the same moment. ### The fights that need it - **Castle sieges** (Guilds and alliances). The largest fights in the game, with several guilds on each side. Calls have to reach every party, and often allied guilds in their own Discord servers. - **Guild PvP and contested bosses** (Up to the full guild). Guild battles over objectives and bosses that turn into PvP. Parties fight in different places, and the caller decides when to commit. - **Guild events** (A few parties). Smaller guild content where one caller still beats six party leaders repeating each other. ### A channel layout for Throne and Liberty ``` GUILD COMMS 🔊 Command caller, backup caller 🔊 Party 1 🔊 Party 2 🔊 Party 3 🔊 Party 4 🔊 Party 5 🔊 Party 6 🔊 Party 7 🔊 Party 8 🔊 Party 9 🔊 Party 10 🔊 Party 11 🔊 Party 12 ``` Set each party channel's user limit to six so channels match in-game parties. Every party channel gets a speaker bot; Command doesn't need one. ### Recommended plan: Guild Master 12 speaker channels, $15/month, 7 days free. Seventy players in parties of six is twelve party channels, which is exactly Guild Master. If your siege alliance runs two Discord servers, the Alliance plan relays one caller into both, and the allied server gets Guild Master free. ### Keep parties in their own channels Seventy people in one voice channel is not comms, it's noise. With one channel per party, each party talks about its own fight — who's low, who's out of cooldowns — and the caller comes through on top in all twelve. [How it works](https://www.nocapbots.com/docs/voice-relay/how-it-works.md) explains why Discord needs a bot per channel to do this. > Parties 1 to 4, left gate. Parties 5 to 8, right gate. 9 to 12 hold. > > — Splitting a siege > Everyone, on the boss now. Ignore the adds. > > — A contested boss ### Sieges with an allied guild Don't move your allies into your server for the night. On the Alliance plan, link the two Discord servers with a single-use code and run `/start-cross-server` from the server whose caller runs the siege: the caller reaches the party channels of both. [Alliance comms across two Discord servers](https://www.nocapbots.com/blog/alliance-comms-across-two-servers.md) covers who should call. > **Tip: Party leaders reach the caller.** Give party leaders Priority Speaker in their party channel. Their priority key reaches the caller; their normal key stays with their party. Five minutes per leader: [set up your priority key](https://www.nocapbots.com/blog/party-leader-priority-key.md). ### Throne and Liberty questions #### How many channels does a Throne and Liberty guild need? One per party of six. A full 70-player guild is twelve, which is Guild Master. A guild that fields four or eight parties fits Squad Leader or Raid Commander — see [pricing](https://www.nocapbots.com/pricing). #### Can our siege alliance hear one caller across two Discord servers? Yes. The Alliance plan links a second server, which gets Guild Master free, and either server can start a cross-server relay. See [alliances](https://www.nocapbots.com/docs/voice-relay/alliances.md). #### Is there a delay between the caller and the parties? About a tenth to three tenths of a second. When one person is talking the audio isn't re-encoded at all — see [how it works](https://www.nocapbots.com/docs/voice-relay/how-it-works.md). ## WvW commander comms for Guild Wars 2 squads Source: https://www.nocapbots.com/games/guild-wars-2 Last updated: 2026-11-07 > A commander's WvW squad holds up to 50 players, and most guilds build it in subgroups of five because shared boons reach five allies. Give each subgroup its own channel for boon and stability calls, and relay the commander into all of them. ### The fights that need it - **WvW squads** (Up to 50 players). A commander's squad holds up to 50, usually in subgroups of five. Subgroups coordinate their own boons; everyone follows the commander's tag and voice. - **Two squads on one map** (Two commanders). When two commanders run separate squads, each squad should hear its own commander — and both should hear the map lead. - **Guild raids and GvG** (A guild squad). Guild-only nights where the guild's own commander calls, with the same layout and fewer channels. ### A channel layout for Guild Wars 2 ``` WVW 🔊 Command commander, lieutenants 🔊 Subgroup 1 🔊 Subgroup 2 🔊 Subgroup 3 🔊 Subgroup 4 🔊 Subgroup 5 🔊 Subgroup 6 🔊 Subgroup 7 🔊 Subgroup 8 🔊 Subgroup 9 🔊 Subgroup 10 ``` Ten subgroups of five fills a 50-player squad. Match channel names to the squad's subgroup numbers so players know where to go when the commander moves them. ### Recommended plan: Guild Master 12 speaker channels, $15/month, 7 days free. A full squad in ten subgroups is ten speaker channels, which fits Guild Master's twelve with room for a scout channel. A guild running half-squads of 20 to 40 fits Raid Commander. ### The commander is heard everywhere The tag shows where to go; the voice says when. Put the commander and lieutenants in Command and give them the caller roles: the commander as **primary**, a lieutenant as **backup**, relayed only while the commander is quiet. See [configuration](https://www.nocapbots.com/docs/voice-relay/configuration.md). > Stack on tag. Stab on three… two… one. > > — Before the push > Push now. Bomb the left side, then reset to tag. > > — The engage ### Subgroups keep their own comms Inside a subgroup, the firebrand and the scrapper talk about boons and cleanses without talking over the commander. If a subgroup is wiped or a flank is breaking, its lead holds their priority key to tell the commander — [talk back](https://www.nocapbots.com/docs/voice-relay/talk-back.md) explains the setup. ### Two commanders on one map Put each squad's subgroup channels on its own [voice team](https://www.nocapbots.com/docs/voice-relay/voice-teams.md) with its own commander role. Each squad hears only its commander, while a map lead with the main caller role and no team is heard by both. ### Guild Wars 2 questions #### Why not keep the whole squad in one channel? You can, and many squads do. It stops working when subgroups need to talk among themselves — boons, cleanses, who's down — without drowning out the commander. Separate channels keep both. #### Can lieutenants talk to the commander? Yes. Give them Priority Speaker in their subgroup channel; their priority key reaches Command. See [talk back](https://www.nocapbots.com/docs/voice-relay/talk-back.md). #### How many speaker channels does a full squad need? Ten for ten subgroups of five, which fits Guild Master. See [speaker bots](https://www.nocapbots.com/docs/voice-relay/speaker-bots.md) and [pricing](https://www.nocapbots.com/pricing). ## Fleet comms for EVE Online on Discord Source: https://www.nocapbots.com/games/eve-online Last updated: 2026-11-07 > An EVE fleet can hold 256 pilots, in up to five wings of up to five squads. Put the FC in one channel and relay them into each wing's channel: wings and logi keep their own chatter, and the broadcast reaches every pilot at the same moment. ### The fights that need it - **Alliance fleet ops** (Up to 256 pilots). One FC, wing commanders and squad commanders. Wings talk among themselves; the FC's calls — align, warp, primary — have to reach everyone. - **Coalition ops** (Several alliances). Each alliance runs its own Discord. A cross-server relay lets one FC reach the fleet channels of two servers without anyone switching. - **Structure timers and defense fleets** (A few wings). Timers you know about in advance, with a fleet formed from whoever is online. The layout stays the same; fewer channels get a speaker bot. ### A channel layout for EVE Online ``` FLEET OPS 🔊 Fleet Command FC, backup FC 🔊 Wing 1 🔊 Wing 2 🔊 Wing 3 🔊 Wing 4 🔊 Wing 5 🔊 Logi logistics coordinate reps here 🔊 Scouts scouts report with their priority key ``` Five wings, logi and scouts is seven speaker channels, with one to spare on Raid Commander for capitals or a second logi channel. Wing commanders and scouts hold their Priority Speaker key to reach Fleet Command. ### Recommended plan: Raid Commander 8 speaker channels, $8/month, 7 days free. Five wings, a logi channel and a scout channel fit Raid Commander's eight. For coalition ops across two alliance Discords, the Alliance plan's cross-server relay puts one FC in both, and the second server gets Guild Master free. ### The FC's calls reach every wing Fleet calls don't tolerate a relay chain. If wing commanders repeat the FC, the last wing warps seconds after the first. With a relay, every wing hears the FC directly, about a tenth to three tenths of a second behind — see [how it works](https://www.nocapbots.com/docs/voice-relay/how-it-works.md). > Fleet, align to the gate. Warp on my call… warp, warp, warp. > > — FC > Primary is the Guardian. Lock and shoot. > > — FC ### Logi keeps its own channel Logistics pilots coordinate reps among themselves and still need every FC call. A Logi speaker channel gives them both. If a logi anchor needs the FC — “logi is capping out” — their priority key reaches Fleet Command. Setup in [talk back](https://www.nocapbots.com/docs/voice-relay/talk-back.md). ### Coming from Mumble or TeamSpeak Many alliances still run fleets on Mumble for shouts to linked channels. The relay is the Discord version of that shout: one FC, every wing channel. We compared both in [Mumble vs Discord for guilds and fleets](https://www.nocapbots.com/blog/mumble-vs-discord.md). ### EVE Online questions #### Can one FC reach two alliances' Discord servers? Yes. On the Alliance plan, link the second server with a single-use code and run `/start-cross-server`: the FC's voice goes to the speaker channels of both. See [alliances](https://www.nocapbots.com/docs/voice-relay/alliances.md). #### Can wing commanders talk to the FC without the whole fleet hearing? Yes. A wing commander with Priority Speaker in their wing channel holds their priority key; it reaches Fleet Command and their own wing, not the other wings. See [talk back](https://www.nocapbots.com/docs/voice-relay/talk-back.md). #### Does it replace in-game fleet broadcasts? No, and it doesn't need to. Broadcasts and the watchlist stay in the client; the relay only carries voice. ## Guild war comms for Where Winds Meet on Discord Source: https://www.nocapbots.com/games/where-winds-meet Last updated: 2026-11-07 > A Where Winds Meet guild war puts up to 30 of your guild on the field, and leadership can appoint up to four guild war commanders. Give each commander their own squads with voice teams, keep the guild leader heard by everyone, and every squad hears the right call. ### The fights that need it - **Guild wars** (Up to 30 a side). Objectives spread across the map, with squads fighting in different places at the same time. Each needs its own calls, and all of them need the leader's. - **Guild war commanders** (Up to four). The game lets leadership appoint up to four commanders. On Discord, each one can be a caller heard only by their own squads. - **Guild events and practice** (A few squads). Scrims and guild content where the same layout, with fewer channels, keeps everyone on one call. ### A channel layout for Where Winds Meet ``` GUILD WAR 🔊 Command guild leader, commanders 🔊 Squad 1 commander A 🔊 Squad 2 commander A 🔊 Squad 3 commander B 🔊 Squad 4 commander B 🔊 Squad 5 commander C 🔊 Squad 6 commander D ``` Thirty players in squads of five is six channels. Put each commander's squads on their own voice team; the guild leader has the main caller role and no team, so every squad hears them. ### Recommended plan: Raid Commander 8 speaker channels, $8/month, 7 days free. Six squad channels fit Raid Commander's eight, with room for a scout or reserve channel. A guild fielding four squads or fewer fits Squad Leader. ### One team per commander Make one Discord role per commander, then one [voice team](https://www.nocapbots.com/docs/voice-relay/voice-teams.md) per role with that commander's squad channels. A commander is heard only in their own squads, so four commanders can call at once without talking over each other. All of them sit in Command, so they hear each other. > Squads 1 and 2, take the left tower. Now. > > — Commander A > Everyone, fall back to the tree and defend. > > — Guild leader, heard by all ### Set it up before war night 1. **Make the channels.** A Command channel and one voice channel per squad of five, as in the layout above. 2. **Make the roles.** One role per commander, plus a main caller role for the guild leader. The [getting started](https://www.nocapbots.com/docs/voice-relay/getting-started.md) guide covers the rest. 3. **Add the teams.** Switch on **Voice teams** on the configuration page and add one per commander, then run `/stop` and `/start` so they load. ### Where Winds Meet questions #### How many channels does a Where Winds Meet guild war need? Thirty players in squads of five is six squad channels, which fits Raid Commander. See [pricing](https://www.nocapbots.com/pricing). #### Can four commanders call at the same time? Yes. Each commander's squads are a [voice team](https://www.nocapbots.com/docs/voice-relay/voice-teams.md), so each commander is heard only by their own squads, and the guild leader on no team is heard by everyone. #### Do squads lose their own comms? No. Squads stay in their own channel and talk normally; the commander comes through on top. Squad leads can reach their commander with [talk back](https://www.nocapbots.com/docs/voice-relay/talk-back.md). # Templates ## A Discord server template for gaming guilds Source: https://www.nocapbots.com/templates/gaming-guild-discord-server Last updated: 2026-11-07 > Copy the layout below: an info category, guild chat, events, an officers' room and a comms category with one command channel plus one voice channel per party. Pair it with five roles — Guild Master, Officer, Shot Caller, Party Leader and Member — and the server is ready for a 60-player fight. ### The layout Categories in capitals, text channels with `#`, voice channels with 🔊. Rename anything to fit your guild; what matters is the shape of the COMMS category. ``` INFO # welcome # rules # announcements # pick-your-roles GUILD # general # looking-for-group # builds-and-guides # clips-and-screenshots EVENTS # raid-schedule # event-signups # war-reports OFFICERS (private: Officer and Guild Master) # officer-chat # recruitment 🔊 Officers COMMS 🔊 Command callers talk here 🔊 Alpha one channel per party 🔊 Bravo 🔊 Charlie 🔊 Delta 🔊 Echo 🔊 Foxtrot HANGOUT 🔊 Lounge 🔊 Duos 🔊 AFK ``` > **Tip: One party channel per party, not per player.** Make as many party channels as the parties you field in your biggest fight. Six covers 30 to 36 players in parties of five or six; add channels as the guild grows. ### The roles | Role | Who | Permissions that matter | | --- | --- | --- | | Guild Master | The guild's leader and co-leaders. | Administrator. | | Officer | Officers who run events and recruitment. | Manage Messages, Move Members, Manage Events, Mute Members. | | Shot Caller | The people who call fights. | Speak in Command. This is the role the relay broadcasts — see [configuration](https://www.nocapbots.com/docs/voice-relay/configuration.md). | | Party Leader | One per party. | **Priority Speaker** in the party channels, so they can reach the caller — see [talk back](https://www.nocapbots.com/docs/voice-relay/talk-back.md). | | Member | Everyone in the guild. | Connect and Speak in party and hangout channels. | Give `@everyone` read-only access to INFO and nothing else, so new joiners see the rules and the role picker before the rest of the server. ### Why the voice channels look like this Discord sends your voice only to the channel you're in. Put a 40-player raid in one channel and party leaders can't talk to their party without talking over the caller; split them into parties and nobody hears the caller. The COMMS category is built to have both: parties in their own channels, and the caller relayed into all of them. The trade-offs are in [can you talk in two Discord voice channels at once?](https://www.nocapbots.com/blog/talk-in-two-discord-voice-channels.md) - **Command** holds the shot callers. Limit who can speak there to Shot Caller and Officer, so the channel stays clean. - **Party channels** get a user limit equal to your game's party size — five or six — so channels match in-game parties. Limits are explained in [Discord voice channel limits for large guilds](https://www.nocapbots.com/blog/discord-voice-channel-user-limit.md). - **AFK** is set as the server's inactive channel in Server Settings → Overview, so idle members drop out of party channels. ### Set it up 1. **Create the server.** In Discord, add a server, choose **Create My Own**, then **For a club or community**. 2. **Add the categories and channels.** Create each category from the layout, then its text and voice channels. Drag channels to reorder them. 3. **Create the roles.** Server Settings → Roles. Add Guild Master, Officer, Shot Caller, Party Leader and Member, in that order from the top. 4. **Set channel permissions.** Make OFFICERS private to Officer and Guild Master. In Command, allow Speak only for Shot Caller and Officer. In each party channel, give Party Leader the **Priority Speaker** permission. 5. **Set party sizes.** Edit each party channel and set its user limit to your game's party size. 6. **Relay the caller.** Invite the Callout bot, pick Command as the shot caller channel and Shot Caller as the caller role, and give each party channel a speaker bot. [Getting started](https://www.nocapbots.com/docs/voice-relay/getting-started.md) walks through it in about ten minutes. > **Tip: Save it as your own template.** Once it's built, Server Settings → Server Template creates a link that copies your channels, roles and permissions — not your messages or members — into a new server. Handy for an alt guild or a second team. ### Adjust it for your game | Game | Party channels | Change | | --- | --- | --- | | [Throne and Liberty](https://www.nocapbots.com/games/throne-and-liberty) | Up to 12 parties of six | Party user limit 6. | | [Black Desert](https://www.nocapbots.com/games/black-desert) | Parties of five | Split COMMS into Attack and Defense channels for node wars. | | [Guild Wars 2](https://www.nocapbots.com/games/guild-wars-2) | Up to 10 subgroups of five | Name channels after squad subgroups. | | [Albion Online](https://www.nocapbots.com/games/albion-online) | One per zerg party | Add a Scouts channel that reports to the caller. | | [EVE Online](https://www.nocapbots.com/games/eve-online) | Up to 5 wings | Add Logi and Scouts channels. | | [Where Winds Meet](https://www.nocapbots.com/games/where-winds-meet) | Six squads of five | One voice team per guild war commander. | # Blog ## TeamSpeak vs Discord for gaming guilds Source: https://www.nocapbots.com/blog/teamspeak-vs-discord Published: 2026-11-07 Updated: 2026-11-07 Topic: Comparisons > Discord wins on everything around the fight: your members are already there, there's no server to rent, and text, events and roles come built in. TeamSpeak still wins in the fight itself, because whisper lists let one commander talk into several channels at once. Most guilds now run on Discord and add a voice relay to get that back. ### At a glance | | TeamSpeak | Discord | | --- | --- | --- | | Hosting | You rent a server or run one yourself. | Nothing to host. A server is free. | | Getting members in | A second app and a server address. | They're already on Discord. | | Voice to other channels | Whisper lists: a hotkey that talks into chosen channels or groups. | None. Your voice reaches only the channel you're in. | | Who may talk | Talk power per channel. | Roles and channel permissions, plus Priority Speaker. | | Text and community | Basic. | Channels, threads, events, roles, onboarding and a huge choice of bots. | | Cost | Server rental, and a licence for bigger servers. | Free; Nitro and server boosts are optional. | ### Why guilds moved to Discord Not because the voice is better. Because everything around the fight is: recruitment happens in Discord, sign-ups happen in Discord, the guild's memes happen in Discord. Asking a new recruit to install a second voice client and type in a server address loses some of them before their first raid. - **One place.** Chat, events, sign-ups and voice in the same app your members open every day. - **Nothing to run.** No server rental, no slot count, no updates on raid night. - **Bots for the rest.** Sign-ups, roles and moderation are a bot away — we list the ones guilds use in [the best Discord bots for gaming guilds](https://www.nocapbots.com/blog/best-discord-bots-for-guilds.md). ### What guilds miss from TeamSpeak One thing, mostly: **whisper**. On TeamSpeak a commander could hold a hotkey and talk into every squad's channel at once, while squads kept chatting among themselves. Discord has nothing like it. A Discord account holds one voice connection, and your voice reaches only the channel you're in — [why that is](https://www.nocapbots.com/blog/talk-in-two-discord-voice-channels.md). Without whisper, guilds on Discord fall back to one of two bad options: everyone in one channel, so party leaders can't talk to their party without talking over the caller, or parties in their own channels, with leaders repeating every call late. ### Getting whisper back on Discord A voice relay does the whisper's job with bots. One bot listens in the callers' channel; a speaker bot in each party channel plays what it hears. The caller talks once and every party hears them, about a tenth to three tenths of a second later, while still talking among themselves. [How it works](https://www.nocapbots.com/docs/voice-relay/how-it-works.md) has the details, and [how to whisper to other channels on Discord](https://www.nocapbots.com/blog/discord-whisper-to-other-channels.md) maps each TeamSpeak whisper setup to its Discord equivalent. The other direction — a squad leader reaching the commander — uses Discord's own Priority Speaker key, carried back to the callers by the relay. That's [talk back](https://www.nocapbots.com/docs/voice-relay/talk-back.md). ### Which should your guild use? | Your guild | Use | | --- | --- | | Friends, one group at a time | Discord. One voice channel is all you need. | | One or two parties, one fight | Discord, everyone in one channel. | | Four or more parties, raids, sieges or zergs | Discord with a voice relay, so parties keep their own channels and everyone hears the caller. | | You need to own the voice server itself | TeamSpeak or [Mumble](https://www.nocapbots.com/blog/mumble-vs-discord.md), self-hosted. | ### Moving from TeamSpeak to Discord 1. **Rebuild the channel tree.** One voice channel for callers and one per squad. Our [gaming guild server template](https://www.nocapbots.com/templates/gaming-guild-discord-server) has a layout to copy. 2. **Turn server groups into roles.** Officers, callers and squad leaders each become a Discord role. 3. **Turn talk power into permissions.** Limit who can speak in the callers' channel, and give squad leaders Priority Speaker in their squad channel. 4. **Turn the whisper list into speaker channels.** Every channel the commander used to whisper to gets a speaker bot. [Getting started](https://www.nocapbots.com/docs/voice-relay/getting-started.md) takes about ten minutes. 5. **Run both for a week.** Keep the TeamSpeak server up for a week or two of raids, then let it lapse. ### Put it into practice - [How Voice Relay carries Discord voice](https://www.nocapbots.com/docs/voice-relay/how-it-works.md): Why Discord voice needs bots to reach several channels, how the speaker bots relay audio with no transcoding, and what latency to expect. - [Talk back: let party leaders reach the caller](https://www.nocapbots.com/docs/voice-relay/talk-back.md): Set up Discord Priority Speaker so party leaders can talk to the caller with a priority push-to-talk key while their normal key stays in their squad. - [Set up Voice Relay from an empty Discord server](https://www.nocapbots.com/docs/voice-relay/getting-started.md): Set up a Discord voice relay in about ten minutes: make the channels and a caller role, invite the bot, pick roles and speaker channels, then type /start. ## How to whisper to other channels on Discord Source: https://www.nocapbots.com/blog/discord-whisper-to-other-channels Published: 2026-11-07 Updated: 2026-11-07 Topic: Guides > Discord has no whisper: your voice only reaches the channel you're in. TeamSpeak whisper lists and Mumble shouts let a commander talk into other channels with a hotkey. On Discord the same result takes a relay that plays the caller into each party channel, plus Priority Speaker for the way back. ### What whisper did - **TeamSpeak** has whisper lists: a hotkey bound to a list of channels, server groups or people. Hold it and you talk to them instead of your own channel. The speaker needs enough talk power for the target channels. - **Mumble** has whisper and shout shortcuts: talk to your current channel, to a parent channel and its subchannels, or to every linked channel at once. Guilds built their comms on it. The commander sat in a command channel and whispered to every squad; squads talked among themselves in their own channels and heard the commander on top. ### Why Discord can't A Discord account holds one voice connection at a time, and Discord sends your microphone only to the channel that connection is in. There are no linked channels and no whisper keybind. Requests for one have sat on Discord's feedback site for years. [Can you talk in two Discord voice channels at once?](https://www.nocapbots.com/blog/talk-in-two-discord-voice-channels.md) goes through the workarounds people try. ### A relay is the whisper Bots have the same one-connection rule, so a relay uses several: one listens to the callers, and a speaker bot in each party channel plays them. The effect is the old whisper list, set up once instead of per hotkey. [How it works](https://www.nocapbots.com/docs/voice-relay/how-it-works.md) explains the audio path. | On TeamSpeak or Mumble | On Discord with Voice Relay | | --- | --- | | A whisper list of squad channels | Speaker channels: each one gets a speaker bot. | | Who may whisper (talk power) | The primary and backup caller roles. Nobody else in the callers' channel is relayed. | | Separate lists, such as left flank and right flank | [Voice teams](https://www.nocapbots.com/docs/voice-relay/voice-teams.md): each team's caller reaches only that team's channels. | | Squad leaders whispering back to command | [Talk back](https://www.nocapbots.com/docs/voice-relay/talk-back.md): their Priority Speaker key reaches the callers. | | Shouting into another guild's server | A [cross-server relay](https://www.nocapbots.com/docs/voice-relay/alliances.md) between two linked Discord servers. | > **Note: One difference.** A TeamSpeak commander could pick targets per key press. A relay's routes are set before the fight: a caller always reaches their team's channels. Agree the teams in advance, and use an overall caller on no team for calls everyone needs. ### Set it up 1. **Make the channels.** One channel for callers and one per squad — or copy our [server template](https://www.nocapbots.com/templates/gaming-guild-discord-server). 2. **Pick who is relayed.** Give callers a role and set it as the primary caller role on the dashboard. 3. **Add speaker bots.** One per squad channel, invited and assigned in a couple of clicks. Then type `/start`. The full walkthrough is [getting started](https://www.nocapbots.com/docs/voice-relay/getting-started.md). ### Put it into practice - [How Voice Relay carries Discord voice](https://www.nocapbots.com/docs/voice-relay/how-it-works.md): Why Discord voice needs bots to reach several channels, how the speaker bots relay audio with no transcoding, and what latency to expect. - [Voice teams: run several callers at once](https://www.nocapbots.com/docs/voice-relay/voice-teams.md): Use Voice Relay's voice teams to run attack and defense callers at the same time, each heard only by their own speaker channels. - [Talk back: let party leaders reach the caller](https://www.nocapbots.com/docs/voice-relay/talk-back.md): Set up Discord Priority Speaker so party leaders can talk to the caller with a priority push-to-talk key while their normal key stays in their squad. ## Mumble vs Discord for guilds and fleets Source: https://www.nocapbots.com/blog/mumble-vs-discord Published: 2026-11-07 Updated: 2026-11-07 Topic: Comparisons > Mumble is still the voice server you can control end to end, and its shouts to linked channels are made for fleets. Discord is where your members already are, with nothing to host. Guilds that switch keep the fight-time structure by relaying the commander into each squad channel. ### At a glance | | Mumble | Discord | | --- | --- | --- | | Hosting | Self-hosted or rented server; open source. | Nothing to host. | | Audio | Opus, low latency, quality you tune yourself. | Opus with good defaults and noise suppression. | | Channels | Nested and linked channels; whisper and shout to them. | Flat voice channels in categories; one channel at a time. | | Permissions | Detailed ACLs per channel and group. | Roles and channel overrides, plus Priority Speaker. | | Identity | Certificates, or accounts on your own server. | Discord accounts, which members already have. | | Community | Voice only. | Text, threads, events, onboarding and bots. | ### Who still runs Mumble Groups that want to own their voice server: large EVE alliances and coalitions with their own infrastructure, and guilds that rely on shouts to linked channels. For them, a channel tree of Fleet → Wings → Squads with a commander shouting down it is the whole point. ### Why guilds move anyway - Recruits already have Discord; nobody needs a certificate or a server address. - Sign-ups, announcements and voice live in one app. - No server to keep patched and paid for. The cost of moving is the shout. A Discord account talks only to the channel it's in, so a commander can't reach every wing. That is the same problem TeamSpeak guilds have when they move — we covered it in [TeamSpeak vs Discord for gaming guilds](https://www.nocapbots.com/blog/teamspeak-vs-discord.md). ### Keeping the shout on Discord Map the tree onto channels and put a [speaker bot](https://www.nocapbots.com/docs/voice-relay/speaker-bots.md) in each wing or squad channel. The commander talks in the command channel and the relay plays them into every one. For a coalition where each alliance has its own Discord, two servers can be linked so one FC reaches both — see [alliances](https://www.nocapbots.com/docs/voice-relay/alliances.md). | Mumble | Discord with Voice Relay | | --- | --- | | Shout to subchannels | One speaker bot per wing or squad channel. | | Linked channels across groups | Voice teams within one server, or a cross-server relay between two. | | ACL for who may shout | Caller roles: only they are relayed. | | Whisper up to command | Priority Speaker key, carried back by [talk back](https://www.nocapbots.com/docs/voice-relay/talk-back.md). | Running fleets? [Fleet comms for EVE Online on Discord](https://www.nocapbots.com/games/eve-online) has a channel layout with wings, logi and scouts. ### Put it into practice - [How Voice Relay carries Discord voice](https://www.nocapbots.com/docs/voice-relay/how-it-works.md): Why Discord voice needs bots to reach several channels, how the speaker bots relay audio with no transcoding, and what latency to expect. - [Alliances: relay across two Discord servers](https://www.nocapbots.com/docs/voice-relay/alliances.md): Link two Discord servers with a single-use invite code so one caller reaches the speaker channels of both. The allied server gets Guild Master free. - [Speaker bots: one bot per party channel](https://www.nocapbots.com/docs/voice-relay/speaker-bots.md): How the Callout speaker bots work: one slot per channel on your plan, an invite button each, picking channels, private channels and stage channels. ## The best Discord bots for gaming guilds Source: https://www.nocapbots.com/blog/best-discord-bots-for-guilds Published: 2026-11-07 Updated: 2026-11-07 Topic: Comparisons > Pick bots by the job, not the hype: one for sign-ups and events, one for roles and moderation, and — once fights outgrow one voice channel — a voice relay for comms. Most guilds need three or four bots, and Discord's built-in tools cover more than they used to. ### Bots by job | Job | What to look for | Well-known options | | --- | --- | --- | | Raid and event sign-ups | Role and class slots, reminders, a calendar view. | Raid-Helper, Apollo. | | Roles and onboarding | Button or reaction roles, roles on join. | Carl-bot, or Discord's own Onboarding. | | Moderation and logs | Auto-moderation, message and member logs. | Dyno, Carl-bot, or Discord's AutoMod. | | Temporary voice channels | A channel per group that disappears when empty. | Temp-voice bots such as VoiceMaster. | | Voice comms for big fights | One caller heard in every party channel at once. | [Voice Relay](https://www.nocapbots.com/voice-relay). | ### Start with what Discord already does - **Onboarding** asks new members questions and hands out roles — no role bot needed for the basics. - **AutoMod** blocks spam, links and keywords. - **Events** schedule raids with an RSVP button and a reminder. - **Priority Speaker** lets a caller cut through a busy channel — [how to use it](https://www.nocapbots.com/blog/discord-priority-speaker.md). ### The one job Discord can't do: voice across channels Every other job above has a built-in or a bot. Getting one caller into several voice channels doesn't, because Discord sends your voice only to the channel you're in. A relay uses one bot to listen to the callers and a speaker bot per party channel to play them. That's what Voice Relay does — [how it works](https://www.nocapbots.com/docs/voice-relay/how-it-works.md). ### A starter stack by guild size | Guild | Bots | | --- | --- | | One or two groups | A sign-up bot. Discord's Onboarding, AutoMod and Events for the rest. | | Three to eight parties | Sign-ups, a roles bot, and Voice Relay on Raid Commander (8 party channels). | | A full guild or an alliance | Sign-ups, roles, moderation with logs, and Voice Relay on Guild Master (12) or Alliance (24 across two servers). | ### Before you add any bot - **Check what it asks for.** A bot that only plays voice doesn't need Administrator. NoCap Bots asks for View Channels, Connect and Speak — see [permissions](https://www.nocapbots.com/docs/permissions.md). - **Check it's maintained.** A bot that broke last patch will break on raid night. - **Decide who manages it.** Give officers access without handing over your account: [managers](https://www.nocapbots.com/docs/managers.md). Setting up a server from scratch? Start with our [gaming guild server template](https://www.nocapbots.com/templates/gaming-guild-discord-server). ### Put it into practice - [Permissions and privacy: what NoCap Bots can access](https://www.nocapbots.com/docs/permissions.md): What signing in with Discord shares, what the bots are allowed to do, who can set up a server, and how to take any of it back. - [Set up Voice Relay from an empty Discord server](https://www.nocapbots.com/docs/voice-relay/getting-started.md): Set up a Discord voice relay in about ten minutes: make the channels and a caller role, invite the bot, pick roles and speaker channels, then type /start. - [Managers: share the dashboard with your officers](https://www.nocapbots.com/docs/managers.md): Invite managers to a NoCap Bots server by email or Discord username and choose what they can touch: configuration, billing or other managers. ## What is a shot caller in gaming? Source: https://www.nocapbots.com/blog/what-is-a-shot-caller Published: 2026-11-07 Updated: 2026-11-07 Topic: Leadership > A shot caller is the player who makes the calls in a fight — where to go, what to hit, when to commit — while everyone else executes. It's a voice job first: the call has to reach every party at the same moment, short and in the same shape every time. ### The job In a big fight nobody can see everything, and if everyone decides for themselves the group falls apart. The shot caller watches the whole fight and decides; everyone else commits to the call. A wrong call that everyone follows usually beats a right one that half the group follows. The name changes by game — commander in Guild Wars 2, FC in EVE Online, caller or shotcaller in Albion and Black Desert — but the job is the same. ### Shot caller, raid leader, party leader | Role | What they do | | --- | --- | | Shot caller | Makes the calls during the fight, live. | | Raid leader | Plans the night: who comes, which parties, which strategy. Often also the caller, but not always. | | Backup caller | Takes over when the caller dies, lags or needs a breather. | | Party leader | Turns the caller's intent into what their party does, and tells the caller what they can't see. | ### How to get better at calling - **Start small.** Call a five-person group before you call fifty. - **Keep one shape.** Who, what, when — every call, in that order. More in [how to run voice comms for 100-player PvP](https://www.nocapbots.com/blog/voice-comms-for-large-scale-pvp.md). - **Name places the same way every time.** Agree names for gates, camps and objectives before the fight. - **Review recordings.** Listen to yourself after a fight: what was late, what was unclear, what nobody needed. - **Stay calm out loud.** The group's panic follows the caller's voice. ### What a caller needs from voice comms - **To be heard everywhere at once.** If party leaders repeat the call, it arrives late and different. A relay puts the caller in every party channel — [why Discord needs one](https://www.nocapbots.com/blog/talk-in-two-discord-voice-channels.md). - **Quiet.** Only callers should be broadcast. NoCap Bots relays only the [primary and backup caller roles](https://www.nocapbots.com/docs/voice-relay/configuration.md#voice-priority-filtering). - **A way back.** Party leaders need to reach the caller without the whole raid hearing: [talk back](https://www.nocapbots.com/docs/voice-relay/talk-back.md). Calling for a specific game? See [Voice Relay by game](https://www.nocapbots.com/games) for layouts and plans for Albion Online, Black Desert, Throne and Liberty, Guild Wars 2, EVE Online and Where Winds Meet. ### Put it into practice - [Configure roles, channels and voice priority](https://www.nocapbots.com/docs/voice-relay/configuration.md): The Voice Relay configuration page explained: starter role, shot caller channel, primary and backup caller roles, and the four things /start needs. - [Talk back: let party leaders reach the caller](https://www.nocapbots.com/docs/voice-relay/talk-back.md): Set up Discord Priority Speaker so party leaders can talk to the caller with a priority push-to-talk key while their normal key stays in their squad. - [How Voice Relay carries Discord voice](https://www.nocapbots.com/docs/voice-relay/how-it-works.md): Why Discord voice needs bots to reach several channels, how the speaker bots relay audio with no transcoding, and what latency to expect. ## Discord Priority Speaker: what it does and how to use it Source: https://www.nocapbots.com/blog/discord-priority-speaker Published: 2026-11-07 Updated: 2026-11-07 Topic: Guides > Priority Speaker lowers everyone else's volume in the channel while you hold a separate priority push-to-talk key. It needs push to talk, the permission on a role or channel, and the desktop app. Guilds give it to callers and party leaders so the voice that matters cuts through. ### What it does When someone with Priority Speaker holds their priority key, Discord turns down everyone else in the channel so they're heard over the noise. Let go and the volume comes back. Nothing happens on the normal push-to-talk key or on voice activity. ### Give it to a role (admins) 1. **Pick the role.** Server Settings → Roles → the role, for example Party Leader or Shot Caller. 2. **Allow Priority Speaker.** Under the voice permissions, switch on **Priority Speaker**. 3. **Or only in some channels.** To limit it, leave it off on the role and allow it in each channel's permissions instead — for example only in party channels. ### Use it (members) 1. **Switch to push to talk.** User Settings → Voice & Video → Input mode: **Push to Talk**. Priority Speaker doesn't work with voice activity. 2. **Bind the priority key.** User Settings → Keybinds → Add a keybind → **Push to Talk (Priority)**, and record a button. 3. **Keep a normal key too.** Bind **Push to Talk (Normal)** to another button for everyday talking. > **Note: Desktop app only.** Keybinds live in the Discord desktop app. On mobile and in the browser there's no priority key to hold. ### How guilds use it - **Callers in a busy channel.** The caller's voice cuts through thirty people talking. - **Party leaders reaching the caller.** With Voice Relay, a party leader's priority key is the signal to carry their voice back to the callers' channel, while their normal key stays in their party. That's [talk back](https://www.nocapbots.com/docs/voice-relay/talk-back.md); the leader's checklist is [set up your priority key in five minutes](https://www.nocapbots.com/blog/party-leader-priority-key.md). ### If it isn't working | Symptom | Check | | --- | --- | | Nothing gets quieter | You're on voice activity, or you pressed the normal key. Switch to push to talk and use the priority bind. | | Only you hear everyone quieter | You don't have the permission in this channel. Ask an admin to allow it on your role or the channel. | | The priority key does nothing at all | You're on mobile or the browser, or the keybind isn't recorded. Use the desktop app. | Talk back still not reaching the caller? The relay's checklist is in [troubleshooting](https://www.nocapbots.com/docs/voice-relay/troubleshooting.md#priority-key). ### Put it into practice - [Talk back: let party leaders reach the caller](https://www.nocapbots.com/docs/voice-relay/talk-back.md): Set up Discord Priority Speaker so party leaders can talk to the caller with a priority push-to-talk key while their normal key stays in their squad. - [Troubleshooting Voice Relay](https://www.nocapbots.com/docs/voice-relay/troubleshooting.md): Fix common Voice Relay problems: /start won't run, nobody hears the caller, a bot can't access a channel, a full channel, an offline bot or a dead priority key. ## Discord voice channel limits for large guilds Source: https://www.nocapbots.com/blog/discord-voice-channel-user-limit Published: 2026-11-07 Updated: 2026-11-07 Topic: Under the hood > A voice channel's user limit can be set from 1 to 99, or left off; video in a voice channel stops at 25, and an audio-only stage holds up to 10,000 listeners. The limit big guilds hit first isn't technical: with a whole raid on open mics nobody hears the caller, which is why raids split into party channels. ### The numbers | What | Limit | | --- | --- | | User limit on a voice channel | Off, or any number from 1 to 99. | | Video in a voice channel | 25 people. | | Audio-only stage channel | Up to 10,000 listeners; speakers are invited up. | | Video in a stage channel | 50 people, more on boosted servers. | | A bot's voice connections | One per server, so one bot can play into one channel. | ### Set or remove a limit Edit the channel and drag **User Limit**: anywhere from 1 to 99, or all the way down for no limit. Party channels are a good use — set the limit to your game's party size so channels match in-game groups. Our [gaming guild server template](https://www.nocapbots.com/templates/gaming-guild-discord-server) does exactly that. ### Why one big channel fails first - **Crosstalk.** Forty open mics means someone is always talking. The caller competes with everyone. - **Parties can't talk.** A party leader can't sort out their own party without talking over the call. - **Priority Speaker helps, a bit.** It turns everyone down while the caller holds their key — [how it works](https://www.nocapbots.com/blog/discord-priority-speaker.md) — but parties still can't talk among themselves. A stage fixes the noise by muting the audience, which also takes away the parties' comms. The trade-offs are in [can you talk in two Discord voice channels at once?](https://www.nocapbots.com/blog/talk-in-two-discord-voice-channels.md) ### Split into parties, keep the caller The structure that works at any size: each party in its own channel, the caller in a command channel, and the caller relayed into every party channel by a [speaker bot](https://www.nocapbots.com/docs/voice-relay/speaker-bots.md) per channel. Size it by parties, not players: | Players | Parties of five | Plan | | --- | --- | --- | | 20 | 4 | Squad Leader — 4 speaker channels, $5 a month | | 40 | 8 | Raid Commander — 8, $8 a month | | 60 | 12 | Guild Master — 12, $15 a month | | 120, or two guilds | 24 | Alliance — 24 across two linked servers, $25 a month | Every plan starts with seven days free — see [pricing](https://www.nocapbots.com/pricing) — and [getting started](https://www.nocapbots.com/docs/voice-relay/getting-started.md) takes about ten minutes. ### Put it into practice - [Speaker bots: one bot per party channel](https://www.nocapbots.com/docs/voice-relay/speaker-bots.md): How the Callout speaker bots work: one slot per channel on your plan, an invite button each, picking channels, private channels and stage channels. - [Set up Voice Relay from an empty Discord server](https://www.nocapbots.com/docs/voice-relay/getting-started.md): Set up a Discord voice relay in about ten minutes: make the channels and a caller role, invite the bot, pick roles and speaker channels, then type /start. - [How Voice Relay carries Discord voice](https://www.nocapbots.com/docs/voice-relay/how-it-works.md): Why Discord voice needs bots to reach several channels, how the speaker bots relay audio with no transcoding, and what latency to expect. ## Party leaders: set up your priority key in five minutes Source: https://www.nocapbots.com/blog/party-leader-priority-key Published: 2026-11-04 Updated: 2026-11-06 Topic: Guides > Ask for Priority Speaker, switch on push-to-talk, and bind two keys: normal for your party, priority for your party and the caller. It only works in the Discord desktop app. Keep priority for what the caller can act on. ### What you need - The Discord **desktop app** — keybinds don't exist on mobile. - A role with **Priority Speaker** in your party's channel. Ask your server admins; it's set in Server Settings → Roles or on the channel. - Two spare buttons. Mouse side buttons are ideal. ### Setup 1. **Push to talk on.** User Settings → Voice & Video → Input mode: Push to Talk. Raise the release delay a little so your last word isn't clipped. 2. **Normal key.** User Settings → Keybinds → Add a keybind → **Push to Talk (Normal)**. Record your first button. This talks to your party. 3. **Priority key.** Add another keybind → **Push to Talk (Priority)**. Record your second button. This talks to your party and the caller. 4. **Test it.** Ask the caller to listen while you press each key. Only the priority one should reach them. > **Tip: Pick keys you won't confuse.** Put priority on the button that's harder to hit by accident. A stray priority press in the middle of a call is worse than a slow one. ### What's worth saying on priority | Say it | Keep it in the party | | --- | --- | | “Alpha wiped, rezzing at camp.” | Who's low on health. | | “Bravo, enemy zerg on east flank, 20+.” | Cooldown timings. | | “Charlie in position.” | Who pulled aggro. | The test: will the caller change a call because of it? If not, it's for your party. ### If it isn't working Nine times in ten it's the wrong keybind or a missing permission. The checklist is in [troubleshooting](https://www.nocapbots.com/docs/voice-relay/troubleshooting.md#priority-key), and the full server-side setup is in [talk back](https://www.nocapbots.com/docs/voice-relay/talk-back.md). ### Put it into practice - [Talk back: let party leaders reach the caller](https://www.nocapbots.com/docs/voice-relay/talk-back.md): Set up Discord Priority Speaker so party leaders can talk to the caller with a priority push-to-talk key while their normal key stays in their squad. - [Troubleshooting Voice Relay](https://www.nocapbots.com/docs/voice-relay/troubleshooting.md): Fix common Voice Relay problems: /start won't run, nobody hears the caller, a bot can't access a channel, a full channel, an offline bot or a dead priority key. ## Running attack and defense calls at the same time Source: https://www.nocapbots.com/blog/attack-and-defense-callers Published: 2026-10-21 Updated: 2026-11-08 Topic: Guides > Use two callers, each heard only by their own parties, plus an overall commander heard by everyone. Keep all the callers in one channel so they can hear each other, and agree the handover phrases before the fight. ### When to split Split the calls when your parties are doing two different jobs in two different places for most of the fight: one group taking objectives while another holds the base, or two lanes that never meet. If the groups merge every few minutes, one caller is usually better. ### The shape that works | Who | Heard by | | --- | --- | | Attack caller | The attack parties only. | | Defense caller | The defense parties only. | | Overall commander | Everyone — for the calls that change the whole plan. | In NoCap Bots these are [voice teams](https://www.nocapbots.com/docs/voice-relay/voice-teams.md). Each team has caller roles and speaker channels. A channel on no team hears every caller, and a caller on no team is heard everywhere — which is exactly the overall commander. ### Set it up 1. **Make the roles.** One Discord role per side, for example Attack Caller and Defense Caller. Give the overall commander the main caller role, with no team role. 2. **Add two teams.** On the configuration page, switch on **Voice teams**, add Attack with its caller role and channels, then Defense. 3. **Check it's live.** A running relay picks up team changes within a few seconds; `/status` shows the teams. See the [command reference](https://www.nocapbots.com/docs/voice-relay/commands.md). ### Keep the callers in one room All the callers sit in the shot caller channel. They hear each other, so the attack caller knows when defense is collapsing without anyone relaying it. Party leaders on both sides can still reach them with [talk back](https://www.nocapbots.com/docs/voice-relay/talk-back.md). ### Agree the handover The weak point in split calls is the moment a side runs out of work. Agree the phrases beforehand: > Defense, you're with attack now. Follow attack calls. The overall commander says it, so every party hears it at once. Teams don't need to change in the middle of a fight — the commander's call is enough. ### Put it into practice - [Voice teams: run several callers at once](https://www.nocapbots.com/docs/voice-relay/voice-teams.md): Use Voice Relay's voice teams to run attack and defense callers at the same time, each heard only by their own speaker channels. - [Configure roles, channels and voice priority](https://www.nocapbots.com/docs/voice-relay/configuration.md): The Voice Relay configuration page explained: starter role, shot caller channel, primary and backup caller roles, and the four things /start needs. - [Voice Relay slash commands](https://www.nocapbots.com/docs/voice-relay/commands.md): Every Callout slash command: /start, /stop, /status, /ping, /start-cross-server and /stop-cross-server, and who can use them. ## Alliance comms across two Discord servers Source: https://www.nocapbots.com/blog/alliance-comms-across-two-servers Published: 2026-10-12 Updated: 2026-11-06 Topic: Leadership > Keep both guilds in their own servers. Link them, agree which server's caller runs the fight, and start a cross-server relay from either side so one caller reaches every party in both. Party leaders on both sides can still talk back. ### Don't merge the servers The usual fix for an alliance fight is to ask one guild to join the other's server for the night. Half of them can't find the channels, roles are wrong, and the permissions you set up so carefully don't apply. Keep each guild where it is. ### Link the two servers On the Alliance plan, one server creates a single-use invite code and the other pastes it in. The second server gets Guild Master — 12 speaker channels — at no extra cost. [Alliances](https://www.nocapbots.com/docs/voice-relay/alliances.md) has the step-by-step. ### Decide who calls Before the fight, agree which server's caller runs it. The cross-server relay takes the caller from the server that starts it and plays them into the speaker channels of both. Whoever starts it, starts the call. 1. **Both servers set up.** Each server needs its own speaker channels and roles, like any normal setup. 2. **Start cross-server.** The calling server types `/start-cross-server`. Either server can start one; `/stop-cross-server` ends it. 3. **Check both sides.** Ask one party on each server to confirm they hear the caller. > **Note: Teams don't apply across servers.** A cross-server relay sends the caller to everyone and ignores voice teams; your teams stay saved for normal relays. Plan split calls within one server. ### Talking back across the alliance Party leaders on both servers can use their priority key to reach the caller, exactly as they would at home. The same etiquette applies — see [party leaders: set up your priority key](https://www.nocapbots.com/blog/party-leader-priority-key.md). ### Put it into practice - [Alliances: relay across two Discord servers](https://www.nocapbots.com/docs/voice-relay/alliances.md): Link two Discord servers with a single-use invite code so one caller reaches the speaker channels of both. The allied server gets Guild Master free. - [Plans, billing and transfers](https://www.nocapbots.com/docs/billing.md): NoCap Bots plans and billing: free trial, upgrading, cancelling, payment details, moving a subscription to a new server and server transfer requests. - [Voice Relay slash commands](https://www.nocapbots.com/docs/voice-relay/commands.md): Every Callout slash command: /start, /stop, /status, /ping, /start-cross-server and /stop-cross-server, and who can use them. ## How to run voice comms for 100-player PvP Source: https://www.nocapbots.com/blog/voice-comms-for-large-scale-pvp Published: 2026-10-02 Updated: 2026-11-06 Topic: Leadership > Give one person the call, name a backup, and let party leaders talk up only when the caller needs it. Keep every call in the same shape — who, what, when — and the fight stays readable even at a hundred players. ### One voice makes the call Large fights fall apart when three people give three directions. Pick a shot caller before the fight and agree that their call stands, even when it's wrong. A wrong call followed by everyone beats a right call followed by half. Name a **backup caller** too. If the caller dies, lags out or needs a breather, the backup picks up without anyone asking who's in charge. In NoCap Bots that is the primary and backup role: the backup is relayed only while the primary is quiet — see [voice priority filtering](https://www.nocapbots.com/docs/voice-relay/configuration.md#voice-priority-filtering). ### Every call has the same shape Who, what, when. Say it in that order, every time, so players can stop listening the moment they know it's not for them. > Alpha, Bravo — push north gate. Now. > > — Who, what, when > Everyone — hold on the bridge. On my mark. > > — When can be a promise of a later call - **Who** first, by party name. It's how squads filter. - **What** in as few words as possible. Use the names your guild already uses for places. - **When** last: now, on my mark, or after the next wave. ### Party leaders run their party Each party keeps its own channel for its own chatter: cooldowns, heals, who's low. The party leader turns the caller's intent into what their party does. When the caller needs to know something — a flank is collapsing, a party is wiped — the leader uses their **priority key** to reach the caller directly. [Talk back](https://www.nocapbots.com/docs/voice-relay/talk-back.md) explains the setup. > **Note: Priority means priority.** Agree that the priority key is for information the caller can act on. If every leader narrates their fight to the caller, the caller hears nothing. ### Before the fight 1. **Sort parties.** Everyone in their party channel ten minutes before. Leaders confirm numbers. 2. **Check the relay.** Run `/start`, then `/status` — it shows whether it's live and who is speaking. A quick “Alpha, say yes” from the caller confirms every party hears them. 3. **Say the plan once.** The caller explains the plan in plain words, then asks for questions on the priority key only. ### When one caller isn't enough Some fights have two objectives at once. Rather than one caller trying to run both, split the calls — we wrote that up in [running attack and defense at the same time](https://www.nocapbots.com/blog/attack-and-defense-callers.md). ### Put it into practice - [Configure roles, channels and voice priority](https://www.nocapbots.com/docs/voice-relay/configuration.md): The Voice Relay configuration page explained: starter role, shot caller channel, primary and backup caller roles, and the four things /start needs. - [Talk back: let party leaders reach the caller](https://www.nocapbots.com/docs/voice-relay/talk-back.md): Set up Discord Priority Speaker so party leaders can talk to the caller with a priority push-to-talk key while their normal key stays in their squad. - [Voice teams: run several callers at once](https://www.nocapbots.com/docs/voice-relay/voice-teams.md): Use Voice Relay's voice teams to run attack and defense callers at the same time, each heard only by their own speaker channels. ## Can you talk in two Discord voice channels at once? Source: https://www.nocapbots.com/blog/talk-in-two-discord-voice-channels Published: 2026-09-18 Updated: 2026-11-06 Topic: Under the hood > No: a Discord account can be in one voice channel at a time, and your voice only reaches that channel. Guilds work around it by cramming everyone into one channel, using a stage, or relaying the caller with one bot per party channel — the last keeps squads in their own channels. ### The limit Join a voice channel and Discord sends your microphone to the people in that channel and nobody else. Click into another channel and you leave the first one. That is true across servers too: one account holds one voice connection at a time. For a five-person dungeon that is exactly right. For a 60-player siege split into eight parties it is a problem, because the one person everybody needs to hear — the shot caller — can only sit in one of those channels. ### What guilds try instead | Approach | What goes wrong | | --- | --- | | Everyone in one channel | Sixty open mics. Party leaders can't talk to their party without talking over the caller. | | A stage channel | Clean for the caller, but the audience can't talk at all, so parties lose their own comms. | | Party leaders repeat the call | Every call arrives late and slightly different, eight times. | | The caller hops between channels | By the time they reach the fourth party, the fight has moved. | Each of these trades one problem for another. What you actually want is for parties to keep their own channel and their own chatter, with the caller laid on top. ### How a voice relay does it Bots have the same rule as people: one voice connection per server. So a relay uses several. One bot sits in the caller's channel and listens; one **speaker bot** sits in each party channel and plays what the listener hears. [How it works](https://www.nocapbots.com/docs/voice-relay/how-it-works.md) covers the audio path in detail. - Parties stay in their own channels and talk normally. - The caller is heard everywhere at the same moment — about a tenth to three tenths of a second behind. - Only chosen roles are relayed, so a random person in the caller channel isn't broadcast to everyone. > **Tip: Count your parties, not your players.** You need one speaker bot per party channel, not per player. A 60-player raid in eight parties needs eight. See [speaker bots](https://www.nocapbots.com/docs/voice-relay/speaker-bots.md). ### And the other direction? A relay carries the caller out to the parties. For party leaders to reach the caller, Discord's Priority Speaker permission does the job: a second push-to-talk key that the relay carries back to the caller channel. We wrote up the setup in [party leaders: set up your priority key](https://www.nocapbots.com/blog/party-leader-priority-key.md). ### Try it Setting it up takes about ten minutes from an empty server: [getting started](https://www.nocapbots.com/docs/voice-relay/getting-started.md) walks through it. ### Put it into practice - [How Voice Relay carries Discord voice](https://www.nocapbots.com/docs/voice-relay/how-it-works.md): Why Discord voice needs bots to reach several channels, how the speaker bots relay audio with no transcoding, and what latency to expect. - [Speaker bots: one bot per party channel](https://www.nocapbots.com/docs/voice-relay/speaker-bots.md): How the Callout speaker bots work: one slot per channel on your plan, an invite button each, picking channels, private channels and stage channels. - [Set up Voice Relay from an empty Discord server](https://www.nocapbots.com/docs/voice-relay/getting-started.md): Set up a Discord voice relay in about ten minutes: make the channels and a caller role, invite the bot, pick roles and speaker channels, then type /start.