Re: Damn Blizzard



Did you interupt your ganking in Redridge to make that post?

I haven't been in Redridge in quite some time. I spent most of last night
and today running up my skinning skill (again) around Ironforge and then
moving onto that area to the north (the name escapes me right now, the
place with the dam). I grew tired of enchanting (again).

According to your post, you take pleasure in other's misery, you really
should try ganking lowbies & then camping their corpses.


Maybe you have a suggestion as to what a player can do about queues?

Sure! Check email, surf the WoW forums, check Yahoo! email, see if any of
your mods have had updates released, surf around Thotbott, take a shower,
grab dinner, get some from the wife (hey, the queue can last up to an hour
sometimes!), moderate the forums from another online game (that's probably
just me, though), etc.

The short answer: don't play unless you can queue up 45 mins before your
playing time window. People with limited playing time should quit the game
until Blizzard gets around to fixing the problem. Of course this is not a
solution, but a result of a problem, meaning your suggestion is useless.

Personally when I get screwed by a restaurant, retail business, ect... I
make sure I let the corporate office know in the form of a call, email, or
letter. What you call whining is actually very effective in getting
satisfaction in many cases. I might also post about it in various forums
online, specially of said business does it's business on-line. What some
call queue whining actually helps keep pressure on Blizzard to fix the
problem. People posting in public & sending messages to Blizzard keeps the
issue on the front burner. As they say, if you don't like it, don't read
it.


Blizzard has a huge problem & they also have the resources to fix the
problem. Unfortunately they choose to pocket those resources & put up
with the "queue-whiners".

Where did you come by this information? Or are you just assuming?

The problem has existed for quite some time. Regardless of promises &
opinions, they are taking their time fixing it.

The server I play it doesn't see a queue until late evening which doesn't
directly effect me. Too bad for the groups & small raids that loose a
key player due to lock-ups, crashes, & other forms of disconnects.
Disconnects can equal 45 min queue.

I've only been playing WoW since about last October when SWG released
their
NGE. But in that time I've only been disconnected from the server once
that I can remember. And it was due to scheduled server maintenance.

I've never had WoW crash on me. The code works fine, fix your computer.

How does that Usenet cliche' go again about reading comprehension?
Personally I don't have a problem with disconnects. I do have a problem
when we have to stop an instance looking for a replacement tank/resser ect..
to complete it. Seeing a disconnect in the late evening means that player
is gone. This has never happened to you?

I work in a headquarters of a large corporation. I see the debates on
problems & issues that require resources to fix. Debates & politics that
go on with many wanting nothing but to ignore the problem as fixing it cuts
into margins. Public comments/complaints & direct complaints are a huge
help to the people on the other side of that debate, giving them the ammo
they require to push through plans to solve problems plaguing the customer
base. I have forwarded complaints from the Usenet to the vice-pres of
Marketing with some success.

Trust me, in this case there are two factions at Blizzard, there always are.
One side wants to do nothing, using the bean-counters to keep an eye on how
much it is costs in lost customers vs. how much it costs to fix it. This
looks good to the finance guys. The other side wants to fix it, pointing
to the complaints, specially the public complaints. Fixing the problem
becomes the solution to the Marketing & C.S. people. Back in Engineering we
have already put together the plans, ran them through costing, & continue to
push to fix what we see as a truly huge problem. When it comes down to it,
most of the time it is all about when it starts to cut into profits, then &
only then will the money become available to start fixing the problem.
Otherwise the only way the money is freed up is because of public complaints
that may be hurting in ways that are difficult to measure.

Someone posted that Blizzard claims that there is a ongoing hardware upgrade
project. We can thank the queue whiners for it (if it is true & really
fixes the problem).


.

Relevant Pages

  • RE: [Full-Disclosure] Re: Full Disclosure != Exploit Release
    ... > wasn't important to fix. ... specific bug. ... and they wouldn't be fixing it as they are concentrating on supporting 32bit ... The information contained in this email and any attachments is ...
    (Full-Disclosure)
  • Re: Redirect
    ... Yes, and if it's garbage on purpose, don't fix it. ... And do you now understand that fixing 4 is just plain stupid? ... Suppose I want a password to be max 20 characters. ... > submitted data first. ...
    (comp.lang.php)
  • Re: Fixing Start AND End Dates of tasks
    ... You really can't fix both start and end directly. ... making the task a fixed duration task and fixing the start date with a "Must ... to meet those dates and if the initial calculation says no, ...
    (microsoft.public.project)
  • RE: [Full-Disclosure] Re: Full Disclosure != Exploit Release
    ... While I agree that they should be fixing their problems, ... >> wasn't important to fix. ... > specific bug. ... The information contained in this email and any attachments is ...
    (Full-Disclosure)
  • Re: Fearful of SP2
    ... > complaints because they're in a newsgroup. ... > probably are many installations without problems, ... And except for very rare situations, they always get a fix ...
    (microsoft.public.windowsxp.general)
Loading