Execution Check & Play Tips
Help other users by sharing your direct test results and spoiler-free tips.
Lurker D 18 Way ~=FINAL=~v2.scx Download· For 6 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: - Input: A StarCraft: Brood War map review in English (but the user only provided metadata/description, not a full review text). Wait, the user said: "아래 영문
를 바탕으로
본문만 새로 작성해라." But then they provided map data, not a full review text. Let me re-read carefully.
- The user provided: "Here's a thinking process:" then a long prompt with constraints, and at the end: "Provided map data: Title: Lurker D 18 Way ~=FINAL=~, Filename: Lurker D 18 Way ~=FINAL=~v2.scx, Internal title same, Internal description: Modified Version by TerrorMarine&Altarian.Probes to Mine xtra minerals.30 Second RoundsUpgrades to 255. Genre: UMS.
Players: 6. Teams: -. Expected time: -. Difficulty: -. Version: -. Tags: -. Tileset: Waste land/Desert." - Wait, the user says "아래 영문
를 바탕으로" (Based on the following English StarCraft map review), but then they give map data, not a review text. Maybe the "map data" is what I need to base the review on? Or maybe the user forgot to paste the actual review? The prompt says "Here's a thinking process:" which is the system/ai thinking format, but the actual instruction is: "아래 영문
를 바탕으로
본문만 새로 작성해라." Then there's a lot of constraints, and then "Provided map data: ...". - I need to generate a Korean review based on this map data, following all the strict constraints.
The "English StarCraft map review" might refer to the map data provided, or perhaps the user expects me to write a review *as if* I'm reviewing this map, using the given data as the source, without inventing things beyond what's given. Let's parse the constraints very carefully: - Output: Korean review body only, 900-1100 chars (including spaces).
- Then a blank line. - Then the same content, no headings, in English (but the user said "all sentences in English? Actually: "모든 문장을 한글로 작성하고 영문 문장을 출력하지 마라." -> "Write all sentences in Korean and do not output English sentences." Wait, later: "제목, 머리말, 목록, Markdown, 부연 설명은 쓰지 마라." and "원문에 없는 사실은 추가하지 마라." Also: "아래 영문
를 바탕으로
본문만 새로 작성해라." -> "Based on the following English StarCraft map review, write only the Korean review body." - Then: "모든 문장을 한글로 작성하고 영문 문장을 출력하지 마라." -> "Write all sentences in Korean and do not output English sentences." - "고유명사는 가능한 한 한글로 음역해라." -> Romanize proper nouns as Korean phonetics.
- "공백 포함 900~1,100자로 작성하며 제목, 머리말, 목록, Markdown, 부연 설명은 쓰지 마라." -> Write 900-1100 chars including spaces, no title, headings, lists, Markdown, supplementary explanations. - "원문에 없는 사실은 추가하지 마라." -> Do not add facts not in the original text.
- "고정 길이 제한 없음" seems not a constraint, but earlier: "Total output of 1800~3000 characters" - wait, the user wrote: "공백 포함 900~1,100자로 작성하며 제목, 머리말, 목록, Markdown, 부연 설명은 쓰지 마라." and earlier "Total output of 1800~3000 characters (so Korean + English + blank line must fit in this range)". But then they also say "공백 포함 900~1,100자로 작성하며...".
Let's re-read the whole prompt structure. The prompt structure as given: "아래 영문
를 바탕으로
본문만 새로 작성해라. 모든 문장을 한글로 작성하고 영문 문장을 출력하지 마라. 고유명사는 가능한 한 한글로 음역해라. 공백 포함 900~1,100자로 작성하며 제목, 머리말, 목록,
| URL | https://star.huzy.net/map/cmtqbntc5002fdzohstnrr4uo |
|---|---|
| File Name | Lurker D 18 Way ~=FINAL=~v2.scx |
| Uploader | HUZY |
| Map Type | Use Map More maps |
| File Size | 85.29 KB |
| Date registered | 2026-09-07 06:26:45 |
| Views | 0 |
| Likes | 0 |
| Rating | (0) |