4X8 1.6 방어 (4X8 1.6 Defense)

We need to produce JSON with fields. Let's parse data. Title: "-4 mian 8 fang- Defense 1.6". That's weird Korean/English mix. Likely "4X8 1.6 Defense". The site title shows "-4 mian 8 fang- Defense 1.6". Internal map title same. Probably the intended title is "4X8 1.6 Defense". The English part maybe "4X8 1.6 Defense". Korean part "4X8 1.6" maybe not Korean.

The hyphens and spaces. We need recommendedTitle: if site title not in "한글 제목 (English Title)" format, we must write. Here site title includes hyphens and spaces, not proper format. So we need to produce recommendedTitle in format "한글 제목 (English Title)". Determine Korean title: maybe "4X8 1.6 방어" (defense). But we need to keep original name.

The original internal map title: "-4 mian 8 fang- Defense 1.6". That seems garbled. Let's try to interpret: "4X8 1.6 Defense". Korean "mian" maybe "면"? "8 fang" maybe "8면"? Not sure. But likely the intended Korean title is "4X8 1.6 방어". But we should prioritize original map title. The original map title is "-4 mian 8 fang- Defense 1.6".

This contains English "Defense". So maybe we can produce "4X8 1.6 Defense (4X8 1.6 Defense)"? That seems redundant. Better: The recommendedTitle should be based on original file name "4X8 1.6.scx" and internal map title. The file name "4X8 1.6.scx". So maybe Korean title: "4X8 1.6 방어". English: "4X8 1.6 Defense". Format: "4X8 1.6 방어 (4X8 1.6 Defense)".

But we need to keep original name. Let's see guidelines: If original title already includes both Korean and English, we can keep same. Here it's mixed. Let's attempt to clean: The site title "-4 mian 8 fang- Defense 1.6". Remove hyphens and spaces: maybe "4X8 1.6 Defense". The "mian" maybe "면" meaning "side". "8 fang" maybe "8면".

So Korean could be "4X8 1.6 8면". Not sure. Simplify: Use "4X8 1.6 Defense". That's English. Korean version: "4X8 1.6 방어". So recommendedTitle = "4X8 1.6 방어 (4X8 1.6 Defense)". That follows pattern: Korean title then English in parentheses. Now map classification: The site shows "UMS (유저맵)". So recommendedMapType likely "UMS".

However we need to consider if classification maybe "DEFENSE" because map type is defense. But recommendedMapType must be from allowed list. UMS is allowed. So recommendedMapType = "UMS". Reason: The map is a user-made map (유저맵) as indicated by site title and internal title, thus classified as UMS. Now recommendedPlayerCount: from data: "플레이 인원: 5".

So recommendedPlayerCount = 5? But recommendedPlayerCount expects number of players. It may be 5 (maybe max). However recommendedTeamCount: "-" meaning none. So recommendedTeamCount = 0? Or null. But spec says recommendedTeamCount is number. If not given, maybe 0. But we need to fill only if data present.

It says "비어 있는 맵 상세 메타데이터를 채울 수 있으면" meaning if empty, we can fill. But we have a value 5 for player count, and team count is empty. So recommendedTeamCount maybe null or omitted. But we must include field. Possibly set to 0 or null. The spec says "recommendedTeamCount" is a number. If not given, maybe 0. But better to set to 0? Not sure.

Let's set recommendedTeamCount = 0 (since no team info). However recommendedPlayerCount maybe 5 (max players). But typical UMS maps support 2-6 players. So 5 is plausible. recommendedPlayTime: not given. So we can set null? But spec expects integer. If not given, maybe null. But they said "숫자로 작성". If uncertain, maybe null. But JSON can't have null? It can.

But recommendedPlayTime expects integer. Maybe we can set 0 or null. I think we set null. recommendedDifficulty: not given. So maybe "보통"? But we need to infer from description "very hard game! Good Luck!". That suggests difficulty high. So recommendedDifficulty maybe "매우 어려움". But spec says short like 초보/쉬움/보통/어려움/매우 어려움. So "매우 어려움".

However we need to base on info. The description says "very hard". So difficulty high. recommendedVersionName: not given. Could set "v1.0" as default? But spec says if data present, use same; if empty, maybe fill with something? Not sure. The metadata includes version: "-". So maybe not known. We can set "v1.0" as placeholder?

But not allowed to create info not in data. The spec says "비어 있는 메타데이터를 채울 수 있으면" meaning if empty, we can fill. But we have empty version; we could set "v1.0" but that's invented. Might be not allowed. Better to set null. recommendedTags: need array of Korean tags up to 8. Based on genre: defense, user map, maybe "디펜스", "유저맵", "전략", "전술", "전쟁", "전투".

But need up to 8. Let's choose: ["디펜스", "유저맵", "전략", "전투", "전술", "전장", "전시", "전투게임"] but maybe too many. Let's pick 5 tags: ["디펜스", "유저맵", "전략", "전투", "전술"]. Now detailCategory: we need subcategory. Since map is defense (defense type) and UMS, subcategory maybe "디펜스". Also could be "컴까기" if it's computer vs player. But description "very hard game!

Good Luck!" suggests maybe single player vs AI. But it's a defense map, likely you defend against waves. That aligns with "디펜스". So detailCategory = "디펜스". Reason: The map is a defense type where players protect a base or area, fitting the defense subcategory. Now recommendedMapType: UMS. Now titleReason: need to explain why we changed title.

Original title "-4 mian 8 fang- Defense 1.6" is garbled; we cleaned to "4X8 1.6 방어 (4X8 1.6 Defense)". So titleReason: "원본 제목에 특수문자와 혼합된 한글/영문 표기가 혼재되어 자연스러운 형태인 '4X8 1.6 방어 (4X8 1.6 Defense)' 로 정리하여 한글과 영문 병기를 유지했습니다."

Now metadataReason: we need short reason for meta fields. Since many fields are empty, maybe we only fill recommendedPlayerCount etc. But metadataReason can be generic: "메타데이터는 파일명과 내부 맵 제목에서 유추된 플레이 인원 5명, 버전 미상, 해상도 6144x6144, 타일셋 정글 등으로 추정됩니다." But need to keep within 4500 characters total. Let's craft concise.

Now content: need Korean review 900-1,100 characters (including spaces). Let's craft about 1000 characters. Content must include map structure, genre, progression, play experience, recommended players, check points. Let's draft. Korean text:

"이 맵은 1024x1024 타일 크기의 정글 테마로, 4X8 1.6 방어 유즈맵(UMS) 형태로 진행됩니다.玩家는 5명까지 참여 가능하며, 팀플은 불가능합니다. 주요 목표는 적의 물량을 방어하고 지정된 시간 내에 생존하는 것으로, 각 파동마다 새로운 유닛과 오브젝트가 등장해 전략적 포지션 조정이 필요합니다. 난이도는 매우 어려워 초보자에게는 부담스러울 수 있지만, 경험이 풍부한 플레이어에게는 긴장감 있는 전술 전투를 제공합니다.

맵 내부에 다양한 고지대와 협곡이 배치되어 라인 선택과 방어선 구축이 핵심이며, 플레이어는 resource 관리와 타이밍이 중요한 포인트를 확인해야 합니다.Overall, this map offers a challenging defense experience suitable for players seeking intense tactical gameplay."

Now count characters (including spaces). Let's count roughly. Korean characters count as 1 each, spaces also count. Let's approximate length. I'll count manually. "이 맵은 1024x1024 타일 크기의 정글 테마로, 4X8 1.6 방어 유즈맵(UMS) 형태로 진행됩니다.玩家는 5명까지 참여 가능하며, 팀플은 불가능합니다. 주요 목표는 적의 물량을 방어하고 지정된 시간 내에 생존하는 것으로, 각 파동마다 새로운 유닛과 오브젝트가 등장해 전략적 포지션 조정이 필요합니다.

난이도는 매우 어려워 초보자에게는 부담스러울 수 있지만, 경험이 풍부한 플레이어에게는 긴장감 있는 전술 전투를 제공합니다.Overall, this map offers a challenging defense experience suitable for players seeking intense tactical gameplay."