Guide · 2026-08-31

When later content arrives early: three leaks in five weeks on Taiwan mobile

✍️ Alice・愛麗沙

Result, 9/14: the “future material” arrived. Taiwan’s 9/9 update log (3541097) relists 阿爾米斯’s 特殊鋼錠 ×2 → 銀合金錠 ×1 barter unchanged (once per account per day) and opens 班克爾 with three more 銀合金錠 routes; the reclaim announced for 9/9 is not mentioned in either 9/9 notice. The guild ship is still absent.

Between 2026-07-27 and 2026-08-26, the Taiwan mobile service handed players content from a version it had not shipped yet — three separate times, in five weeks. Every one closed by the same formula: emergency or scheduled maintenance, reclaim the output, return the inputs, pay compensation, never roll the server back, punish nobody. That last clause is not universal. On the Korean mobile service, the same class of accident on day three ended in 365-day account restrictions. There is no Western mobile service and no announced date for one; everything below is the operator’s record on the services that have gone first, and the reading of what it predicts is labelled as inference.

A hooded sorcerer boss standing in ruins, surrounded by red magic orbs
Content that exists in the build before it exists on your server is the recurring shape of these incidents · Image: Nexon

Three leaks, one closing formula

ServiceDateWhat arrived earlyHow it was closedSanctions
TW mobile2026-07-27A level-65 mystic die produced runesEmergency maintenance 06:00, scheduled to 08:30, ran to 10:00; runes reclaimed and corrected, correct items reissuedNone
TW mobile2026-08-05 → 08-06Guild-ship construction opened, live roughly 19 hoursEmergency maintenance 2026-08-06 06:00–08:00 (ended 07:00) closed it; ledger settled at the 8/12 maintenanceNone
TW mobile2026-08-26Colhen smithy barter: Special Steel Ingot ×2 → Silver Alloy Ingot ×1Barter and exchange listings removed the same day; ingots to be reclaimed 2026-09-09None
KR mobile2025-03-30A main-story dungeon re-enterable without clearing; NPC shop purchase caps stopped applying after the 06:00 resetEmergency maintenance 06:40–09:00, extended365-day restriction under operating-policy clause [4-4]

The Taiwan rows and the Korea row describe the same category of failure. The difference in the last column is the whole article.

The first one: a die that does not make runes

On 2026-07-27 (TW mobile), an emergency maintenance opened at 06:00, was scheduled to 08:30, and actually ran to 10:00. The official notice (3509755) said a level-65 mystic die had produced runes that, in the operator’s own words, “should not be obtainable in the current version” — Nexon Taiwan, notice 3509755.

That wording is worth sitting with, because the item’s own official guide agrees. Thread 3474905 defines the mystic die as an item that gives one piece of equipment when used, with up to four rarity-upgrade attempts and a per-die ceiling on stats. Runes are not in the specification at all. This was not a generous roll. It was a different item’s loot table.

Nexon reclaimed the runes, corrected them, reissued the correct items, and then did something it has not done before or since on the Taiwan service: it paid a third, separate apology packet on top of the base compensation and the extended-maintenance packet. The apology packet contained one Rebirth Stone.

The second one: a ship that ate thousands of logs

On 2026-08-05 (TW mobile), guild-ship construction opened. It should not have. It stayed open roughly 19 hours before an emergency maintenance on 2026-08-06 (06:00–08:00, ended 07:00) shut it.

The in-game guild ship material delivery interface, listing required materials and quantities
Guild-ship construction consumes real life-skill materials in the thousands — logs, fine wood, tar · Image: Nexon

This one hurt more than the die, because guild-ship construction is not a button. It consumes life-skill materials in the thousands — logs, wood, fine wood, tar — gathered by many people across many days. Nineteen hours was long enough for guilds to organise around it.

The 8/6 notice (3517461) set out the settlement: guild coin and contribution earned by delivering guild-ship materials would be reclaimed at the 8/12 maintenance, with shortfalls handled as negative values, and consumed materials returned after that same maintenance. The 8/12 scheduled-maintenance notice (3521199) then added four words the 8/6 notice had not contained: build progress was reset too.

That is the pattern to remember. The first notice tells you what comes back. The second notice tells you what does not.

As of writing, guild ship still sits on the official Known Issues page (3505986) marked fixed as of 8/6, with no reopening date. On the Korean mobile service, guild ship was 2025-08-21 content.

The third one: a material Taiwan cannot spend

On 2026-08-26 (TW mobile), the Colhen smithy’s barter line offered Special Steel Ingot ×2 → Silver Alloy Ingot ×1. Silver Alloy Ingot is a later-version material. It has no known recipe and no known barter on the Taiwan service that consumes it; its other three sources all sit in Bancor, a town Taiwan has not opened.

Hand-drawn illustration of three metal ingots with an arrow curving back toward them
Two 2-for-1 steps mean one Silver Alloy Ingot traces back to eight steel ingots — but only the last step's inputs come back · Illustration: this site

The barter and exchange listings were pulled on 8/26 and the listed stock batch-expired. Notices 3532156 and 3531550 set 2026-09-09 as the date the ingots are reclaimed — from bag, storage box and mailbox — with the spent materials returned. Both dates are written as expected or planned, not fixed.

Here is the arithmetic that makes this the most expensive of the three, in the least visible way. One Silver Alloy Ingot traces back through two 2-for-1 steps to eight steel ingots. Only the last step’s inputs are returned. The rest of the chain was paid for in daily exchange counts, over several days, and daily counts do not come back.

A related incident on 2026-08-25 (TW mobile) rhymes with all of it: a class-advancement quest force-ran a weapon upgrade and destroyed the runes engraved on the weapon submitted as material. Nexon said the mechanic would change, and reissued the lost runes in three waves — 8/26, 9/2 and 9/9.

The formula, written out

Stack the three and the procedure is identical every time:

  1. Close the door at the next maintenance, emergency if the leak is still live.
  2. Reclaim the output — the runes, the guild coin and contribution, the ingots — wherever it sits, including mailboxes.
  3. Return the inputs, but only the final step’s inputs.
  4. Pay compensation on the outage, not on the loss.
  5. Never roll back the server.
  6. Punish nobody, on the Taiwan service so far.

Korea drew the line somewhere else

Official banner announcing the 7/22 00:00 service launch
Taiwan mobile launched 2026-07-22; Korea mobile launched 2025-03-27 and hit its first leak on day three · Image: Nexon

On 2025-03-30, day three of the Korean mobile service, a main-story dungeon could be re-entered without being cleared, and after the 06:00 content reset the NPC shop’s purchase caps stopped applying. Emergency maintenance ran 06:40–09:00 and was extended. Compensation went out to everyone.

And then, after a full data sweep, accounts that had run the dungeon more than three times were given a 365-day restriction under clause [4-4], the abnormal-use-of-the-game clause. In June 2025 the Korean mobile service restricted roughly 4,000 accounts for 3 to 30 days over a separate incident.

Read the published threshold carefully, because it is the operator’s actual doctrine: the line was repetition, not benefit. Walking through an open door once was not sanctioned. Walking through it a fourth time was.

What this is worth to a reader whose service is NA PC

There is no Western mobile Mabinogi and no announced date for one. What the North American PC service does share with all of the above is the settlement doctrine — on 2018-08-06 (NA PC), faced with duplicated rare gear on Alexina and similar activity on Ruairi, Nexon America removed the items from accounts rather than rolling the servers back. Same instinct, eighteen years and three services apart.

So, as inference rather than news: if a Western mobile service ever launches, the three Taiwan incidents are a preview of its first five weeks, and the Korea incident is a preview of where the sanction line would fall. The practical reading is unglamorous and holds on every service in the record —

If a door opens that your version has no business having open, walk through it once, look, and leave. One pass has never been sanctioned anywhere in this record. Repetition has, on one service, cost a year.

And do not spend anything scarce behind that door. The compensation is paid on the downtime. It is not paid on your daily exchange counts, your build progress, or four days of gathering.