Stupid build 22490 completely kills custom maps

General Discussion
21

I’m not defending anything. I’m just suggesting that we act civilized instead of being a bunch of turds, for lack of a more forum appropriate term.

I’m just really tired of all the six year olds around here who act as though we all need to be yelling screaming angry about everything, instead of realizing there are bigger things in the world we can rage over.

I’ve been through and seen everything from custom games that dont work to the game suddenly deciding it wants to use my crappy integrated graphics instead of the $800 video card in my machine, the ranked matches that don’t get recorded, etc. etc. Beleive me when I tell you, these things annoy me too. It’s just my opinion that we’re better off not being enraged over a video game and describe the problems accurately and without hyperbole.

Any universe where not ladening my sentences with 100 curse words is “defending” something and wanting to see problems and issues described truthfully and accurately is a bad thing isn’t a universe I want to be in.

1 Like
22

thx for sharing
dev team doesnt play wc3 at all i believe too
ruined the online gameplay experience in just one update

1 Like
23

It’s not reasonable to expect devs to test all the absurd amount of custom content out there.

Though they could at least test a couple of current maps that people have been actively playing and see that something happened…

24

it is reasonable for them to know what the ramifications are of deleting large folders from casc/for them to know how to configure their builds before pushing them to the live client though

also this particular issue affects probably 99% of custom maps, so it’s not like they need to test all custom content

1 Like
25

What you say is reasonable, though there have been other custom game issues which were not this broad which could easily be missed in limited testing.

1 Like
26

This issue affected the Blizzard campaign. Testing a single campaign map would result in seeing it immediately.

Fortunately this has been corrected.