Where Winds Meet Guild War: Offense and Defense Voice Setup
For Where Winds Meet 30v30 guild wars, the cleanest Discord setup gives offense and defense their own party channels and their own commander. Both commanders sit in one command channel. ShotCaller's Voice Teams sends each commander only to their own side, so the two can coordinate without either side hearing calls meant for the other.
Guild war spreads about 30 players over Top, Mid and Bot, and one voice struggles to cover pushes and defense at the same time. Here's how to organize it.
Why guild war comms fall apart
A Where Winds Meet guild war is a three-lane fight with towers, jungle bosses and the Goose and Tree objective. In-game voice doesn't scale to coordinating all 30 players, so competitive guilds use Discord.
Most guilds then hit one of these problems:
- One commander tries to call lanes, rotations and base defense together, and calls get missed.
- Everyone shares one channel, so defenders hear push calls that don't apply to them.
- Each group has its own channel and leader, and the leaders lose contact with each other.
Splitting the calls by team fixes the first two. Keeping both commanders in one channel fixes the third.
A voice setup for 30v30
Here's a starting layout. Change the channel count to match your roster and plan.
| Team | Commander role | Party channels |
|---|---|---|
| Offense | Offense Commander | Offense Top, Offense Mid, Offense Bot |
| Defense | Defense Commander | Defense Base, Defense Rotate |
| None | Guild Leader | Open to all |
Both commanders join a channel named something like Command. That's your shotcaller channel. Party members join their own party channel and stay there.
Here's what each person hears in that setup:
- Offense players hear the Offense Commander, the Guild Leader and their own party.
- Defense players hear the Defense Commander, the Guild Leader and their own party.
- Commanders hear each other and everyone else in Command.
The Guild Leader role has no team, so that voice reaches everyone. Use it for calls the whole guild needs, like the Goose or a full retreat.
Set it up before the next guild war
Step 1: Create the Discord roles
Create Offense Commander, Defense Commander and Guild Leader roles, and assign them to your callers. Add your backup callers to the same roles.
Step 2: Connect the channels
Follow the ShotCaller Discord bot guide to pick the shotcaller channel and assign a speaker bot to each party channel. Add Guild Leader as a shotcaller role so that caller reaches everyone.
Step 3: Add the teams
On the Configure page, turn on Voice Teams, then add Offense and Defense. Choose each team's commander role and channels. The configuration docs explain every field.
Step 4: Start before the match
Have callers join Command, then type /start. The bot lists both teams and warns you if a team channel has no bot. Team changes need /stop and then /start, so make them before the match. The command reference has the rest.
Do a short test in your pre-war meeting. Have each commander count to five, and ask one player from each side to confirm what they heard.
Who calls what
Teams separate the audio. You still need to agree who owns each decision. A split many guilds could start from:
| Call | Owner |
|---|---|
| Lane pushes and tower focus | Offense Commander |
| Rotations between lanes | Offense Commander, with a warning to Defense |
| Base defense and enemy rotations | Defense Commander |
| Goose and Tree timing | Guild Leader |
| Full retreat | Guild Leader |
Keep calls short and agree a tie-break before the match. Our PvP shotcalling guide goes deeper on call structure, and What Is a Shotcaller? is a good share for new callers.
Let party leaders report back
Commanders can't see the whole map, so party leaders need a way to report without crowding a channel. Give them Priority Speaker in their party channel. When they hold Push to Talk (Priority), their voice reaches Command, and both commanders hear it. The talk-back guide shows the keybinds.
Both commanders hear every report, so an enemy sighting from a defense party leader reaches the Offense Commander too.
Should you use one commander instead?
One commander is simpler, and it suits guilds with one strong caller. A plain broadcast to every channel is enough for that. Split teams are worth it when you have two capable callers and your guild is often fighting on two fronts. You can switch Voice Teams off for a war and your teams stay saved.
Teams also apply to larger guild setups. Discord Bots for Gaming Guilds covers what else to run around voice.
FAQ
Can I run offense and defense commanders in Where Winds Meet on Discord?
Yes. Put both commanders in one command channel and use Voice Teams to send each one to their side's party channels. They hear each other directly, and each side hears only its own commander.
How many Discord channels do I need for a 30v30 guild war?
It depends on your parties. The layout above uses five party channels plus a command channel. Every party channel needs a speaker bot, so check that your plan covers your count.
Can the whole guild hear one person?
Yes. Give that person a shotcaller role that isn't in any team. A caller with no team is heard by every channel.
Does in-game voice work for guild wars?
In-game voice doesn't scale to coordinating all 30 players, which is why guilds use Discord for competitive guild wars.
Can players still talk to their party?
Yes. Members talk in their party channel as normal and hear their commander through the bot.
Can I talk to just one team as a caller?
Yes. A caller reaches their own team. How to Whisper in Discord explains the limits of this kind of routing.
Does it work if we fight with an allied guild?
Cross-server events ignore teams, so everyone hears the caller.
Get your guild ready
Set your teams up once and they're ready for every guild war. The Voice Teams guide has the complete walkthrough, and How to Run Two Shotcallers on Discord covers the general version. Try it free for 7 days. See plans.