실행 확인과 플레이 팁
직접 실행한 결과와 스포일러 없는 팁을 남겨 다른 이용자를 도와주세요.
Into_the_Darkness.scm 다운로드 · 4인용
이 리뷰는 생성형 AI가 맵 파일 정보와 설명을 바탕으로 작성한 참고용 분석입니다.
We need to produce JSON object only, with fields as defined. We need to analyze map "Into the Darkness". Provided data: title: Into the Darkness (both site and internal). No other description other than internal description: "Explore a new world and conquer all of your enemies...even if it means your own allies.
There are only a limited supply of resources...leaving you one option: survial.~Creator FenixAdun777 (BlackKnight777)". So likely a melee map, 4 players, maybe FFA? No team info. It mentions allies; you might have to fight your own allies? It might be a free-for-all scenario with limited resources and survival. Given genre currently MELEE (밀리).
Need to decide recommendedMapType: If it's a melee map (standard melee), recommendedMapType is MELEE. But the description suggests maybe it's a survival or something: "limited supply of resources...leaving you one option: survial." That suggests a survival style maybe "SURVIVAL". However, it's still a melee map type?
The map type classification in SC: MELEE refers to standard melee maps (like regular melee). If it's a custom survival scenario, it's likely UMS (Use Map Settings). The internal description suggests custom scenario: limited resources, survive, maybe a "survival" map.
The presence of "Explore a new world and conquer all of your enemies...even if it means your own allies." suggests maybe a FFA with backstabbing. Thus recommendedMapType might be UMS. We need to decide detailCategory: The map is likely a survival map: "survival" subcategory. Or maybe "밀리" (melee) but detailCategory could be "서바이벌".
Since limited resources and survival objective, detailCategory = "서바이벌". Provide reason. We also need recommendedTitle: The site title is "Into the Darkness". That's already English. Need to add Korean translation? The rule: If site title is not in format "한글 제목 (English Title)", we must write recommendedTitle.
The site title is English only, so we need to produce Korean title + English in parentheses. We need to create a natural Korean translation. "Into the Darkness" could be "어둠 속으로" or "어둠으로의 여행". Usually "어둠 속으로" works. So recommendedTitle: "어둠 속으로 (Into the Darkness)". Ensure format: Korean title (English Title).
Provide titleReason: "사이트 표시 제목이 영어만 있어 한글 번역을 추가하여 한글/영문 병기 형식으로 구성". Now recommendedPlayerCount: Provided: 플레이 인원: 4. So recommendedPlayerCount = 4. Team count: Not given, assume 1 (free-for-all). So recommendedTeamCount = 1. Play time: Not given; we need to infer? Not enough info; we should leave null or omit. The instruction: if uncertain, null or omit.
But we need to include field if we can infer? Safer to omit? The JSON schema expects those fields but we can set null?
It didn't say we must include them; it says "비어 있는 맵 상세 메타데이터를 채울 수 있으면 recommendedPlayerCount, recommendedTeamCount, recommendedPlayTime, recommendedDifficulty, recommendedVersionName, recommendedTags를 작성한다." So we should include them only if we can infer. For play time we cannot infer, so we omit (i.e., not include).
However the JSON structure expects those keys; but we can still include them with null? The spec: "플레이 인원/팀 수/예상 플레이 시간은 제목, 내부 설명, 이미지에서 근거가 있을 때만 숫자로 작성한다. 확실하지 않으면 null 또는 생략한다." So we can set null. Let's include null for playTime, difficulty, versionName. For tags we can infer some tags: survival, melee, limited resources, 4-player.
We'll provide tags like ["생존", "밀리", "4인", "자원 제한", "유즈맵"] maybe up to 8. But we need to ensure they are Korean. We also need recommendedDifficulty: unknown; we can set null. recommendedVersionName: unknown; null. Now content: Must be Korean review 900-1100 characters (including spaces). Then a blank line, then
| URL | https://star.huzy.net/map/cmt9jczys0f5g63ohh2037j86 |
|---|---|
| 파일명 | Into_the_Darkness.scm |
| 업로더 | HUZY |
| 맵 타입 | 밀리 맵 더 보기 |
| 파일 크기 | 88.88 KB |
| 등록일시 | 2026-08-26 12:30:12 |
| 조회수 | 0 |
| 좋아요 | 0 |
| 평점 | (0) |
로그인 하시고 댓글을 남겨 볼까요?