WC3 update to 1.27 broke maps

[Bond009]

Does anyone know what changes were made? it seems the code all works fine still so it wasnt the same issue that changed from 1.23 to patch 1.24 where jass and vjass objects changed.
this seems to be more about object data. like now items wont work like a speed scroll doesnt work now but still shows the buff, and a mana pot doesnt work now. stuff like that.
Any info is appreciated.

 

[PurgeandFire]

Scroll of speed and mana potions are still working.

This update shouldn't have broken any maps since it didn't touch the internal MPQs (to my knowledge). If you are getting any issues, it is most likely from the Wc3 client itself. What bugs are you getting and when do you get them?

 

[Bond009]

https://www.youtube.com/watch?v=XXoKIXJvSoA

skip to 1min and then to 2mins and watch for a little bit its not the normal mana spell its a custom one that fills a little more than normal mana spell so the things affected are all customer MPQ values in the object data.

Maybe because of the map optimizer or the Widgetizer193 tools? does anyone know if Vexorian is still around?

 

[PurgeandFire]

So this didn't happen in patch 1.26?

Can you link the map?

 

[Dr Super Good]

Possible the widgitized data is not compatible with the new patch. Frankly wigitizer has always been quite buggy.

 

[DracoL1ch]

Possible the widgitized data is not compatible with the new patch. Frankly wigitizer has always been quite buggy.

so they forcefully destroyed big chunk of mappool with that? that's pretty hilarious (and retarded).

 

[Dr Super Good]

so they forcefully destroyed big chunk of mappool with that? that's pretty hilarious (and retarded).

No the "retarded" part was the people making tools which could break in future patches. Spazler is a good example because if WC3 gained MPQ4 support then it would break the maps.

 

[DracoL1ch]

No the "retarded" part was the people making tools which could break in future patches. Spazler is a good example because if WC3 gained MPQ4 support then it would break the maps.

like tools which grants 80% map size reducing aren't useful and aren't obligatory to be supported by the company itself. not gonna say blizz should care about it, but it's definitely the way to piss off community even more

 

[Dr Super Good]

like tools which grants 80% map size reducing aren't useful and aren't obligatory to be supported by the company itself. not gonna say blizz should care about it, but it's definitely the way to piss off community even more

If map makers open sourced their maps after official development stopped then it would not be a problem as someone could always update and fix the map. It is not Blizzard's fault for bad development practices. If WC3 needed an update to cope with new operating systems, map makers can provide an update to cope with new WC3.

 

[Bond009]

If WC3 needed an update to cope with new operating systems, map makers can provide an update to cope with new WC3.

thats true, but the problem is all the guys that developed those tools are pretty inactive now it seems, Vex hasnt been on since 2013 it seems and i forget who the guy is that made the widgetizer. but those tools helped speed loads and optimize map size which is pretty important in some games barely making the 8MB limit.
What really should have happened is after they were done making those tools, make those open source so if someone came around with enough talent they could continue the progress.

 

[PurgeandFire]

PitzerMike (the creator of Widgetizer) still has the source to those tools. I believe he made them open source and posted the links on wc3c.net, but wc3c did a rewind so I doubt that post still exists.

Anyway, all this is speculation. You should really link the map so that other people can test it and investigate it themselves.

 

[Bond009]

it worked perfect before the 1.27 update it has been hosting constantly for years
http://www.hiveworkshop.com/forums/maps-564/custom-hero-footies-v4-0a-163172/

 

[Ezekiel12]

Just posting a probably complex map does not help very much.
Create a testmap, do research and document as precise as possible all occurrences where something does not work anymore. Post that and someone will continue so we can find the exact causes to this.

 

[Bond009]

Just posting a probably complex map does not help very much.
Create a testmap, do research and document as precise as possible all occurrences where something does not work anymore. Post that and someone will continue so we can find the exact causes to this.

Well i know now its some combination of using vexorians optimizer and the widgetizer because i just tested the map before all that and it works fine. so now i have to figure out what those programs do to make it mess up in patch 1.27
these are some of the things that are messing up

i guess there is really no reason to test the map now, just speculate what widgetizer is doing to mess it up.. im 99% sure its not vexorians program because other maps that use it are still being hosted and seem unaffected.

 

[Dr Super Good]

Possibly the internal way widgitizer works is not producing correct output anymore. Maybe there were subtle formatting changes?