Warcraft III: Reforged Hotfixes -- Updated September 29 General Discussion

With hotfixes to the game today: Match processing for team games has been improved.

With hotfixes to the game today: Match processing for team games has been improved.

New Hotfixes have been applied! Including: 🔖 Custom Game List Fixes ⬆️ Match Processing Improvements 📜 https://t.co/PROLPUFHxW

With hotfixes that have just been applied: Fixed an issue where Ping was not showing accurately in the custom game list. Added a Region tab to the custom game list. The game result server has been updated to improve match processing.

With a bundle of hotfixes that were applied moments ago:

• Fixed an issue where the Campaign Manager could crash the game.
• Fixed a crash caused by setting the field of an ability using BlzSetAbility*Field and then removing that ability from a unit.
• Fixed an issue with ranks being incorrectly formatted for three-digit numbers.
• Ping in custom games which cannot be correctly retrieved should no longer be displayed as “?”.
• Fixed a server performance issue.

11:30 a.m. PDT – August 22, 2022

• Leaderboards are recording incorrect data.
• Players may receive negative MMR. This should be a temporary state while the game calculates through past game results.
• There is a Leaderboard formatting issue when ranks go past the 100 rank.
• The Campaign Manager may cause crashes in Campaign.

Warcraft III: Reforged Hotfixes -- Updated August 19 General Discussion

August 19, 2022 – 10:45 a.m. PDT We’ve just applied hotfixes to the game to address the following issues: Fixed an issue preventing LAN functionality. Fixed an bug that prevented AT players from matching against RT players.

August 19, 2022 – 10:45 a.m. PDT We’ve just applied hotfixes to the game to address the following issues: Fixed an issue preventing LAN functionality. Fixed an bug that prevented AT players from matching against RT players.

2:45 p.m. PDT – August 18, 2022

We’re currently investigating and working to fix the following issues:

• A bug is causing the game to freeze or crash when joining a LAN game.
• Arranged Teams (AT) are not able to match against Random Teams (RT).
• Match processing and display errors.
  • At this time, we believe that matches are being correctly recorded, and will be displayed as expected once this bug is fixed.

Patch 1.33 is now live and features: 🏆 Ranked Play 🔝 Leaderboards 👤 Player Profiles ❗️ and more. 📜… https://t.co/O9lN1ig5cH

The latest patch is now live and includes Ranked Play, Player Profiles, Leaderboards, and more.

View Full Article

The latest patch is now live and includes Ranked Play, Player Profiles, Leaderboards, and more.

View Full Article

OP updated with full patch notes for version 1.33.0.

Complete patch notes are here.

✅ Testing of Patch 1.33 has completed ⚙️ Updates begin August 17, 10 AM PDT 🛠 Maintenance expected to take 4-8 hour… https://t.co/GLm4PYLd9L

We’re completing our testing of Patch 1.33, and we plan to deploy this update on Wednesday, August 17.

We expect to take the game offline at about 10:00 a.m. PDT on August 17, and we expect maintenance for this patch to take 4-8 hours.

Thanks again to everyone who tested the patch on our PTR and provided feedback in our PTR Discussion and Feedback forum. We really appreciate it!

InsaneMst:

I have experienced some issues with an error thrown by the World Editor in PTR 1.33 patch: invalid object id. This error happens sometimes with default HD units that have no counterparts in SD mode.

Hello.

Can you please specify a test map and steps we might take to reproduce this error?

Thank you!

We have now closed the 1.33 test environment for public testing. We will continue our 1.33 testing internally, and we’ll let you know when we’re ready to patch the live game. Thank you very much for all of your testing and feedback.

In about 15 minutes, at 10:30 a.m. PDT, we’re going to deploy hotfixes to the PTR that should address the following:

• Fixed an issue where the Terrain Palette would crash the editor in both SD and HD modes.
• Fixed an issue where the FileAliases.JSON had incorrect file paths for some textures.

Thank you very much for all of your testing and feedback!

Is that the SD or the HD editor? Thank you.