Unknown Server

We need to translate the human-readable text between tags, preserving HTML tags. The given text appears plain (no HTML tags shown). It says "sVanilla Survival is a ...". We need to translate to Korean, preserving proper nouns etc. Keep Minecraft terms untranslated: mob, mobs, loot, spawn, spawner, build, builds, biome, redstone, nether, end, creeper, enderman, mod, mods, server, skin, vanilla, survival, creative, hardcore. Also proper nouns: sVanilla (maybe treat as proper noun, keep as-is). Also version numbers (1.20+) none present. Need to translate everything else into Korean, natural fluent.

We must not add or remove meaning. Keep tags: there are none. So just translate the paragraph.

Let's translate.

Original:

"sVanilla Survival is a semi-vanilla Minecraft server that brings back the classic survival experience with a modern twist. Established in 2019, this server features a never-resetting map and a thriving trading-based economy where players can build lasting legacies. With support for both Java and Bedrock crossplay, the server welcomes players across all platforms. Combat is kept traditional with no crystal PvP - battles are fought the old-fashioned way using swords, axes, and bows, though an experimental mechanic allows fireworks launched from crossbows to explode like anchors. The server embraces a semi-anarchy philosophy with no land claims and griefing allowed, creating an authentic survival challenge within an expansive world border. Currently supporting 25-42 players, sVanilla maintains a strict no-hacks policy while allowing total freedom in how you play. Whether you're a builder seeking unlimited creative freedom, a trader looking to dominate the economy, or a warrior ready for intense PvP battles, sVanilla Survival offers an old-school Minecraft experience that rewards skill, strategy, and community engagement."

We need to keep certain terms untranslated: "semi-vanilla" includes "vanilla" which is a Minecraft term, keep as is? The rule: Keep Minecraft game terms in English, untranslated: mob, mobs, loot, spawn, spawner, build, builds, biome, redstone, nether, end, creeper, enderman, mod, mods, server, skin, vanilla, survival, creative, hardcore. So "vanilla", "survival", "creative", "hardcore" must stay English. Also "server" stays English. "semi-vanilla" contains "vanilla" but the prefix semi-? Likely we keep "semi-vanilla" as is? The term includes vanilla which is untranslated; we could keep "semi-vanilla" unchanged. Probably keep as is.

Also "Java" and "Bedrock" are proper nouns (platform names) keep as is. "PvP" is abbreviation but not in list; but it's a term; we can keep as is? Might translate? Usually keep as is. Safer to keep as is.

"crossplay" maybe not in list; could translate? Probably keep as is? Not sure. The instruction: Keep Minecraft game terms in English, untranslated: list. Others can be translated. So "crossplay" is not Minecraft-specific; we can translate to Korean: "크로스플레이". However "Java" and "Bedrock" are proper nouns, keep.

"anchors" maybe not in list; translate? Could keep as is? It's a generic word; translate to Korean: "닻". But "anchors" as metaphor; maybe translate.

We need to keep meaning. Let's translate everything except the listed terms and proper nouns.

Proper nouns: sVanilla, Java, Bedrock, maybe "sVanilla Survival" as a name? Keep sVanilla Survival as is? The rule: Keep proper nouns, usernames, brand names, version numbers (1.20+), and code as-is. So "sVanilla Survival" is a brand name (server name). Keep as is. Also "Java" and "Bedrock". Also maybe "sVanilla" alone.

Thus we keep "sVanilla Survival" unchanged. Also "sVanilla" alone unchanged.

Now translate rest.

Let's produce Korean translation.

We'll go sentence by sentence.

1. "sVanilla Survival is a semi-vanilla Minecraft server that brings back the classic survival experience with a modern twist."

We keep "sVanilla Survival" and "semi-vanilla" (contains vanilla) and "Minecraft" (maybe not in list but it's the game name; could translate? Probably keep as is? It's a proper noun; keep as is). "server" is in list -> keep English. "survival" in list -> keep English. So we need to translate the rest: "is a ... that brings back the classic ... experience with a modern twist."

Korean: "sVanilla Survival은 클래식한 서바이벌 경험을 현대적인 감각으로 되살려 주는 세미-바닐라 마인크래프트 서버입니다."

But we need to keep "semi-vanilla" unchanged? It's "semi-vanilla". We'll keep as is. "Minecraft" keep. "server" keep. "survival" keep.

Thus: "sVanilla Survival은 세미-바닐라 마인크래프트 서버로, 현대적인 감각으로 클래식한 서바이벌 경험을 되살려 줍니다."

Make sure to keep terms: "세미-바닐라" contains hyphen; we keep "세미-바닐라"? The term "semi-vanilla" we keep as is but we could keep English "semi-vanilla". The rule: Keep Minecraft game terms in English, untranslated: list includes "vanilla". It didn't say to keep "semi-vanilla". But likely we keep the term as is because it's a compound with vanilla. Safer to keep "semi-vanilla" unchanged. So we should not translate "semi-vanilla" to Korean. Keep "semi-vanilla". So we need to keep the exact string "semi-vanilla". So we cannot change it to Korean. So we must keep "semi-vanilla". So the phrase: "sVanilla Survival은 semi-vanilla 마인크래프트 서버로, 현대적인 감각으로 클래식한 서바이벌 경험을 되살려 줍니다."

But "마인크래프트" is Korean translation of Minecraft; but Minecraft is a proper noun; we should keep as is? The rule: Keep proper nouns, usernames, brand names, version numbers (1.20+), and code as-is. Minecraft is a brand name/proper noun, so keep as "Minecraft". So we should not translate to Korean. So keep "Minecraft". So we need to keep "Minecraft" unchanged.

Thus: "sVanilla Survival은 semi-vanilla Minecraft 서버로, 현대적인 감각으로 클래식한 서바이벌 경험을 되살려 줍니다."

Check: "서버" is Korean word; but "server" is in list to keep untranslated. So we must keep "server" not translate. So we need to keep "server". So we cannot translate to Korean "서버". Must keep "server". So phrase: "... semi-vanilla Minecraft server로, ..." but we need Korean particles attached? Usually we keep the English word and attach Korean particles after it, like "server는". That's acceptable. So we keep "server" as is.

Thus: "sVanilla Survival은 semi-vanilla Minecraft server로, 현대적인 감각으로 클래식한 survival 경험을 되살려 줍니다."

But "survival" is in list, keep English. So we keep "survival". Also "classic" translate? Not in list, translate to Korean "클래식한". Could also keep "classic" but better translate.

Thus final sentence: "sVanilla Survival은 semi-vanilla Minecraft server로, 현대적인 감각으로 클래식한 survival 경험을 되살려 줍니다."

Check: we kept "sVanilla Survival", "semi-vanilla", "Minecraft", "server", "survival". Good.

2. "Established in 2019, this server features a never-resetting map and a thriving trading-based economy where players can build lasting legacies."

We need to keep "2019" as is (numbers). "this server" -> keep "server" untranslated. So "this server" maybe "this server". We'll keep "server". So translate: "2019년에 설립된 이 server는 jamás 리셋되지 않는 지도와 활발한 무역 기반 경제를 특징으로 하며, 여기서 플레이어는 지속 가능한 유산을 건설할 수 있습니다." Need to keep "map"? Not in list; translate to Korean "지도". "economy" translate "경제". "players" translate "플레이어". "build" is in list -> keep English "build". "lasting legacies" translate "지속 가능한 유산". "legacy" maybe "유산". Keep meaning.

But we need to keep "build" unchanged. So we can say "건설할 수 있습니다" but that uses Korean verb; we need to keep "build" as is? The rule: Keep Minecraft game terms in English, untranslated: build, builds,... So we must keep the word "build" exactly. So we cannot translate "build" to Korean. We need to keep "build". So we need to embed the English word "build" in the sentence. For example: "플레이어는 build를 통해 지속 가능한 유산을 만들 수 있습니다." But "만들다" is Korean verb; we keep "build" as noun? Could say "플레이어는 build하여 지속 가능한 유산을 만들 수 있습니다." But "build" as verb? Might be awkward. Better to keep "build" as is and treat as verb: "플레이어는 build해서 지속 가능한 유산을 만들 수 있습니다." However that mixes English verb with Korean particles. Usually we keep the term and add Korean particles: "build를". So "플레이어는 build를 통해 지속 가능한 유산을 만들 수 있습니다."

Thus we need to keep "build". Also "builds" appears elsewhere? Not here.

Now "never-resetting map": keep "never-resetting"? Not in list; translate maybe "절대 리셋되지 않는". Keep "map" as "지도". So "절대 리셋되지 않는 지도".

"thriving trading-based economy": translate "번성하는 무역 기반 경제". "thriving" -> "번성하는". "trading-based" -> "무역 기반". "economy" keep? Not in list; translate "경제". So "번성하는 무역 기반 경제".

"where players can build lasting legacies": "where" -> "where". Keep "players" -> "플레이어". "can" -> "할 수 있다". "build" keep English. "lasting legacies" -> "지속 가능한 유산". So "플레이어는 build를 통해 지속 가능한 유산을 만들 수 있는".

Now full sentence: "2019년에 설립된 이 server는 절대 리셋되지 않는 지도와 번성하는 무역 기반 경제를 특징으로 하며, 플레이어는 build를 통해 지속 가능한 유산을 만들 수 있습니다."

Check: we kept "server". Good.

3. "With support for both Java and Bedrock crossplay, the server welcomes players across all platforms."

We need to keep "Java", "Bedrock". "crossplay" not in list; translate? Could keep as is? Might translate to "크로스플레이". But we need to keep meaning. We'll translate to Korean: "크로스플레이". "the server" -> keep "server". "welcomes" translate "환영합니다". "players" -> "플레이어". "across all platforms" -> "모든 플랫폼에서". So: "Java와 Bedrock 크로스플레이를 지원하는 이 server는 모든 플랫폼의 플레이어를 환영합니다."

Check: we kept "Java", "Bedrock", "server". Good.

4. "Combat is kept traditional with no crystal PvP - battles are fought the old-fashioned way using swords, axes, and bows, though an experimental mechanic allows fireworks launched from crossbows to explode like anchors."

We need to keep "PvP"? Not in list; but it's a term; maybe keep as is. Could translate "PvP" as "플레이어 대 플레이어" but better keep as is. We'll keep "PvP". "Combat" translate "전투". "is kept traditional" -> "전통적인 방식으로 유지됩니다". "with no crystal PvP" -> "크리스탈 PvP 없이". "battles are fought the old-fashioned way using swords, axes, and bows" -> "전투는 전통적인 방식으로 검, 도끼, 활을 사용하여 진행됩니다". "though an experimental mechanic allows fireworks launched from crossbows to explode like anchors." -> "하지만 실험적인 메커니즘으로, 크로스보우에서 발사된 불꽃놀이는 닻처럼 폭발할 수 있습니다."

We need to keep "fireworks"? Not in list; translate "불꽃놀이". "crossbows" -> "크로스보우". "anchors" -> "닻". Keep meaning.

Now ensure we keep any Minecraft terms: "swords", "axes", "bows" not in list; translate. "mechanic" not in list; translate.

Thus Korean: "전투는 전통적인 방식으로 유지되며, 크리스탈 PvP 없이 검, 도끼, 활을 사용하여 싸움이 이루어집니다. 다만 실험적인 메커니즘으로, 크로스보우에서 발사된 불꽃놀이는 닻처럼 폭발할 수 있습니다."

Check: we kept "PvP". Good.

5. "The server embraces a semi-anarchy philosophy with no land claims and griefing allowed, creating an authentic survival challenge within an expansive world border."

We need to keep "server". "semi-anarchy" not in list; translate? Could keep as is? Might translate "반무정부" but better keep as "semi-anarchy"? The rule only mentions Minecraft terms; we can translate. We'll translate to Korean: "반무정부 철학". But "semi-anarchy" maybe "반무정부". We'll translate.

"no land claims" -> "땅 주장 없음" but natural Korean: "땅 주장 금지 없음" maybe "땅 주장이 허용되지 않음". We'll say "땅 주장이 없고".

"griefing allowed" -> "그리핑이 허용됨". "griefing" not in list; translate maybe "그리핑". Keep as is? Could keep English but better translate to Korean "해충 행위"? Usually "그리핑" is used. We'll keep as English? Not sure. Safer to keep as English? Not in list, we can translate. Let's translate "그리핑" as "괴롭힘" but that's not accurate. In Minecraft community, "그리핑" is used as loanword. We'll keep as English "griefing"? The rule: keep Minecraft game terms in English untranslated; griefing is not a Minecraft term? It's a behavior. Could translate. I'll keep as English "griefing" to avoid confusion. But we can also keep as is. Let's keep as English "griefing" because it's a known term. However we need to decide. I'll keep as English "griefing" to avoid altering meaning.

"creating an authentic survival challenge within an expansive world border." -> "확장된 세계 경계 내에서 autént한 서바이벌 도전을 만듭니다." Need to keep "survival". So "authentic survival challenge" -> "authentic한 서바이벌 도전". "authentic" translate "진정한". So "진정한 서바이벌 도전". "within an expansive world border" -> "넓은 세계 경계 내에서". So phrase: "이는 넓은 세계 경계 내에서 진정한 서바이벌 도전을 만든다."

Now full sentence: "이 server는 반무정부 철학을 받아들여, 땅 주장이 없고 grieifing이 허용되며, 넓은 세계 경계 내에서 진정한 서바이벌 도전을 만든다."

Check: we kept "server". Also we kept "survival". Good.

6. "Currently supporting 25-42 players, sVanilla maintains a strict no-hacks policy while allowing total freedom in how you play."

We need to keep "sVanilla". "players" translate? Not in list; translate "플레이어". "no-hacks policy" -> "해킹 금지 정책". "strict" -> "엄격한". "while allowing total freedom in how you play" -> "당신이 플레이하는 방식에 대한 완전한 자유를 허용하면서". So: "현재 25-42명의 플레이어를 지원하는 이 sVanilla은 엄격한 해킹 금지 정책을 유지하면서, 당신이 플레이하는 방식에 대한 완전한 자유를 허용합니다."

Check: we kept "sVanilla". Good.

7. "Whether you're a builder seeking unlimited creative freedom, a trader looking to dominate the economy, or a warrior ready for intense PvP battles, sVanilla Survival offers an old-school Minecraft experience that rewards skill, strategy, and community engagement."

We need to keep "builder"? Not in list; translate "건설자". "unlimited creative freedom" -> "무제한의 창의적 자유". "creative" is in list? Actually "creative" is in list (Minecraft game term). So we must keep "creative" untranslated. So "무제한의 creative 자유". But we need to keep "creative" as is. So phrase: "무제한의 creative 자유를 추구하는 builder". However "builder" not in list; translate "건설자". So "건설자는 무제한의 creative 자유를 추구하는". Hmm.

"trader" not in list; translate "거래상". "looking to dominate the economy" -> "경제를 지배하려는". "economy" not in list; translate "경제". So "거래상은 경제를 지배하려는".

"warrior" -> "전사". "ready for intense PvP battles" -> "격렬한 PvP 전투에 대비한". Keep "PvP". "intense" translate "격렬한". So "전사는 격렬한 PvP 전투에 대비한".

"sVanilla Survival" keep as is. "offers" -> "제공합니다". "an old-school Minecraft experience" -> "오래된 스타일의 Minecraft 경험". "old-school" translate "오래된