wow patcher trick

[WarderX]

Didn't see this posted ever, and I thought I would throw it out here for people on networks that can't use blizzard's p2p thing reliably.

Every time you start the wow patcher, you apparently get 256kb worth of the patch from a direct http download, and then it attempts to switch over to the p2p system to download the rest of the patch.

The trick is just to close the patcher and re-open it in your wow folder over and over. You keep getting the 256k "bursts" every time you open it (they accumulate).

It's a tedious fix, but it can be worth it if the patch is only like 4mb (todays).

Not sure if it will work for everyone, but it helps me on my network.

[Vagoo]

or you could just use the blizzard patcher with the appropriate ports open and get 4mb in 10 seconds.

[WarderX]

reading is good

[eVasiege]

Originally Posted by FuckYou

or you could just use the blizzard patcher with the appropriate ports open and get 4mb in 10 seconds.

Not at a university.

[redjunkopera]

Originally Posted by FuckYou

or you could just use the blizzard patcher with the appropriate ports open and get 4mb in 10 seconds.

Care to link or elaborate. This start-stop crap makes me want to gouge my eyes out.

This is one beef that I continue to have with blizzard. They can build a robust client... they've shown that... they are no hacks. Why oh why can't they design their shit so you don't need to read a faq or reconfigure your network settings in order to play their games JUST LIKE EVERYONE ELSE MANAGES TO DO.

I have the same network issues trying to run D2 even going through all of their little guides and walkthroughs.

[Tirinal]

Here: World of Warcraft v2.05 to v2.06 US Patch - FileFront.com. Why do you people persist in using their downloader?

It's like watching a train wreck in slow motion. On the one hand you kind of want to help, on the other hand it's pretty funny.

[Vagoo]

seriously, ive patched from home and at work by opening the ports the patcher asks you to and have never failed to DL patches at anything less than extremely high speeds.

from the faq:

If you are using a firewall, you will need to ensure that ports 6112, 3724, and 6881 through 6999 are open in order for the Blizzard Downloader to connect correctly.

correctly forward those ports to your PC (correctly being the operating word) and report back if you actually cant DL a patch.

> reading is good

i read your post. i responded by saying that using the patcher as intended works better.

[skeezer]

i get the patch and use this - http://capnbry.net/wow/downloads/WoWTorrentEx-3.zip - to extract the torrent file out, then i just use my own torrent client.

in case that link doesnt work, here is the wiki - Blizzard Downloader - Wikipedia, the free encyclopedia

[WarderX]

Well, there are some people who are connected to the internet through hubs that they have no control over.

[Hozz]

Originally Posted by FuckYou

or you could just use the blizzard patcher with the appropriate ports open and get 4mb in 10 seconds.

I have everything forwarded to my machine and it still doesnt really help. Its better than not forwarding the ports but I sure as hell cant pull 4mb in 10s using their BT client. Strangely enough, using a different BT client, I can get the patch much faster.

[Vagoo]

strange. ive heard similar stories but always assumed the person has a configuration issue, since the multiple locations and networks ive tried it on have always worked well.

this is an outside possibility but windows firewall could also be interfering.

[Elidrin]

Originally Posted by FuckYou

seriously, ive patched from home and at work by opening the ports the patcher asks you to and have never failed to DL patches at anything less than extremely high speeds.

from the faq:



correctly forward those ports to your PC (correctly being the operating word) and report back if you actually cant DL a patch.

> reading is good

i read your post. i responded by saying that using the patcher as intended works better.

The last 3mb patch they had before you could play Burning Crusade fucked me hard, it took forever and ever. All of the appropriate ports are open and it was just fucked. Not sure about the patch tonight, will check it. But yes in general if you have the ports open the downloader acts ok...

[Vagoo]

yes, that 3mb patch from 2.03 to 2.05 was acting strange to be sure.

[Marduk]

Originally Posted by FuckYou

strange. ive heard similar stories but always assumed the person has a configuration issue, since the multiple locations and networks ive tried it on have always worked well.

this is an outside possibility but windows firewall could also be interfering.

I am no computer expert, but I know my way around them as I have had a pc for about 16 years. I spent hours reading faqs configuring Windows Firewall and my Router and opening all the ports and forwarding it to my computer. (I manually opened all the ports mentioned by Blizzard in Windows Firewall and you can only do one at a time). And I disconnected the router and connected directly to the modem, in case I didn't forward the ports correctly (even though I followed faqs). However after spending hours doing that shit it still didn't work, and now I just download patches from 3rd party sites.

What annoys me is that they are the only online game I have ever played where I had to sit down and read a lot of technical gibberish that I have absolutely no interest in learning just to get the patches down at a reasonable speed. And even when reading all the faqs at Blizzards website and googling my routers configuration info like mad it didn't work.

I have had no problems using Bittorrent for other things, so in my opinion they did something wrong with their download client.

[Vagoo]

its always possible that your ISP has an issue / block but that is unlikely. odd.