한글 제목 (English Title)

Here's a thinking process:

1. Analyze the Request: - Role: StarCraft: Brood War custom map reviewer. - Source Data: Provided map data (title, filename, internal title, description, genre, players, tags, tileset). - Output Rules: - Output must be JSON, Markdown, tables, lists, or headers - NO. - First write Korean review: 900-1100 characters (including spaces).

- Then, after a blank line, translate the same content into English (no subsection headers like "", etc.). - No "Korean Review", "StarCraft Brood War Map Review", etc. as headers. - Output starts directly with the review body text. - Total output: 1800-3000 characters (including spaces).

- Must naturally cover: map structure, genre, gameplay style, player experience, recommended audience, pre-play check items. - Do NOT invent: creator, triggers, win conditions, story, balance changes. - Do NOT list: map size, resolution, tile units, encoding, and repeat the same explanation. - Use the provided data only, no made-up info. 2.

Identify the Source Data: I need to look at the actual prompt to see the map data. The user said: "다음 를 자연스러운

로 번역해라." But then pasted something that seems to be instructions/rules, not the actual map data. Wait, the prompt ends with "Here's a thinking process:" and then the thinking block. Actually, the user's message is: "다음 를 자연스러운

로 번역해라. 제목, 머리말, 목록, Markdown, 부연 설명 없이 한국어 번역 본문만 출력해라. 원문에 없는 맵 정보나 평가를 추가하지 마라. Here's a thinking process: