Execution Check & Play Tips
Help other users by sharing your direct test results and spoiler-free tips.
[1950]6.25_[18.9].scx Download· For 7 players
This review is a reference analysis generated by generative AI based on map file information and descriptions.
Here's a thinking process:
1. Analyze the Request: - Role: StarCraft: Broodwar 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.
(Wait, "Output must be JSON, Markdown, tables, lists, or headers - NO." - this seems contradictory. Let me read carefully: "Output the Korean review, 900-1100 chars (including spaces).
Then, after a blank line, translate the same content into English, no subtitles/headers like "Korean Review", "StarCraft Broodwar Map Review", "Map Review", "Translation" as headings. Output starts directly with the review body. Total output: 1800-3000 chars (including spaces on-spaces).
Content must naturally cover: map structure, genre, ...) - Actually, re-reading: "Output the Korean review, 900-1100 chars (including spaces). Then, after a blank line, translate the same content into English, no subtitles/headers like "Korean Review", "StarCraft Broodwar Map Review", "Map Review", "Translation" as headings.
Output starts directly with the review body. Total output: 1800-3000 chars (including spaces on-spaces). Content must naturally cover: map structure, genre, ..." Wait, the prompt says: "다음 를 자연스러운
로 번역해라. 제목, 머리말, 목록, Markdown, 부연 설명 없이 한국어 번역 본문만 출력해라. 원문에 없는 맵 정보나 평가를 추가하지 마라." - Let me re-read the entire prompt carefully. - Prompt: "다음 를 자연스러운
로 번역해라. 제목, 머리말, 목록, Markdown, 부연 설명 없이 한국어 번역 본문만 출력해라. 원문에 없는 맵 정보나 평가를 추가하지 마라. Here's a thinking process:
1. Analyze the Request: - Role: StarCraft: Broodwar 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.
(Wait, "Output must be JSON, Markdown, tables, lists, or headers - NO." - this seems contradictory. Let me read carefully: "Output the Korean review, 900-1100 chars (including spaces).
Then, after a blank line, translate the same content into English, no subtitles/headers like "Korean Review", "StarCraft Broodwar Map Review", "Map Review", "Translation" as headings. Output starts directly with the review body. Total output: 1800-3000 chars (including spaces on-spaces). .
Content must naturally cover: map structure, genre - Actually, re-reading: "다음 를 자연스러운
로 번역해라. 제목, 머리말, 목록, Markdown, 부연 설명 없이 한국어 번역 본문만 출력해라. 원문에 없는 맵 정보나 평가를 추가하지 마라. Here's a thinking process:
1. Analyze the Request: - Role: StarCraft: Broodwar 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.
(Wait, "Output must be JSON, Markdown, tables, lists, or headers - NO." - this seems contradictory. Let me read carefully: "Output the Korean review, 900-1100 chars (including spaces).
Then, after a blank line, translate the same content into English, no subtitles/headers like "Korean Review", "StarCraft Broodwar Map Review", "Map Review", "Translation" as headings. Output starts directly with the review body. Total output: 1800-3000 chars (including spaces on-spaces). .
Content must naturally cover: map structure, genre - Actually, re-reading: "다음 를 자연스러운
로 번역해라. 제목, 머리말
| URL | https://star.huzy.net/map/cmu9ff09a005urnohy1lls09f |
|---|---|
| File Name | [1950]6.25_[18.9].scx |
| Uploader | HUZY |
| Map Type | Use Map More maps |
| File Size | 186.35 KB |
| Date registered | 2026-09-20 15:19:30 |
| Views | 2 |
| Likes | 0 |
| Rating | (0) |