듀란죽이기 RPG 地圖系列與版本
根據檔名與標題分類為相同系列的 2個版本。請比較註冊日期、版本名稱、檔案大小與玩家反應，以選擇想要的檔案。
最近註冊版本듀란죽이기 RPG
v1.0 · 듀란죽이기.scx
듀란죽이기 RPG는 스타크래프트 브루드워에서 즐길 수 있는 대표적인 유즈맵 중 하나로, 특정 목표를 향해 캐릭터를 성장시키고 협동하는 재미를 제공한다. 본 맵은 플랫폼 타일셋을 기반으로 넓은 전장이 펼쳐지며, 플레이어들은 각자의 유령이나 영웅 유닛을 조작하여 정해진 경로를 따라 이동하며 적대 세력과 전투를 벌이게 된다. 전체적인 맵 구조는 복잡한 미로 형태와 넓은 평지, 그리고 특정 유닛들이 대기하거나 밀집해 있는 구역들로 나뉘어 있어 탐험하는 재미를 더해준다. 플레이어는 동료들과 함께 힘을 합쳐 적을 처치하고 자원을 확보하며 캐릭터를 강화해 나가는 방식으로 게임을 진행하게 되며, 이 과정에서 지속적인 유닛 조작과 상황 판단이 요구된다. 클래식한 스타크래프트 브루드워 유즈맵 특유의 감성을 고스란히 담고 있으며, 친구들과 함께 멀티플레이로 가볍게 즐기거나 협동 플레이의 묘미를 느끼고 싶은 유저들에게 적합하다. 플레이 전에는 제공된 맵의 특성과 기본적인 진행 방식을 가볍게 파악하는 것이 원활한 플레이에 도움이 되며, 복잡한 컨트롤보다는 역할 분담과 협력이 중요한 요소로 작용한다. 전통적인 RPG 장르의 유즈맵을 선호하는 플레이어라면 한 번쯤 색다른 재미를 느낄 수 있는 맵이다. Kill Duran RPG is one of the representative Use Map Settings available in StarCraft: Brood War, offering the fun of growing characters and cooperating toward a specific goal. Based on a platform tileset, this map unfolds across a wide battlefield where players control their respective ghost or hero units, moving along designated paths to engage in combat with hostile forces. The overall map structure is divided into complex maze-like shapes, wide plains, and areas where specific units wait or cluster, adding to the fun of exploration. Players proceed by teaming up with allies to defeat enemies, secure resources, and strengthen their characters, a process that requires continuous unit control and situational judgment. It retains the unique sentiment of classic StarCraft: Brood War custom maps and is well-suited for users who want to casually enjoy multiplayer with friends or experience the thrill of cooperative play. Before playing, briefly grasping the characteristics and basic progression method of the provided map helps ensure smooth gameplay, as role division and cooperation act as more important elements than complex micro-control. For players who prefer traditional RPG-genre custom maps, this is a map where you can experience a unique kind of fun.
下載 0觀看次數 0喜歡 0
先前的版本 1듀란죽이기 RPG
無版本資訊 · !_듀란죽이기 (1).scx
Here's a thinking process: 1. **Analyze the Request:** - **Role:** StarCraft: Broodwar map reviewer - **Source Data:** Provided map data (title, filename, internal title, internal description, genre, players, etc.) - **Output Rules:** - No JSON, Markdown code blocks, tables, lists, headings - First: Korean review, 900-1100 chars (with spaces) - Then: A blank line, then - "of the same content, no subtitle/heading" - No "Korean Review", "StarCraft Broodwar Map Review", etc. as headings - Output starts immediately with the review body text - Total output: 1800-3000 chars (including the Korean and English parts) - Cover: map structure, genre, play style, player experience, recommended players, pre-play checks - Don't invent maker, triggers, win conditions, story, balance changes - Don't list map size, resolution, tile units, encoding, and don't repeat the same explanation - Original English text provided in the prompt (but I need to output Korean first, then of same content, no headings) Wait, let me re-read the output rules carefully: "- First: Korean review, 900~1,100 chars (including spaces) - Then: A blank line, then - of the same content, no subtitle/heading - - No "Korean Review", "StarCraft Broodwar Map Review", etc. as headings - - Output starts immediately with the review body text - - Total output: 1800~3,000 chars (including the Korean and English parts) - - Cover: map structure, genre, play style, player experience, recommended players, pre-play checks - - Don't invent maker, triggers, win conditions, story, balance changes - - Don't list map size, resolution, tile units, encoding, and don't repeat the same explanation" And also: "아래 영문 를 바탕으로 본문만 새로 작성해라. 모든 문장을 한글로 작성하고 영문 문장을 출력하지 마라. 고유명사도 가능한 한 한글로 음역해라. 공백 포함 900~1,100자로 작성하며 제목, 머리말, 목록, Markdown, 부연 설명은 쓰지 마라. 원문에 없는 사실은 추가하지 마라." So the user wants me to: - Take the English map review data (which seems to be just the map metadata/description, not a full review text? Actually the prompt says "Here's a thinking process:" and then gives the constraints, but the actual English text to base the review on seems to be the map data provided after "Here's a thinking process:" Wait, let me read the very beginning: "아래 영문 를 바탕으로 본문만 새로 작성해라." Then the constraints. Then "Here's a thinking process:" is actually part of the prompt template, but the actual data to work with is the map info provided after that? Let me look at the structure. The user message is: "아래 영문 를 바탕으로 본문만 새로 작성해라. ... Here's a thinking process:" then the thinking process stuff, then "Map Data Given:" with the map details. Then "Output Requirements:" with the rules. Then "Map Data:" with the map info. Actually, the structure is a bit jumbled. Let me parse the entire user message: - Starts with "아래 영문 를 바탕으로 본문만 새로 작성해라." (Translate the following English StarCraft map review into Korean...) - Then constraints: "모든 문장을 한글로 작성하고 영문 문장을 출력하지 마라. 고유명사도 가능한 한 한글로 음역해라. 공백 포함 900~1,100자로 작성하며 제목, 머리말, 목록, Markdown, 부연 설명은 쓰지 마라. 원문에 없는 사실은 추가하지 마라." - Then "Here's a thinking process:" followed by AI reasoning steps (this is likely the system prompt or template) - Then "Map Data Given:" with the map details - Then "Output Requirements:" with rules - Then "Map Data:" repeating the map info I think the actual English map review data/description is the "Map Data Given" section. The user wants me to Here's a thinking process: 1. **Analyze the Request:** - **Role:** StarCraft: Broodwar map reviewer - **Source Data:** Provided map data (title, filename, internal title, internal description, 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 subtitle/heading - No "Korean Review", "StarCraft Broodwar Map Review", etc. as headings - Output starts immediately with the review body text - Total output: 1800-3000 chars (including the Korean and English parts) - Cover: map structure, genre, play style, player experience, recommended players, pre-play checks - Don't invent maker, triggers, win conditions, story, balance changes - Don't list map size, resolution, tile units, encoding, and don't repeat the same explanation - **Map Data Given:** - Title: 듀란죽이기 RPG - Filename: !_듀란죽이기 (1).scx - Internal title: 듀란죽이기 RPG - Internal description: 만든이:[Amarua]-zzang 깜둥이를 죽이자??.쪼깨 업해씸다.. - Genre: RPG (RPG) - Players: 6 - Teams: - - Expected play time: - - Difficulty: - - Version: - - Tags: - - Tileset: Platform 2. **Deconstruct the Output Requirements:** - Korean review: 900-1100 chars (with spaces) - Then a blank line - Then of the same content (no headings, just the text) - Total: 1800-3000 chars - No headings, no markdown, no JSON, no lists/tables - Start directly with the review text - Cover map structure, genre, gameplay, experience, recommended players, pre-play checks (naturally, based on data) - Don't invent things not in data - Don't list tile set, resolution, etc. explicitly, but can naturally mention platform tileset context Important: The English part must be a direct translation of the Korean content, no headings, just text after a blank line. Let's plan the Korean review text length. Need 900-1100 chars including spaces. That's quite long. I need to write a substantial review covering: - Genre: RPG - Players: 6 - Theme: Killing Duran (based on title and internal desc "kill the zerg/cocoon??" actually internal desc: "만든이:[Amarua]-zzang 깜둥이를 죽이자??.쪼깨 업해씸다.." -> roughly "Let's kill the zerg/cocoon, make it better...") - Map structure: platform tileset - Gameplay: RPG style, likely hero-based, killing units, progression - Experience: cooperative or competitive? 6 players, no teams info, so maybe FFA or mixed - Recommended: RPG fans, those who like killing waves, etc. - Pre-check: maybe difficulty, version, but data is sparse, so keep it general based on what's given I need to be careful about character count. Let's aim for ~1000 chars Korean. Then same length. Total ~2000 chars, within 1800-3000. Let's start drafting Korean text. I'll write in a natural review style, no headings, just flowing text. I'll count chars mentally/approx. I need to include spaces in count. I'll try to be verbose but structured. Key points to cover naturally: - Genre RPG with platform tileset - 6 players, no team info - Theme of killing Duran/zerg - Creator Amarua-zzang - Internal description humor/enthusiasm - Playstyle: likely killing units, RPG progression - Suitable for: RPG fans, cooperative or FFA depending on design - Pre-play: expect custom RPG mechanics, possibly wave survival or boss fight I need to avoid listing "map size, resolution, tile units, encoding". I can mention "platform tileset" naturally as part of description, but not as a list item. The rules say "Don't list map size, resolution, tile units, encoding and don't repeat
下載 0觀看次數 1喜歡 0