Patch 1.24c is live!

12-02-2009, 09:23 PM

Changelog:

--------------------------------------------------------------------------
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.

Much to the dismay of all the ladder players, it's another small bugfix-only patch. Oh, and it breaks compatibility with old replays as well. Enjoy.

12-02-2009, 09:30 PM	#2
Vexorian	Those ladder players deserved it. Is it me or did they just fix the infamous boolexpr-returns-something-other-than-1-or-0 bug?

12-02-2009, 09:34 PM	#3
Rising_Dusk	Read and be enlightened. The short answer, Vex, is no.

12-03-2009, 09:04 AM

Rao Dao Zao

Quote:

Originally Posted by Vexorian

Those ladder players deserved it.

12-03-2009, 02:39 PM

Kueken

Quote:

- Fixed a minor memory leak when using GroupEnum natives.

Am I misinterpreting this, or did they fix the null boolexpr leak, making things like BoolExprUtils obsolete?

€

Quote:

EDIT:
It's confirmed that they fixed the null boolexpr leak.

kk, seems so

12-03-2009, 07:58 PM

Flame_Phoenix

Quote:

Those ladder players deserved it.

I seriously don't get why ...

Though I am happy they finally fixed the campaign ... it was pathetic to have a game with a campaign you can't play.
Petty they didn't fixed other Blizz maps though.

Anyway, I guess MAC users should be happy now ...
Too bad I just don't care :P

12-07-2009, 07:24 PM

brainiac

Quote:

Originally Posted by Vexorian

Those ladder players deserved it.

Is it me or did they just fix the infamous boolexpr-returns-something-other-than-1-or-0 bug?

Did this get fixed or not? Didn't see any mention of it in the thread that got linked.