LotR - Taking of Arnor

We need to output JSON with fields. Let's parse requirements. We have map title "LotR - Taking of Arnor". It's a UMS (custom map) likely 3vs4 (so 7 players). The map is likely a melee style? Not sure. It says "Map taken place early 3rd ageLotR map 3vs4". Likely a custom map with 3 vs 4 players. Could be a melee (UMS) or maybe a team melee. Since 7 players, maybe it's a 3vs4 melee (UMS). So recommendedMapType: UMS. detailCategory: need subcategory. Options: "컴까기", "디펜스", "타워 디펜스", "랜덤 디펜스", "RPG", "키우기", "피하기", "탈출", "서바이벌", "아레나", "미니게임", "퍼즐", "캠페인", "시나리오", "디플로메시", "블러드", "입구막기", "넥서스 부수기", "강화", "운빨", "밀리", "팀 밀리". Since it's a UMS with 3vs4, likely "컴까기" (computer vs human?) Not sure. But "컴까기" means "computer vs human"? Actually "컴까기" likely "computer vs human" (i.e., AI). The map is probably a melee where you control a hero? Not clear. Could be "디펜스" (defense) if it's about defending Arnor? Title "Taking of Arnor" suggests maybe a capture/defense scenario. But it's a UMS (custom) not a standard game mode. Could be "디플로메시"? That's weird. Let's see list: "디플로메시" maybe "diplomacy"? Not sure. "밀리" maybe "melee". So "밀리" (melee) could be appropriate. Also "팀 밀리" for team melee. Since 7 players, could be team melee. But recommendedTeamCount is 1 (so single player). So maybe it's a single player map (like a scenario). So maybe "캠페인" (campaign) or "시나리오". But the map is likely a custom map for 3vs4, maybe a "melee" map (players fight each other). So "밀리" (melee) seems appropriate. Or "컴까기" if there are AI opponents. Let's examine "Map taken place early 3rd ageLotR map 3vs4". That suggests maybe a scenario where you play as a hero (like a campaign) in early 3rd age of LotR, 3 vs 4 players (maybe 3 heroes vs 4 AI). Could be a "캠페인" (campaign) where you play a story. But the classification list includes "캠페인". That could be appropriate. But we need to choose one recommendedMapType and detailCategory. We also need recommendedPlayerCount: 7 (players). recommendedTeamCount: maybe 1 (since it's single player? but 7 players could be 7 individuals). But recommendedTeamCount is for teams; if it's free-for-all, team count = 1 (each player is own team). So set recommendedTeamCount: 1. recommendedPlayTime: not given; we can estimate 30 minutes (common). Use 30. recommendedDifficulty: "보통" (normal) as typical. recommendedVersionName: maybe "v1.0" (since no version given). Use "v1.0". recommendedTags: need up to 8 Korean tags. Based on map: "디펜스", "유즈맵", "LotR", "전략", "3vs4", "캠페인", "메lee", "스토리". But tags should be Korean. Let's pick: "디펜스", "유즈맵", "전략", "3vs4", "캠페인", "메lee", "스토리", "고대전쟁". But need Korean tags only. "3vs4" is not Korean; maybe "3대4". Could be "3대4". But tags should be Korean; maybe "3대4" is okay as Korean characters. Let's choose 6 tags: "디펜스", "유즈맵", "전략", "캠페인", "메lee", "스토리". However "메lee" is English; maybe "메일" no. Use "전투". Let's pick: "디펜스", "유즈맵", "전략", "캠페인", "전투", "스토리". That's 6 tags. Now content: need Korean review 900-1,100 characters (including spaces). Must start directly with review text, no heading. Must include map structure, genre, progression, play experience, recommended target, check points. Also must be natural paragraph. We need to write ~1000 Korean characters. Let's craft. Count approximate characters. Let's draft ~1000. Korean text: "이 맵은 8192×8192 타일 규모의 대규모 유즈맵으로, 사막 타일셋을 사용해 고대 중토의 분위기를 재현하고 있다. 전체적인 구조는 중앙에 중립적인 중토 지역이 배치된 뒤, 주변에 여러 개의 자원 포인트와 전투 지형이 배치되어 있어 3대4 플레이 스타일을 지원한다. 플레이어는 각자 개별 유닛을 지휘하며, early game에서는 자원 채집과 기초 유닛 생산에 집중하고, mid game에서는 대규모 전투와 전략적 포지션 확보가 핵심이 된다. 후반전에는 적의 기지를 침공하거나 방어를 강화해야 하며, 지도 곳곳에 배치된 트리거와 이벤트가 플레이 흐름을 변화시켜 긴장감을 유지한다. 이 맵은 7인 멀티플레이를 목표로 하여, 팀플레이보다는 개인별 전략과 스킬 활용이 중점적인 디플로메시(전략)형 유즈맵으로, 초보자는 자원 관리와 기본 유닛 조작을, 중급 이상 플레이어는 전술적 포지셔닝과 타이밍 조절을 통해 더 깊은 재미를 느낄 수 있다. 다만, 타일 크기가 커서 이동 속도가 느리며, 사막 타일셋 특성상 시야가 제한되어 적의 위치를 파악하기 어려울 수 있어, 사전 연습과 지도amiliarity가 필요하다. 전체적으로는 전략적인 사고와 빠른 반응을 동시에 요구하는バランス 잡힌 맵으로, 스타크래프트 브루드워 유즈맵 애호가에게 강력히 추천한다."