Guide
Running a multilingual Discord server: separate channels or one?
Two languages in one channel works for a while, and then nobody talks to anybody. Separate channels work too, until the smaller one runs empty. Here is which split holds up when, and how to spot the tipping point early.
No Administrator permission required. Set it up in the web dashboard.
Why this goes wrong
Running several languages rarely fails on the technology and almost always on supervision. In a mixed channel the biggest language wins within days, without anyone forbidding anything: answers arrive faster there, so that is where people write. The rest read along for a while, post less often and are eventually gone. Split the channels and the problem turns around. Everyone has a home, but two rooms of fifteen feel deader than one of thirty, and your team suddenly needs eyes in a language it may not read. Worst of all is the half solution: a German button under an English notice. Whoever sees that does not conclude that a word is missing, but that the server was not built for them. A gap stands out more than a language that is absent altogether.
What to decide first
Decide four things before the first channel exists. How many languages can you genuinely supervise? A language without a moderator who reads it is an unsupervised room, so count moderators, not members. Which language is the fallback everyone drops back to when nothing fits? Ours is English, because that is where the bot lands when no server language is set. Does the split run through channels or through roles? Roles keep the list short but also hide the room from the people who could help. And what stays shared? Rules, announcements and voice tolerate a split worst of all. Direction matters too: one channel first, and only split once a language has enough regulars. Opening empty rooms in advance is the surest way to keep them empty.
Step by step
- Count for a week which languages actually turn up in your general channel, and decide on that number rather than on a feeling.
- Set the server language in the dashboard on its-netting.com. It governs the rendered cards and the bot texts on that server.
- Give the two or three biggest languages a channel of their own and one person from the team who genuinely reads along there.
- Keep rules, announcements and the welcome in the fallback language plus the largest one, and pin a link to the remaining versions.
- Look at the numbers again after four weeks: split further only when a room carries itself, and merge back as soon as one falls silent.
The mistakes almost everyone makes
The first mistake is opening ten channels because the bot speaks ten languages. That number is a ceiling, not a plan. The second is translating the surface and leaving the error messages as they are. Those get read exactly when something is going wrong anyway. The third is machine translation with nobody who speaks the language: on our side the build checks ten languages before it builds at all, 775 keys times ten, and a missing key does not quietly fall back to English but raises a counter. The fourth is making the moderator of a language its translator as well; that person quits twice. The fifth is missing the departure, because nobody says goodbye: the messages simply stop.
Frequently asked questions
Below roughly a dozen regulars per language a shared channel stays livelier. Above that a split pays off, because by then enough people are around to answer each other. Regulars are what decides it, not the member count.
In the language set for the server; with no setting, the member’s Discord language decides, and English follows if that is not one of the ten. Slash command names are served by Discord itself and shown to everyone in their own client language, so you may well see something different from the person next to you in the same channel.
In practice yes, as soon as you punish by them. A warning for a rule somebody could not read will not survive the appeal. So keep the enforced part short enough that a proper translation stays realistic.
Not from the member count, which stays put. Look at how many people write in that channel per week and how long the first answer takes. If the response time there pulls away from the main channel, the group is already on its way out.
One channel per language, or everything in one?
Below roughly a dozen regulars per language a shared channel stays livelier. Above that a split pays off, because by then enough people are around to answer each other. Regulars are what decides it, not the member count.
Which language does the bot answer in?
In the language set for the server; with no setting, the member’s Discord language decides, and English follows if that is not one of the ten. Slash command names are served by Discord itself and shown to everyone in their own client language, so you may well see something different from the person next to you in the same channel.
Do the rules have to exist in every language?
In practice yes, as soon as you punish by them. A warning for a rule somebody could not read will not survive the appeal. So keep the enforced part short enough that a proper translation stays realistic.
How do I notice that a language group is drifting away?
Not from the member count, which stays put. Look at how many people write in that channel per week and how long the first answer takes. If the response time there pulls away from the main channel, the group is already on its way out.