([H])Foresta River

Here's a thinking process:

1. Analyze the Request: - Role: StarCraft: Brood War map reviewer. - Source Data: Provided map metadata only. - Output Rules: - No JSON, Markdown code blocks, tables, lists, headings. - First: Korean review, 900-1100 chars (including spaces). - Then: A blank line, then the English version of the same content, no subtitle/headings.

- Forbidden substrings/phrases: "", " ", " ", " ", " ", "Translation" (as headings/subtitles). Actually, the prompt says: "Forbidden substrings/phrases: " ", " ", " ", " ", " ", "Translation" (as headings/subtitles)." This likely means I shouldn't output those as standalone headings or markdown. I'll just avoid any markdown formatting entirely.

- Output starts immediately with the review body text. - Total output: 1800-3000 chars (including spaces). So Korean (900-1100) + blank line (1) + English (900-1100) = ~1801-2201, fits 1800-3000. - Must naturally cover: map structure, genre, gameplay style, player experience, recommended players, pre-play checks.

- Must NOT invent: creator, triggers, win conditions, story, balance changes. - Must NOT list: map size, resolution, tile units, encoding, or repeat the same explanation. - Must NOT use Markdown, headings, etc. - High proper nouns as Korean phonetic translations as much as possible.

- Original text has some messy internal description: "Une map créée par l'ancien Blast100$, Chevreuil([H])adresse @ = chevreuilct59@hotmail.comicq # =75248357du clan = l'HoGrE et ses acolytes". I need to parse this or just refer to generally. The rule says "Don't invent creator...". I can mention the creator as given but carefully, or avoid naming.

I'll likely just refer to "the map by its creator" if needed, but better to just describe gameplay without focusing on creator name to stay safe. Actually, the internal description is part of the data, I can reference it but must not invent. I'll probably just say "by a creator known as..." but careful.

I'll just focus on gameplay aspects derived from genre, players, tileset. - Tileset: Platform. I can describe terrain as platform-style, maybe cliffs, ramps, etc. - Genre: MELEE (밀리) -> I'll write "밀리(MELEE) 장르" or just describe as melee style. - Players: 3 -> 3인 플레이 - Teams: - -> no teams, free-for-all or open.

- Expected play time: - -> I can note typical melee duration or leave generic. - Difficulty: - -> N/A - Version: - -> N/A - Tags: - -> N/A

2. Drafting - Korean Review (Target: 900-1100 chars including spaces): - Must start immediately, no headings. - Cover: map structure, genre, gameplay style, player experience, recommended players, pre-play checks. - Naturally incorporate given data: title Foresta River, 3 players, melee genre, platform tileset, no teams.

- Avoid inventing creator details, triggers, win conditions, story, balance. - Avoid listing map size, resolution, tile units, encoding. - No markdown, no lists, just prose paragraphs. - Proper nouns: "Foresta River" -> 포레스타 리버 (or phonetic). I'll use Korean phonetic translation: "포레스타 리버".

The prompt says "high proper nouns as Korean phonetic translation as much as possible." So I'll translate names into Korean sound. - Let's draft in Korean, aiming for ~1000 chars. Draft (mental): "포레스타 리버는 스타크래프트 밀리 장르를 기반으로 한 3인 플레이 맵입니다. 플랫폼 타일셋을 활용한 맵 구조는 개방된 전장과 여러 고지대 지점을 적절히 배치하여 유닛의 이동 경로와 시야 확보에 신경을 쓴 느낌을 줍니다.

3명의 플레이어가 팀 없이 자유롭게 대결하는 형태이며, 밀리 특성상 초반 자원 분배와 유닛 생산 속도가 게임의