자신을 지켜라 (Protect YourSelf (PYS))

We need to produce a JSON object with fields as specified. We have map data: site title: Protect YourSelf (PYS), internal title same. Description: "Don't die!". Play count: 6 players. No team count given. No difficulty, version, tags. We need to infer recommendedMapType: The map is a UMS (user map) with "Don't die!" presumably a survival or avoidance type?

The description is minimal. Based on title "Protect YourSelf" suggests you need to protect yourself perhaps from enemies, maybe a survival or defense? Since no more info, we may recommend UMS as map type, and detailCategory maybe "생존" or "피하기"?

The allowed detailCategory examples: 컴까기, 디펜스, 타워 디펜스, 랜덤 디펜스, RPG, 키우기, 피하기, 탈출, 서바이벌, 아레나, 미니게임, 퍼즐, 캠페인, 디플로메시, 블러드, 입구막기, 넥서스 부수기, 밀리. Given "Don't die!" suggests survival or avoidance. Could be "피하기" (dodging) or "서바이벌". The map size 1024x1024 volcanic tileset. Could be a map where you avoid lava? Title "Protect YourSelf" maybe you must survive attacks.

Thus detailCategory could be "서바이벌". Since "피하기" also plausible but we need justification: internal description "Don't die!" indicates survival objective. Thus recommendedMapType remains UMS (as given). mapTypeReason: "내부 설명과 제목에서 특정 목표가 없어 유즈맵으로 분류". recommendedTitle: The site title is already "Protect YourSelf (PYS)" which is Korean?

Actually it's English with Korean parentheses? It has English title and abbreviation. This seems fine: it's English title with Korean abbreviation? It includes English title and (PYS). It doesn't have Korean translation. According to rules: if site title is not "한글 제목 (English Title)" format, we must write recommendedTitle.

The site title is "Protect YourSelf (PYS)" which is English title with abbreviation in parentheses, not Korean. So we need to provide a Korean title plus English title in parentheses. We need to derive a natural Korean title that matches meaning: "자신을 보호하라" or "너 자신을 지켜라". Could be "너 자신을 지켜라 (Protect YourSelf)". Or "자신을 지켜라 (Protect YourSelf)".

Should we keep the abbreviation? The recommendedTitle format: "한글 제목 (English Title)". So we need Korean title then space then English title in parentheses. The English title should be the original English title? The original English title is "Protect YourSelf". So recommendedTitle: "너 자신을 지켜라 (Protect YourSelf)". Or "자신을 지켜라 (Protect YourSelf)".

We'll pick "너 자신을 지켜라 (Protect YourSelf)". TitleReason: "사이트 표시 제목이 한글 없이 영어만 제공되어 자연스러운 한글 제목을 추가하고 영어 원문을 괄호 안에 보존". Now recommendedPlayerCount: given 6. Team count: not given, we can infer maybe 1 (free-for-all) or null. Since not sure, we can set null. But spec says if uncertain, null or omit. We'll set null. RecommendedPlayTime: unknown, could be null.

But we can estimate typical survival map maybe 20 minutes? But better to not guess. Use null. RecommendedDifficulty: unknown, null. RecommendedVersionName: unknown, null. RecommendedTags: we can give ["유즈맵", "서바이벌", "피하기"] maybe up to 8. Must be Korean tags. We'll include "유즈맵", "서바이벌", "피하기". Provide as array.

metadataReason: explain we used given player count etc. detailCategory: "서바이벌". detailCategoryReason: "내부 설명 'Don't die!'와 제목 'Protect YourSelf'에서 생존 목표를 유추". Now we need to write Korean review 900-1100 characters (including spaces). Then

after a blank line, no heading. The combined content must be 1800-3000 characters. We need to produce Korean review that discusses map structure, genre, progression, player experience, target audience, pre-play checkpoints. Must not mention site stats, downloads etc. Must not assert uncertain info as fact; use "추정된다", "보인다".

Must not mention things not in data. We must not use headings like "