흙의 흐름 (Flows Of Dirt)

We need to produce JSON with fields. Must follow constraints: Korean review 900-1100 characters (including spaces). Then a blank line, then

same content (no extra heading). Total characters 1800-3000 including both Korean and English plus blank line? The blank line counts as a newline? Probably counts as characters? We'll aim Korean ~1000 chars, English similar ~1000 chars, total ~2000 plus blank line (2 chars newline?). Ensure within 1800-3000. We must not mention site stats etc.

We have map: Flows Of Dirt, internal description: Destroy all enemy buildings. So it's a melee map? It says current genre MELEE (밀리). The description: destroy all enemy buildings suggests a standard melee victory condition (destroy all enemy buildings). So it's a classic melee map (like a standard 4-player map). No UMS triggers indicated.

So recommendedMapType likely stays MELEE. But we need to see if any indication of UMS? The description is simple, likely a standard melee map. So recommendedMapType = MELEE, mapTypeReason: "표준 밀리 맵으로, 적 모든 건물 파괴勝利 조건과 4인 플레이 구성이 전형적". Title: site display title Flows Of Dirt (English). It's English only.

Need recommendedTitle with Korean translation plus English in parentheses. Original title English only. So we need to produce Korean translation (natural) and keep English in parentheses. What is a good Korean translation? "흙의 흐름" maybe? Flows Of Dirt -> "흙의 흐름". Could also be "흙의 흐름 (Flows Of Dirt)". We'll do that.

TitleReason: "원본 제목이 영문만 있어 자연스러운 한글 번역을 앞에 배치하고 원문 보존". Metadata: recommendedPlayerCount: given 4. recommendedTeamCount: not given, but for melee usually each player is own team (FFA) so teamCount = 1? Actually team count refers to number of teams? In melee each player is own team, so teamCount = 1 per player?

The schema expects recommendedTeamCount maybe number of teams per side? For melee, often teamCount = 1 (each player solo). We'll set 1. recommendedPlayTime: not given; we can estimate typical melee 4-player map maybe 20-30 minutes. We'll set 30. recommendedDifficulty: not given; we can set 보통. recommendedVersionName: not given; we can set v1.0 (or null?

but we must write something if we can infer? We can set v1.0 as placeholder but must base on evidence? There's no version. Might be better to leave null? The spec says we can fill if we can infer; if not, we can omit or null.

It says "비어 있는 맵 상세 메타데이터를 채울 수 있으면 recommendedPlayerCount, recommendedTeamCount, recommendedPlayTime, recommendedDifficulty, recommendedVersionName, recommendedTags를 작성한다." So we should fill if we can infer; if not, we can leave null or omit. For version we have no info, better to omit or set null. But JSON expects a value; we can set null.

We'll include null. recommendedTags: we can include ["밀리", "4인", "정글 타일셋", "건물 파괴"] maybe limit 8. We'll choose appropriate. detailCategory: need more specific subcategory. Since it's a standard melee map with destroy all enemy buildings, subcategory could be "밀리" (melee) maybe "밀리" is the detailCategory? They gave examples like 컴까기, 디펜스, etc.

For melee, maybe "밀리" is appropriate. So detailCategory = "밀리". detailCategoryReason: "적 모든 건물 파괴라는 승리 조건과 표준 밀리 구성이 전형적". Now content: Korean review 900-1100 characters. Must include map structure, genre, progression, play experience, recommended audience, pre-play check points. Let's craft about 1000 characters.

We need to count characters including spaces and punctuation. Let's draft ~1000. I'll write Korean paragraph ~1000 characters. We need to ensure after Korean review we put a blank line (i.e., two newline characters) then