From what I’ve seen this has been a recurring issue since 2019.
What software company has the same issue pop up and not document the problem and solutions??? Employees move on for one reason or another all the time, smart management plans for a brain drain. People are upset because this year the problem occurred AGAIN and was solved in 4 days, only for it to happen AGAIN 2 weeks ago. (EDIT: my bad, "happen AGAIN a week ago is what I should have typed. These forum threads can be confusing!)
Nobody is going to read all of these posts from the start and several probably thought this has been an unsolved problem for a month, not realizing there was a solution 2 weeks ago. How many people have tried clearing their cache or reinstalling base on old forum “solutions” when the issue for a while has not been on the client side but rather the company’s?
As if it wasn’t already quite the show, now microsoft axes a bunch of jobs due to “redundancy” and “corporate synergies” and this problem ( which has been ongoing for 6 YEARS) is back. Not saying this is the reason, but I could see an employee solving this issue 4 weeks ago, getting told they are no longer needed a few days ago, and saying “well ok then, oops delete delete delete” on the way out the door.
Hey guys and gals, CS can’t solve a problem like this because it’s not their job to code, they have to address all the issues regardless. Shikamaru caught some flack because of his/her post, but I can understand the frustration and also confusion from this thread. Once CS employee acknowledges this problem days ago, then a different CS employee says the same thing 3 days later. While the 2nd response was probably the “update”, it came off as nobody is tracking this issue when originally reported 6 days ago.
This is my rant, I know CS is in the same boat and we all just have to wait for a 2nd hotfix this year.
One that ceased development of SC2 over three years ago, and as a result lost the personnel who managed PR for the game and personnel who knew the source code intimately.
In other words, those who are called in to fixes malfunctions within the game service are doing so cold. So unfortunately, it’s not going to be fast or as easy as it once was.
Don’t blame the TS agents, it’s not their fault in anyway.
And as someone pointed out a few posts above, the layoffs very well may be causing havoc everywhere in the company while everyone and everything is sorted out.
SC2’s code isnt just in the client that we see. There’s unfathomable amounts of code in the multiple, interconnecting backend services.
It’s doesn’t take purposeful changes to break something. Often times it’s older code that glitches or hardware that malfunctions. Sometimes it’s conditions that deteriorate so the code and/or hardware don’t know what to do.
The recurring commander level lock bug is something that’s happening on the backend.
Definitely not affecting all accounts. Mine are fine but I’m trying to keep people on Facebook and Reddit updated. I know there have been similar issues in the past where the affected accounts are ones that didn’t log in during certain stretches of time.
Hopefully we’re closer to a permanent fix here. I appreciate the communication from both the community managers and MVPs. I’d like to see some of that with regards to the league placement bugs going forward too.
For now, all we can do is share as much information as possible and work through it together.
Some kind of anti-cheat/anti-hack program reset commanders to level 5 if they’re above and there’s no entry in the “purchases” database indicating they’re allowed to.
Issue:
There’s no entry in the purchases database about free commanders, so they always get reset to level 5 if spotted by the previous program.
Workaround:
A program was made that put back the free commanders to normal if they get “hit” by the anti-cheat/hack.
Our predicament:
The workaround program encounter bugs due to changes over time, and start failing its job with many players. Or maybe it just crash and don’t restart automatically.
Random Commander selection gave me Raynor, and he successfully level to level 6.
With other posts indicating it work again above, and other indicating the opposite, I guess there’s some kind of scan&repair going on right now, that fix accounts 1 by 1.
Be more optimistic: if like I supposed, a program is checking and fixing account 1 by 1, then each server may run this program simultaneously, and the fix on US server would not delay the fix on other servers.
But once again, that’s optimism based on an unverified theory.
Same here. I’m back to level 5 on all the free commanders, Kerrigan, Reynor and Artanis.
Many weeks were past. This bug doesnt fix.
Many times with this bug. So dispointed.
I playing Vorazun, Karax and Fenix but I still want play free commander more.
