Let the Warcraft universe feel the power of The Hive and send our fellow brothers into the battle of storm, earth and fire. Shape a new son, give him the right looks and arm him with a unique spell to rule the battlefield for our good! Heed my call!

• First Place: 100 reputation points + Special Rank Icon on the hive
• Second Place: 65 reputation points
• Third Place: 40 reputation points
• Remaining entries: 10 reputation points
• Judge: 10 reputation points

Link to contest thread: [+100 Rep] Team Contest - Hive Member

Razosh made a write-up of the news from BlizzCon. You can read it here.

SPECIAL MELEE MAPPING CONTEST - 1v1

• First Place: 30 reputation points, your entry on the award icon, a Back2Warcraft T-shirt, and $100 through paypal!
• Second Place: 20 reputation points, an award icon, a Back2Warcraft T-shirt, and $50 through paypal
• Third Place: 10 reputation points, an award icon, a Back2Warcraft T-shirt, and $25 through paypal

In addition, higher quality maps will have a chance to go on competitive map pools in 3rd party leagues and tournaments.

[Link to contest thread: [$100 Prize Pool] Melee Mapping Contest - 1v1]

Note: The JASS Checker has been reverted to the old version for now because of recently discovered instabilities.

I have just updated the JASS checker with a new feature I have been working on the past few months. It is super technical, so to sum it up, it is now more precise with reporting leaks than before.

The long story is this: The JASS checker performs a static analysis of the JASS in a map. What this means is that it does not run the JASS code but sort of looks at it. The limitation is that it might not know what value a variable has so in the case of an if-statement, it would have to assume that the 'then' statements are executed and then the 'else' statements and their results are combined.
However, in this latest version it makes an attempt to keep track of the value of things. This was super important to make the JASS checker more precise, especially because the blizzard.j file makes use of the global variable bj_wantDestroyGroup to determine whether the helper function must deallocate an allocation inside an if-statement. Because of the former way this was done, it had to assume that the allocation was never leaking and thus failed to report leaks in worry that they might be false positives.

I made a mess of this. The JASS checker is complex and pretty good. Use it!