매트릭스 불릿타임 8.3 (-Matrix-Bullet-Time 8.3)

We need to produce JSON object with content: Korean review 900-1100 characters (including spaces). Then a blank line (one empty line) then

, same content translated, no heading. Overall content length (Korean + blank line + English) 1800-3000 characters including spaces. We must not add any extra fields besides JSON keys. Must ensure content string includes newline separation between Korean and English (blank line). No extra explanation.

We need to infer map details: Title "-Matrix-Bullet-Time 8.3". It's likely a UMS map with sci-fi bullet time theme, likely a melee? Probably a custom map (UMS) maybe a " verded "?? The description: "Matrix Bullet Time Final V8.3 Created by ThePieMaster Revised by: .{TM}. ***************************************** Requires Six Players (or 3 very good players)".

So it's a multiplayer map requiring six players. Likely a melee style? Could be a "team melee"? Since it's matrix bullet time maybe a mod that alters game speed? Could be a "UMS" map type. It requires six players, team count unknown; maybe free-for-all? Not sure. We'll set recommendedMapType = UMS (since given current classification is UMS).

But we may decide if it's more like "MELEE"? The description indicates "Requires Six Players (or 3 very good players)" suggests it's a standard melee map for 6 players. Many UMS maps are melee style. We'll keep UMS as mapTypeReason: "내부 설명에 6인 플레이 필요 및 유즈맵 특성 표기, 일반적인 전투 중심 맵으로 판단". That seems fine. Title: Site display title "-Matrix-Bullet-Time 8.3".

It has leading dash and maybe encoding issues? It shows "-Matrix-Bullet-Time 8.3". The dash at start maybe a stray character. According to rule: If site display title has garbled characters, we should produce recommendedTitle natural. The title currently has leading dash; maybe it's an artifact.

We'll produce recommendedTitle without leading dash: "Matrix Bullet Time 8.3 (Matrix Bullet Time 8.3)". However we need format: Korean title (English Title). Since original is English only, we need Korean translation then English in parentheses. Korean translation could be "매트릭스 불렛 타임 8.3". So recommendedTitle: "매트릭스 불렛 타임 8.3 (Matrix Bullet Time 8.3)".

TitleReason: "원본 제목이 영어만 있으므로 자연스러운 한글 표기를 앞에 추가하고 원문 영어 제목을 보존". Now metadata: recommendedPlayerCount: 6 (from description). recommendedTeamCount: null or omitted? The spec says if uncertain, null or omit. We can set null. recommendedPlayTime: unknown; we can omit or null. recommendedDifficulty: unknown; maybe "보통". We'll guess? Better to omit if uncertain.

But spec says we can fill if we have basis. No basis, so omit or null. recommendedVersionName: we have version 8.3, so "v8.3". recommendedTags: array of Korean tags: e.g., ["매트릭스", "불렛 타임", "UMS", "6인전", "SF", "액션"] but limit 8. We'll choose relevant. DetailCategory: need more specific subcategory. Since it's a melee-style UMS map likely "컴까기"? Not sure.

The map may be a standard melee map with bullet time effect (maybe a mod altering game speed). Could be considered "유즈맵" but detailCategory could be "컴까기"? That is computer killing? Usually UMS melee maps are just "유즈맵". The detailCategory examples include "컴까기", "디펜스", etc. For a standard melee map, maybe detailCategory is empty?

But we must provide detailCategory string. We could set detailCategory: "일반전" but not in list. Maybe we choose "기타"? Not in list. The spec says detailCategory is more specific subcategory in Korean, examples given but not restricted? It says 예: ... So we can use other appropriate Korean term like "일반전" or "메리".

But to stay safe, maybe choose "일반전" though not listed. However maybe better to pick "유즈맵" as detailCategory? But detailCategory is supposed to be more specific subcategory; could be same as mapType? If uncertain, we can set same as recommendedMapType? Not exactly. The spec: detailCategory is more specific subcategory Korean.

If uncertain, we could set same as mapType? But they gave examples like 컴까기, 디펜스 etc. For a generic melee UMS, maybe we set detailCategory: "일반전" (normal battle). We'll also provide detailCategoryReason: "내부 설명에 특정 미션이나 목표가 없어 일반적인 전투 중심 유즈맵으로 판단". Now content: Korean review 900-1100 characters.

Must include map structure, genre, progression, player experience, target audience, pre-play checkpoints. We need to craft about ~1000 characters Korean. Then