New Wc3 Patch 1.23

[Super-Sheep]

Ye , but because he uses gamecache for storing gameplay data like spell damage and stuff like that, people could use SyncStored -functions with GetLocalPlayer and join DotA game with their fake map, and pwn everybody.

Then how this never happens?

 

[Viikuna]

Maybe Blizzards new patch actually works, and it is harder now to play one game with 2 different maps, or then still it happens. Dont really know.

 

[Archangel_Tidusx]

glad i use gui. the patch just helps me.

 

[busterkomo]

glad i use gui. the patch just helps me.

I can't see how it helps you, really. You're no better off than before the patch. The way Blizzard prevented the exploit is pretty annoying. Now, almost every time I want to test a map or a spell I have to change the file-name.

 

[Eccho]

Yeah, that is really suffering:7

 

[Seralas]

When i try to patch to 1.21b (from 1.21a, did reinstall) I get a checksum error with a sound file...random? I think so. So i can't even comment on 1.23...Oh joy.

It says:

The patch could not be applied because it does not match the file checksum.

Filename: UI\SoundInfo\DialogueSounds.slk.

The irony is, when I put in the original exe into a cracked warcraft game folder, it patched up to 1.21b fine the first time I patched up a while back...

 

[Eccho]

Well, then it might have been a checksum error in the mpq archive you know.

 

[Squiggy]

The patch gives me fatal errors after updating - got back to 1.21 -.-

 

[Seithu]

The Patch works for me without further complications :3

 

[Eccho]

After further reading... The new patch is making gamecaches exploitable. Avoid it in your maps.

 

[Vicboy]

Garena
but
oh wait!
thats screwed up aswell..
everybody and their grandma updated to 1.23 and you cant join/see their games...

j o y

useless patch for a banner system and a failed attempt to fix some bugs...

btw how long has it been since they patched? 1.22 - 1.23?

http://www.hiveworkshop.com/forums/...craft-iii-tft-without-cd-safe-supplied-92639/

 

[Set-]

The game-cache exploits were fixed about 3 days ago,
So where most crashes and errors that 1.23 caused.

So far the patch has been working fine for me, and there is no duplicate system that is preventing me from playing maps I had in v1.22 or v1.21

I think it may be that your guys' WarCraft III has some MPQ error that isn't letting you play maps and/or causing exploits in your game caches.

For example:
Try replacing your cache.mpq file with
cache.exe

It actually stops the exploits

 

[Eccho]

The game-cache exploits were fixed about 3 days ago,
So where most crashes and errors that 1.23 caused.

So far the patch has been working fine for me, and there is no duplicate system that is preventing me from playing maps I had in v1.22 or v1.21

I think it may be that your guys' WarCraft III has some MPQ error that isn't letting you play maps and/or causing exploits in your game caches.

For example:
Try replacing your cache.mpq file with
cache.exe

It actually stops the exploits

I was talking about the exploit letting users have a similiar map which would be considered as the same as the original, but by using GetLocalPlayer and SyncStored<value> could exploit the values store to whatever he wanted to. The exploit has been notified in the latest days in Dota for instance.

How can they fix that exploit of gamecaches without releasing a new patch eh?
My wc3 works perfectly fine. Those errors about not letting you host a specific file, or such, is the effect of blizzard introducing us to b.net 2.0. That however, could most likely have been fixed.

Last question... cache.exe? cache.mpq? Where did you find that?

 

[TriggerHappy]

After further reading... The new patch is making gamecaches exploitable. Avoid it in your maps.

Thats actually what they fixed.

Before they had some easy hash, now I believe its SHA-1.

 

[Eccho]

Why has confirmed testing still said that they are exploitable? Or maybe I must check the date again.

Edit: The date seem to be correct. Let me bring up some quotes

The new hashing method is sha-1, still applied only to the important files (so translation maps should still be possible).

Yeah blizz needs to fix this Sync stuff until then using gamecache as freely as DOTA does is not a great idea. I wonder how the Table + structs methods would be abusable. Edit: I think that in some of my more recent spells that use Table it is possible to make them unstoppable by using this exploit, fuck.

Well it doesn't mean you have to believe in it. But I do, since they also tested and verified the exploit, and that it was still possible.

Tested. Confirmed. Can be edited by local syncing. Even if you can't bypass the hash, there's the possibility of a hack to do it without editing the script itself.

 

[Reaper2008]

@Khaine: I dunno why you get this error, my wc3 works just fine with maps spread in all folders. A friend of mine had problems like this, when he tried to play a game the screen went all funny and wc3 lagged superbly.I think it was his hardware that caused the error, what pc do you have?

 

[Aegis Runestone]

Okay, I took some time to read through this, and it mostly sounds like a bad patch.

So, my question is... is it really safe to download this patch? Or should I wait until 1.23b?

And is there anyway we can get Blizzard to make 1.23b?

 

[wyrmlord]

I'd hope they decide to release a patch to fix the arbitrary bytecode execution bug.

 

[Kam]

After extensive testing any map that has had an option such as "remove as much WE data as possible" used on it can't be hosted, at least by me. (Otherwise known as protecting.)

What the frak did Blizzard do and when are they going to fix it.

 

[punwisp]

Ha! I bet no one thought of this theory!

They make useless patches to cause bugs, which then they release another patch to fix those bugs! Its genius, because then they get payed more money! =)

 

[LordDz]

Ha! I bet no one thought of this theory!

They make useless patches to cause bugs, which then they release another patch to fix those bugs! Its genius, because then they get payed more money! =)

Causing rage isn't something that companies wants really.. It's easier to remember something bad than something good..