아이스큐브스 (Icecubes)

Here's a thinking process:

1. Analyze the Request: - Role: StarCraft: Brood War map reviewer. - Source Data: Provided map data (title, filename, internal title, description, genre, players, teams, playtime, difficulty, version, tags, tileset). - Output Rules: - No JSON, Markdown code blocks, tables, lists, headings. - First: Korean review, 900-1100 characters (including spaces).

- Then: A blank line, then the same content in English, without any subtitles/headings. - No "Korean Review", "StarCraft Brood War Map Review", etc. as headings. - Output starts directly with the review body. - Total output: 1800-3000 characters (including spaces). This means Korean + English together must be 1800-3000 chars.

Since Korean is 900-1100, English must be roughly the same, so total ~1800-2200, which fits the 1800-3000 range. - Content: Map structure, genre, gameplay style, player experience, recommended targets, pre-play checks. - No fabrication of maker, triggers, win conditions, story, balance adjustments.

- No listing map size, resolution, tile units, encoding, and no repeating the same explanation.

- Specifically: "맵 구조, 장르, 진행 방식, 플레이 경험, 추천 대상, 플레이 전 확인 사항을 자연스럽게 설명한다." and "타일셋, 인코딩을 나열하지 않고 같은 설명을 반복하지 않는다." So I need to naturally describe the map based on the given data, without explicitly listing "tileset: platform" as a bullet, but I can mention it naturally within the description.

Also, I must not repeat the same explanation in Korean and English; they should be translations of each other, but the rule says "same content" - I think it means the content should be the same, but since it's a translation, it will naturally be similar. I need to make sure the English part is a translation of the Korean part, not just random text.

Let's plan the Korean review text. It needs to be 900-1100 characters (with spaces). That's quite long. I need to elaborate on the given data naturally. Given data points: - Title: Icecubes - Internal description: "Make your path throught the eternal ice-graveyard." - Genre: MELEE (밀리) - likely melee map, 4 players.

- Players: 4 - Tileset: Platform (this suggests a platform-based map, maybe floating platforms, icy themes given the title/description) - No teams info, so FFA or individual melee.

I need to construct a review that flows naturally, covering: - Map concept/setting (eternal ice-graveyard, platform tileset) - Genre: melee, 4 players - Gameplay flow: navigating the ice graveyard, path-making - Player experience: what to expect - Recommended for: who would enjoy it - Pre-play checks: maybe player count, map type, etc.

But I must not list "tileset: platform" explicitly as a fact block, but I can describe it as "the map features a platform-based layout" or similar within the flow. - Wait, the prompt says: "다음 를 자연스러운

로 번역해라." But then it gives map data, and rules. Actually, re-reading: "Here's a thinking process:" then the prompt. The prompt is: "다음 를 자연스러운

로 번역해라. 제목, 머리말, 목록, Markdown, 부연 설명 없이 한국어 번역 본문만 출력해라. 원문에 없는 맵 정보나 평가를 추가하지 마라." Then it gives the map data in a structured format, but the output rules are about Korean review 900-1100 chars, then English same content, total 1800-3000, no headings, no JSON/Markdown/lists, etc. Wait, the initial instruction says: "다음 를 자연스러운

로 번역해라." But then it gives map data that isn't a review text, it's metadata. And it says "원문에 없는 맵 정보나 평가를 추가하지 마라." So I need to generate a review based *only* on the given metadata, without adding new info. The