스타휴지 StarCraft HUZY 스타크래프트 유즈맵 맵 다운로드 커뮤니티
한국어

체스들의싸움3.4ver 맵 시리즈와 버전

파일명과 제목을 기준으로 같은 시리즈로 분류된 2개 버전입니다. 등록일, 버전명, 파일 크기와 이용자 반응을 비교해 원하는 파일을 선택하세요.

  1. 체스들의싸움3.4ver 미리보기
    최근 등록 버전

    체스들의싸움3.4ver

    버전 정보 없음 · [_________________체스게임3.scx

    만든이,수정이:starcraft_zealot버전:VA3.4수정된점:1.유닛이11 종류가 증가 하였다.2.비숍의 밸런스를 맟추었다.3.SCV가 추가 되었다.4.넥서스를 조금 강화 시켰다.

    다운로드 0
    조회 0
    좋아요 0
  2. 체스들의싸움3.1ver 미리보기
    이전 버전 1

    체스들의싸움3.1ver

    버전 정보 없음 · [ 체스게임3.scx

    Here's a thinking process: 1. **Analyze the Request Thoroughly:** - Role: Korean game reviewer/SEO editor specializing in StarCraft: Brood War custom maps. - Task: Write a detailed blog/article/review based on provided map image/metadata, optimized for search engines. - Output Format: Must be a single JSON object. No Markdown code blocks, no tables, no explanations outside JSON. - Language: Korean. - Structure: Natural paragraph sections, not new titles. Content starts directly with the Korean review. - Specific Rules: - Korean review first, 900-1100 chars (with spaces). - Then a blank line. - Then of the same content, no headings like " " etc. - Total content (Korean + English) must be 1800-3000 chars. - No unsure elements stated definitively. Use "추정된다", "보인다" etc. - No fabricating creator, triggers, win conditions, story, balance numbers. - Include natural keywords: map title, filename, genre, StarCraft map, UMS, play features. - No site traffic, downloads, ratings, distribution channels, community reactions, popularity estimates. - No "search on site", "refer to other archives/community reviews" messages. - Review content: map structure, genre, progression, play experience, recommended targets, pre-play check points. Not site evaluations. - no site stats, distribution channels, community reactions added. - Map metadata given: title "체스들의싸움3.1ver", filename "[ 체스게임3.scx", internal title same, description includes maker, modifications, SC zealot version, modified points (units increased, queen+ units fixed, values improved, balance adjusted), genre currently ARENA, players 8, team -, play time -, difficulty -, version -, tags -, hash, size 1024x1024, resolution 3072x3072, tile unit 96x96, tileset platform, encoding cp949, same group/other versions -, current classification ARENA. - Rules about recommendedMapType: must be one of the listed. If unsure, use same as current genre/classification. But there are specific rules about UMS vs MELEE etc based on image/description. Current classification is ARENA. Description mentions chess, units, queen, balance, etc. It's a chess map. Likely UMS or ARENA. But need to follow rules: "예를 들어 현재 분류가 MELEE여도 이미지/제목/설명상 컴퓨터 상대 유즈맵이면 recommendedMapType은 UMS 또는 더 적절한 enum, detailCategory는 컴까기로 둔다." Current is ARENA. Description is about chess game, units, combat. It's likely a PvP or UMS chess map. I should determine recommendedMapType based on description. Chess map with units, balance, 8 players. Could be ARENA or UMS. The current classification is ARENA. But chess maps are often UMS or ARENA. I'll check the rules: "recommendedMapType은 아래 허용값 중 하나만 사용한다. 확실하지 않으면 현재 장르/분류와 같은 값을 사용한다." So if unsure, use current: ARENA. But there's also: "예를 들어 현재 분류가 DEFENSE인데 실제로는 컴까기라면 recommendedMapType은 UMS, detailCategory는 컴까기로 둔다." Here current is ARENA. Description: "체스들의싸움3.1ver", units, queen, balance. It's a chess map. I think it's best to set recommendedMapType as ARENA since current classification is ARENA and I'm unsure, but maybe it's UMS? Chess is typically UMS or custom. I'll lean towards ARENA as per "if unsure, use current". But let's see the detailCategory rules: "detailCategory는 더 구체적인 하위 분류를 한국어로 작성한다. 예: 컴까기, 디펜스, 랜덤 디펜스, RPG, 키우기, 피하기, 탈출, 서바이벌, 아레나, 미니게임, 퍼즐, 캠페인, 디플로메시, 블러드, 입구막기, 넥서스 부수기, 밀리." Chess map could be "컴까기" or "아레나". The description mentions units, combat, balance. It's a chess-style map. I'll set detailCategory as "아레나" or "컴까기"? The current classification is ARENA. If I set detailCategory as 컴까기, that might be more specific

    다운로드 0
    조회 0
    좋아요 0