업데이트됨: 마지막으로 헤이안 클랜 목록을 2025년 6월 11일에 업데이트했습니다.
로블록스의 헤이안의 생생한 세계로 뛰어들면, 클랜의 개념이 단순한 커뮤니티 소속을 넘어선다는 것을 발견하게 될 것입니다. 이는 귀하의 캐릭터 외모와 관련이 있습니다! 많은 게임들이 클랜을 특별한 능력과 연결짓지만, 헤이안에서는 캐릭터의 머리색과 스타일을 결정합니다. 주술회전의 좋아하는 캐릭터를 체현하고 싶었던 적이 있나요? 클랜을 재롤링하면 그 꿈에 한 발짝 더 가까워질 수 있습니다. 귀하의 경험을 최적화하기 위해 궁극적인 헤이안 클랜 목록 및 가이드를 탐색해 보겠습니다.
헤이안 클랜 목록
아래는 헤이안의 모든 클랜에 대한 포괄적인 목록이며, 머리색에 따라 분류되었습니다. 각 클랜의 희귀도와 비율도 함께 기재되어 있습니다:
검은 머리 클랜
| 클랜 | 희귀도 | 비율 |
|---|---|---|
| 토도 | 9.44% | 14 |
| 제닌 | 0.303% | 0.45 |
| 오코츠 | 0.236% | 0.35 |
| 후시구로 | 0.539% | 0.8 |
| 미치자네 (하얀 눈) | 6.068% | 9 |
갈색 머리 클랜
| 클랜 | 희귀도 | 비율 |
|---|---|---|
| 쿠사카베 | 13.486% | 20 |
금발 머리 클랜
| 클랜 | 희귀도 | 비율 |
|---|---|---|
| 나나미 | 10.114% | 15 |
| 다쿠마 (노란 눈) | 10.789% | 16 |
| 아베 (연두색 눈) | 0.135% | 0.2 |
흰머리 클랜
| 클랜 | 희귀도 | 비율 |
|---|---|---|
| 고조 | 0.067% | 0.1 |
| 이누마키 | 13.486% | 20 |
기타 머리 클랜
| 클랜 | 희귀도 | 비율 |
|---|---|---|
| 이에리 (생강) | 6.743% | 10 |
| 쿠기사키 (생강) | 10.114% | 15 |
| 카시모 (청록색) | 5.394% | 8 |
| 하카리 (밝은 보라색) | 2.697% | 4 |
| 료멘 (연한 빨강, 빨간 눈) | 0.067% | 0.1 |
| 이타도리 (밝은 빨강) | 10.115% | 15 |
| 요루이치 (어두운 분홍색) | 0.202% | 0.3 |
헤이안에서 클랜을 재롤링하는 방법
헤이안에서 클랜을 바꾸는 방법이 궁금하신가요? 간단합니다: 캐릭터를 삭제하고 새로 만드세요. 새 캐릭터를 만들 때마다 클랜이 무작위로 할당됩니다. 일부 클랜은 출현 비율이 매우 낮을 수 있으므로 인내가 필요합니다. 특정 클랜을 찾고 있다면 더욱 그렇습니다. 클랜은 순전히 미적 요소로만 작용하며, 게임 플레이상의 장점은 없지만 고조와 미치자네 클랜은 무한 저주 기술에 접근할 수 있습니다.
헤이안 경험이 즐겁다면 아래 댓글에 좋아하는 클랜을 공유하세요. 선택한 클랜에 어떤 저주 기술이 어울리는지 확인하려면 제 헤이안 저주 기술 티어 목록도 확인하는 것을 잊지 마세요.
헤이안에서 클랜은 무엇인가요? 헤이안의 클랜은 귀하의 캐릭터 머리색과 스타일을 결정하며, 이는 주술회전의 캐릭터에서 영감을 받았습니다.
헤이안에서 클랜을 재롤링할 수 있나요? 네, 캐릭터를 삭제하고 새로 시작함으로써 헤이안에서 클랜을 재롤링할 수 있습니다.
헤이안의 클랜은 어떤 이점이 있나요? 장점을 제공하는 클랜은 고조와 미치자네이며, 두 클랜 모두 무한에 접근할 수 있습니다.
헤이안에 대해 더 알아볼 준비가 되셨나요? Moyens I/O의 다른 멋진 가이드를 확인해 보세요.
우리의 활동을 지원해주세요 ❤️
이 글이 마음에 드셨다면, 앞으로도 좋은 콘텐츠를 계속 발행할 수 있도록 팁을 남겨주세요.
















![THINK: The user wants to translate the title "Catch a Brainrot Tier List & Guide (RELEASE)" into Korean. I need to break down the key terms and concepts in the English title and find their appropriate Korean equivalents.
Catch a Brainrot: This is a playful, internet slang phrase.
"Brainrot" (뇌절) is a common internet slang in Korean, referring to something so cringey, overdone, or nonsensical that it makes your brain "rot" or shut down. It can also mean obsessing over something to an unhealthy degree.
"Catch a Brainrot" could be interpreted as "falling into brainrot," "getting brainrot," or simply "experiencing brainrot."
A common way to express "getting into / falling into [something bad/annoying/overdone]" in Korean internet slang is by using the noun and then implying the action. For example, "뇌절" itself can be used. Or, one might say "뇌절 각" (a situation ripe for brainrot), or "뇌절 유발" (brainrot-inducing).
However, "Catch a Brainrot" here seems to be the topic of the tier list. The tier list is about brainrot. So, maybe just referring to "brainrot" is enough.
Let's consider the nuance. "Catch a Brainrot" implies an action or a state. A tier list for brainrot items/situations.
Perhaps something like "뇌절 요소" (brainrot elements/factors) or "뇌절 유형" (brainrot types).
Or, simply using "뇌절" as the core concept.
If it's about identifying and categorizing different "brainrot" things, then "뇌절" as a concept is central.
"Catch a Brainrot" can be a bit tricky. Does it mean "how to get brainrot" or "how to identify brainrot"? Given the "Tier List & Guide," it's more likely about identifying and navigating different types of brainrot.
Let's try to capture the "catch" part. If it's about identifying or understanding brainrot.
"뇌절" is the direct translation for brainrot.
"잡다" (japda) means "to catch," but "뇌절을 잡다" doesn't sound natural in this context.
"뇌절에 대한" (about brainrot) or "뇌절 알아보기" (understanding brainrot).
Considering "Catch a Brainrot" as a playful, informal title, a direct translation might lose the feel.
Let's focus on what the tier list is. It's a tier list of brainrot-inducing things or brainrot situations. So the focus is on "brainrot."
Just "뇌절" might be sufficient as the object of the list.
Tier List: "티어 목록" (tieo mongnok) or "티어 리스트" (tieo riseuteu) are common. "등급표" (deunggeuppyo) is also possible for "tier list" or "ranking chart." "티어표" (tieopyo) is very common internet slang. "티어표" fits the informal tone better.
& Guide: "&" is often translated as "및" (mit), "그리고" (geurigo), or just omitted and implied by context. "Guide" is "가이드" (gaideu) or "안내서" (annaeseo). "가이드" is more common in such contexts.
(RELEASE): "(출시)" (chulsi), "(공개)" (gonggae), or "(발매)" (balmae). "(출시)" or "(공개)" are suitable for a content release. "(공개)" is perhaps more general for a release of information/content.
Combining them:
Option 1 (Focus on "brainrot" as the subject):
뇌절 티어표 & 가이드 (공개)
(Noejjeol tieopyo & gaideu (gonggae))
Option 2 (Trying to keep "catch"):
Is there a way to say "spotting brainrot" or "understanding brainrot" in a concise, slangy way?
"뇌절 잡기" (noejjeol japgi) - "catching brainrot," but again, "잡기" sounds like a game or a physical action.
"뇌절 포착" (noejjeol pochak) - "detecting/spotting brainrot," but "포착" is a bit too formal.
"뇌절 알아보기" (noejjeol arabogi) - "getting to know brainrot," "learning about brainrot."
"뇌절 공략" (noejjeol gongnyak) - "brainrot strategy/guide," implies how to deal with/understand brainrot. This is often used for game guides. This could fit "Catch a Brainrot Tier List & Guide."
Let's reconsider "Catch a Brainrot." If it's a guide for catching brainrot elements, then "뇌절 공략" or "뇌절 가이드" directly fits the "Guide" part.
The title is "Catch a Brainrot Tier List & Guide."
This implies the Tier List is about catching/understanding brainrot.
Let's break "Catch a Brainrot Tier List" as "뇌절 티어표." This means a tier list of brainrot.
Then "Guide" is just "가이드."
So, "뇌절 티어표 & 가이드" (Noejjeol tieopyo & gaideu) seems the most natural and concise translation for "Brainrot Tier List & Guide."
What about "Catch a"?
If the original was "How to Catch Brainrot: A Tier List & Guide," then "뇌절 잡는 법: 티어표 및 가이드" would be appropriate.
But it's "Catch a Brainrot Tier List & Guide." This phrasing suggests the tier list itself is a "catch a brainrot" type of list. It's almost like a category.
Perhaps "뇌절 캐치" (noejjeol kaechi - brainrot catch) could be integrated.
"뇌절 캐치 티어표 & 가이드" (Noejjeol kaechi tieopyo & gaideu)
"캐치" (kaechi) as in English "catch" is sometimes used for "catching on," "spotting," or "grabbing attention." This could work.
Let's compare:
뇌절 티어표 & 가이드 (공개) - Very direct, concise. "Brainrot Tier List & Guide (Release)." This implicitly covers "Catch a Brainrot" by making "brainrot" the subject of the list/guide.
뇌절 캐치 티어표 & 가이드 (공개) - Adds "캐치" which directly translates "Catch" and fits the informal tone. "Brainrot Catch Tier List & Guide (Release)." This explicitly states it's about catching or identifying brainrot.
Given the playful nature of "Catch a Brainrot," "뇌절 캐치" feels a bit more aligned with the original's intent of "spotting" or "identifying" brainrot items/situations. "캐치" is often used in Korean slang for "catching a glimpse," "catching on," or "spotting something."
Let's try to verify "뇌절 캐치". "밈 캐치" (meme catch) or similar phrases are used. It makes sense in an internet context.
So, the structure would be:
"Catch a Brainrot" -> 뇌절 캐치
"Tier List" -> 티어표
"& Guide" -> & 가이드
"(RELEASE)" -> (공개)
Putting it together:
뇌절 캐치 티어표 & 가이드 (공개)
Final check for plain text requirement:
"Return only the translated title as plain text. Do not include any explanations, additional text, formatting, or extra punctuation."
The chosen translation is "뇌절 캐치 티어표 & 가이드 (공개)". This fits all requirements.뇌절 캐치 티어표 & 가이드 (공개)](https://kr.moyens.net/wp-content/uploads/2026/07/1783863662_THINK-The-user-wants-to-translate-the-title-Catch-a-280x210.jpg)

![THOUGHT: The user wants to translate a title into Korean.
The title is "Haze Seas: Trello, Wiki & Discord Resources".
I need to break down the title into its components and translate each part.
Haze Seas: This sounds like a proper noun, possibly the name of a game, project, or community.
"Haze" can be translated as 안개 (an-gae).
"Seas" can be translated as 바다 (ba-da).
So, "Haze Seas" could be 안개 바다. If it's a fantasy name, sometimes direct translation works.
: (colon) - This is a separator, often kept as is or sometimes replaced by another connector in Korean if the flow requires it, but usually, a direct colon is fine, or contextually implied. However, the request specifically asks for plain text and no extra punctuation, so I should just translate the words and not add any extra punctuation like a colon if it's not explicitly part of the original word. The colon acts as a separator in the English title, so I should represent the relationship between the first part and the second part directly in Korean without adding a literal colon character in the final output. The instruction "Do not include any explanations, additional text, formatting, or extra punctuation" reinforces this.
Trello, Wiki & Discord Resources: This lists different types of resources.
Trello: This is a specific platform name, usually kept as is in Korean, written in Hangul. 트렐로 (teu-rel-lo).
Wiki: Also a specific platform/concept, usually kept as is in Korean, written in Hangul. 위키 (wi-ki).
&: "and". In Korean, this can be 와/과 (wa/gwa) or 및 (mit) or 그냥 (geu-nyang - just) or an implied 'and' by listing. Given it's a list of resources, '및' (and/as well as) is a good choice for connecting the last item in a list of categories.
Discord: Another platform name, kept as is in Korean, written in Hangul. 디스코드 (di-seu-ko-deu).
Resources: 자원 (ja-won - natural resources), 자료 (ja-ryo - data/material/resources), 리소스 (ri-so-seu - direct transliteration of resource, often used in IT/software contexts). For this context (Trello, Wiki, Discord for a project/community), 자료 or 리소스 would be appropriate. 자료 seems more natural for "information/guide resources".
Let's combine these:
Option 1 (direct translation, with implied colon/connection):
안개 바다: 트렐로, 위키 및 디스코드 자료
(Here, the colon is still present)
The instruction "Return only the translated title as plain text. Do not include any explanations, additional text, formatting, or extra punctuation." suggests I should not include the colon character if possible. I should try to make the Korean flow naturally without it.
Let's re-evaluate the structure without the colon:
"Haze Seas - Trello, Wiki & Discord Resources" implies "Resources for Haze Seas, specifically Trello, Wiki, and Discord ones." or "Haze Seas: These are the Trello, Wiki, and Discord resources related to it."
Korean sentence structure might be: "[Project Name] 관련 [Resource List] 자료" (Related [Resource List] Resources).
So, "[Haze Seas] 관련 트렐로, 위키 및 디스코드 자료"
안개 바다 관련 트렐로, 위키 및 디스코드 자료.
This sounds natural and avoids the colon.
Let's verify the "Haze Seas" translation again. If it's a proper noun, it might be better to transliterate or find a more common usage if it refers to a specific known entity. However, without more context, "안개 바다" (Fog Sea / Haze Sea) is a direct and reasonable translation for a name like "Haze Seas."
Let's consider "리소스" vs "자료". "리소스" is a direct transliteration and commonly used in IT/game contexts for "resources." "자료" is more general for "data/materials/information." Given Trello, Wiki, Discord are tools for managing information/materials, both work. "자료" might feel slightly more natural for "information resources" in a general sense. However, "리소스" is perfectly acceptable and often used. I'll go with 자료 for now.
So, the structure is:
[Project/Community Name] + [Connector for relatedness] + [List of platforms] + [Type of resources].
"Haze Seas" = 안개 바다
"related to" / "for" = 관련 (gwan-ryeon) or 의 (ui - possessive, less common here)
"Trello, Wiki & Discord" = 트렐로, 위키 및 디스코드
"Resources" = 자료
Combining:
안개 바다 관련 트렐로, 위키 및 디스코드 자료
This fits the "plain text" and "no extra punctuation" requirement as it directly translates the meaning without including the English colon.
Final check on the parts:
Haze Seas -> 안개 바다 (An-gae Ba-da)
Trello -> 트렐로 (Teu-rel-lo)
Wiki -> 위키 (Wi-ki)
Discord -> 디스코드 (Di-seu-ko-deu)
& -> 및 (mit - and, as well as)
Resources -> 자료 (ja-ryo - materials, data, resources)
The colon's function is to relate "Haze Seas" to the list of resources. "관련" (gwan-ryeon - related, concerning) serves this function naturally in Korean.
The translation "안개 바다 관련 트렐로, 위키 및 디스코드 자료" seems robust.안개 바다 관련 트렐로, 위키 및 디스코드 자료](https://kr.moyens.net/wp-content/uploads/2026/07/1783230518_THOUGHT-The-user-wants-to-translate-a-title-into-Korean-280x210.jpg)



