4v4 공유 자유 전투 (4v4 Shared Free For All)

We need to produce JSON with content etc. No markdown, just raw JSON object. We must generate Korean review 900-1100 characters (including spaces). Then after that a blank line, then

same content, no heading. Total characters including both Korean and English plus blank line must be 1800-3000 characters (including spaces). We'll need to count roughly. Map details: Title: 4v4 Shared Free For All. File name: 4v4_Shared_Free_For_All.scm. Description: ToNy AkA Going-Newb-StylP.S. Stupidest map ever. Current genre: MELEE (밀리). Player count: 8.

Team count: - (none). Play time unknown. Difficulty unknown. We need to decide recommendedMapType. Since description says "Stupidest map ever" and title indicates 4v4 Shared Free For All, likely a free-for-all melee map with shared resources? The classification MELEE currently. Could be a melee map (standard). So recommendedMapType could stay MELEE.

But we need to consider if it's a UMS (custom). The description says "Stupidest map ever" suggests maybe a joke map, but still likely a melee map. So we keep MELEE. mapTypeReason: "제목과 설명에서 공유 자원 기반의 자유 전투 형태를 나타내며, 기존 MELEE 분류와 일치한다."

Now recommendedTitle: site display title is "4v4 Shared Free For All". Already English only? It's English. We need recommendedTitle in format "한글 제목 (English Title)". Since original title is English only, we need to add a Korean translation before parentheses. Provide natural Korean translation: "4v4 공유 프리 포 올" maybe?

But better: "4v4 공유 프리 포 올 (4v4 Shared Free For All)". However we need to keep original English title inside parentheses. So recommendedTitle: "4v4 공유 프리 포 올 (4v4 Shared Free For All)". titleReason: "원본 제목이 영어만 있으므로 자연스러운 한글 표기를 앞에 추가하고 원문을 보존". Now recommendedPlayerCount: 8.

recommendedTeamCount: Since it's free-for-all, each player is solo, so team count = 1 (or null). According to spec, if uncertain, null or omit. We have player count known. Team count we can set 1 (each player solo) but spec says team count is number of teams; if free-for-all, it's 1 per player?

Actually team count is number of teams; if each player is own team, team count equals player count? Usually team count is number of teams, not players. For FFA, team count = 8 (each player a team). But spec may expect team count as number of teams; but they gave example recommendedTeamCount: 1 for melee?

In the JSON schema example they used recommendedTeamCount: 1. That suggests for melee they treat as single team? Hmm. In melee map, usually it's 1v1 or 2v2 etc. But they set 1 maybe meaning no teams (everyone independent). We'll follow that: recommendedTeamCount: 1 (indicating no fixed teams). We'll note in metadataReason. recommendedPlayTime: unknown.

Could estimate typical melee map 20-30 minutes. Since uncertain, we could set null or omit. But spec says if uncertain, null or omit. We'll omit? But we need to include field; we can set null. JSON allows null. We'll set null. recommendedDifficulty: unknown; we can set "보통" as default? Might be guess. Better to set null? They said if uncertain, null or omit.

We'll set null. recommendedVersionName: unknown; we can set null or maybe "v1.0". Better to set null. recommendedTags: we can include ["유즈맵", "밀리", "공유 자원", "FFA"] but limit 8. Provide Korean tags. metadataReason: Provide basis. detailCategory: Need more specific subcategory. Since it's a melee FFA with shared resources, maybe detailCategory: "밀리" (or "FFA").

The list includes "밀리". So detailCategory: "밀리". detailCategoryReason: "플레이 인원 8명, 팀 구분이 없는 자유 전투 형태이며, 자원 공유 특성을 가진 밀리 맵이다."