New WC3 Patch

[Laosh'Ra]

The new wc3 patch introduced hash-tables to gui and fixed various jass issues, including the return bug.
Several jass-focused maps (including DotA) abused this return bug in order to get a hash-similar effect. As a result, those maps don't work anymore until they use blizzards newly introduced functions instead.

To sum it up:
-DotA doesn't work right now, this might be an opportunity for less popular maps to give it a try.
-The return bug doesn't work anymore, you might want to fix your maps if you made use of it.
-You can now easily use Hash Tables in GUI as well. Check http://www.clancbs.com/board/showthread.php?t=3672 for more info.

[D.a.r.k.s.t.a.r]

It's only a matter of days til the next DotA gets out, i believe. It would really be a great time to host our maps. Sadly, there's not many new maps left.

Go Soulchess, go RvsS!

[DiamondBlade]

Blizzard fails.

function H2I takes handle h returns integer
 return h
 call DoNothing()
 return 0
endfunction

Still probably works.

function F takes nothing returns boolean
    if true then
        return true
    elseif true then
    endif
    return true
endfunction

False positive.
This crashes maps, though it's a legit function.

Blizzard also failed to notify about 90% of gamers (non-mappers) about this game-breaking patch.

[D.a.r.k.s.t.a.r]

Wonder why they couldn't leave it the way it is. It's way too late to bring out a revolutionary patch for mapmakers. And if i remember right, most things were working right?

[Lord of the Korn]

its time for ToJ! mwhahhahahah *owns all with a lazer gun*

[voyager[m]]

Originally Posted by D.a.r.k.s.t.a.r

Wonder why they couldn't leave it the way it is. It's way too late to bring out a revolutionary patch for mapmakers. And if i remember right, most things were working right?

They couldn't leave it the way it was simply because of the arbitrary exploit, in which a virus "code" at a loss of a better word was injected using byte-code into the map by exploiting a buffer overflow.

Its blizzards duty as a company to get this issue fixed [and from what I've read at wc3c.net it hasn't exactly worked, DiamondBlade highlights this above.]

And the fact DotA is out of commision for a few days, as brilliant news.

[Laosh'Ra]

this totally reminds me of the people in charge of the last few wc3 patches...

[DiamondBlade]

> They couldn't leave it the way it was simply because of the arbitrary exploit
Actually, that was fixed before 1.24.
Though I guess by fixing the return bug, they're preventing any potential problems in the future.

Instead of checking/counting/w.e the returns though, why can't the morons just check if the return is of the correct type? ¬_¬
I mean.. How much can you fuck things up to break ifs. ._.

[voyager[m]]

Originally Posted by DiamondBlade

> They couldn't leave it the way it was simply because of the arbitrary exploit
Actually, that was fixed before 1.24.

I was always under the impression that the "fix" was a small file downloaded from battle.net each login, meaning the script could still be executed if you played it directly into singleplayer and that it acted as a temporary fix.

Im not saying this patch was perfect, far from it, just that Blizzard was justified to [attempt to] break compatibility by removing the return bug.

[DiamondBlade]

It's possible that, that's the case. I just heard that it was fixed. No more details.
As I don't go on b.net much, I'm not interested.

> Blizzard was justified to [attempt to] break compatibility by removing the return bug.
I'm sure there were other things they could've done.
How about only removing C2I and I2C?
Also, don't forget that they didn't actually remove the return bug.

Apparently, this still works:

function H2I takes handle h returns integer
    return h
    call DoNothing()
    return 0
endfunction