얼음 머니 --clan-HeroesMa§ter (IceMoney --clan-HeroesMa§ter)

We need to produce a JSON object with content (Korean review 900-1100 chars, then blank line, then

same content, total 1800-3000 chars). Also recommendedMapType etc. We have map data: site title: IceMoney --clan-HeroesMa§ter (looks garbled due to §). Original file name: [ICE]$$MONEY$$.scx. Internal map title same as site title. Internal description: MINERALS :*******.GAS :.SIZE :256x256.TYPE :ICE.CREATOR : Predateur_Fenix & ZeratulLeSombre.

Current genre/classification: MELEE (밀리). Players: 8. Team count: -. Expected play time: -. Difficulty: -. Version: -. Tags: -. Map hash: etc. Tile size 256x256 (standard). Tileset: 플랫폼 (platform). Encoding cp1252. We need to decide recommendedMapType. The map seems like a melee map?

Title IceMoney suggests maybe a money map (resource abundant) but internal description says minerals ******* (many) and gas . Size 256x256, type ICE, creator names. Likely a melee map focused on money (resources). Could be a UMS? But classification currently MELEE. The description doesn't indicate any special triggers or game mode; just resources.

So likely it's a standard melee map (maybe a custom melee map). So recommendedMapType stays MELEE. If uncertain, we can keep same as current. But we need to check if any indication of UMS: no mention of triggers, no special gameplay. So MELEE. Thus mapTypeReason: "내부 설명에 특정한 트리거나 게임 모드가 없으며, 표준 자원 배치와 크기로 보아 일반적인 밀리 맵으로 판단".

Now recommendedTitle: Need to produce natural Korean title (English Title) format. The site title has garbled characters: IceMoney --clan-HeroesMa§ter. The § is likely an encoding artifact. The internal title same. Likely intended: IceMoney --clan-HeroesMaster? Or IceMoney --clan-HeroesMaster? The garbled § maybe from a special character.

We should produce a cleaned title: IceMoney --clan-HeroesMaster (IceMoney --clan-HeroesMaster). But we need Korean and English. The title appears already English with some Korean? Actually "IceMoney" is English, "--clan-HeroesMa§ter" maybe "HeroesMaster". So recommendedTitle: IceMoney --clan-HeroesMaster (IceMoney --clan-HeroesMaster). That repeats same?

Usually format: Korean title (English Title). But if original is English, we can put Korean translation then English in parentheses. The instruction: "원본 제목이 영어만 있으면 자연스러운 한글 표기를 앞에 쓰고 원문 영어 제목을 괄호 안에 보존한다." So we need a Korean version before the English title in parentheses. So we need to create a Korean translation of IceMoney --clan-HeroesMaster.

Could be "아이스머니 --클랜-히어로즈마스터". That seems natural. Then recommendedTitle: "아이스머니 --클랜-히어로즈마スター (IceMoney --clan-HeroesMaster)". Actually Korean: 아이스머니 --클랜-히어로즈마스터. Parentheses English original. Thus titleReason: "사이트 표시 제목에 특수문자 §가 인코딩 오류로 보이므로 제거하고, 영어만 있는 원제에 자연스러운 한글 표기를 붙임". Now recommendedPlayerCount: we have players: 8.

Team count: - (likely free-for-all). So recommendedTeamCount: 1 (if solo) or maybe each player is individual, team count 1 per player? In JSON schema, recommendedTeamCount likely number of teams? For melee map with 8 players, could be 8 teams of 1 each, but they said if unclear use null. However we have player count 8, team count unknown.

Could set recommendedTeamCount: 1 (meaning each player is own team). But maybe better to set null. But they said "플레이 인원/팀 수/예상 플레이 시간은 제목, 내부 설명, 이미지에서 근거가 있을 때만 숫자로 작성한다. 확실하지 않으면 null 또는 생략한다." We have player count given as 8 (from data). So we can set recommendedPlayerCount: 8. Team count: not given, so null or omit. We'll include null.

Play time: not given, so null. Difficulty: not given, so null or maybe "보통"? But we shouldn't guess. So null. Version: not given, so null. Tags: not given, we can infer: ["ICE", "자원맵", "밀리"] maybe. But we should not fabricate?

The instruction: "제공 데이터에 없는 제작자, 정확한 트리거, 승리 조건, 스토리, 밸런스 수치는 지어내지 않는다." Tags are not explicitly given but we can infer from map title and type? Might be considered fabrication? Safer to leave empty array?

But they said "비어 있는 맵 상세 메타데이터를 채울 수 있으면 recommendedPlayerCount, recommendedTeamCount, recommendedPlayTime, recommendedDifficulty, recommendedVersionName, recommendedTags를 작성한다." So we can fill if we can infer. Tags: we can add ["ICE", "밀리", "자원맵"] maybe based on internal description: TYPE: ICE. That's not fabrication, it's from data.

So we can include "ICE". Also "밀리" from classification. Also maybe "자원맵" from mineral/gas abundance. That's somewhat inference but maybe okay. But we need to avoid fabricating. I'd include tags derived from data: "ICE", "밀리". Also maybe "플랫폼" tileset. But tags should be search-friendly. We'll include ["ICE", "밀리", "플랫폼"].

Now recommendedVersionName: not given, could be null. We'll set null. Now detailCategory: more specific subcategory. For a melee map, detailCategory could be "밀리" (already classification) or maybe "자원맵".

But allowed subcategories list includes: 컴까기, 디펜스, 타워 디펜스, 랜덤 디펜스, RPG, 키우기, 피하기, 탈출, 서바이벌, 아레나, 미니게임, 퍼즐, 캠페인, 시나리오, 디플로메시, 블러드, 입구막기, 넥서스 부수기, 강화, 운빨, 밀리, 팀 밀리. So we can use "밀리". That's same as classification but allowed. Or maybe "자원맵" not in list. So we set detailCategory: "밀리".

Provide detailCategoryReason: "내부 설명에 특수한 게임 모드 없이 표준 자원 배치로 보아 일반 밀리 맵으로 판단". Now metadataReason: we need to explain why we recommended certain metadata. We'll write: "플레이 인원은 제공 데이터에서 8명으로 확인하여 사용했으며, 나머지 필드는 제공되지 않아 null로 처리하였고, 타일셋과 타일 크기 및 TYPE: ICE에서 태그를 유도함". Now content: need Korean review 900-1100 characters (including spaces). Then blank line, then