A bilingual name does not have to be a word-for-word translation. It needs to help two groups recognize the same community, say its name comfortably, and find the right place to join. Decide which parts of the identity must stay identical and which can change with the language.
A scene from an imagined guild
The English-speaking members pictured a harbour when they heard Tidehouse. Their Japanese friends pictured a building waiting for the sea to come in. Over a shared sketch of a lantern on a pier, the group found the image they actually wanted: somewhere to return after a long journey. They kept the English title, chose a natural Japanese companion name, and wrote one sentence explaining the connection. The sketch became more useful than the dictionary.
Choose a relationship between the two names
There are several workable arrangements. You can keep one Latin-script name everywhere, pair an English title with a Japanese reading, or create two natural names connected by the same image. An illustrative pair such as Lantern Assembly and 灯火の集い shares a welcoming idea without pretending that every word matches. Document the relationship in a sentence. If the English version sounds like a military unit while the Japanese version suggests a relaxed social circle, revise the pair before members build conflicting expectations around it.
Ask people to read before you explain
Show each version separately to fluent readers of that language. Ask what kind of guild they expect, how they would say the name, and what shortened form they would use. Leave room for unexpected answers. A dictionary can suggest a meaning, but it cannot predict every association inside a particular gaming group. When you use kanji with a less obvious reading, supply kana in a sensible location. Avoid making a decorative reading the only route to understanding a name that must work in routine conversation.
Give members one reliable way to search
Choose a stable shared identifier for your website, recruitment account, or tag. It can be a short Latin spelling even when the visible Japanese name uses Japanese script. Search each version and the identifier separately in the actual places your members use. Look for confusion with another active community, not just an exact match on a general search engine. Keep a written record of the chosen spacing and capitalization. Consistent presentation makes member-created event posts more useful and keeps the two language versions visibly connected.
Write the welcome message in both voices
Draft a short welcome paragraph for each language rather than translating a slogan in isolation. Explain what you play, how often you gather, and which language a newcomer can use to ask a question. Read the proposed name inside those paragraphs. A poetic phrase may feel natural in one introduction and strangely grand in the other. Resolve that tension by adjusting the name or the tone, then let bilingual members review the complete introduction. Keep the final pronunciation note short enough to reuse in a Discord welcome channel.
