확정적인 파이브 나이츠 TD 등급 리스트를 만드는 것은 작은 일이 아니었습니다. 200개 이상의 유닛을 고려해야 했기 때문입니다. 하지만 우리는 게임의 최강 후보자들만을 강조하기 위해 최종 유닛 등급 리스트를 신중하게 선별했습니다. 등급을 살펴보겠습니다!
파이브 나이츠 TD 등급 리스트

게임의 엄청난 다양성을 고려하여, 우리는 각 희귀도 카테고리의 상위 10개 유닛으로 초점을 좁혔습니다. 뛰어난 재능만을 보여줍니다.
파이브 나이츠 TD의 상위 10개 에이펙스 유닛
| 유닛 이름 | 비용 | 피해 유형 | 배치 |
|---|---|---|---|
서리의 프레디 |
$17,500 (€16,339) | 관통 확산 / 느리게 함 | 1 |
우주 보니 |
$25,000 (€23,292) | 지속적인 폭발 | 2 |
커피 |
$400 (€372) | 피해 + 쿨다운 부스터 | 8 |
무덤의 폭시 |
$34,000 (€31,650) | 소환자 | 3 |
크로노스 엔도 프레디 |
$24,879 (€23,059) | 핵 폭발 수동 | 1 |
블랙 아이스 프레디 |
$17,500 (€16,339) | 원뿔 AoE 수동 | 2 |
과거의 결과 |
$11,340 (€10,497) | AoE 수동 | 1 |
어둠의 기사 인형 |
$21,000 (€19,516) | AoE 수동 | 2 |
금도금 기사 |
$21,000 (€19,516) | AoE 수동 | 2 |
늙은 크람푸스 |
$11,340 (€10,497) | AoE 느리게 함 수동 | 1 |
파이브 나이츠 TD의 상위 10개 악몽 유닛
| 유닛 이름 | 비용 | 피해 유형 | 배치 |
|---|---|---|---|
문 드롭 |
$6,000 (€5,557) | AoE 기절 | 2 |
일식 발로라 |
$850 (€785) | 지원 | 3 |
서리 여왕 발로라 |
$1,200 (€1,109) | 쿨다운 부스터 / 느리게 함 | 3 |
엔나드 |
$18,000 (€16,647) | 체인 쇼크 | 2 |
발키리 프라임 |
$10,000 (€9,265) | 지속적 | 2 |
나야 나 |
$12,500 (€11,611) | 원뿔 AoE | 1 |
피클 항아리 |
$3,000 (€2,785) | 지원 느리게 함 | 3 |
DJ 뮤직맨 |
$1,000 (€926) | 쿨다운 부스트 / 레인저 부스트 | 1 |
이국적인 버터 |
$15,000 (€13,898) | AoE | 1 |
갈레온 폭시 |
$8,000 (€7,404) | 폭발 느리게 함 | 3 |
파이브 나이츠 TD의 상위 10개 비밀 유닛
| 유닛 이름 | 비용 | 피해 유형 | 배치 |
|---|---|---|---|
오래된 프레드베어 |
$600 (€556) | 원뿔 AoE 느리게 함 | 3 |
버킷 밥 |
$300 (€279) | AoE 느리게 함 | 4 |
클라운 트랩 |
$8,000 (€7,404) | 폭발 기절 | 3 |
강화된 엔도 02 |
$500 (€464) | 원뿔 AoE | 4 |
스크랩 베이비 |
$8,000 (€7,404) | AoE | 2 |
롤빗 |
$4,000 (€3,702) | 원뿔 AoE 기절 | 2 |
야간 경비원 애프톤 |
$550 (€509) | 원뿔 AoE 중독 / 느리게 함 | 3 |
전화 남자 |
$750 (€694) | AoE 느리게 함 | 3 |
하이드라 망글 |
$20,000 (€18,546) | 충전 AoE 화상 | 3 |
오래된 스프링 보니 |
$600 (€556) | 원뿔 AoE | 3 |
그게 전부입니다! 이제 당신은 꿈의 FNAF 팀을 구성할 준비가 되었습니다. 다른 타워 디펜스 경험을 탐험하고 싶은 분들은 Anime Rangers X가 좋은 옵션이라는 것을 기억하세요.
우리의 활동을 지원해주세요 ❤️
이 글이 마음에 드셨다면, 앞으로도 좋은 콘텐츠를 계속 발행할 수 있도록 팁을 남겨주세요.





서리의 프레디
우주 보니
커피
무덤의 폭시
크로노스 엔도 프레디
블랙 아이스 프레디
과거의 결과
어둠의 기사 인형
금도금 기사
늙은 크람푸스
문 드롭
일식 발로라
서리 여왕 발로라
엔나드
발키리 프라임
나야 나
피클 항아리
DJ 뮤직맨
이국적인 버터
갈레온 폭시
오래된 프레드베어
버킷 밥
클라운 트랩
강화된 엔도 02
스크랩 베이비
롤빗
야간 경비원 애프톤
전화 남자
하이드라 망글
오래된 스프링 보니









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



