탈것은 Ninja Time에서 탐색하는 데 필수적이며, 특히 빠른 이동에는 배틀 패스가 필요합니다. 그러나 탈 수 있는 애완동물을 얻는 것은 즉각적이지 않습니다. 퀘스트를 완료하거나 클랜 스핀 중에 행운을 기대해야 합니다. Ninja Time에서 탈것을 얻는 방법에 대한 자세한 내용은 아래의 포괄적인 가이드를 읽어보세요.
Ninja Time에서 탈것 얻는 방법
-
Kaba NPC는 Ishikage NPC에서 마을 문까지 가는 도중 왼쪽 두 번째 다리 너머에 위치해 있습니다. -
레벨 22에 도달하여 Kaba NPC로부터 “A Good Company” 퀘스트를 수락하세요. -
퀘스트를 완료한 후 Kaba NPC로부터 다양한 탈것을 구매할 수 있습니다. -
Bird mount은 Kaba로부터 1 골드 코인에 구매할 수 있습니다.
Ninja Time에서 탈것은 Leaf Village의 Kaba NPC가 지정한 특정 퀘스트를 완료하여 얻을 수 있습니다. 퀘스트를 시작하려면 레벨 22에 도달해야 하며, 이는 주 스토리를 따라가면 간단합니다. 목표 레벨에 도달하면 강가에 있는 Kaba NPC를 찾아 “A Good Company”라는 퀘스트를 수락하세요.
탈것 퀘스트의 완수 작업은 단 하나입니다: 500,000 미터 여행하기입니다. 퀘스트를 수행하다 보면 몇 분 안에 완료할 수 있습니다. 또는 대시하고 점프하여 거리를 더 빨리 이동할 수 있습니다. 특정 가족 특성을 통해 이동 속도를 높이면 프로세스를 더욱 가속화할 수 있습니다. 퀘스트를 완료하면 Kaba의 상점에 접근할 수 있게 되어 코인을 사용해 탈것을 구매할 수 있습니다.
Ninja Time에서 Purple Eyes 클랜으로 조기 접근하여 탈것 얻기
운이 좋으면 Purple Eyes Clan을 조기에 얻을 수 있습니다. Ninja Time에서 레벨 22에 도달하기 전에 탈것을 얻을 수 있습니다. 레벨 7에 도달한 후 Purple Eyes Clan 스킬 트리에 두 개의 스탯 포인트를 투자하여 두 개의 탈것을 잠금 해제할 수 있습니다. Bird Invocation mount는 비행이 가능하여 다른 것보다 더 큰 장점이 있습니다.
Ninja Time에서 탈것 장비 및 소환하기
탈것을 핫바에 바인딩한 후 Ninja Time에서 1, 2, 3, 4 키를 사용하여 소환하세요. Purple Eyes Clan 탈것의 경우 назначенные 스킬 버튼을 이용하여 효과적으로 소환하세요.
Ninja Time에서 탈것 조작하기
Ninja Time에서 탈것을 조작하는 것은 간단합니다. A와 D를 사용하여 좌우로 회전하고, W와 S로 앞으로 및 뒤로 가속합니다. W 키를 두 번 눌러 질주를 합니다. 탈것이 비행할 수 있다면, 스페이스 키를 눌러 위로 올라가고 Ctrl 키를 눌러 내려옵니다. 탈것에서 내리려면 X 키를 누릅니다.
이로써 Ninja Time에서 탈것을 얻는 방법에 대한 우리의 가이드를 마칩니다. Purple Eyes Clan과 같은 클랜을 더 알아보려면, Ninja Time 클랜 목록 및 티어 리스트를 확인하여 추가 정보를 얻으세요.
자주 묻는 질문 (FAQ)
How do I get my first mount in Ninja Time?
첫 번째 탈것을 얻으려면, Kaba NPC로부터 “A Good Company” 퀘스트를 완료하세요. 레벨 22에 도달한 후에 가능합니다. 퀘스트를 완료하려면 500,000 미터를 여행해야 하며, Kaba의 상점에서 탈것을 구매할 수 있습니다.
Can I get mounts without completing quests?
예, Purple Eyes Clan의 일원이라면 퀘스트를 완료하지 않고 조기에 탈것을 잠금 해제할 기회가 있습니다. 레벨 7에 도달하고 스킬 트리에 두 개의 스탯 포인트를 투자하면 비행 및 지상 탈것을 소환할 수 있습니다.
What types of mounts are available in Ninja Time?
Ninja Time에서는 퀘스트를 통해 얻은 비행 탈것이나 Purple Eyes Clan의 소환 스킬을 통해 접근할 수 있는 다양한 탈것이 있습니다. 특정 탈것은 필요한 퀘스트를 완료한 후 Kaba의 상점에서 구매할 수 있습니다.
How do I control my mount in Ninja Time?
탈것을 조작하려면 A와 D 키로 방향을 바꾸고, W로 앞으로 이동하며, S로 뒤로 이동합니다. W를 두 번 눌러 질주하고, 비행 탈것의 경우 스페이스 키로 상승하고, Ctrl로 하강합니다. X를 눌러 탈것에서 내립니다.
우리의 활동을 지원해주세요 ❤️
이 글이 마음에 드셨다면, 앞으로도 좋은 콘텐츠를 계속 발행할 수 있도록 팁을 남겨주세요.
























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



