실행 확인과 플레이 팁
직접 실행한 결과와 스포일러 없는 팁을 남겨 다른 이용자를 도와주세요.
u.b_testmap(hard).scx 다운로드 · 5인용
이 리뷰는 생성형 AI가 맵 파일 정보와 설명을 바탕으로 작성한 참고용 분석입니다.
We need to produce JSON with content containing Korean review ~900-1100 characters, then a blank line, then
same content (no extra heading). Total characters including both Korean and English (including blank line?) 1800-3000 characters. Must not include any markdown or extra text. Must output only JSON object.
We have map data: site title UBClan Test Map(Hard), file name u.b_testmap(hard).scx, internal title same, description: "UBClan Test Map(Hard)Craet by :: `U.b]_Luxury". Likely a test map, unknown genre but classified as UMS. We need to infer map type: It's a test map, likely a melee or something? Since it's a test map maybe it's a melee test?
Without details, we cannot assume specifics. We'll keep recommendedMapType same as current: UMS. But we need mapTypeReason: based on classification and lack of specific genre indicators. DetailCategory: need specific subcategory; we have no info, but we can guess maybe it's a test map for melee? Could be "테스트" but not in list.
Since we don't know, we can set detailCategory same as recommendedMapType? But detailCategory must be Korean subcategory like 컴까기, 디펜스 etc. Since we have no evidence, we should set detailCategory to same as recommendedMapType? Not allowed; must be from list. Could choose "기타" but not in list.
The allowed detailCategory candidates list includes many but not "기타". We could choose something generic like "미니게임" if uncertain? But better to be safe: If uncertain, we can set detailCategory same as recommendedMapType? The instruction: detailCategory is more specific subcategory in Korean. If uncertain, we could set it to same as recommendedMapType?
Not exactly; they said "확실하지 않으면 현재 장르/분류와 같은 값을 사용한다." That refers to recommendedMapType: if uncertain, use current genre/classification. For detailCategory, they didn't explicitly say, but we can infer similar: if uncertain, use same as recommendedMapType? But detailCategory expects Korean subcategory; we could maybe set it to "UMS" but that's not Korean.
Better to set detailCategory to "기타" but not allowed. Perhaps we can set detailCategory to "미니게임" as a generic placeholder? However we need to provide detailCategoryReason. Since we have no info, we can say "제목 및 설명에서 구체적인 장르 유추 불가, 테스트 맵으로 간주하여 미니게임 유형으로 추정". That might be acceptable.
But we need to ensure recommendedMapType is one of allowed enums: UMS is allowed. Good. We need recommendedTitle: site title is "UBClan Test Map(Hard)". It's already Korean? Actually it's English with Korean? It's English phrase with parentheses. There's no Korean.
According to rules: If site title is not in format "한글 제목 (English Title)", we must write recommendedTitle in that format. Original title is English only, so we need to add a natural Korean translation before, preserving English in parentheses. So recommendedTitle should be something like "UBClan 테스트 맵 (하드) (UBClan Test Map(Hard))"?
But format: "한글 제목 (English Title)". So Korean title then space then English title in parentheses. The English title should be the original? Probably we keep original English title inside parentheses. So Korean title: "UBClan 테스트 맵 (하드)". Then English title: "UBClan Test Map(Hard)". So recommendedTitle = "UBClan 테스트 맵 (하드) (UBClan Test Map(Hard))".
TitleReason: site title lacked Korean, added natural Korean translation. We also need recommendedPlayerCount: provided as 5. So set 5. Team count: not provided ("-") so null or omit? The spec: if uncertain, null or omit. We'll omit recommendedTeamCount? The JSON expects the key; we can set null. Probably better to set null.
recommendedPlayTime: not provided, so null or omit. We'll set null. recommendedDifficulty: not provided, null or maybe we can infer "보통"? But we shouldn't guess. So null. recommendedVersionName: not provided, null. recommendedTags: we need array of Korean tags up to 8. We can include ["UMS", "테스트맵"] but tags should be Korean. So ["테스트맵", "UMS"] maybe.
We'll include ["테스트맵", "UMS"]. metadataReason: we can note that we used provided player count, title etc. detailCategory: we set as "미니게임". detailCategoryReason: based on lack of specific genre indicators, test map considered a mini-game type. Now content: Need Korean review 900-1100 characters (including spaces). Then blank line, then
| URL | https://star.huzy.net/map/cmtf2bjv0002i57ohpzz9gsc2 |
|---|---|
| 파일명 | u.b_testmap(hard).scx |
| 업로더 | HUZY |
| 맵 타입 | 유즈맵 맵 더 보기 |
| 파일 크기 | 76.73 KB |
| 등록일시 | 2026-08-30 09:19:48 |
| 조회수 | 0 |
| 좋아요 | 0 |
| 평점 | (0) |
로그인 하시고 댓글을 남겨 볼까요?