Metin2 Boss Timer Planning Guide 2026: Discord Pins, Timezones & Skip Calls

Every officer has lived this ping: “Azrael in four minutes” dropped in a channel nobody watches, half the roster in another timezone, and three people landing without poison resist. That is not a spawn problem. That is a Metin2 boss timer planning gap — and in 2026 it still burns more nights than a missed Metin stone.

This playbook is how officers and players actually run world bosses and Metin stones: Discord pins, one shared timezone, a rotation that names who tags, potion and resist prep before the window, and a clear rule for when to skip a spawn. Pair war weeks with our guild war preparation guide. For stack math, keep the consumables yang budget open. I wrote it in the same voice I use in officer chat: short sentences, names on a list, no hero story after a wipe we should have skipped.

Players are part of the system, not just the ping list. If you are on tag, you read the pin before you farm. If you are on farm rotation, you stay off the all-call unless the scout writes go. If you are new, you ask for the channel once, then you stop asking “when is the boss” in general. That is how a roster stops wasting nights.

Why Metin2 boss timer planning beats last-minute pings

World bosses and Metin stones do not reward the loudest Discord message. They reward the guild that already knows the next window, who is on tag, and whether tonight is even worth the ride. Last-minute pings create three failures at once: late arrivals, wrong resist, and a scramble that looks like attendance when it is really panic. I have watched a +8 roster lose a clean spawn because three people converted the clock wrong and two more showed with fire resist on a poison map. The boss did not beat them. The board did.

Planning is not a spreadsheet hobby. It is an officer habit. You pin one board. You name one timezone. You publish who tags. You tell people what to bring. You also tell people when to stay on farm. Guilds that skip that last line burn out their core on every grey spawn and then show up empty for the one that mattered.

Treat timers like war hour, just shorter. The fight lasts minutes. The prep lasts the afternoon. If your roster only starts thinking when the boss emote hits chat, you are already late by one potion crate and one timezone conversion.

Last-minute culture trains people to ignore you. If nine pings a night are “NOW NOW NOW” and only one of them was real, your core will mute the channel by Thursday. Planning is how you earn the right to ping once. A quiet board that updates on time beats a loud board that lies. Officers who complain that “nobody comes” usually have a trust problem, not a spawn problem.

Write the why on the pin as well as the when. “World boss — we need eight — resist poison — skip if under six.” People make better decisions when they can read the rule without waiting for you in voice. That is the whole job: fewer surprises, fewer heroic wipes, more nights that actually drop loot.

Pin the board: Discord, timezone, and one source of truth

Pick a single channel. Pin a single message. Everything else is noise. Officers who run timers in three chats plus DMs plus a random screenshot will always have someone in the wrong map. The pin is the law. Voice can call the pull. Voice does not replace the pin.

Write the pin like a raid note, not a meme:

• Spawn name — world boss, Metin stone, or event king, spelled the same way every time
• Next window — clock time plus the cycle if you know it (for example “22:40 CET, +3h if missed”)
• Timezone — one label only. CET or server time. Never both without a conversion line
• Tag lead — character name and Discord mention
• Backup tag — named, not “someone else ping”
• Prep line — resist type, red/blue overflow, antidote yes or no
• Skip rule — the sentence that lets people farm instead of griefing an empty pull

Timezone fights kill more timers than rival guilds. A Polish officer, a Turkish night-shift, and a Brazilian student will not “just know” what 22:40 means. Publish one home timezone on the pin and a conversion for the two biggest groups. If your server lives on CET, write CET in the title of the pin and repeat it in the first line. Do not rotate the home timezone every week because someone complained. Rotate the conversion line.

Update the pin after every successful or missed spawn. A stale pin is worse than no pin: people show up to yesterday’s window and then stop trusting the board. The officer who last edited the pin owns the next edit. If that officer logs off, the backup tag updates it. No “we will fix it later.”

Prefer an editable Discord message over a screenshot. Screenshots go stale the second someone kills the boss and nobody re-uploads. An editable pin lets the backup tag change one clock line from a phone. Mobile players are half your night-shift. If they cannot update the board from the tram, you do not have a board — you have a desktop hobby.

Onboard new members with a three-line paste, not a lecture: home timezone, where the pin lives, and who they ping if they can take a tag. If a new player has to ask “when is Azrael” in general chat, the pin failed the social test. Put the channel name in the guild MOTD. Repeat it after every war debrief. People forget. Officers remind.

World bosses vs Metin stones: same board, different clock

Do not mix these in your head. World bosses are rare, political, and expensive in potions. Metin stones are frequent, farm-adjacent, and easy to over-ping. Both belong on the same pin so the roster sees the week, but the attendance rule is not the same.

Spawn type	Typical window	Who must show	Prep focus	Skip when
World / map boss	Known cycle after last kill or server reset	Tag lead, tank, core DPS	Map resist, red overflow, food	War hour overlap or under minimum headcount
Metin stone rotation	Short map cycle, often 15–40 minutes	Named runner plus optional peel	Cheap farm pots, return scrolls	Better farm map tonight or runner already burned
Event / kingdom boss	Announced window, sometimes one-shot	Full published roster	War-grade stacks, caller	Roster already spent on war the same evening
Backup / second cycle	Next window after a miss or contest	Tag lead only until confirm	Light stacks, no all-ping	Primary kill was clean; let people farm

World bosses need a minimum headcount written on the pin. If you need eight for a clean Azrael-class pull and you have five, you skip or you send a scout, not a hopeful zerg. Metin stones need a named runner, not a guild-wide @here every cycle. Spam trains people to mute the channel. Then the world boss ping dies in the same mute.

If your server publishes official spawn text, still convert it onto your pin. Game chat scrolls. Discord pins stay. Officers who rely on “watch world chat” lose the people who were in a dungeon with filters on.

Know which clock your realm actually uses. Some private servers reset a boss to a fixed wall clock after maintenance. Others start a cycle from the last kill. Mixing those models is how you post 22:40 for three weeks while the real window drifted to 23:10. Write “last kill 19:05 CET — +3h cycle — next 22:05” or “reset clock 21:00 server.” If you are guessing, say you are guessing and send a scout, not a full ping.

Log the last kill on the pin even when a rival took it. Their loot timer is still your next window. Pride does not change the cycle. Officers who refuse to write a rival’s kill time donate the next two spawns because the roster thinks the board is dead.

Rotation: who tags, who tanks, who farms

A timer board without names is a wish list. Assign three seats per important spawn and publish them for the week, not for the next five minutes. “Whoever is online” is how the same three people get the job until they stop logging in. Write the week on Sunday night, the same way you publish a war roster. If someone cannot take their window, they tag the backup in the pin channel — not in a private message the rest of the guild never sees.

• Tag lead — first on the spawn, first to mark, first to call contest. Lives in the timezone of the window when possible. Has return scrolls and a clean bag.
• Backup tag — online or one ping away. Takes the pin edit if the lead drops. Does not start a second call unless the lead is silent for the agreed minute.
• Tank / hold — the body that eats the first mechanic so DPS can land. Confirm resist on this person before anyone else.
• Caller — often the officer. Target, peel, retreat. Can be the tag lead on small pulls; split the jobs on contested world bosses.
• Farm rotation — the people who are not on this window. Write them down so they stop feeling guilty for Seungryong.

Rotate tag lead across the week so the same three accounts do not live on the stone. Burnout is a timer problem. If your best ninja is on every Metin and every world boss, you will lose that ninja the week war starts. Pair this with the same role discipline you use in guild war prep: names on a list beat “whoever is online.”

Who tags is a trust job. The tag lead does not need the biggest weapon. They need to be early, sober about contests, and willing to call a skip. Ego tagging — racing a rival and dragging six undergeared alts — is how you donate the spawn and your potion crates.

Late arrivals get a two-minute rule. If the pin said 22:40 and you land at 22:43 with the pull already contested, you follow the caller — you do not start a second mark. Second marks split DPS and feed the rival. People who are late farm the next window or peel if asked. They do not rewrite the plan in chat.

Alts can tag if the main is in war prep or a dungeon lock. Publish the alt name on the pin so nobody reports “wrong person tagging.” Do not let a silent alt race your own tag lead. That is how friendly fire starts and how the backup thinks the lead is missing.

Potion and resist prep before the window

The timer is useless if the first three arrivals are drinking the last reds from a farm bag. Prep is part of the pin, not a side quest. Publish the resist type with the clock. Fire map, poison floor, dark room — write the word. “Bring resist” is how people bring yesterday’s Cape Dragon Fire stack to a poison boss. I would rather see a late confirm in Discord (“poison on, reds stacked”) than a silent mount and a wipe on the first DoT tick.

Minimum personal bag for a world-boss window:

• Red overflow beyond a normal farm pull — you will eat more hits in a contest
• Blue enough for the full mechanic, not for one rotation
• Correct map resist equipped before you mount, not after the emote
• Antidote if the map or boss applies poison; do not assume the tank packed extras
• Return scroll and a repair float so a wipe does not end the night in the shop panic

Metin stone runs can stay cheaper. Do not empty the war crate on a fifteen-minute stone unless the stone is the night’s income plan. That split is the same mental budget as farm week versus war week in the consumables yang budget: tonight’s stone uses today’s farm income; a contested world boss uses last week’s reserve.

Officers should check bags on the core, not on the whole Discord. Ask the tank and the tag lead. If those two are short, the pull is short. Fund a small officer pool for resist and reds when the window is real and the roster is confirmed. That pool is logistics. It is not a reason to empty the guild bank on every stone.

Food buffs belong on world-boss nights, not on every stone. Cheap farm food is fine for Metin routes. War-grade food is for the window you already called mandatory. Mixing those two is how the guild bank looks rich on Tuesday and empty on the contested Friday boss. Freeze risky +8 attempts the same night as a world boss. A failed upgrade removes a core fighter faster than a missed stone.

Steady Yang for daily stones still comes from routes. Use the Yang farming guide for income, not as an excuse to skip the pin. If time is the bottleneck — two windows tonight, war tomorrow, bags empty — a planned Yang top-up through Metin2 listings covers the crate gap. Face-to-face trade, exact server, no passwords. Process questions live in the FAQs.

When to skip a spawn

Skipping is the adult part of timer work. Officers who never skip train the roster to treat every ping as mandatory. Then nobody believes the important ping. Write the skip rule on the pin before emotions start.

Skip a world boss when any of these are true:

• You are under the published minimum headcount with five minutes left
• War hour or a higher-value event starts inside the same window
• Core resist is missing on tank and tag lead
• A contest is already lost on the field and a wipe would only farm their loot timer
• Your tag lead is the only person online and the boss is not a solo job on this realm

Skip a Metin stone when the runner is tired, the map is contested by a farm group you cannot peel, or the same Yang is available on a quieter route. Stones are income. Income has alternatives. World bosses often do not.

Call the skip in the same channel as the pin, in the same timezone, with a next window. “Skip 22:40 CET — under six — next 01:40 CET — farm Seungryong.” That sentence saves more Yang than a heroic wipe. People who wanted to come will farm. People who needed rest will rest. The pin stays honest.

Do not skip in silence. Silence looks like a no-show and the backup tag will start a second, worse pull. Do not skip after you already burned the crate. Skip is a decision before mount, not after the first death.

A scout is not a skip. Send one fast class to confirm the field: empty, contested, or already dead. The scout updates the pin. The roster stays on farm until the scout writes “go” or “skip.” Officers who ping the whole guild to “check” have already spent the political capital of a real call.

Political skips are still skips. If a larger ally already holds the field and your agreement says they take this cycle, you write that on the pin and you farm. Breaking a timer pact for ego loot is how you lose the next three contested windows when you actually need the help. Put the pact in the same channel as the clock. Hidden deals in officer DM are how the roster shows up angry and late.

Officer week: timers next to war and farm

A clean week looks like a calendar, not a vibe. Monday you refresh the pin and name tag leads for the midweek bosses. Wednesday you confirm resist types if the map pool rotated. Friday you decide which weekend windows are mandatory and which stones are optional. War week overrides stone spam. If Sunday is war, Saturday night is not four contested world bosses and an empty repair float.

Keep a short after-action line under the pin: who showed, who was late, whether the skip rule fired, how many reds the tank burned. You do not need a novel. You need enough memory that next week’s rotation is fair. Guilds that never audit timers always pick the same three people and then wonder why the channel goes quiet.

Private PVP realms cycle faster. Official Gameforge windows hurt more per miss because Yang is slow. The planning habit is identical: one pin, one timezone, named tags, prep on the board, skip rules that people can obey without asking permission in voice.

Weekdays can run a thin rotation: tag lead, backup, one tank. Weekends can publish two mandatory windows and leave the rest optional. Do not copy a weekend all-hands onto a Tuesday work night and then scold the roster for “no loyalty.” Loyalty is showing up when the pin said it mattered. If everything matters, nothing does.

Hand the board off before you sleep. The last line of a good officer night is not “gg.” It is an updated clock, a named night-shift tag, and a skip rule the next person can fire without waking you. That is Metin2 boss timer planning as a shift job, not as a personality cult around one always-online lead.

A pin you can paste tonight

If your channel has no board yet, paste this and fill the brackets. Keep the labels. Change the names. Do not decorate it with ten emojis — people scan the first three lines and then look away.

• HOME TZ: CET
• WORLD: Azrael-class — last kill 19:05 CET — cycle +3h — NEXT 22:05 CET (TR 23:05 / BR 17:05)
• TAG: MainNinja (@lead) — BACKUP: AltSura (@backup)
• NEED: 8 — TANK resist poison before mount — red overflow — antidote yes
• SKIP: under 6 at T-5, or war hour, or scout says field lost
• METIN: Dragon Valley runner @name — optional peel — no @here
• FARM TONIGHT: Seungryong if skip fires

After the window, edit three things only: last kill, next clock, who showed. If the scout called skip, write the reason in one short clause. Next week’s officer should understand the night in ten seconds. If they need a voice recap, the pin is still a diary, not a board.

Contested fields get one extra line: “CONTEST — caller @name — no second mark — late arrivals peel or farm.” That line stops the chat argument that starts when six people land late and each wants to be the hero. The caller already has a job. Your job is to add damage or leave. Timer planning dies in those arguments more often than it dies to a rival’s gear.

If two officers disagree on skip versus go, the pin owner decides for this window and you audit after. Split calls in the last two minutes are how you get two half-pulls and zero loot. Rank is less important than a single voice. Publish who owns the pin on Monday so that fight never happens at 22:39.

Use the same paste after war week, not a new format. People learn one shape. When you invent a second board for “important bosses only,” the old board dies and the new one is empty by the second weekend. One pin. One shape. Update it like a clock, not like a blog post.

FAQ — Metin2 boss timer planning

What is Metin2 boss timer planning?

It is the officer system for world bosses and Metin stones: one pinned board, one timezone, named tag leads, potion and resist prep before the window, and a published skip rule. The fight is short. The plan is the afternoon before it. If your guild only talks about a boss when the emote appears, you do not have a plan — you have a reaction.

How should we pin timers in Discord?

One channel, one pin, updated after every spawn. Include name, next clock, timezone, tag lead, backup, prep line, and skip rule. Voice can call the pull. Voice does not replace the pin. Prefer an editable message so the backup can change the clock from a phone. Screenshots go stale the minute the boss dies.

Which timezone should the guild use?

One home timezone — usually server time or CET for European realms — plus a conversion line for the two largest player groups. Do not rotate the home label every week. Rotate the conversion. If half the roster is in Turkey and Brazil, write those two offsets on the pin every time. Do not expect people to keep a converter tab open while they farm.

Who should tag the world boss?

A named tag lead who can be early, not necessarily the highest gear. Publish a backup. Ego races and silent “someone tag” pings are how you donate the spawn.

What potions and resist belong on the timer board?

Write the map resist by name. World bosses need red overflow, enough blues for the full mechanic, antidote when poison is in play, and a return scroll. Stones can stay on cheaper farm stacks.

When should we skip a spawn?

Skip when you are under minimum headcount, war overlaps the window, tank and tag lead lack resist, or the contest is already lost. Call the skip in the pin channel with the next time. Do not skip in silence. A scout can confirm the field first; a silent no-show makes the backup start a worse pull.

How do we rotate who shows up?

Publish tag lead, backup, tank, and a farm rotation for the week. Do not put the same three accounts on every stone and every world boss. Burnout is a timer failure. Swap names midweek if someone took two contested nights in a row. Fair rotation is how you still have a ninja in war week.

How does Yang farming sit next to a timer week?

Daily stones run on today’s farm income. Contested world bosses run on last week’s reserve. Farm routes stay in the Yang farming guide. When the crate gap is time, not route, use Metin2 listings as a planned top-up — never as a substitute for a skip call.

Run Metin2 boss timer planning like a small war: pin the clock, name the tag, pack the resist, and skip when the window is a lie. Show up for the spawns that pay. Farm when they do not. Update the pin before you log off.

Updated August 2026. Written by Can — SageGameCenter.