Patch 1.27

Warseeker · Mar 3, 2016

I think Blizzard need to fix some spell stats because if for example you cast finger of death (item) on a Golem which is immunity against spells, well the effect still presist but it doesn't cause damage to the target.
They could usualy fix the last chapter of TFT which sometime bug Illidan forces from attempting the circle.
In RoC, Chapter 05, Undead campaign, the banshee can use Possession on an Elf Worker and turn it for the advantage of the undead army, they should fix that aswell by disabling the building construction stats of The Worker as they did in the 8th chapter.

Somebassoon · Mar 3, 2016

Pretty sure the Helf Worker one is intentional, to show the powers of possession.

Also, one thing I would really really like is a lag free "attack zone" system, that basically allows you to dictate which units in which regions can or cannot attack which areas/regions. Right now any system like that would cause massive lag, but having one that's widely available and easy to use could go a long way.

Dr Super Good · Mar 4, 2016

Blizzard needs to switch WC3 to actually using shaders. It turns out it uses the fixed pipelines from pre D3D8 era. No wonder the graphics give problems in Windows 10.

Somebassoon · Mar 4, 2016

Expanding on the "Allowing Hero models to turn off hero glow without reimporting a model" point, giving hero models built in decay animations would be nice as well.

Warseeker · Mar 5, 2016

I'm not sure Blizzard will listen to none of this wishes, they do stuff on their own way

Somebassoon · Mar 5, 2016

You never know. I'd love to see a far simpler buff stacking system, that just lets you use multiple buffs from the same spell type easily in a smooth way.

Zwiebelchen · Mar 6, 2016

Warseeker said:
I'm not sure Blizzard will listen to none of this wishes, they do stuff on their own way

... except that Blizzard contacted the Hive staff about suggestions for a new patch already.

Warseeker · Mar 6, 2016

Zwiebelchen said:
... except that Blizzard contacted the Hive staff about suggestions for a new patch already.

Really? Since when Blizzard started making requests...

Zwiebelchen · Mar 6, 2016

Warseeker said:
Really? Since when Blizzard started making requests...

Obviously, as Blizzard hired new personnel for retro game team, they needed input for what is broken and/or needed a fix, since everyone working on WC3 in the first place moved on to other projects. And who would have more knowledge about WC3 than the biggest WC3 community?

Kyrbi0 · Mar 7, 2016

Zwiebelchen said:
Obviously, as Blizzard hired new personnel for retro game team, they needed input for what is broken and/or needed a fix, since everyone working on WC3 in the first place moved on to other projects. And who would have more knowledge about WC3 than the biggest WC3 community?

While it's truly an obvious solution, the also obvious fact is that big (game) companies aren't historically known for taking that route (which, I suspect, is the understanding at the heart of Warseeker's question).

DracoL1ch · Mar 8, 2016

the only reason to even touch wc3 is to give a hand to oldfags "look, we are still good company". if they piss off fans, it won't work, and spends will be in vain.

Zwiebelchen · Mar 8, 2016

Kyrbi0 said:
While it's truly an obvious solution, the also obvious fact is that big (game) companies aren't historically known for taking that route (which, I suspect, is the understanding at the heart of Warseeker's question).

Correct; but then again, blizzard has a reputation for listening to it's fans at least occasionally. Remember the return bug and hashtables.

Warseeker · Mar 8, 2016

Zwiebelchen said:
Correct; but then again, blizzard has a reputation for listening to it's fans at least occasionally. Remember the return bug and hashtables.

But Why Blizzard didn't listen when she started making patches 1.21 , 1.22...etc?

Is it because of this active community?

PurgeandFire · Mar 8, 2016

Warseeker said:
But Why Blizzard didn't listen when she started making patches 1.21 , 1.22...etc?

Is it because of this active community?

Blizzard has been a lot more involved with their playerbase now than before. With things like Twitter, community managers, etc. people have much easier access to Blizzard employees. If you rewind a couple of years, most things were done behind closed doors.

Part of it is customer satisfaction, part of it is PR. Blizzard is partially known for the communities they've produced, so they might feel obligated to invest in those communities to keep them thriving. Not a lot of companies do that (at least not on the level that Blizzard does), but it definitely has its rewards--along with some downsides.

In this case, classic games are revamped almost entirely as a service to fans. You don't make nearly as much money shipping an old title as you do a new one. But there is still a lot of merit to it--and still money to be made if done correctly. Nintendo is a great example of this. They've been revamping all their older games (Ocarina, Majora's Mask, Wind Waker, and Twilight Princess) into HD versions. Almost everything is exactly the same, but textures are updated and a few features/conveniences are added here and there. Yet, it is actually quite successful--and it is worth the investment since it allows people to play their older games without having to buy separate consoles. Same thing applies to Blizzard--and if they are going to bother updating their classic games, then what better audience to appeal to than their devoted communities?

LeP · Mar 12, 2016

Seems like they will release the patch tuesday.
https://www.youtube.com/watch?v=iJqnZQq8pQ0

Bannar · Mar 12, 2016

Very fresh info. I'm eager to see how the situation develops, especially since there were no real official "balance test maps".

See the unofficial patch notes here.

DracoL1ch · Mar 12, 2016

Bannar said:
Very fresh info. I'm eager to see how the situation develops, especially since there were no real official "balance test maps".

See the unofficial patch notes here.

its not patch notes, its trash

Meatmuffin · Mar 12, 2016

EDIT: nvm, someone already posted about it

EDIT2: In my opinion, 1.27a will be a small performance update to indicate that they are still working on the game. The same thing happened with Diablo 2, two days ago, they improved performance on modern pc's, increased hack detection and added better support for Mac OS. I didn't even bother downloading the new patch, though I am extremely exited to see what patches are upcoming for both Diablo 2 and Warcraft 3.

Zwiebelchen · Mar 12, 2016

Why would they only announce all that in china? I still don't get it.
I'd say this video is fake, again.

edo494 · Mar 12, 2016

because china is like, 85% of remaining player base.

We will know if its fake or not on 15th

A Void · Mar 12, 2016

Patch 1.27 has been announced.

edo494 · Mar 12, 2016

inb4 fake video

SpasMaster · Mar 12, 2016

edo494 said:
inb4 fake video

The guy in the video is a Blizzard Developper. He's talking about a patch that has been rumoured for awhile. After Blizzard has been repeatedly talking about revisitng old games. What's so unbelievable about a new patch coming out?

edo494 · Mar 12, 2016

I am not retarded

but you know, it could be someone similar and blah blah, basically

Lets see if the patch fixes the Jass VM that someone(cant remember the name of this guy[presumably, everyone on internet is guy unless proven otherwise]) posted about, allowing virus injection

Statharas · Mar 12, 2016

Literally "Updated battle.net functionality to our new Battle.net infrastructure".

There is a WoW patch (6.2.4) coming with the above.

Darxy · Mar 15, 2016

edo494 said:
because china is like, 85% of remaining player base.

We will know if its fake or not on 15th

85%? From where did you pull that number?

A Void · Mar 15, 2016

Patch 1.27a has been released.

Darxy · Mar 21, 2016

A Void said:
Patch 1.27a has been released.

And what does the patch has to do with this?

Bannar · Mar 21, 2016

That's rather easy to guess - instead of keeping three threads alive (which are related to exact same subject), it's better to stick to just one.

A Void · Mar 22, 2016

Darxy said:
And what does the patch has to do with this?

Use your brain and think for a minute, this is about patch 1.27 in general, the other is about the release of patch 1.27a and patch notes. When 1.27b comes out I will create a new thread, just like 1.27a.

That's rather easy to guess - instead of keeping three threads alive (which are related to exact same subject), it's better to stick to just one.

Bad idea. Sticking two different subjects?

Bannar · Mar 22, 2016

Sure, but you can't deny that many people treat all of these "1.27" threads in the exact same way.

method.killOfftopic().invoke();

// running away

edo494 · Mar 22, 2016

until patch 1.27b is released, they both are about the exact same thing, so undeeded redundancy

Darxy · Mar 29, 2016

A Void said:
Use your brain and think for a minute, this is about patch 1.27 in general, the other is about the release of patch 1.27a and patch notes. When 1.27b comes out I will create a new thread, just like 1.27a.

Alright, I fail to see the difference between 1.27 and 1.27a

Mind enlightening me, please?

Ezekiel12 · Mar 29, 2016

Alright, I fail to see the difference between 1.27 and 1.27a

Mind enlightening me, please?

Currently there is only 1.27a but in the future there might be 1.27b. Those two are both of course then 1.27. It's just the naming scheme Blizzard uses now.

A Void · Mar 29, 2016

Darxy said:
Alright, I fail to see the difference between 1.27 and 1.27a

Mind enlightening me, please?

1.27 is the general patch name which includes 1.27a, 1.27b, 1.27c ect... Currently only patch 1.27a is released.

Edit: Just like Ezekiel12 said.

anufis · Mar 30, 2016

Interesting. I am probably the only unique person in the world who had my map stop working with 1.27a. Spent 6 hours yesterday to figure it out(just made new version of the map after 2 month of work and decided it's finally time to test, so I thought it was problem in new version of my map or reinstalled JNPG)

PurgeandFire · Mar 30, 2016

anufis said:
Interesting. I am probably the only unique person in the world who had my map stop working with 1.27a. Spent 6 hours yesterday to figure it out(just made new version of the map after 2 month of work and decided it's finally time to test, so I thought it was problem in new version of my map or reinstalled JNPG)

That is definitely interesting. Another user also experienced bugs in their map--it was supposedly related to the Widgetizer.

When we get the discussion forum up and running, hopefully you'll stop by and shed some light on the issue.

Statharas · Mar 30, 2016

anufis said:
Interesting. I am probably the only unique person in the world who had my map stop working with 1.27a. Spent 6 hours yesterday to figure it out(just made new version of the map after 2 month of work and decided it's finally time to test, so I thought it was problem in new version of my map or reinstalled JNPG)

Of course, the other people that had their maps stop working were duplicates of you.

Patch 1.27

Similar threads