Audio Recording (automatic mode) and Voice Conversation (resident mode) can both want the bot in a voice channel. A bot can only be in one voice channel per Discord server, so the two features follow a simple rule that depends on where you set them. You never have to choose a winner by hand: the panel tells you what will happen before you save, and shows it afterwards.
🔌 The one rule to remember
- Same voice channel → the bot does both, at once, on a single connection.
- Different voice channels → the feature whose channel you set first keeps the priority. The other one gives way.
Only the automatic mode of Audio Recording and the resident mode of Voice Conversation compete this way. A recording started by hand with /record start and an on-demand /voice-chat start keep their usual behaviour, see the last section.
🤝 Scenario 1: the same voice channel
Set Voice channel it stays in (Voice Conversation, resident mode) and Target voice channel (Audio Recording, with Enable automatic recording on) to the same channel.
- The bot stays in the channel in resident mode and members can talk to it.
- When people are in the channel, it also records automatically, exactly as Audio Recording usually does.
- Both use one connection. Recording does not mute the bot and the conversation does not cut the recording.
- Everyone in the channel is told about both: the notice that the bot listens and answers, and the notice that it records.
- When the recording ends (everyone left), the bot stays for the conversation. If the resident conversation is switched off meanwhile, the recording simply carries on, and the bot leaves when it ends.
Both features show a Shares the channel badge, and the server's log gets one line saying so.
🥇 Scenario 2: different channels, the first one set has the priority
Say Audio Recording is set on #meetings and Voice Conversation on #lounge.
The one you set first keeps the priority. What that means depends on which one it is.
Audio Recording was set first
- The resident conversation uses the bot in #lounge while nobody is in #meetings.
- As soon as people join #meetings, the bot leaves #lounge for #meetings and starts recording.
- When the recording ends, the bot goes back to #lounge on its own.
Voice Conversation was set first
- The bot stays in #lounge, for the conversation.
- The automatic recording of #meetings does not start while the conversation is using the bot.
- A recording that is already running is never cut short to make room.
In both cases the feature that gives way shows a Gives way badge and the other one Has priority.
⏱️ Scenario 3: the order you set them in
What counts is the moment each feature started wanting its channel:
- Turning on Voice Conversation's resident mode and picking its channel, or turning on Audio Recording's automatic recording and picking its channel, sets that moment.
- Changing the channel sets it again, now. Moving a feature to another channel makes it the newest.
- Saving other settings (a role, a timeout, a model) changes nothing: the moment stays the one it was.
- Switching the mode or the automatic recording off clears it. Turning it back on sets a new one.
- Disabling a feature on the server and enabling it again also starts afresh.
The order is the panel's record, kept per server. Servers set up before this existed keep the behaviour they always had: the resident conversation keeps the bot, until one of the two channels is changed.
Examples
| What you do | Result |
|---|---|
| Set the recording on #meetings, then the conversation on #lounge | Recording has priority. The conversation gives way while the bot records. |
| Then move the recording to #events | The recording is now the newest: the conversation has priority. |
| Then move the conversation to #events too | Same channel: they share it. |
| Move one of them away again | The one moved is the newest, so the other has priority. |
⚠️ The confirmation window
When you save the second feature on a channel different from the first one's, the panel opens a window before saving. It names both channels, says the first feature keeps the priority, says what the bot will do, and suggests picking the same channel if you want both in one place.
Choose Save anyway to keep your choice, or Go back to change it. Nothing is saved until you confirm.
🏷️ Where you see it
- Server settings home (the list of features): a line above the list says what was settled, and both features carry a badge.
- Each feature's settings page: a badge and one sentence at the top say how this feature stands.
- Audit log of the server: one line when the two get settled, saying either that they share a channel or which one keeps the priority. It is written once; saving again without moving a channel adds nothing.
| Badge | Meaning |
|---|---|
| Has the bot to itself | The other voice feature does not want the bot. |
| Shares the channel | Same channel: the bot does both there. |
| Has priority | Its channel was set first. |
| Gives way | The other channel was set first. It uses the bot when it is free. |
🎛️ Manual use is unchanged
- A recording someone starts with
/record startalways takes the bot, even from a resident conversation. The conversation steps aside and comes back when the recording ends. /voice-chat start(on demand) never moves the bot out of a recording or out of a resident channel, and tells the person who holds it and where.