Kill each other

Here's a thinking process:

1. Analyze the Request: - Role: StarCraft: Brood War map reviewer. - Input: Map data provided (title, filename, internal title, internal 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 English version of the same content, also 900-1100 characters. - No "Korean Review", "StarCraft Brood War Map Review", "Map Review", etc. as headings/subtitles. - Output starts immediately with the review body text. - Total output: 1800-3000 characters (including spaces).

- Content to cover: map structure, genre, gameplay style, player experience, recommended players, pre-play check items. - Do not invent maker, triggers, win conditions, story, balance adjustments. - Do not list map size, resolution, tile units, encoding, and repeat the same explanation.

- Map Data: - Title: Kill each other - Filename: (6)KILLER_MAP.scm - Internal title: Kill each other - Internal description: DESTROY EVERYONE! - Genre: MELEE (밀리) - Players: 6 - Teams: - - Expected playtime: - - Difficulty: - - Version: - - Tags: - - Tileset: Wasteland (황무지)

2. Deconstruct the Output Requirements: - Korean review: 900-1100 chars (with spaces). - Then a blank line. - Then English version of the exact same content, also 900-1100 chars. - Total output 1800-3000 chars. - No headings at all. The Korean text must start immediately with the review content. Same for English after the blank line.

- Must naturally explain map structure, genre, gameplay style, player experience, recommended targets, pre-play check items. But without inventing data not given. I have to work with what's given: 6 players, melee genre, wasteland tileset, "destroy everyone" objective.

- I need to generate a coherent review around 900-1100 Korean chars, then the English version of that same text. - Total output: 1800-3000 chars (fits two ~900-1100 char blocks + blank line). - "Do not list map size, resolution, tile units, encoding, and repeat the same explanation." So I shouldn't mention those technical details.

I'll focus on gameplay experience. Let's draft the Korean review. I need ~900-1100 chars. Let's aim for ~1000. I'll write, then count. - Draft Korean review (mental): "킬 이터는 브루드워의 메일 맵답게 6명의 플레이어가 황무지 전장에서 서로를 향해 돌진하는 치열한 밀리전 양상을 보입니다. 내부 설명처럼 '모든 사람을 파괴한다'는 목표 아래, 팀 없이 각자도생하는 구도가 특징입니다.

웹랜드 타일셋이 주는 척박하고 넓은 대지는 시야 확보와 진격 경로에 전략적 깊이를 더하며, 6인 멀티플레이 특유의 혼돈과 긴장감이 교차합니다. 별도의 난이도나 제한된 플레이타임 안내가 없어 누구나 즉시 참여할 수 있지만, 인원 수에 따라 게임의 흐름과 지속 시간이 크게 달라질 수 있으니 플레이 전 인원 확인이 권장됩니다. 단순하고 직관적인 규칙 덕분에 스타크래프트 입문자부터 베테랑까지 부담 없이 즐길 수 있으며, 빠른 판단을 요구하는 액션 중심의 매치를 선호하는 플레이어에게 적합합니다.

팀 플레이보다는 개인 전술과 리소스 효율이 승패를 가르는 핵심 요소가 되므로, 협동보다는 경쟁적인 플레이를 즐길 때 빛을 발하는 맵입니다." -> Let's count characters (including spaces). I'll count later. First, ensure it covers required aspects: map structure, genre, gameplay style, player experience, recommended players, pre-play check items. It does. - Need to make sure it's 900-1100 chars including spaces.

I'll count precisely after drafting. - Also, the English version must be the exact same content translated, no headings, same char count roughly. Here's a thinking process: