떠있는 스택 스포어 방어 (FLOATSTACKEDSPORE)

We need to produce a JSON object with the fields as described. We have map data: site title: FLOATSTACKEDSPORE (all caps). Original filename: Floating_StackedSporeDefenc.scm. Internal title: same. Description: "Float Stacked SporeFloat your drone to the position you want it to defend, and turn off the lights to stack it."

Genre/classification: UMS (유즈맵). Players:5. Team: -. Expected playtime: -. Difficulty: -. Version: -. Tags: -. We need to fill recommended fields.

We need to decide recommendedMapType: Since classification is UMS, and description suggests a defense-ish map: "float your drone to the position you want it to defend, and turn off the lights to stack it." This sounds like a defense map where you place spores (Zerg building) and stack them? Might be a tower defense or something similar.

The title suggests "Floating Stacked Spore Defense"? Likely a defense map where you stack spores to defend. Could be a "디펜스" (defense) subcategory. So recommendedMapType could be TOWER_DEFENSE or DEFENSE? The allowed enum includes TOWER_DEFENSE and DEFENSE.

Since it's about stacking spores to defend, maybe it's a tower defense where you place spores as towers. However description: "Float your drone to the position you want it to defend, and turn off the lights to stack it." That sounds like you move a drone (worker) to a spot, then turn off lights to stack? Not fully clear. Might be a "디펜스" (defense) map.

Since we are not certain, we can keep same as current classification: UMS. But recommendedMapType must be one of the enum. If uncertain, we can set recommendedMapType same as current classification? The instruction: "확실하지 않으면 현재 장르/분류와 같은 값을 사용한다." So if uncertain, use same as current classification. Current classification is UMS. So recommendedMapType = UMS.

We need mapTypeReason: reason for classification: It's a UMS (유즈맵) as indicated by internal classification, no clear melee or team melee etc. RecommendedTitle: The site display title is FLOATSTACKEDSPORE (all caps). There's no Korean. According to rules: If site display title is not in "한글 제목 (English Title)" format, we must write recommendedTitle.

Original title is English only (all caps). We should produce a natural Korean translation before the English title in parentheses. The map seems about "Floating Stacked Spore Defense". So Korean could be "플로팅 스택드 스포어 디펜스" or "부유하는 스포어 쌓기 방어". But we should not add genre keywords arbitrarily.

The recommendation: "원본 제목이 영어만 있으면 자연스러운 한글 표기를 앞에 쓰고 원문 영어 제목을 괄호 안에 보존한다." So we need a natural Korean rendering of the English title. The English title is "FLOATSTACKEDSPORE". It likely means "Floating Stacked Spore". Could be "부유하는 스포어 쌓기" or "플로팅 스택드 스포어". Korean natural: "플로팅 스택드 스포어". Then parentheses with original English title.

So recommendedTitle = "플로팅 스택드 스포어 (FLOATSTACKEDSPORE)". However we might want to add spacing: maybe "플로팅 스택드 스포어 (FLOATSTACKEDSPORE)". That's fine. TitleReason: we changed title to add Korean translation because original title was English only and not in Korean-English format.

Now metadata: we need recommendedPlayerCount, recommendedTeamCount, recommendedPlayTime, recommendedDifficulty, recommendedVersionName, recommendedTags. We have player count: 5 (from data). Team count: not given, could be 1 (free-for-all) or maybe each player solo. Since team count not specified, we can set recommendedTeamCount = 1 (individual).

Playtime: unknown; we can leave null? The instruction: "플레이 인원/팀 수/예상 플레이 시간은 제목, 내부 설명, 이미지에서 근거가 있을 때만 숫자로 작성한다. 확실하지 않으면 null 또는 생략한다." So we can omit recommendedPlayTime or set null. But the JSON schema expects a value; we can set null. However the type might be integer; but we can set null. We'll include null. Difficulty: unknown; set null or omit.

We'll set null. Version: unknown; set null or maybe "v1.0"? Not given; we can set null. Tags: we need to produce Korean tags array, up to 8. Based on map: defense, floating, spore, stacking, UMS, maybe "디펜스", "유즈맵", "스포어", "스택", "플로팅". We'll pick ["디펜스", "유즈맵", "스포어", "스택", "플로팅"]. Now detailCategory: more specific subcategory Korean.

Since it's a defense map where you stack spores to defend, maybe "디펜스" or "타워 디펜스"? The description: "Float your drone to the position you want it to defend, and turn off the lights to stack it." That sounds like you place a drone to defend a spot, then turn off lights to stack (maybe stacking spores as defense). Could be "입구막기"? Not sure. Safer to use "디펜스".

If we think it's tower defense, we could use "타워 디펜스". But we need detailCategoryReason. Given uncertainty, we can set detailCategory = "디펜스". Reason: based on description indicating defending a position by stacking spores. Now metadataReason: we used player count from data, team count assumed 1 as solo, etc.

Now content: need Korean review 900-1100 characters (including spaces). Then blank line, then