Iced T

Here's a thinking process:

1. Analyze User Request: - Source: StarCraft: Broodwar map review data (provided in the prompt). - Task: Write a Korean review based *only* on the given data. - Constraints: - Output 900~1100 chars (Korean) + blank line + same content translated (also ~900~1100 chars) = total 1800~3000 chars. - No JSON, Markdown, tables, lists, headings, subheadings.

- No "Korean Review", "SCBW Map Review", "", "", "Translation" as headings. - Output starts directly with the first sentence of the review. - All sentences in Korean for the first part. - Proper nouns (map title, etc.) should be Korean-transliterated as much as possible.

- Do not invent facts not in the source data (no maker, triggers, win conditions, story, balance, size, resolution, tile units, encoding, etc.). - Do not repeat the same explanation.

- The English part should be "same content translated without subheadings" - meaning it's the Korean review translated into English, or just the same content in English, also without headings, ~900-1100 chars. - Blank line between the two sections. 2.

Examine Source Data: - Title: Iced T - Filename: (8)_Iced_T.scx - Internal title: Iced T - Internal description: Destroy all enemy buildings. One Entrance Plenty Resources - Genre: MELEE (밀리) - Players: 8 - Teams: - - Expected playtime: - - Difficulty: - - Version: - - Tags: - - Tileset: Platform

Key info to use: - Map name: "Iced T" (keep as is or Koreanize? Rules say "possible as Korean phonetic transcription" for proper nouns. Iced T -> 아이스 티 or just "아이스 티". I'll use "아이스 티" or keep "Iced T" but Korean context. Since it says "highly transliterate proper nouns", I'll Koreanize: "아이스 티". But the internal description is short. Genre: MELEE (밀리).

Players: 8. Tileset: Platform. Objective: Destroy all enemy buildings. One entrance, plenty resources. - I must not invent anything. So I'll only use what's given. - Structure: I need to write a natural review covering map structure, genre, gameplay, player experience, recommended targets, pre-play checks. But only using given data.

I have to extrapolate a bit naturally but without inventing facts. E.g., "This is a melee map for 8 players..." is fine because genre and player count are given. "Objective is to destroy enemy buildings." given. "One entrance, plenty resources." given. Tileset: Platform. I can describe gameplay style based on that. - I need to hit 900-1100 chars (Korean).

That's quite long. I need to be descriptive but factual. I'll have to expand naturally within the constraints, using the given data as anchors, not inventing specifics but describing the experience implied by the data. E.g., "8인 멀티플레이 맵", "전체 건물 파괴 승리 조건", "한 입구에 풍부한 자원", "플랫폼 타일셋" etc.

I can use reasonable descriptions that follow from the data without inventing fake details. - Let's plan the Korean text. I'll write ~1000 chars. I need to count carefully. I'll write in Korean, no headings, just a paragraph or flowing text. Then blank line, then English version of same content, also ~1000 chars, no headings.

- Constraints check: "모든 문장을 한글로 작성하고 영문 문장을 출력하지 마라." Wait: "아래 영문

를 바탕으로

본문만 새로 작성해라." Actually user says: "Here's a thinking process: ... Output is immediately the review body first sentence." And "아래 영문

를 바탕으로

본문만 새로 작성해라." Wait, the prompt is a bit mixed. Let's read carefully:

User says: "아래 영문

를 바탕으로

본문만 새로 작성해라. 모든 문장을 한글로 작성하고 영문 문장을 출력하지 마라. 고유