@Amigoltu
Please, don't take my post as some kind of rant. You asked why people were upset, and I explained. I'll elaborate more on each point.
@Sir Moriarty
As I said before, I have not encountered a single bug with the 1.30 version. Speaking about Jass, this version runs it better than earlier ones, and even the error reporting was updated, giving the user better descriptions of the problem.
Just because you didn't encounter them, doesn't mean there weren't any. Patch 1.29 utterly broke the sound system, and introduced a slew of weird crashes and bugs. Some of them were fixed with 1.30, most weren't. Sound issues are still present in 1.30.1, like sounds not playing properly at all, or playing globally instead of locally, etc. The game was nigh unplayable for a period of around several weeks after patch 1.29, many popular custom maps consistently crashed. The game still desyncs very frequently at the start of a map - if you have a lobby of 8+ people, it's almost guaranteed that someone will desync.
Yeah, these bugs are being fixed, but:
1) These patches did not introduce significant improvements that outweigh the lack of poor testing on Blizzard's behalf,
2) It takes a long time for Blizzard to fix these bugs, while the game remains broken or unplayable for weeks at a time.
Considering the above, the inevitable question comes up - are these patches really that important that they need to be rushed out in half-finished states, potentially introducing bugs, while not really improving much at all?
@Sir Moriarty
You say tools are not working anymore... What tools? SharpCraft? Again, as far as I heard, blizzard is planning to add TESH functionality to standard WE in one of the next patches. And what other tools are there missing?
Any tools that relied on injecting themselves into the WC3/WorldEditor process. There was an extremely useful utility called GProxy++ that allowed reconnecting to a host bot game if you lost connection - now that will be gone. There was also another variant of that same tool that didn't require injecting - but it will be broken, too, once 1.30.2 is rolled out. GMSI, which is a utility for procedurally generating object data, relied on reading .mpq archives for initializing itself. WEX, obviously, is broken - and the JassHelper version included with the game now doesn't work for my map for some reason, effectively killing my map entirely, because I can't update it anymore. Useful utilities that came with JNGP such as ObjectMerger are also gone. The TileSetter from JNGP was also a nice tool - and while it's use is diminished now that the stock worldeditor properly supports tileset editing, worldedit still can't remove/replace cliff tiles, for example. TileSetter can. A lot of people have to keep a copy of WC3 1.26 just to work on their maps because of these reasons. The Blizzard replacements are simply not on par with the community tooling yet.
@Sir Moriarty
About WE... Those ARE upgrades. JNPG could remove limits, but they did not make the game actually playable with them removed. You would most likely have crashed, had lags, etc. Blizzard made this and made the game playable. These limit increases are actually usable now.
That's not true at all. The limit removers were just that - they adjusted several constants within WE to allow to bypass the doodad/whatever limit. Maps that did so before worked perfectly fine in my experience. The only useful limit that was raised was the JASS Instruction Ops limit.
@Sir Moriarty
Eventually, poor communication? Blizzard seems to be posting plenty in their forums and even here. What are you talking about?
Most of their tooling-breaking changes come out entirely out of the blue when they land in PTR. That was the case with CASC, now with host bots. There is rarely any explanation as to why these changes are necessary, what they would break, what they wouldn't, etc. We don't know what plans Blizzard has for the game in the long-term - there's no communication regarding that. Communication with Hive ceased after PTR 1.30.2 landed, as far as I know, and the blizzard forums are such a cesspool of immature toxicity that I don't even want to go there.
Most of community requests after 1.29 remain unanswered - not even denied, just ignored.
Maybe the issue is not with blizzard not listening. Maybe it is with the community not knowing what they want.
There are multiple thread with aggregated community requests. Each patch prior to 1.30 received tons of feedback, suggestions, and requests, but they stopped after that, because almost all of them went unanswered. The problem is that the community isn't united. There are multiple subsections that each want their own thing - melee people want fixes and updates to the ladder system, custom games competitive scene want bots and ban lists, custom games casual scene want to be able to play without bots, casual modders want updates to worldeditor and GUI triggering, veteran modders want extensions to JASS, better documentation, more expandability, and most importantly, for tools not to break.
Unfortunately, the recent patches haven't done much to please any of these groups, whilst breaking a lot, as I described above. The whole hostbot situation seems to be resolving itself as Blizzard address the concerns regarding it, but, a lot of people wonder whether it was really that important? There are many other things that could significantly improve WC3, but they choose to do the most controversial things.
Most of this is just fact, not my opinion, with the exception of a few points. You asked and you got an answer, and I hope this helps to understand the whole perspective.
If you want to argue about any of this with me, I will promptly ignore you.
