Monobattles SpacePort v1.0

Here's a thinking process:

1. Analyze the Request: - Role: StarCraft: Broodwar map reviewer. - Source Data: Provided map data (title, filename, internal title, description, genre, players, tags, tileset). - Output Rules: - No JSON, Markdown code blocks, tables, lists, headings. - First: Korean review, 900-1100 chars (with spaces).

- Then: A blank line, then an English version of the same content, also 900-1100 chars (with spaces). - Total output: 1800-3000 chars (including Korean + English + blank line). - The Korean review must naturally cover: map structure, genre, gameplay style, player experience, recommended audience, pre-play check items.

- Don't invent maker, triggers, win conditions, story, balance numbers. - Don't list map size, resolution, tile units, encoding, and don't repeat the same explanation. - High proper nouns as much as possible in Korean phonetic transcription. - No "Korean Review", "StarCraft Broodwar Map Review", etc. as headers.

- Output starts immediately with the review body text. - The English version must follow immediately after a blank line, no headers. - Original English text must NOT be outputted. Wait, re-read: "아래 영문

를 바탕으로

본문만 새로 작성해라." -> "Based on the following English StarCraft map review, write a new Korean review body only." Then: "모든 문장을 한글로 작성하고 영문 문장을 출력하지 마라." -> "Write all sentences in Korean and don't output English sentences." But then later: "총 1800~3,000자이며 제목, 머리말, 목록, Markdown, 부연 설명은 쓰지 마라." Wait, let's re-read carefully the whole prompt. Prompt: "아래 영문

를 바탕으로

본문만 새로 작성해라. 모든 문장을 한글로 작성하고 영문 문장을 출력하지 마라. 고유명사도 가능한 한 한글로 음역해라. 공백 포함 900~1,100자로 작성하며 제목, 머리말, 목록, Markdown, 부연 설명은 쓰지 마라. 원문에 없는 사실은 추가하지 마라. Here's a thinking process:

1. Analyze the Request: - Role: StarCraft: Broodwar map reviewer. - Source Data: Provided map data (title, filename, internal title, description, genre, players, tags, tileset). - Output Rules: - No JSON, Markdown code blocks, tables, lists, headings. - First: Korean review, 900-1100 chars (with spaces).

- Then: A blank line, then an English version of the same content, also 900-1100 chars (with spaces). - Total output: 1800-3000 chars (including Korean + English + blank line). - The Korean review must naturally cover: map structure, genre, gameplay style, player experience, recommended audience, pre-play check items.

- Don't invent maker, triggers, win conditions, story, balance numbers. - Don't list map size, resolution, tile units, encoding, and don't repeat the same explanation. - High proper nouns as much as possible in Korean phonetic transcription. - No "Korean Review", "StarCraft Broodwar Map Review", etc. as headers.

- Output starts immediately with the review body text. - The English version must follow immediately after a blank line, no headers. - Original English text must NOT be outputted. Wait, re-read: "아래 영문

를 바탕으로

본문만 새로 작성해라." -> "Based on the following English StarCraft map review, write a new Korean review body only." Then: "모든 문장을 한글로 작성하고 영문 문장을 출력하지 마라." -> "Write all sentences in Korean and don't output English sentences." But then later: "총 1800~3,000자이며 제목, 머리말, 목록, Markdown, 부연 설명은 쓰지 마라." Wait, let's re-read the whole prompt structure carefully.

Actually, the prompt structure is: - First line: "아래 영문

를 바탕으로

본문만 새로 작성해라." - Second line: "모든 문장을 한글로 작성하고 영문 문장을 출력하지 마라." - Third line: "