Warcraft 3: Reforged just killed LAN - and the latency excuse only covers half of it

LAN is how a lot of us learned Warcraft 3. Four boxes on a desk, one switch, cables everywhere, and somebody's cousin who only ever went Night Elf. So it stings a little that the version Blizzard actually sells in 2026 doesn't do it anymore.

Reforged's big 3.0 patch - the one that landed alongside the paid Forsaken Kingdom expansion - makes the game require an internet connection at all times, single-player included, and strips out LAN mode completely. The patch notes didn't bother explaining why. The explanation came from lead developer Brad Chan, who framed it as a trade-off: the team rebuilt the game's networking to cut latency for international players, and keeping the old LAN code alive next to the new stack wasn't sustainable from a security and stability standpoint.

I'll be honest - I believe the netcode half of that. Warcraft 3 is a lockstep RTS from 2002, and anyone who's played ladder from outside the traditional strongholds knows the pain of queueing into a server half a planet away. Micro in this game is brutally timing-sensitive. Pull a hurt unit back one beat late, miss a surround, eat a stun because your command arrived after the fact - that's what bad ping feels like here. The update also brings new regional server locations, including Singapore, India, Japan and South America. If you play from Sao Paulo or Mumbai, that could be the single biggest quality-of-life change Reforged has ever shipped. And maintaining two network paths, one modern and one inherited from a game old enough to rent a car, is exactly the kind of legacy baggage that breeds desyncs and exploits. Fine. Point taken.

What that argument doesn't cover is offline single-player. Latency to an international server has nothing to do with playing the campaign on a laptop on a train. There's no opponent, no packets, nothing to desync. Tying the campaign to a live connection is a DRM-shaped decision wearing a netcode costume, and nobody has explained why it was necessary.

The competitive angle is the one that actually worries me. Reforged's scene didn't survive that disastrous launch thanks to Battle.net - it survived because the community built its own infrastructure. Community ladders (W3Champions is the one every serious player knows) and grassroots events have leaned on the game's LAN-style hosting. Blizzard itself has acknowledged that third-party platforms depend on LAN protocols, and says it intends to support community initiatives going forward. Nice sentence. What matters is what that support looks like in practice and how quickly it arrives, because a ladder that goes quiet for weeks loses players it never gets back.

There is an escape hatch. Blizzard says the original, un-updated Classic client - included with a Reforged purchase - keeps offline play and LAN intact. So the LAN party lives on, just on the old client and without the new content. But note what else 3.0 changed: the unit-selection cap went from 12 to 24. That's not a cosmetic tweak, it changes how armies are controlled at a mechanical level. Classic-on-LAN and Reforged-online are now quietly drifting into two different games, and the playerbase gets split one more time.

My read: the server work is overdue and probably great news for anyone outside Europe, North America and Korea. The offline lock is indefensible. And whether 3.0 gets remembered as the patch that fixed Reforged's netcode or the one that kneecapped its community ladder depends on a promise Blizzard hasn't put any detail behind yet.

Image: Syced / CC0, source: https://commons.wikimedia.org/wiki/File:LAN_party_in_France_in_2003.jpg