Full disclosure: It's 11:50pm...4.5 hours into Operation Why The Balls Can't I Play DiabloIII... I'm tired and grumpy.
So, when the program and the launcher for the program get their information about what's "Up to date" from two different places, doesn't this indicate a mild departure from best practice?
... and why in the name of Diablo's shaved armpits isn't there a "repair" option, because I'd be willing to bet that the problem could be fixed by tweaking a couple of strings somewhere in some file, if only there was some kind of consistency-checking widget that could spot the error.
So I've been downloading Russian language packs, notepadding (yes, that's a verb) random files, deleting those, copying these, renaming that. I actually have a collection of bookmarked foolproof plans. None of them worked.
Oh well. I found a thread from some guy who totally has a foolproof method. I just need to find some goat's blood, some black candles and something called "4MB of EDO RAM, preferrably burnt". Whatever the hell that means.
Fresh install didn't work. Waiting until morning did.
But really, this isn't a patch-rollout complaint... I'm fine with the delay between patches hitting the various zones. The thing that makes me want to strangle puppies is that two components of the same software package disagree about the state of the universe. The launcher says all is well, the game itself says it needs to restart so the launcher can patch it. That's messed up... and it looks messed up, as if something needs fixing on my computer when it turns out that the safest and most reliable way to solve the damn problem is to do absolutely nothing. God knows patching a multi-language, multi-zone app is hard, but that's a basic issue with data consistency that shouldn't be plaguing us ordinary shlubs.
God we SHOULD NOT have to be uninstalling and reinstalling games are people really that blinded by this.
If a game's files become corrupted, what else should we be expected to do? You do realize that most games do not have a repair option, right?
I don't know about you, but I've been playing PC games for the past, oh, 15-20 years now. If the worst thing you have to do is reinstall a game, you've no reason to complain. If you have to reinstall a game qutie often, you've probably got a problem with your computer.
Can't remember the exact fix, but you have the Singapore disc, and so when installed, it has your agent.db pointing there, just search enus agent fix, and follow the instructions.
1. please close Diablo3 first, and use Notepad open "agent.db" this file (*1)
Where is the "agent.db" file? (*2)
Win7 & Vista is in C:\ProgramData\Battle.net\Agent\agent.db
WinXP is in C:\Documents and Settings\All Users\Application Data\Battle.net\Agent\agent.db
Mac user can see this post (thanks NDT) http://us.battle.net...5037?page=5#100
**NOT the Diablo3 game folder's agent.db !! (thanks Darkstaf and Eliarainne)
So, when the program and the launcher for the program get their information about what's "Up to date" from two different places, doesn't this indicate a mild departure from best practice?
... and why in the name of Diablo's shaved armpits isn't there a "repair" option, because I'd be willing to bet that the problem could be fixed by tweaking a couple of strings somewhere in some file, if only there was some kind of consistency-checking widget that could spot the error.
So I've been downloading Russian language packs, notepadding (yes, that's a verb) random files, deleting those, copying these, renaming that. I actually have a collection of bookmarked foolproof plans. None of them worked.
Oh well. I found a thread from some guy who totally has a foolproof method. I just need to find some goat's blood, some black candles and something called "4MB of EDO RAM, preferrably burnt". Whatever the hell that means.
Funny post, tho.
Streaming Monday - Friday 5pm to 10pm EST.
Twitch.tv/beefaaleaf (@beefaaleaf - twitter)
Link to Profile: http://us.battle.net/d3/en/profile/beefaaleaf-1514/hero/82969
But really, this isn't a patch-rollout complaint... I'm fine with the delay between patches hitting the various zones. The thing that makes me want to strangle puppies is that two components of the same software package disagree about the state of the universe. The launcher says all is well, the game itself says it needs to restart so the launcher can patch it. That's messed up... and it looks messed up, as if something needs fixing on my computer when it turns out that the safest and most reliable way to solve the damn problem is to do absolutely nothing. God knows patching a multi-language, multi-zone app is hard, but that's a basic issue with data consistency that shouldn't be plaguing us ordinary shlubs.
WTFF.
/rant
I don't know about you, but I've been playing PC games for the past, oh, 15-20 years now. If the worst thing you have to do is reinstall a game, you've no reason to complain. If you have to reinstall a game qutie often, you've probably got a problem with your computer.
1. please close Diablo3 first, and use Notepad open "agent.db" this file (*1)
Where is the "agent.db" file? (*2)
Win7 & Vista is in C:\ProgramData\Battle.net\Agent\agent.db
WinXP is in C:\Documents and Settings\All Users\Application Data\Battle.net\Agent\agent.db
Mac user can see this post (thanks NDT)
http://us.battle.net...5037?page=5#100
**NOT the Diablo3 game folder's agent.db !! (thanks Darkstaf and Eliarainne)
2. find ALL(there have three or more)
ttp://****.patch.battle.net:1119/patch
and change to
http://enUS.patch.battle.net:1119/patch
**** is your client version. (like below)
enGB
enSG
esES
deDE
frFR
itIT
plPL
zhTW
koKR
esMX
ptBR