Tank Defense V4.1 맵 시리즈와 버전
파일명과 제목을 기준으로 같은 시리즈로 분류된 2개 버전입니다. 등록일, 버전명, 파일 크기와 이용자 반응을 비교해 원하는 파일을 선택하세요.
최근 등록 버전Tank Defense V4.1
버전 정보 없음 · [ 12A.scm
Here's a thinking process: 1. **Analyze the Request:** - Role: Korean game reviewer/SEO editor specialized in StarCraft: Brood War custom maps. - Task: Write a detailed blog/article/review based on provided map image/metadata, optimized for search engines. - Output: Must be a single JSON object. No markdown blocks, no tables, no explanations outside JSON. - Language: Korean primarily, with included in `content`. - Specific formatting rules: Korean review first (900-1100 chars including spaces), then a blank line, then of the same content. No section headers like "Korean Review", " ", etc. Content must start directly with the review text. - Content rules: Include map structure, genre, gameplay, experience, recommended players, etc. No made-up producer, triggers, win conditions, story, balance numbers. No site stats, download counts, ratings, distribution channels, community reactions, popularity estimates. - SEO: Naturally include map title, filename, genre, SC map, UZMAP, play characteristics. - Metadata handling: Use provided data. Estimate uncertain elements with "추정된다", "보인다". Don't invent data not in the provided set. - Map classification: Check `recommendedMapType`, `detailCategory`, `recommendedTitle`, etc., based on strict rules. - Map data provided: - Site display title: Tank Defense V4.1 - Original filename: [12A.scm (with spaces] - Internal map title: Tank Defense V4.1 - Internal map description: Don't let any enemies through! - Current genre/classification: DEFENSE (디펜스) - Player count: 4 - Teams: - - Estimated play time: - - Difficulty: - - Version: - - Tags: - - Map hash: bc85871bb5948f2 - Map size: 4096 x 4096 - Full resolution: 4096 x 4096 - Tile unit: 128 x 128 - Tile set: Space - Encoding: cp949 - Same group/other version candidates: - 2. **Determine Map Classification & Rules Application:** - Current classification: DEFENSE (디펜스) - Internal description: "Don't let any enemies through!" -> This is a defense/tower defense style. - Rules about `recommendedMapType`: - If DEFENSE but actually is wave-based defense against enemies walking through, it's likely DEFENSE or TOWER_DEFENSE. - Rules: "If current classification is DEFENSE but actually it's komkka (computer killing/map vs AI), then recommendedMapType is UMS, detailCategory is 컴까기." - "If current classification is DEFENSE but actually it's tower defense, recommendedMapType is UMS or appropriate enum, detailCategory is 디펜스." Wait, need to re-read carefully. - Actually: "If current classification is MELEE but image/title/map description shows it's a UMS map against computers, then recommendedMapType is UMS or more appropriate enum, detailCategory is 컴까기." - "If current classification is DEFENSE but actually it's komkka, recommendedMapType is UMS, detailCategory is 컴까기." - "If current classification is DEFENSE but actually it's tower defense, recommendedMapType is UMS, detailCategory is 디펜스." Hmm, the rules say: "If current classification is DEFENSE but actually it's tower defense, recommendedMapType is UMS or more appropriate enum, detailCategory is 디펜스." Wait, the list of representative subcategories includes "디펜스", "타워 디펜스", etc. - Let's read the exact rules again: - "예를 들어 현재 분류가 MELEE여도 이미지/제목/설명상 컴퓨터 상대 유즈맵이면 recommendedMapType은 UMS 또는 더 적절한 enum, detailCategory는 컴까기로 둔다." - "예를 들어 현재 분류가 DEFENSE인데 실제로는 컴까기라면 recommendedMapType은 UMS, detailCategory는 컴까기로 둔다." - "예를 들어 현재 분류가 DEFENSE인데 실제로는 타워 디펜스라면 recommendedMapType은 UMS, detailCategory는 디펜스로 둔다." Wait, the text says: "예를 들어 현재 분류가 DEFENSE인데 실제로는 컴까기라면 recommendedMapType은 UMS, detailCategory는 컴까기로 둔다." and then "예를 들어 현재 분류가
다운로드 0조회 0좋아요 0
이전 버전 1Tank Defense V4.1
버전 정보 없음 · [ 12A.scm
Here's a thinking process: 1. **Analyze the Request:** - **Role:** StarCraft: Broodwar map reviewer. - **Source Data:** Provided map data (title, filename, internal title, 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 the - Same content, no headings/subtitles. - Total output: 1800-3000 chars (including spaces). - Cover: map structure, genre, gameplay style, player experience, recommended audience, pre-play checks. - Do NOT invent: creator, triggers, win conditions, story, balance changes. - Do NOT list: map size, resolution, tile units, encoding, repeat same explanations. - **Map Data Given:** - Title: Tank Defense V4.1 - Filename: [ 12A.scm - Internal title: Tank Defense V4.1 - Internal description: Don't let any enemies through! - Genre: DEFENSE (디펜스) - Players: 4 - Teams: - - Expected play time: - - Difficulty: - - Version: - - Tags: - - Tileset: Space 2. **Deconstruct the Constraints:** - Korean review: 900-1100 chars (with spaces). - Same content, after a blank line, no headings. - Total output: 1800-3000 chars. So Korean + blank line + English must total 1800-3000 chars. Since Korean is 900-1100, English must be similar, totaling ~1800-2200, which fits the 1800-3000 range. I need to make sure both are substantial enough. - No headings at all. The output must start directly with the review text. Same for English part. - The English part must follow a blank line after the Korean part. It should be a direct translation of the Korean review, no headings. - I must not use markdown, lists, tables, or headings like "Korean Review" etc. - I need to naturally describe map structure, genre, gameplay, experience, recommended audience, pre-play checks, based on the given data, without inventing fake details, and without listing tile size/resolution/etc. 3. **Drafting - Korean Review (Target: 900-1100 chars with spaces):** - I need to write a coherent review about "Tank Defense V4.1" based on the given data. - Genre: Defense. - Description: Don't let any enemies through! - Players: 4. - Tileset: Space. - I need to expand naturally on the gameplay, experience, who it's recommended for, what to check before playing, all without inventing fake details. - I must count characters carefully. Target: 900-1100 including spaces. That's quite long. I'll need to write extensively but carefully. - Let me plan the content: - Start directly with the review text (no heading). - Talk about the defense genre, the core objective, the space tileset setting, the 4-player setup, the tension of holding lines, the strategic placement, the replay value, suitability for casual or competitive play, note that it's a defense map, the "don't let enemies through" premise, maybe mention the version V4.1 implies evolution, the filename quirk, but without making up triggers or balance. - I need to hit 900+ chars. Let me aim for ~1000 chars. I'll write in Korean, natural flow, no bullet points, just prose. - I must remember: no headings, start directly with text. - Let me start drafting Korean text mentally: "스타크래프트 브루드워 디펜스 맵 중에서도 '탱크 디펜스 V4.1'은 우주 타일셋을 배경으로 한 적의 진격을 막아내는 핵심적인 방어 플레이에 집중한 맵이다. 맵의 기본 컨셉은 '적군이 절대로 통과하지 못하게 하는 것'으로, 플레이어는 진입로를 차단하고 기지를 방어하며 물밀듯 몰려오는 적을 견뎌내는 임무를 맡는다. 전체적인 분위기는 긴박하고 전략적이어서, 유닛 배치와 기술 타이밍, 리소스 관리 등이 승패를 가르는 중요한 요소가 된다. 4인 플레이가 지원되며, Here's a thinking process: 1. **Analyze the Request:** - **Role:** StarCraft: Broodwar map reviewer. - **Source Data:** Provided map data (title, filename, internal title, description, genre, players, etc.) - **Output Rules:** - No JSON, Markdown code blocks, tables, lists, headings. - First: Korean review, 900-1100 characters (including spaces). - Then: A blank line, then the of the same content, no headings/subtitles. - No "Korean Review", "StarCraft Broodwar Map Review", "Map Review", " ", " ", "Translation" as headings. - Output starts directly with the review body. - Total output: 1800-3000 characters (including spaces). - Cover: map structure, genre, gameplay style, player experience, recommended audience, pre-play checks. - Do NOT invent: creator, triggers, win conditions, story, balance changes. - Do NOT list: map size, resolution, tile units, encoding, repeat same explanations. - **Map Data Given:** - Title: Tank Defense V4.1 - Filename: [ 12A.scm - Internal title: Tank Defense V4.1 - Internal description: Don't let any enemies through! - Genre: DEFENSE (디펜스) - Players: 4 - Teams: - - Expected play time: - - Difficulty: - - Version: - - Tags: - - Tileset: Space 2. **Deconstruct the Constraints:** - Korean review: 900-1100 chars (with spaces). - Same content, after a blank line, no headings. - Total output: 1800-3000 chars. So Korean + blank line + English must total 1800-3000 chars. Since Korean is 900-1100, English must be similar, totaling ~1800-2200, which fits the 1800-3000 range. I need to make sure both are substantial enough. - No headings at all. The output must start directly with the review text. Same for English part. - The English part must follow a blank line after the Korean part. It should be a direct translation of the Korean review, no headings. - I must not use markdown, lists, tables, or headings like "Korean Review" etc. - I need to naturally describe map structure, genre, gameplay, experience, recommended audience, pre-play checks, based on the given data, without inventing fake details, and without listing tile size/resolution/etc. 3. **Drafting - Korean Review (Target: 900-1100 chars with spaces):** - I need to write a coherent review about "Tank Defense V4.1" based on the given data. - Genre: Defense. - Description: Don't let any enemies through! - Players: 4. - Tileset: Space. - I need to expand naturally on the gameplay, experience, who it's recommended for, what to check before playing, all without inventing fake mechanics. - I must count characters carefully. Target: 900-1100 including spaces. That's quite long. I'll need to write extensively but carefully. - Let me plan the content: - Start directly with the review text (no heading). - Talk about the defense genre, the core objective, the space tileset setting, the 4-player setup, the tension of holding lines, the strategic placement, the replay value, suitability for casual or competitive play, note that it's a defense map, the "don't let enemies through" premise, maybe mention the version V4.1 implies evolution, the filename quirk, but without making up triggers or balance. - I need to hit 900+ chars. Let me aim for ~1000 chars. I'll write in Korean, natural flow, no bullet points, just prose. - I must remember: no headings, start directly with text. - Let me start drafting Korean text mentally: "스타크래프트 브루드워 디펜스 맵 중에서도 '탱크 디펜스 V4.1'은 우주 타일셋을 배경으로 한 적의 진격을 막아내는 핵심적인 방어 플레이에 집중한 맵이다. 맵의 기본 컨셉은 '적군이 절대로 통과하지 못하게 하는 것'으로, 플레이
다운로드 0조회 0좋아요 0