1. Join us in our custom games night on Saturday, July 28. If you'd like to create a map for the night, check out the map challenge!
    Dismiss Notice
  2. The results for Texturing Contest #28 are out! Step by to congratulate our winners!
    Dismiss Notice
  3. Join in on Icon Contest #17 and show your interpretation of a legendary equipment set!
    Dismiss Notice
  4. We've created the Staff Job Openings thread. We're currently in need of icon, video production, and social/multimedia positions to be filled. Thank you!
    Dismiss Notice
  5. Music Contest #10 Retro is out! Join us for some retro/vintage fun!
    Dismiss Notice
  6. Don't be stagnant - embrace change! The time has come to evolve and join the Techtree Contest #12 - Evolution.
    Dismiss Notice
  7. On May 20th a new law about privacy and data processing comes into work in the EU. I am no lawyer and I need help figuring out if we comply and if not, what we must do about it. Please message me if you can provide any assistance. Read more. Ralle
    Dismiss Notice
  1. StoPCampinGn00b
    Created by StoPCampinGn00b
    May 2, 2018
    Blizzard needs your help!

    Position: Software Engineer, UI
    Location: Irvine (Southern California, USA)
    Division: Classic Games (Warcraft 3)
    >Link<

    Responsibilities
    • Work closely with designers and other engineers to establish a shared vision for compelling UI features.
    • Implement functional and elegant UI features from approved concept images and paper designs.
    • Develop back-end functionality to support front-end features.
    Requirements
    • Comfortable working in both C++ and JavaScript
    • A minimum of 5 years’ experience in a professional software development environment.
    • A solid understanding of best practices and techniques regarding JavaScript
    • Extensive expertise in working on front end view frameworks, such as React, Ember, Vue, etc…
    • Experience with web page layout and styles optimization
    • Expert analysis, troubleshooting, and debugging skills
    • Expert knowledge of computer science fundamentals, including algorithms, data structures, and design patterns
    • Self-motivated with strong initiative
    • Able to work in a fast-paced, dynamic work environment
    • Passion for Blizzard games
    Pluses
    • Experience developing for multiple platforms.
    • Experience with Node and NPM.
    • Computer Science or related degree.

    This announcement is specifically for the position of UI Software Engineer, but you can find other Classic Game job openings here.

    Either way, please contact our friendly neighborhood Blizz employee, @Kam, directly in private if you are considering joining the team.
  2. StoPCampinGn00b
    Created by StoPCampinGn00b
    May 1, 2018
    [​IMG]
    Patch 1.29.2 is LIVE on Battle.net

    The Battle.net ladder has been completely reset, and a flurry of more bugs have been squashed. 13+ player bugs, World Editor mini-map bug, and a few changes to some ladder maps and natives have all been implemented.

    The Blizzard post also includes a list of known issues.

    Stay tuned for more updates and make way for 1.29 projects utilizing things like the new natives, increased limits, and 24 players to come forth!

    Path 1.29.2 (PTR)

    You guys know the drill :]

    The 1.29.2 PTR includes an even longer list of bug fixes than the previous 1.29.1 patch, including fixing the World Editor mini-map, fixing arranged team for ladder, some changes to a couple natives, a couple 13+ player fixes, and various changes to things like ladder maps and other technical aspects.

    There also includes a statement on improving the process and expanding communication.

    Full patch notes, statements, and download links to the PTR are located here on Blizzard's forums.
    1.29 Megathread - 1.29.1 Thread

    ~Will edit this thread when the patch leaves PTR and goes live on the main Battle.net servers
  3. StoPCampinGn00b
    Created by StoPCampinGn00b
    Apr 13, 2018
    upload_2018-4-24_0-17-22.png
    Patch 1.29.1 is live on Battle.net!

    This fixes the majority of significant issues and bugs that were on the PTR. We're hearing and getting reports of a bunch of custom maps that broke before are up and dandy again, so that's good news.

    In the full patch notes from Blizzard, there is also a list of known issues that should be fixed in later hot-fixes / patches. If there are issues still worth reporting that aren't acknowledged by Blizzard, please report them. Cheers, on to the next ones!

    Patch 1.29.1 PTR


    Patch 1.29.1 aims to fix a multitude of issues with installation, broken custom maps, and some faults with the editor. It also releases a few changes such as increasing the BNet channel and clan limit to 255. Please test and see if this patch fixes the issues with custom maps, the editor, GB installation, and other bugs!

    Full patch notes and PTR version download:
    https://us.battle.net/forums/en/bnet/topic/20762147702

    NOTE: I will edit this thread when 1.29.1 goes live; no need for another thread when this and other hot fix patches releases.
  4. StoPCampinGn00b
    Created by StoPCampinGn00b
    Apr 10, 2018
  5. Frotty
    Created by Frotty
    Mar 23, 2018
    [​IMG]

    1.29 AND PTR


    The wurst team is excited and curious to see what the new PTR changes will mean for the wc3 modding community. We are anticipating the release to the stable battle.net realms, and will add support to the wurst toolchain as soon as possible.

    At this time, we do not plan to have a separate branch to support PTR installs. However, if the classic team continues to make extensive use of the testing realm, we may consider that option in the future.

    We are actively thinking about what the PTR changes will mean for us and how it should affect 2018's timeline. For example, now that 24-player maps are coming, we will prioritize support for editing map player metadata from vscode.

    [​IMG]
    24 unique player-colors, in wurst!


    UPDATES


    We are quite a bit late with our blog post this month, as there were no major updates to present and we were focusing on quality work as well as keeping an eye on Wurst's stability. That being said, in march we revamped the lambda syntax for more flexibility and cleaner code. Additionally we again have received a number of contributions from the community.

    • Type inference plus new block handling for lambda expressions and closures
    • We resolved several opened issues (#44, #45, #48) and merged 7 pull requests (#47, #49, #50, #51, #51, #54, #55, #56) for the standard library.
    • The Wurst Setup received several stability updates and we are working on further integration with the wurst tool suite.