2025년 12월 4일 업데이트: 모든 레시피를 추가했습니다. 현재 가장 높은 수익을 내는 것은 크레페입니다. 믹스 레시피 섹션에 있습니다.
Roblox Craft Food는 여러분이 발견할 수 있는 다양한 흥미로운 레시피를 제공합니다. 주요 업데이트마다 새로운 추가 요소가 등장하여 모든 것을 추적하는 것이 정말 모험이 됩니다. 여러분의 게임 플레이 경험을 단순화하기 위해, 모든 레시피의 포괄적인 목록을 정리했습니다. 그 목록은 재료, 비용 및 초당 수익을 자세히 설명합니다. 이 가이드를 통해 Craft Food의 모든 레시피를 탐험해 보세요.
Craft Food의 모든 레시피

저는 Craft Food 레시피를 개별 재료에 따라 정리하여 수익이 적은 것부터 많은 것까지 나열했습니다. 각 항목은 이름>재료>재료 비용>수익의 형식을 따르므로 비용과 수익을 쉽게 추적할 수 있습니다. 새로운 재료가 출시될 때마다 이 목록을 업데이트할 것이니 자주 확인하세요!
참고 #1: 아래 테이블은 특정 재료에 따라 레시피를 분류합니다. 일반적으로 레시피 이름에 해당 재료가 포함되어 있거나 가장 높은 가치가 강조되어 있습니다.
참고 #2: Strawberry Banana Cake와 같은 레시피는 더 쉽게 검색할 수 있도록 Banana와 Strawberry 섹션 모두에 나타날 수 있습니다. 중복 항목을 만날 경우를 대비해 미리 알려드립니다!
참고 #3: 아래에 인용된 모든 수익 값은 수정자 없이 기본 금액입니다.
기본 믹스 레시피 (밀가루, 우유, 달걀, 설탕)
기본 믹스![]() ![]() ![]() 이 섹션은 특정 우유 및 달걀 테마 레시피는 제외합니다 (그것들은 아래에 있습니다). |
|---|
| 빵밀가루$10 (€9)$1/s크래커밀가루, 달걀$310 (€275)$5/s쿠키밀가루, 설탕$1.0K (€900)$6/s팬케이크밀가루, 우유, 달걀$340 (€300)$8/s메리앙달걀, 설탕$1.3K (€1.1K)$8/s카스텔라밀가루, 설탕, 달걀$1.3K (€1.1K)$11/s플란달걀, 설탕, 우유$1.3K (€1.1K)$13/s스콘밀가루, 우유, 설탕, 달걀$1.3K (€1.1K)$16/s |
우유 테마 레시피
우유 레시피![]() |
|---|
| 뜨거운 우유우유$30 (€27)$2/s우유 빵밀가루, 우유$40 (€36)$4/s우유 사탕설탕, 우유$1.0K (€900)$7/s우유 쿠키밀가루, 설탕, 우유$1.0K (€900)$10/s당근 우유설탕, 당근, 우유$81.0K (€73.0K)$43/s토마토 우유설탕, 토마토, 우유$301.0K (€270.0K)$92/s토마토 우유 쿠키토마토, 밀가루, 우유, 설탕$301.0K (€270.0K)$107/s상추 우유상추, 우유, 설탕$2.0M (€1.8M)$148/s레몬 우유레몬, 우유$30.0M (€27.0M)$362/s밀크쉐이크레몬, 달걀, 우유$30.0M (€27.0M)$427/s우유 아이스크림우유, 레몬, 설탕$30.0M (€27.0M)$428/s딸기 우유우유, 딸기$100.0M (€90.0M)$602/s딸기 밀크쉐이크딸기, 우유, 달걀, 설탕$100.0M (€90.0M)$814/s바나나 우유우유, 바나나$500.0M (€450.0M)$902/s블루베리 우유우유, 블루베리$1.0B (€900.0M)$1.2K/s바나나 밀크쉐이크바나나, 우유, 달걀, 설탕$500.0M (€450.0M)$1.2K/s블루베리 밀크쉐이크블루베리, 우유, 달걀, 설탕$1.0B (€900.0M)$1.6K/s쿠키 밀크쉐이크밀가루, 우유, 달걀, 설탕, 바나나, 레몬$530.0M (€477.0M)$2.1K/s블루베리 바나나 우유블루베리, 바나나, 우유$1.5B (€1.35B)$2.5K/s초콜릿 우유카카오, 우유$10.0B (€9.0B)$3.6K/s |
달걀 테마 레시피
달걀 레시피![]() |
|---|
| 바삭한 해시브라운 달걀컵감자, 달걀$10.3K (€9.3K)$18/s아침 달걀 오븐구이감자, 밀가루, 달걀, 우유$10.3K (€9.3K)$29/s토마토와 달걀 볶음토마토, 달걀$300.3K (€270.0K)$76/s달걀 샌드위치밀가루, 토마토, 달걀$300.3K (€270.0K)$90/s오믈렛토마토, 우유, 달걀$300.3K (€270.0K)$91/s달걀 샐러드상추, 달걀$2.0M (€1.8M)$124/s야채 감자 팬케이크감자, 토마토, 당근, 밀가루$390.0K (€350.0K)$157/s야채와 달걀 수프토마토, 감자, 당근, 달걀$390.3K (€350.0K)$160/s야채 샌드위치밀가루, 토마토, 상추$2.3M (€2.1M)$225/s구운 토마토와 달걀상추, 달걀, 토마토$2.3M (€2.1M)$228/s베이컨과 달걀고기, 달걀$10.0M (€9.0M)$244/s야채와 함께 스크램블 에그상추, 달걀, 감자, 토마토$2.3M (€2.1M)$280/s햄 에그 치즈고기, 우유, 달걀$10.0M (€9.0M)$287/s특별 야채 도넛바나나, 밀가루, 설탕, 달걀, 상추, 당근$502.1M (€451.9M)$1.8K/s |
Roblox Craft Food에서 가장 좋은 레시피는 무엇인가요?
Roblox Craft Food에는 많은 수익성 있는 레시피가 있지만, 가장 눈에 띄는 옵션 중 하나는 최고 수익을 자랑하는 크레페입니다. 초당 수익이 풍부합니다. 그 외에도 초콜릿 우유와 바나나 밀크쉐이크가 있으며, 이들도 인상적인 수익을 낼 수 있습니다.
Craft Food에서 수익을 극대화하려면 어떻게 해야 하나요?
Craft Food에서 수익을 극대화하려면 크레페와 같이 높은 수익 레시피 제작에 집중하세요. 필요한 재료를 효율적으로 수집하고, 개별적으로 판매하기보다 대량으로 판매하는 것을 고려하여 더 빠른 수익을 얻으세요. 게임의 변경 사항에 대한 업데이트를 항상 확인하는 것도 잊지 마세요!
가장 높은 수익률은 얼마인가요?
현재 Craft Food에서 가장 높은 수익률은 크레페에 있으며, 초당 $9.0K에 최대 $11.1B (€10B)를 제공합니다. 이 수치는 단순 레시피와 비교해 상당히 높은 편입니다.
Craft Food에 신 레시피가 얼마나 자주 추가되나요?
신 레시피는 일반적으로 Roblox Craft Food의 주요 업데이트에 따라 추가되며, 이는 몇 달에 한 번 있을 수 있습니다. 공식 업데이트 목록을 항상 확인하고 커뮤니티 토론을 통해 다가오는 레시피에 대한 힌트를 주의 깊게 살펴보세요.
Roblox Craft Food에서 여분의 재료를 판매할 수 있나요?
네, 여분의 재료를 판매하는 것은 수익을 높이는 좋은 방법이 될 수 있습니다. 판매 시점을 전략적으로 선택하고, 재료 가격이 상승할 때를 주시하세요.
이것으로 Craft Food 레시피에 대한 포괄적인 가이드를 마칩니다. Roblox나 일반 게임에 대한 더 많은 통찰력을 발견하고 싶다면, 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)



