So the game now launches after the 2.0.0 update but now it sits on the lion head opening for a while then it always throws back and error, “THERE WAS AN ERROR IN HANDLING THE REQUEST. 6:9” With a Login button under it. Pressing the login button brings up a login screen. After putting in the login credentials the same error pops back up and continues the loop. At the Botton of the screen there are 3 options. OPTIONS, PLAY OFFLINE (which is greyed out and not clickable) and EXIT GAME.
25 Likes
theyre working on it i guess. hopefully theyll have a fix soon
3 Likes
Indeed.
3 Likes
they certainly love a bit of hope
1 Like
I’d be hanging on their every, few and far between, word!
imagine rolling out updates after a month and it still doesn’t work. Do they even have someone to test the programs by running on a mac??? Only games devs have this kinda audacity to lazily put out updates in production and do live debugging. They should all have been fired if it’s any mission critical services.
5 Likes
Two immutable truths, Yolosolo.
- Developers/Studios often release games/patches knowing full well that there are bugs. It’s a very, very common practice across the industry.
- Internal testing cannot, cannot, replicate the 100,000s of different environments that the software will encounter. There’s a pervasive credo in the industry: “The only true test is production”, where “production” refers to releasing it out to do its job.
So, no, they likely aren’t going to fired for either of your assertions.
1 Like
Except this has been a known issue for 1.5 months, and it’s a bug that is universal to all MAC users. A simple login test on a MAC would have detected this. They literally claimed that MAC issues were fixed in the patch notes.
There is no justifying Blizzard’s utter incompetence, unprofessionalism, and borderline scam. They’ve known for 1.5 months that the game doesn’t work on MAC and yet sell it as if there were no issues.
8 Likes
It’s ok to test in production, but this seems obviously not an environment issue or corner case/weird bug, literally just take the program to run in a mac you’ll catch the issue since everyone is getting the same error.
My hunch is this is a dying game, they don’t even bother to maintain it, they’re running out of devs to layoff since upper management has gutted the company.
1 Like
Two bugs. The first was a missing binary (the game was missing).
As for the time it took, they seemed to have waited until the WCD event to push that fix along with the rest of the WCD updates. The second is separate and is part of a handful of issues that started out effecting everyone. They’ve been working on those, including the 6:9 error for Mac players, since release.
What they literally said is that Macs can now launch the game, something that wasn’t possible before. Now, new issues exist for everyone, and they are resolving thses.
Then it’s not just Bliz you should be mad at. As I described above, it’s industry-wide.
Because they have every intention of fixing it, as they have said twice for both the initial and subsequent Mac issues.
1 Like
See #1 of my truths above. It may have had nothing to do with testing.
That’s likely. It been outsourced to a 3rd party studio for quite a while.
My hunch is that once it’s patch up to some “acceptable” state, what ever that is deemed to be, it will be shelved like D2R, SCR, SC2 and Heroes has been. Those only get intervention when there’s large impact problems. I’m in SC2 quite a bit and it has a handful of issue that are (apparently) deemed not important enough to fix.
1 Like
Given how sour things have gotten i think most of us would be okay with it reaching a level of un interrupted playability.
Like just let the millennials recapture their childhood for a few more years and we’ll be grateful lol
Totally. Don’t get me wrong, I’d be pissed too.
The only things I’ve been pushing back against are people’s misdirected assumptions. In the end, I know it doesn’t help the immediate situation.
Mac issues aside, WC3R has been embarrassing. So I never defend the situation(s). I’m just trying get people to either 1) be mad at the correct parties, or 2) be mad for the right reasons.
They’re telling you straight up here: the game hasn’t been launching on Mac for 1.5 months, the forum was on fire, Blizzard released a patch where they loudly highlighted in a separate note that the issue was fixed. Now, any Mac user trying to launch the game can’t play because they encounter a different error.
Not on some rare configurations, but any Mac user. So what does that mean? Blizzard never even tested the game on Mac after the ‘fix’?
Oh, dude. Are you that Blizzard developer? Or the manager in charge of calming down the forums? Do they pay you a lot? Doesn’t your tongue, along with CaptainJack’s, hurt from sucking up to such a filthy backside?
3 Likes
No, Pbmatch. It is currently launching. It’s failing at some resolution or authentication phase. That wouldn’t be possible if the game didn’t launch.
And again, they said the not launching issue was fixed, and it was as evidenced by the failures from within the game.
See here:
Nope. I’m not an employee.
Not that either.
Care to provide where I’ve licked Bliz’s rear, Pbmatch? Because I haven’t. You’re spinning that fabrication simply because you don’t like what you’re being told, however, that doesn’t require me licking anything. I haven’t ever defended what’s been going on with WC3R at any stage.
Dude, you don’t even need to read further. “They fixed the error, rejoice.” Seriously? What difference does it make to the user if the game doesn’t open at all or opens but doesn’t let you do anything? Are you okay?
You wrote: “Developers/Studios often release games/patches knowing full well that there are bugs.”
But not these kinds of bugs, man.
Developers release games with bugs they couldn’t find themselves. (They looked, their testers looked, and no one found them.) This usually happens due to rare hardware configurations or very specific conditions to trigger the bug.
But here’s the situation:
1.5 months ago: On all Macs, the game wouldn’t launch at all. Yet, they sent the patch to release anyway.
Patch 2.0: On all Macs, immediately after launch, there’s an endless loop of authorization errors. (Plus, it doesn’t work on Windows 7.)
Are these the so-called “hard-to-detect” bugs? What are you?
3 Likes
No not seriously, as I didn’t say anything remotely like that.
Perhaps you should read further instead of cherry picking.
You haven’t got a leg to stand on when it comes to such claims. When you try, it just reveals your desperatism to be right. Unless you work at Bliz in the WC3R dept? If so, then Ill concede to your clains. Otherwise…
No. Very often they are released with full knowledge of existing bugs that will be worked out later. Again, your own words reveal that you don’t know enough to be making such assertions.
No one said they were hard to detect. In fact, I’ve been offer explanations that suggest the contrary.
Dude stop spamming stuff that nobody care lol. We just want to get the game working again and that’s it
3 Likes
No.
And be careful when speaking for everyone. A large amount of posts are peppered around that have other motives.
Man, this is ridiculous. I bought this game a month ago after getting a new laptop because I wanted to relive the game I played when I was 6 years old. But THIS GAME HAS NOT BEEN PLAYABLE SINCE DAY ONE AFTER I PAID FOR IT. At this point, I feel justified in pirating this and running it on an older build.
5 Likes