How to Set Up a Metin2 Private Server in 2026: Complete Admin Checklist

Running a Metin2 private server is more accessible than ever in 2026, but the learning curve for first-time admins is still steep. The game's server-side configuration is split across a dozen different file formats, and most tutorials online are outdated, written for server files from 2014–2018 that behave differently from modern releases.

This guide focuses on the admin configuration layer — the files you will be editing constantly once your server is running. It assumes you have already installed your server files and can start the game server process.

The Core Configuration Files Every Admin Must Know

Before you change anything, understand what each file controls. These are the files you will touch every week:

File	Controls	Format
`item_proto.txt`	Every item in the game — stats, requirements, bonuses, prices	Tab-separated TXT or MySQL
`mob_proto.txt`	Every monster, NPC, boss — level, HP, damage, drops, AI	Tab-separated TXT or MySQL
`mob_drop_item.txt`	What each mob drops and at what probability	Group-block TXT
`common_drop_item.txt`	Shared drops for all mobs in a level range	Group-block TXT
`special_item_group.txt`	Contents of chests and boxes	Group-block TXT
`regen.txt / boss.txt`	Where mobs spawn, how many, how often	Space-separated TXT per map
`refine_proto`	Upgrade chains — materials, costs, success rates	MySQL table

Step 1: Understand Your Proto Format Before Editing

The first decision is whether your server uses TXT-based protos or MySQL-based protos. Modern server packages (2020+) typically use MySQL. Older packages use TXT files. You can usually tell by checking whether item_proto.txt exists in your server's locale folder, or whether the data is only in your database.

If you need to move between formats — for example, you downloaded an item pack in TXT format but your server uses MySQL — use the TXT to SQL Converter to convert without manually reformatting.

Never edit the binary item_proto.bin or mob_proto.bin client files manually. These are encrypted with TEA and compressed with LZO. Edit the server-side TXT or MySQL data, then use your server's patcher to regenerate the client files.

Step 2: Set Up Your Items

item_proto is the most edited file on any server. Whether you are adjusting existing item stats, adding custom equipment, or importing an item pack from the community, you will be working with it constantly.

Key things to configure for each item:

Level requirement (limittype0 = 1, limitvalue0 = your level)
Equipment slot (wearflag — 16 for weapon, 1 for body armor, etc.)
Base stats (value0/value1 for weapon damage or armor defense)
Passive bonuses (applytype0–2 and applyvalue0–2)
Upgrade chain (refined_vnum pointing to the +1 version)

Use the Item Proto Editor for a spreadsheet interface with dropdown menus for all numeric IDs — no memorisation required. See the full item_proto column reference for what every field does.

Step 3: Configure Your Mobs

mob_proto controls everything about how monsters feel to fight. For a fresh server, the most important values to tune are:

Level — must match the zone the mob is in
max_hp — how long fights take
damage_min / damage_max — how dangerous the mob is
exp — levelling speed
gold_min / gold_max — economy balance
aggressive_sight — aggro range (key for dungeon design)

Use the Mob Proto Editor to edit with a searchable table and smart dropdowns. Read the mob_proto complete reference for boss abilities, resistance values, and immune flags.

Step 4: Balance Your Drop Rates — Carefully

Drop rate configuration is where most new admins make critical mistakes that take months to notice. The PCT values in mob_drop_item.txt are not percentages — they are raw numbers divided by 1,000,000. A value of 100 means 0.01%, not 100%.

Additionally, players farming mobs more than 15 levels below their level will get near-zero drops regardless of your PCT values. Always test drop rates with a character at the mob's actual level.

Use the Drop Table Calculator to verify your drop rates before going live. Paste a group block from your mob_drop_item.txt, set the player level, and instantly see the real probability for every item. Read the full drop rate formula guide to understand the complete picture.

Step 5: Common Beginner Mistakes to Avoid

Editing files without backups — Always keep versioned copies of item_proto, mob_proto, and all drop files before making changes
Assuming PCT = percentage — Read the drop rate guide before setting any drop values
Duplicate VNUMs — Adding a new item or mob with a VNUM that already exists will cause silent overrides or server crashes; always check for conflicts first
Wrong subtype for the item type — A sword with type = 1, subtype = 4 is a Bell (Shaman weapon), not a sword. The subtype IDs are type-specific.
Not updating the client files — Editing server-side proto does not automatically update what the game client sees; you need to regenerate the client binary files
Forgetting the level-difference drop penalty — High-level players will not benefit from drop rate improvements on low-level mobs

Your Admin Tools Workflow

Once your server is running, this is the workflow for any content change:

Plan — Decide what you are changing and why (item balance, new content, economy fix)
Edit — Use the appropriate editor tool to make changes with validation
Verify — Use the Drop Table Calculator for drop changes, check for duplicate VNUMs for item/mob changes
Export — Export as TXT or SQL depending on your server format
Test — Test on a local or staging copy before pushing to production
Deploy — Import to your live server, regenerate client files if needed, reload/restart

The Metin2 Tools hub has all five tools you need for steps 2–4: the Item Proto Editor, Mob Proto Editor, Drop Table Calculator, Mob Drop Editor, and TXT to SQL Converter — all free, all browser-based, no account needed.

How to Set Up a Metin2 Private Server in 2026: Complete Admin Checklist