Rock Fruit의 과일은 Swords and Specs만큼 강력하지는 않지만, 초기 게임 경험을 크게 향상시킵니다. 과일 획득이 주로 RNG에 기반하기 때문에, 아래의 Rock Fruit 과일 티어 리스트를 참고하면 효율적으로 리롤하고 최고의 과일을 선택하는 데 도움이 될 것입니다.
Rock Fruit의 과일이란?
Rock Fruit에서의 과일은 특별한 능력을 제공하는 독특한 아이템입니다, 피해는 DevilFruit 능력치에 따라 결정됩니다. 대부분의 희귀 과일은 다섯 가지 능력(Z, X, C, V, F)을 갖고 있으며, 일부 일반 과일은 네 가지(Z, X, C, V)만 가지고 있습니다. One Piece에서 영감을 받은 많은 Roblox 타이틀과는 달리, Rock Fruit에서 과일을 복용해도 수영할 때 피해를 입지 않습니다.
Rock Fruit 과일 티어 리스트

이 티어 리스트는 Rock Fruit의 모든 과일을 PvE와 PvP, 무한 모드, 레이드, 그리고 농사 또는 AFK 파밍 중 효율성을 기준으로 평가하여 순위를 매겼습니다. 각 과일은 DPS, 범위, AoE, 유틸리티(비행과 같은), 군중 제어(CC) 능력에 대해 평가되었습니다. 아래의 종합 리스트에서 각 과일의 장단점을 자세히 확인할 수 있습니다.
Rock Fruit의 과일 리스트
| 과일 | 장점 및 단점 | 티어 |
|---|---|---|
![]() |
+ 메타 DPS 과일 + 괜찮은 스턴 + 훌륭한 범위와 AoE + 모든 콘텐츠에 적합 | S |
![]() |
+ 엄청난 범위 + 우수한 DPS + 최고의 과일 중 하나 − 좁은 AoE 능력 | A |
![]() |
+ 높은 DPS + 많은 스턴 + 좋은 범위와 AoE | A |
![]() |
+ 훌륭한 범위 + 좋은 DPS + 강력한 중반 옵션 − 좁은 선형 AoE 능력 | A |
![]() |
+ 좋은 동결 CC + 좋은 범위와 AoE + 짧은 쿨다운 − 매우 낮은 DPS | A |
![]() |
+ 비행 능력 + 괜찮은 DPS, 범위 및 AoE − 다른 전설 과일에 비해 미미함 | B |
![]() |
+ 괜찮은 중반 선택 + 적절한 DPS 및 AoE − 낮은 범위 | B |
![]() |
+ 좋은 AoE 및 피해 − 한정된 범위 − 스턴이나 CC 없음 | B |
![]() |
+ 좋은 범위 + 순간이동 능력 + 괜찮은 CC − 매우 낮은 DPS | C |
![]() |
+ 괜찮은 AoE와 범위 + 타격 시 HP 회복 − 낮은 DPS | C |
![]() |
+ 괜찮은 범위와 AoE − 초기 게임에 가장 적합 − 낮은 DPS | C |
Rock Fruit에서 과일을 얻고 사용하는 방법

Rock Fruit에서 과일을 얻는 방법은 두 가지입니다: 가챠 롤과 컬러풀 나무 아래에서 수집하는 것입니다. 가챠 상자는 첫 번째 바다의 선술집 안에 편리하게 위치해 있습니다. 각 롤은 50 다이아몬드를 요구합니다. 또한, 매 5분마다 Rock Fruit 세계 곳곳에 흩어져 있는 컬러풀 나무 아래에서 랜덤 과일이 등장할 수 있습니다. 발견한 과일에 걸어가면 자동으로 수집됩니다.
과일을 소비하려면, 인벤토리에서 그것을 장착하고, 들고 사용해야 합니다. 과일을 먹으면 현재 장착한 과일은 영구적으로 잃게 됩니다. 한 번에 하나의 과일만 장착할 수 있습니다. 다른 플레이어와 과일을 거래하거나, 다른 사람들이 줍도록 버릴 수도 있습니다.
이로써 Rock Fruit 과일 티어 리스트가 마무리되었습니다. 무료 다이아몬드를 받고, 혹시 최고 등급의 과일을 획득하고 싶다면, 저희의 Rock Fruit 코드를 확인해보시기 바랍니다.
Rock Fruit 과일 티어 리스트 FAQ
Rock Fruit에서 최고의 과일은 무엇인가요?
Rock Fruit에서 최고의 과일은 Rumble, Rubber, Gura, Smoke, Ice입니다.
한 번에 두 개 이상의 과일을 장착할 수 있나요?
아니요, 플레이어는 한 번에 하나의 과일만 장착할 수 있습니다. 새로운 과일을 소비하면 현재 장착된 과일이 제거됩니다.
과일 움직임의 피해를 증가시키는 방법은 무엇인가요?
과일 능력의 피해는 DevilFruit 능력치에 포인트를 투자함으로써 증가시킬 수 있습니다.
우리의 활동을 지원해주세요 ❤️
이 글이 마음에 드셨다면, 앞으로도 좋은 콘텐츠를 계속 발행할 수 있도록 팁을 남겨주세요.


























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



