벽짓고 살아남기(新능력) 맵 시리즈와 버전
파일명과 제목을 기준으로 같은 시리즈로 분류된 2개 버전입니다. 등록일, 버전명, 파일 크기와 이용자 반응을 비교해 원하는 파일을 선택하세요.
최근 등록 버전벽짓고 살아남기(新능력)
버전 정보 없음 · 벽짓고살아남기(新능력)..bak.scx
벽짓고 살아남기(新능력)만든이 : [L]StarCraft수정자 : Uruz버그제거와 패치진행중..
다운로드 0조회 0좋아요 0
이전 버전 1벽짓고 살아남기(新능력)
버전 정보 없음 · 벽짓고살아남기 (新능력).bak.scx
Here's a thinking process: 1. **Analyze the Request:** - the user wants me to take a provided StarCraft: Broodwar map description, write a Korean review based on it, following strict formatting and content rules, then output the Korean review, then a blank line, then the English version of the same review, with specific constraints. Let me re-read the prompt carefully to extract all constraints: - "아래 영문 를 바탕으로 본문만 새로 작성해라." -> "Based on the following English StarCraft map review, write a new Korean review body." - "모든 문장을 한글로 작성하고 영문 문장을 출력하지 마라." - Write all sentences in Korean, do not output English sentences: "Do not output English sentences." Wait, later it says "same content, no subtitles/headings like 'Korean Review', 'StarCraft Broodwar Map Review', etc. ... Output starts immediately with the review body first sentence." And later: "Total output: 1800-3000 chars (including spaces). Cover: map structure, genre, gameplay style, player experience, recommended audience, pre-play check items. Do NOT invent: maker, triggers, win conditions, story, balance patch notes. - Do NOT list: map size, resolution, tile set, encoding, repeat same explanations. - Use provided data naturally." - "고유명사는 가능한 한 한글로 음역해라." - Transliterate proper nouns into Korean as much as possible. - "공백 포함 900~1,100자로 작성하며 제목, 머리말, 목록, Markdown, 부연 설명은 쓰지 마라." Write including spaces 900~1100 chars, no title, headlist, list, Markdown, supplementary explanation. So the Korean review body must be 900-1100 chars (with spaces). Total output 1800-3000 chars (Korean + English + blank line). So the English review will also be 900-1100 chars? Let's read carefully: "Total output: 1800-3000 chars (including spaces). Cover: map structure, genre, gameplay style, player experience, recommended audience, pre-play check items." So the total output (Korean + blank line + English) must be 1800-3000 chars. So each language review should be roughly 900-1100 chars to fit 1800-3000 total (with blank line ~1 char). So each review body should be ~900-1100 chars. - "모든 문장을 한글로 작성하고 영문 문장을 출력하지 마라." Write all sentences in Korean, do not output English sentences. Wait, there's a contradiction: "Total output: 1800-3000 chars (including spaces). Cover: map structure, genre, gameplay style, player experience, recommended audience, pre-play check items. Do NOT invent: maker, triggers, win conditions, story, balance patch notes. Do NOT list: map size, resolution, tile set, encoding, repeat same explanations. Use provided data naturally." And earlier: "모든 문장을 한글로 작성하고 영문 문장을 출력하지 마라." (Write all sentences in Korean and do not output English sentences.) But then later it says "Total output: 1800-3000 chars (including spaces)." And "Total output: 1800-3000 chars (including spaces)." And "Output starts immediately with the review body first sentence." And "Output the Korean review first, then a blank line, then the English review of the same content, no subtitles/headings like 'Korean Review', 'StarCraft Broodwar Map Review', 'Map Review', "" as headings." And "Total output: 1800-3000 chars (including spaces)." So total output 1800-3000 chars. That means Korean review ~900-1100, blank line ~1, English review -900-1100. But the prompt also says: "모든 문장을 한글로 작성하고 영문 문장을 출력하지 마라." (Write all sentences in Korean and do not output English sentences.) There's a contradiction: "all sentences in Korean, do not output English sentences" vs "total output 1800-3000 chars" with Korean + blank + English. And "Output the Korean review first, then a blank line, then the English review of the same content, no subtitles/headings like 'Korean Review', Here's a thinking process: 1. **Analyze the Request:** - **Role:** StarCraft: Broodwar map reviewer. - **Source Data:** Provided map data (title, filename, internal title, genre, players, etc.) - **Output Rules:** - No JSON, Markdown code blocks, tables, lists, headings. - First: Korean review, 900-1100 chars (including spaces). - Then: A blank line, then of the same content, no subtitles/headings like "Korean Review", "StarCraft Broodwar Map Review", etc. - No "Korean Review", "StarCraft Broodwar Map Review", "Map Review", " ", " ", "Translation" as headings. - Output starts immediately with the review body first sentence. - Total output: 1800-3000 chars (including spaces). - Cover: map structure, genre, gameplay style, player experience, recommended audience, pre-play check items. - Do NOT invent: maker, triggers, win conditions, story, balance patch notes. - Do NOT list: map size, resolution, tile set, encoding, repeat same explanations. - Use provided data naturally. - **Provided Map Data:** - Title: 벽짓고 살아남기(新能力) [wait, it says (新能力) but probably a typo for (新能力)? The data says "新능력" in some places, let's check: "タイトル: 壁 짓고 살아남기(新能力)" - actually it says (新能力) which is Chinese for "new ability", but the internal title says "(新능력)" which is Korean for "new ability". I'll just use the concept of "new ability" or ignore the parentheses if not crucial, but I need to naturally mention the genre and tags. The data has "태그: -" so no tags.) - Filename: 벽짓고살아남기 (新能力).bak.scx - Internal Title: 벽짓고 살아남기(新능력) - Internal Description: 벽짓고 살아남기(新능력)만든이 : [L]StarCraft버그제거와 패치진행중.. - Genre: UMS (유즈맵) - Players: 7 - Teams: - - Expected Play Time: - - Difficulty: - - Version: - - Tags: - - Tileset: Platform - **Key Constraints:** - Korean review: 900-1100 chars (with spaces). - same content, after a blank line, no headings. - Total: 1800-3000 chars (so Korean + English + blank line must be in that range). - No headings at all. - Start directly with first sentence of review. - No inventing maker details beyond what's given, but the description says "만든이 : [L]StarCraft버그제거와 패치진행중.." - I can mention the maker is actively patching/bug fixing, but not invent specific triggers/win conditions. - Must explain map structure, genre, gameplay style, player experience, recommended audience, pre-play check items naturally. - Don't list map size, resolution, tile set, encoding. - Don't repeat same explanations. - **Plan:** a) Write Korean review, 900-1100 chars. Must include: genre (UMS), player count (7), tileset (platform), the fact it's about "building walls and surviving", the maker is patching/bug fixing, no specific difficulty/version given, so I'll describe the gameplay style based on title, the experience of 7 players, etc. Must be natural, no headings. b) Then a blank line. c) Then of the Korean review, same length roughly, no headings, just pure text. d) Ensure total chars 1800-3000. If Korean is ~1000, English ~1000, total ~2000, fits. - **Drafting Korean Review (Mental):** Need to hit 900-1100 chars with spaces. Let's aim for ~1000. I'll write fluently, covering: - The map is "벽짓고 살아남기(新능력)" a UMS map for 7 players. - Core concept: surviving by building walls, likely defensive/tower defense style. - Genre UMS, no team info,
다운로드 0조회 0좋아요 0