Patch 1.24c live!

[Pyritie]

Source: http://forums.battle.net/thread.html?topicId=21559815844&sid=3000

In the process of optimizing the map editor we have made several changes to improve its usability. These updates are now live on the Westfall (PTR) and players are welcome to test the following changes:

--------------------------------------------------------------------------
Patch 1.24c
--------------------------------------------------------------------------

FIXES

- Fixed a problem with the "Chapter Six: The Culling" human campaign map
that was preventing it from loading.
- Fixed an issue that allowed JASS functions to return incorrect values
under certain conditions.
- Fixed an issue that caused the TriggerEvaluate native to return
incorrect values under certain conditions.
- Fixed a minor memory leak when using GroupEnum natives.
- Fixed a crash when using the CreateImage native on PPC Mac.
- Updated Mac World Editor to work with recent JASS changes.

 

[Lambdadelta]

Hooray for Mac users!

 

[Eccho]

Stuff about those fixes can also be found more of here:
http://www.wc3c.net/showpost.php?p=1112715

 

[Coolty44]

It seems like Blizzard is on a patching spree that isn't improving banner systems or Dota for Mac users!!! What joy!!

 

[xp3r009]

Nice, another patch. Probably soon enough I'll patch it, once I get my Warcraft interests back soon enough (hopefully map making).

 

[HINDYhat]

lol @ GroupEnum leak fix.

IT'S ABOUT TIME.

 

[Eccho]

So, if the groupenum null-leak is fixed, does that mean that it wont leak on triggerregisterevent functions are not leaking as well. I imagine it would be related to the boolexpr?

 

[Deaod]

Eccho, TriggerRegister* functions never leaked in the first place.

 

[Eccho]

lol, silly me then :/

Edit: I thought all null params leaked. Damn it me.

 

[Craka_J]

Though it isn't a significant patch, any update that improves their flawed World Editor is totally fine with me!

 

[Duragon]

You shouldn't make these site-wide announcements until the patches go live. It would better suffice as a Warcraft Discussion forum topic.

{EDIT}
This is not a heavy modification. There has been a fix for the GroupEnum leaks for years at this point, and the fix really changes nothing about the ways we do things. The Mac fixes and their fixing the return bug usage in their own campaigns are the best things in this patch, really.

 

[reason 3]

- Updated Mac World Editor to work with recent JASS changes.

It was about damn time...i got bored of seeing thread why i get these BLA BLA BLA errors?

 

[Eccho]

It is already up, why dont you complain there instead now.

Edit, saw you did

 

[Duragon]

I'm not sure what made you think I was complaining at all. Just pointing out that this patch, aside from the Mac stuff and campaign fix, is rather meaningless. (Unfortunately)

 

[D4RK_G4ND4LF]

I tried to find a workaround for these damn enumeration leaks for like 3 hours!!!!!11

well....better now than later

 

[Duragon]

I tried to find a workaround for these damn enumeration leaks for like 3 hours!!!!!11

There was some solution to it posted at Warcraft 3 Campaigns years ago. A simple search there revealed to me that you just had to use a TRUE boolexpr. I'm amazed people don't actually refer to these resources before doing the work on their own.

 

[Xarwin]

Oh my god!
They made another patch!

 

[thedeathunterxx]

nice patch, even though i have no idea what it means lol.

But i hope that in the future they will update the terrain editor...lots of problems still in there.

 

[Rui]

Last weekend I found out that "The Culling" was broken. Thank god someone informed them about it.
I guess we should be glad Blizzard is still releasing patches. It seems little fixes are the preparation of something bigger; let's hope it is.

On the process, an unexploited GetLocationZ() would be great to have. IsUnitInRange() and similar functions could also be put to work (I don't think they're functional?). There are workarounds for these, but it'd still be good to have them.
Battle.Net's disconnection problems have also been mentioned. I wonder if this is somehow connected to any specific trigger action (function)? I noticed I don't disconnect in every map.

EDIT: If they are indeed fixing their own campaigns as Duragon claims, then it would also be appreciated if they could set each map to use the most recent patch balance changes on units. This possibility is reduced since they would probably have to test their campaigns all over for balance issues.

 

[D4RK_G4ND4LF]

There was some solution to it posted at Warcraft 3 Campaigns years ago. A simple search there revealed to me that you just had to use a TRUE boolexpr. I'm amazed people don't actually refer to these resources before doing the work on their own.

I'm amazed people don't actually think other people are insanely ****** instead of thinking that they tried to express something else

I was talking about GUI (I only make GUI stuff) so it IS hard to archive
(however I knew about the boolexpr thing even before I read the linked post)

nevertheless I didn't mention that in my post so you couldn't know...

topic: a friend of mine told me that the patch appears to work with non-english wc3 versions, too

 

[yanbaihu]

Sorry for being a noob and all... but exactly how do you DL this patch? Would very much like to have it to fix WE for my mac. Thanks!

 

[Eccho]

The patch is only in it's "beta stage" you could say. In order to download it, connect to the westfall server before entering b.net

 

[Deaod]

Eccho, i thought so too. Then i tested them because i was already testing null boolexprs. Then i noticed that they dont leak in 1.24b (unlike those enums). The whole "replace TriggerRegisterAnyUnitEventBJ" was for naught (not like i ever did it).

I was talking about GUI[...]

Theres a simple solution to all GUI problems: Use JASS and use the workarounds available there.

 

[yanbaihu]

The patch is only in it's "beta stage" you could say. In order to download it, connect to the westfall server before entering b.net

Oh. Okay.
Thanks heaps!

 

[Craka_J]

nice patch, even though i have no idea what it means lol.

But i hope that in the future they will update the terrain editor...lots of problems still in there.

Just about all the fixes in the patch benefit the World Editor. Mainly for Mac users, but still.

 

[M_Vegeta]

 - Fixed an issue that allowed JASS functions to return incorrect values
under certain conditions.

this bug wasn't supposed to be fix in 1,24 b ?

still they didint fix pool crash >.>

 

[Eccho]

Pool's crash? When?

The incorrect values thingy has to do with the return bug again, now you can't return it no matter what (as far as what I read from Poot's post on wc3c). If you try to do it it will result to the thread crashing instead.

 

[rover2341]

Theres a simple solution to all GUI problems: Use JASS and use the workarounds available there.

...

Anyway Back on Topic, As old as warcraft 3 is now, the fact there still doing these updates is great, i don't expect them to do anything more then just bug patching though for the most part.

 

[Weep]

To any Mac users who previously used the Scripts folder workaround for the broken World Editor, when you install 1.24c, simply remove or rename that folder - you won't need it anymore.

 

[Azeroc]

Oh well... I wish they would release another big patch which would add some better stuff. Like Hashtables were implemented replacing sucky Indexing system for GUI users which wanted MUI.

 

[Dr Super Good]

Wheres my Diablo II patch...

WC3 is working good enough as it is, Diablo II is not.

 

[Eccho]

relax, the team who developed this patch is not the same as the ones working on the d2 patch I think.

 

[Dr Super Good]

They are the same...
Do you never read them complaining?

Just read the D2 patch delay excuse thread on their forums.

 

[Eccho]

this?

Update - 11/18
We've recently completed a revised version of the Diablo II 1.13 patch that removes the increased stash size. A larger stash will unfortunately no longer be a feature included in patch 1.13 due to the previously mentioned concerns. As higher priority work continues on Warcraft III we're hoping to complete our quality assurance tests for the 1.13 patch in the next few weeks. But as always, the types of issues that may appear and take higher priority are rarely foreseeable. We continue to plan a release based on our best intentions.

right. Got that

 

[Deaod]

Like Hashtables were implemented replacing sucky Indexing system for GUI users which wanted MUI.

Hashtables were not implemented with GUI in mind. They were implemented as a compensation for fixing the return bug. As a side effect GUI got hashtables.

Anyway, for the record: The "return bug" is still there (kind of). Refer to the wc3c.net thread for the details.

 

[Rui]

I read somewhere in our forums that storing Ability IDs (or something) is not working properly. Plus, when I was going through the Hashtable functions and I clicked one of them (unit, was it?), the World Editor crashed.

 

[Tylon]

Wait, does this mean that World Editor for Mac now is the same version as for PC?
I mean, my Mac's WE right now is version v1.20d, and my PC's is 1.24b. I've had some problems with imported files when I load my PC-created map in my Mac.

 

[Eccho]

Hashtables were not implemented with GUI in mind. They were implemented as a compensation for fixing the return bug. As a side effect GUI got hashtables.

Anyway, for the record: The "return bug" is still there (kind of). Refer to the wc3c.net thread for the details.

I interpret it as the return bug is not possible to do anymore, since it causes a thread crash (however, yes it does still compile bug cannot be actually used in game).
Is there any other post somewhere more than this one let me know Deaod .__.

Rui, you might have been referring to this:

// Not currently working correctly... 
constant native AbilityId                   takes string  abilityIdString   returns integer 
constant native AbilityId2String          takes integer abilityId          returns string

Those have never worked properly afaik

 

[Deaod]

http://www.wc3c.net/showthread.php?t=108152 Im talking about this one.

 

[Eccho]

Lolwoah... I totally didn't know about those

Edit, so this is still working anymore? Has the patch really been out on westfall for over 10 days, really?
Edit, meh I guess they are

 

[Weep]

Wait, does this mean that World Editor for Mac now is the same version as for PC?
I mean, my Mac's WE right now is version v1.20d, and my PC's is 1.24b. I've had some problems with imported files when I load my PC-created map in my Mac.

My WE version is 1.24c after updating. It's still not equal to the WE for PC - still no shift-double-click to set out-of-range values in the object editor, still crashes if you click away after editing a trigger's name instead of hitting enter...but at least the JASS syntax checker has been brought up-to-date.

 

[MGCǂSpectre]

Well, any race change like nerfing human for example would make even the few left players, quit war3 for good. So we wouldn't really expect such changes.

Again, except for the fixes that looks boring, what is left for adding in patches is new GUI triggers, smth that Blizzard doesn't wanna do. It's enough to say that you don't even have a unit function when you have 'A unit finishes training a unit' and the only reference is Trained unit, no reference for the building doing the training.. and many many others.

 

[Eccho]

GetTriggeringUnit is a response to alot of events, hell, some of the extra responses is just slower and could be replaced by GetTriggeringUnit in general. So yeah, GetTriggeringUnit do reference to the building which is training the unit.

I got your point tho.

 

[MGCǂSpectre]

Now from a gaming experience point of view, because such patches to me are uber useless.

Such 'Patches' if we can even call them so are from the type that make me say like many others - Oh wooow it changed my life, not'. Seriously when you don't have problems with the game this is just COMPLETELY useless to many of us. No1 says race changes anymore - no thx or a few race changes and the few that play war3 will quit this overabused game for good GG.

But without balances there is what to do instead of these needless to 90% of the people patches - Did Blizzard do ban some guys that use phoenix hack that I reported? No. Do they ever do anything to ban them for ever? No. Still MHers and all that shit is there - so happy patches! They increase the gaming fun sooo much with such a MUST SEE patches.

 

[Azeroc]

1.24 patch made maphacking impossible

 

[MGCǂSpectre]

1.24 patch made maphacking impossible

Problem solved? Dunno, sometimes I'm thinking my opponent is either scouting a lot or he uses MH. If he's scouting, not MH, then there are a bunch of other hacks that even when you place them right in front of Blizzard, they don't give a shit.

From gaming - pls nerf hackers - IMBA, from mapmaking - pls add more GUI triggers, that's ridiculous not doing it.

 

[Azeroc]

Basically you are banned if you use any program which manipulates BNet connection. A little time before 1.24, Warden's protection was expanded to custom games. I know that there is chance to maphack if you dc yourself from BNet before turning on maphack (which can be easily discovered just doing /whois)

Well I never seen game with editor who has its all coding language functions in User Interface. But yea, GUI could use some more functions - hashtables were great addition. It would be nice if they add locals for GUI, but I think it could be impossible since locals works only in their function meaning it would fail, since for GUI IF's and even unit groups are in their own function.

 

[SerraAvenger]

Well I never seen game with editor who has its all coding language functions in User Interface. But yea, GUI could use some more functions - hashtables were great addition. It would be nice if they add locals for GUI, but I think it could be impossible since locals works only in their function meaning it would fail, since for GUI IF's and even unit groups are in their own function.

Do hashtables work in GUI? Last time i checked them out (1.23b?), there was basically no GetHandleId support and most of the Hashtable stuff didn't work either.

 

[Azeroc]

1.24 made hashtables for gui...

http://www.hiveworkshop.com/forums/trigger-gui-editor-tutorials-279/hashtables-mui-133407/

 

[xXxTWiST3DxXx]

Thanks for keeping us informed!