While GHOUL RE emphasizes its intense PvP (Player versus Player) environment—including the challenging Perma Death PvP mode—developers have not overlooked the PvE (Player versus Environment) landscape. The latest update introduces exciting Raid bosses, allowing players to take a break from relentless player killing. In this comprehensive GHOUL RE Boss Guide, we provide everything you need to know about these formidable foes.
How to Summon Bosses in GHOUL RE
In GHOUL RE, you can encounter two distinct boss types:
- CCG Bosses and Ghoul Bosses (the smaller encounters)
- Raid Bosses (the more challenging adversaries)

To summon smaller bosses, simply accept missions from your faction’s mission board. As a Ghoul player, you can undertake CCG Boss missions, while CCG members can take on Ghoul Boss missions. Upon accepting a mission, you’ll receive a yellow arrow indicating where the boss has spawned. Although these smaller bosses can be taken down solo, we recommend bringing along a friend or two for support, as rival faction players might disrupt your efforts.
In addition to CCG and Ghoul Boss missions, both factions can participate in Boss Fighting missions. These missions are unique as they spawn both an opposing faction boss and one of your own. This results in a spectacular clash between two NPC bosses, providing an opportunity for you to influence the battle. These encounters tend to be easier than typical boss missions since both bosses will primarily focus on each other, allowing you to deal damage with minimal distraction. Again, team up for safety.

To spawn a Raid Boss, first ensure you have 5,000 Yen (approximately $35.00 USD or €33.00). Next, seek out the Boss Raid NPC—a girl with blonde hair located near the CCG building—to summon one of the three available bosses. Once activated, you’ll be teleported to a designated area to engage in combat. You should definitely gather as many friends as possible, as up to 7 additional players can join you in the battle.
If you want to respawn any boss, simply accept another mission from the mission board or pay the fee again to the Raid Boss NPC.
Comprehensive Guide to GHOUL RE Raid Bosses
Soloing Raid Bosses without advanced tactics is incredibly challenging. These bosses boast immense health and powerful attacks that can deal significant damage. Therefore, it’s highly advisable to team up with a group of players (up to 8 can grapple with a Raid Boss) to increase your chances of success.
Eto Boss Guide in GHOUL RE

Eto는 GHOUL RE의 세 보스 중에서 가장 쉬운 보스라고 할 수 있지만, 격렬한 외형을 가지고 있습니다. 적절한 전략을 사용하면 예상보다 쉽게 처치할 수 있습니다. Eto는 4가지 독특한 공격을 가지고 있습니다:
- 기본 공격 – Eto는 반대쪽으로 팔을 흔들며, 예측할 수 있는 행동으로 막아낼 수 있습니다.
- 비명 – Eto가 머리를 숙이고 비명을 지릅니다. 막기 버튼을 연속으로 눌러서 이 공격에서 입는 피해를 줄이세요.
- 맹타 – Eto가 주먹을 들어서 내리칠 때 발생하며, 이를 막기는 불가능하고 회피해야 합니다.
- 조각 – Eto가 등을 돌리고 있으며 조각을 방출합니다. 이 공격은 막기 버튼을 신속히 눌러 막아낼 수 있습니다.
눈앞에 도전처럼 보일지라도, Eto의 공격을 배우면 팀이 빠르게 처치할 수 있습니다. 대부분의 전투는 3분에서 5분 사이 지속되며, 전투 중에 플레이어들은 적응할 가능성이 높습니다.
Eto를 쉽게 이기려면, 투기장의 한쪽 구석에서 바위 뒤에 숨으세요. Eto는 이곳에 도달할 수 없기 때문에 체력이 회복됩니다. 필요할 경우 회복을 위해 바위 뒤로 물러나며 Eto에게 지속적으로 피해를 주며 이 전략을 반복하세요.
Tatara Boss Guide in GHOUL RE

Tatara는 Eto보다 예측 가능하지만, 더 높은 체력으로 도전이 될 수 있습니다. 처음에는 피해량이 낮아 실망할 수 있지만, 전투를 계속 진행하면 Tatara는 관리 가능한 탱키 보스가 됩니다.
- 기본 공격 – Tatara는 팔을 흔들어 플레이어를 공격하며, 쉽게 막아낼 수 있습니다.
- 화염 방사기 – 주먹을 치며 화염 공격을 방출합니다. 연속으로 막기 버튼을 눌러 이를 효과적으로 방어할 수 있습니다.
- 맹타 + 맹타 – 파란색이 빛나지 않는 주먹을 쥐고 박수를 치며, 땅을 공격합니다. 대부분의 공격은 막아낼 수 있지만, 마지막 맹타는 회피해야 합니다.
- 맹타 – Tatara가 팔을 들어 공격합니다. 이 공격 역시 회피가 필요합니다.
한 플레이어는 방어에 집중하고 다른 플레이어는 피해를 입힙니다. 방어하는 플레이어는 회복 기술을 보유하고 회피에 중점을 두며, 파트너는 뒤에서 공격합니다. 두 플레이어 모두 강력한 장비와 능력이 필요합니다.
Nero Boss Guide in GHOUL RE

Nero는 Raid 보스 중에서 가장 적은 공격을 가지고 있지만 가장 높은 피해를 입힙니다. 대부분의 공격은 막아낼 수 있으므로, 연습하면 이 보스는 가장 쉬운 전투 중 하나가 될 수 있습니다. 그러나 주의하십시오. 넓은 지역에 걸쳐 있는 공격은 플레이어들이 준비가 되어 있지 않은 경우 크게 피해를 입힐 수 있습니다.
- 기본 공격 – Nero는 한 촉수를 옆으로 찌르며, 이를 막을 수 있습니다.
- (점프) 맹타 공격 – 전투 시작 시, Nero는 한 대상을 선택해 맹타 공격을 수행합니다. 이는 막을 수 있으며, Nero와 가까이 머물러 이 공격이 재발하지 않도록 하십시오.
- 포옹 공격 – Nero가 모든 촉수를 펼쳐서 내리침니다. 이 공격은 막기에 어려울 수 있습니다.
- 공 굴리기 공격 – Nero가 촉수를 공 모양으로 말아서 방출합니다. 이 공격은 차단되지 않으면 뒤로 밀려날 수 있으므로 조심하세요.
현재로서는 Nero를 처치하는 치트 방법이 알려져 있지 않습니다.
Loot Drops from GHOUL RE Bosses
대부분의 GHOUL RE 보스들은 유사한 전리품 풀을 공유합니다. Raid 보스들은 약간의 고유한 아이템을 제공하지만, 플레이어들은 모든 보스에서 비슷한 전리품을 기대할 수 있습니다. 아래는 잠재적인 드롭 목록입니다.
| Loot Type | Loot Name |
| 장비 | 판다 마스크, 요모 복장, 시니어 조사관 블랙, 절망 목걸이, 백정 크리스털, 다리 사슬, 피 묻은 망토, 손목 밴드 |
| 조각들 | 링카쿠, 코우카쿠, 우카쿠, 비카쿠, 카쿠주 (정상 및 정제됨) |
| 기타 | 판다 마스크, 요모 복장, 시니어 조사관 블랙, 절망 목걸이, 백정 크리스털, 다리 사슬, 피 묻은 망토, 손목 밴드 |
또한, 각 Raid 보스에는 몇 가지 고유한 드롭이 있지만 이는 보장되지 않습니다:
- Eto – 한쪽 눈을 가진 조각, SSS 올빼미 청사진
- Nero – 기형 가쿠호 조각, 긴쿠이 청사진
- Tatara – 한쪽 눈을 가진 조각, 솔레이스 청사진
이제 GHOUL RE에서 성공적인 보스 레이드에 나설 준비가 되었습니다. 친구들과 함께 흥미진진한 만남을 즐기고 귀중한 전리품을 얻어보세요! 아직 하지 않았다면, 환상적인 무료 아이템을 위한 GHOUL RE 코드를 놓치지 마세요.
FAQ – Frequently Asked Questions About GHOUL RE Bosses
What are the different types of bosses in GHOUL RE?
In GHOUL RE, you will find two main types of bosses: smaller CCG and Ghoul Bosses, and the formidable Raid Bosses.
How to summon Raid Bosses in GHOUL RE?
To summon a Raid Boss, you need to have 5,000 Yen and interact with the Boss Raid NPC located near the CCG building.
Is it possible to defeat Raid Bosses solo?
While technically possible with advanced tactics, it is highly recommended to team up with friends, as Raid Bosses are tough and require multiple players to overcome effectively.
What rewards do I get for defeating bosses in GHOUL RE?
You can expect various loot types including gear, fragments, and unique items from Raid bosses. Rewards can differ between bosses, providing incentives to engage with each one.
Can I respawn bosses in GHOUL RE?
Yes, you can respawn bosses by accepting another mission from the mission board or repaying the fee to the Raid Boss NPC.
우리의 활동을 지원해주세요 ❤️
이 글이 마음에 드셨다면, 앞으로도 좋은 콘텐츠를 계속 발행할 수 있도록 팁을 남겨주세요.















![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)



