| 03-11-2010, 10:54 PM | #1 |
Just to let you know that's there's a new patch.... jaja funny. Code:
- Fixed an exploit rendering buildings non-interactable ("tower hack").
- Fixed an exploit allowing a player to bypass a summon ability's
cooldown ("summon/cooldown hack").
- Fixed a client crash related to workers failing to build in an
unintended way ("new crash hack").
- Fixed an exploit allowing the Blood Mages's Phoenix to be resurrected
instantly ("phoenix hack").
- Fixed a bug allowing players to select an invalid matchmaking race
resulting in all the player's units and buildings becoming sheep
("sheep hack"). |
| 03-12-2010, 01:05 AM | #2 |
10 years late fix... |
| 03-12-2010, 04:54 AM | #3 |
I'm curious to know what exactly caused these bugs... especially the one with the sheep buildings. That just doesn't make any sense at all. |
| 03-12-2010, 06:10 AM | #4 | |
Quote:
To my understanding, Blizzard left the Demon race in Wc3's code and people edited the registry key ammrace (which stores the last played race in ladder) so it held the constant for the Demon Race. Using the quick-game button would then start a game, and you would play as the Demon Race, with sheep replacing all standard starting units. If the gametype was Solo or FFA, the game would instantly end and the bug abuser would end up with a tournament loss. I'm not sure why it's in the patch notes though, it was fixed a month ago. |
| 03-13-2010, 08:59 AM | #5 |
sheep hack sounds epic! But yay, a bunch of melee bug fixes and nothing of value was lost \o/ |
| 03-13-2010, 12:49 PM | #6 |
And there was much rejoicing. Yay...... |
| 03-13-2010, 12:55 PM | #7 |
Replays are broken again! <3 |
| 03-13-2010, 01:25 PM | #8 | |
Quote:
|
| 03-13-2010, 03:53 PM | #9 |
I made a sticky regarding the matter, and I will link to this thread for discussion. |
| 03-13-2010, 05:21 PM | #10 | |
Quote:
Fascinating! |
| 03-13-2010, 11:01 PM | #11 |
meh. I do remember that blizzard.j has something in which if thep player race is invalid it will create sheep. So I guess it is related to that old blizzard.j. lol BTW. I think there may be modding changes. Quick: try to Store null in hashtables... |
| 03-13-2010, 11:16 PM | #12 | |
Quote:
That's a cool way for safety check btw. http://www.thehelper.net/forums/showthread.php?t=146662 |
| 03-14-2010, 12:34 AM | #13 | |
Exactly, it is a bug, I am asking if it was fixed. Quote:
|
| 03-14-2010, 04:50 AM | #14 |
Zinc:if (SaveGroupHandle(InitHashtable(),0,0,null)) BJDebugMsg("works"); else BJDebugMsg("not"); I am not familiar with hashtable functions, but I guess, thats a confirmation for no change with the patch? |
| 03-14-2010, 05:49 AM | #15 |
SaveGroupHandle returns nothing, so I don't think that confirms anything. You should test Zinc:hashtable ht = InitHashtable(); SaveGroupHandle(ht, 0, 0, null); if (HaveSavedHandle(ht, 0, 0)) BJDebugMsg("works"); else BJDebugMsg("not"); However, the Jass equivalent: JASS:function Trig_Melee_Initialization_Actions takes nothing returns nothing local hashtable ht = InitHashtable() call SaveGroupHandle(ht, 0, 0, null) if HaveSavedHandle(ht,0,0) then call BJDebugMsg("works") else call BJDebugMsg("not") endif endfunction //=========================================================================== function InitTrig_Melee_Initialization takes nothing returns nothing set gg_trg_Melee_Initialization = CreateTrigger( ) call TriggerAddAction( gg_trg_Melee_Initialization, function Trig_Melee_Initialization_Actions ) endfunction |
