Shot Calling in Throne and Liberty: Voice Setup for Large-Scale PvP
Throne and Liberty caps parties at six players and guilds at 70, so a full guild fighting a castle siege, a boonstone or riftstone battle, or a tax delivery ambush is split across twelve separate Discord voice channels. The shot caller sits in one of them; the other eleven parties hear nothing. The fix used by large guilds is a voice relay: the caller speaks once and is heard in every party channel at the same time, while each party keeps its own comms.
Why Throne and Liberty makes this harder than most MMOs
Six-player parties are small. A full 70-player guild is twelve of them: twelve voice channels. Castle sieges and big field battles add allied and enemy guilds on top, putting hundreds of players on the battlefield at once. Discord allows every account, including a bot, to sit in only one voice channel per server, so there is no native way for one voice to reach twelve channels. And unlike raid games with 40-player raid comms, TnL fights are fast, positional and objective-driven: a call like "collapse on the boonstone, now" is worthless if only one party of six hears it.
The comms hierarchy that works in practice
- Main caller (shot caller): one voice, heard in every party channel. Calls targets, pushes, retreats and objective swaps.
- Party channels: each six-player party keeps its own channel for party-level comms: heals, cooldowns, peels. The caller's voice plays on top.
- Info callers: one scout or party leader per flank whose voice reaches only the main caller's room. Field reports flow up without spamming the whole raid.
This mirrors how competitive TnL guilds already organize pings and map markers. The voice layer just has to follow the same shape.
How to set it up on Discord
dcshot is a voice relay service for Discord, built for MMO raid callouts. The setup for a TnL guild takes minutes in the web dashboard:
- Create your party voice channels as usual (Party 1–10, or per-role squads).
- Add the relay bots: one bot covers one party channel, up to 16 per Discord server.
- Mark your shot caller; optionally mark an info caller in each party.
- Players just join their party channel. Nothing to install, no overlay required, no second app.
For alliance content it scales further. An in-game TnL alliance pairs two guilds: up to 140 players in twenty-four six-player parties, each guild on its own Discord server. dcshot's alliance feature shares voice across allied Discord servers (up to four), so one caller can lead both guilds without anyone switching servers.
When you don't need a relay
If your guild runs small-scale content (arenas, dungeons, open-world skirmishes with one or two parties), a single shared voice channel is simpler and free. A relay starts paying off when three or more parties need their own comms and still have to hear one leader. For most TnL guilds that line is crossed at the first serious boonstone fight.
Facts worth knowing
Latency
Calls arrive in every party channel with sub-second latency, fast enough for positional PvP calls in live sieges.
Reliability
dcshot runs on a multi-server cluster with automatic failover. If a server fails mid-siege, bots migrate to a healthy machine within seconds.
Pricing
Credit-based, no cash subscription. Run 10 bots during siege season, drop to zero in the off-season. A month at zero costs nothing and credits never expire.
Scale
Up to 16 relay bots per Discord server. A full 70-player TnL guild needs 12 (one per party), so 16 covers it with headroom, plus alliance support across up to 4 Discord servers for multi-guild fights.
Ready before your next siege. Setup takes minutes and players install nothing.
Get started with 500 free credits