Death Frontier

Here's a thinking process:

1. Analyze the Request: - Role: StarCraft: Brood War map reviewer. - Input: Map data for "Death Frontier" (title, filename, internal title/description, genre, players, tags, tileset). - Output Rules: - Output must be JSON, Markdown, tables, lists, or headers - NO. Wait, let me read carefully: "다음 를 자연스러운

로 번역해라. 제목, 머리말, 목록, Markdown, 부연 설명 없이 한국어 번역 본문만 출력해라." - This means: Translate the following StarCraft map review into natural Korean review. Output only the Korean translation body, without titles, headings, lists, Markdown, supplementary explanations. - Then: "원문에 없는 맵 정보나 평가를 추가하지 마라." - Don't add map info or evaluations not in the original text.

- Wait, there's more output requirements later: "1. Role: StarCraft: Brood War map reviewer. - Input: Map data for "Death Frontier" (title, filename, internal title/description, genre, players, tags, tileset). - Output Rules: - Output must be JSON, Markdown, tables, lists, or headers - NO.

- First, write a Korean review, 900-1100 characters (including spaces). - Then, after a blank line, translate the same content into English, without any subtitles/headings like "Korean Review", "StarCraft Brood War Map Review", etc. - No "Korean Review", "StarCraft Brood War Map Review", "Map Review", "

", "

", "Translation" as headings. - Output starts immediately with the review body text. - Total output: 1800-3000 characters (including spaces). - Naturally explain map structure, genre, gameplay style, player experience, recommended targets, pre-play check items. - Do NOT invent producer, triggers, win conditions, story, balance adjustments.

- Do NOT list map size, resolution, tile units, encoding, and don't repeat the same explanation. - Map Data Given: - Title: Death Frontier - Filename: (8)Death_Frontier.scm - Internal title: Death Frontier - Internal description: You have decided to build your base near some mineral Deposits so have your foes.

You also notice there is no Vespiene Gas near your base and its all in the Middle. - Genre: MELEE (밀리) - Players: 8 - Teams: - - Expected play time: - - Difficulty: - - Version: - - Tags: - - Tileset: Wasteland"

Okay, let's parse the actual output requirements vs the initial prompt. The user says: "다음 를 자연스러운

로 번역해라. 제목, 머리말, 목록, Markdown, 부연 설명 없이 한국어 번역 본문만 출력해라. 원문에 없는 맵 정보나 평가를 추가하지 마라." Then there's a big block that seems like system instructions or additional constraints mixed in. Let me read carefully. It starts with: "Here's a thinking process:" then the actual user request?

No, the format is: User prompt, then "Here's a thinking process:" which I need to follow. But the content after "Here's a thinking process:" looks like a mix of role definition, input data, and output rules. Let me re-read the entire message structure: - User: "다음 를 자연스러운

로 번역해라. 제목, 머리말, 목록, Markdown, 부연 설명 없이 한국어 번역 본문만 출력해라. 원문에 없는 맵 정보나 평가를 추가하지 마라." - Then: "Here's a thinking process:" followed by a lot of text that seems to be the system's internal thought process or maybe it's part of the prompt? Actually, in the message, it's: "Here's a thinking process:" then the text.

This is typical of AI prompt formats where the user provides a thinking process example, but here it's embedded. Wait, the entire message after "User" is just the prompt. The "Here's a thinking process:" might be a separator or part of the prompt. Let me read the whole thing as given:

"다음 를 자연스러운

로 번역해라. 제목, 머리말, 목록, Markdown, 부연 설명 없이 한국어 번역 본문만 출력해라. 원문에