We’ve just released Maintenance Patch 1.23.4.8387 which fixes the following issues:

-Fixed an issue where the Season 7 maps were not present in the maps folder.
-Fixed an issue with map preview images failing to download
-Fixed an issue an issue where the matchmaking screen would sometimes not appear.
-Fix for Ladder map vetos

Thanks all – We do indeed have an out of date Polypoid. We will work on updating this asap.

Updates from the PTR will come soon. They are not in this patch.

The Season Roll is happening now and should be done shortly. thanks, Matt

Greetings Cerebrates, Commanders, and Executors,

Patch 1.23.4 has arrived!

Welcome to Season 7!

• New Wraith portrait rewards for ranked matchmaking S, A, B, and U.

Map Pool Update

• (2) Eclipse
• (2) Match Point
• (3) New Sylphid
• (3) Reap the Storm
• (4) Polypoid
• (4) Fighting Spirit
• (4) Circuit Breakers

Ranks

• S Rank - Top 1% of players
• A Rank - 7%
• B Rank - 21%
• C Rank - 21%
• D Rank - 21%
• E Rank - 21%
• F Rank - 8%

For the first two weeks, ranks will be MMR bucketed based on last season’s data. After which we will switch to the percentage-based breakdown above.

Others

• Additional string related bug fixes for EUD.
• Fixes for our most frequent reported crashes.

2020 Ladder Season 2 brings new 1v1 and Team maps to ladder!

View Full Article

The Blizzard Launcher will update after a time, but you can force it by closing and re-opening it. Then there will be a dropdown above the Launch button. You can change that to Public Test Realm.

This is live now. Have a great weekend!

No they don’t. They are files that we write to help us match up game state to find the observer desync issue that has occurred in ASL and KSL a couple of times. Unfortunately, nobody has reported the bug happening since, so we haven’t had much luck in tracking it down.

StarCraft II has been updated with balance changes, and check out the detail here!

View Full Article

We’ve just released patch 1.23.3.8319 which addresses the following: -Fix for EUD strings -Fix for save games no longer allowing players to join -Additional UI stability improvements

Hi folks,

We’re standing up the PTR again and asking for your help to test some big changes coming down the pipe.

Here’s the TLDR: we’re changing how graphics work in SCR. Please test on the PTR to make sure your video card doesn’t run into any problems.

If you want a deeper dive:

In November of last year, we tried to launch an update to the web browser that powers the Remastered front-end UI (CEF). For some people, it had performance and stability issues, so we reverted some key components of the update. However, for compliance reasons, we’re obliged to update it to a more recent version as soon as we can. We’ve been working on our implementation over the last few months, and we’d like to implement a staged rollout on PTR to get broader feedback from our community.

The first stage involves substantial changes to our rendering backends:

• Mac: Metal backend added.
• Windows: DirectX11 and DirectX12 backends added.

These new backends are likely to bring (in some cases significant) performance benefits as well as more reliable hardware compatibility as new video cards are released. Those users with older DX9 hardware will continue to be supported via our DX11 backend. This PTR version contains a “soft” deprecation of our dedicated DX9 backend and our OpenGL backend - both are unnecessary with the new backends in play. (Soft meaning that the backends technically still exist in the codebase, but we don’t anticipate anyone needing to run them anymore). In future, we’ll fully deprecate these superfluous backends.

Needless to say, the renderer is a very fundamental part of the game engine, therefore it’s critical that people try this PTR build to ensure their hardware is fully supported going forward . This change will be rolled out to our live pipeline in future, so this is the chance for us to investigate anything that needs addressing before that happens.

HOW TO RUN THE PTR BUILD?

The PTR environment will be an “opt-in” experience from the Blizzard Launcher. You can opt in and out at any time.

To access the PTR environment from the Blizzard launcher, click the dropdown list of regions. Public Test Realm will show as a separate region.

A few caveats as always to bear in mind with the PTR environment:

• There will be far fewer players online at any given time in the PTR environment - although we hope that most/all players will spend some time in the PTR helping our test efforts, outside of the testing most people will revert to the live environment. Therefore, expect issues such as longer queue times in matchmaking.
• We have fewer proxy servers available in our PTR environment. It’s likely that you will experience greater lag on PTR.
• Your settings, profiles, etc. are all separate on PTR - they will not transfer to or from PTR.

We’re excited to be moving our rendering pipeline forward to provide a better experience for our wonderful community. Thanks for your support, and let the PTR testing begin!

WHEN WILL THE PTR BUILD BE AVAILABLE?

(Soon™). We’ll update this thread when we have a more accurate date.

Thanks for that info. Unfortunately it’s still not obvious why this is crashing for you. Can you reach out to us at [email protected] and we can get some more info from you?

We’re investigating this issue, thanks for the report.

You could also try deleting CSettings.json from your Documents/StarCraft folder. That will delete your local settings file, but it will be downloaded again from the cloud on login.

Could you include a crash ID that appears on Blizzard Error when it crashes?

We just released a fix (build 8310). Thanks for the report.

We’ve released build 8310 with a fix for the map veto issue. Thanks for the report, and apologies again for the inconvenience!

Can you please provide an example map so that we can reproduce the issue?

Yes, it has. Sorry about that. We’re getting that fixed.