While you may or may not be right about very few of us understanding the technical details behind the issues, it would help to put us at ease to show that the dev team is looking into the issue and have an idea about what the issue it and are working on it, and not just this almost radio silence on a game we know is almost abandonware by blizzard, however this response to Shikamaru, I find very unprofessional and impolite in the “tone” of the writing. I can see that Shikamaru was being antagonistic in his comment, but even still that doesn’t warrant someone who is supposed to be the first face we as a community see while browsing the forums to reply in kind, as it both insults Shikamaru, and we the other customers of blizzard who have been struggling with an ongoing issue, which has been happening on and off for a long time, even before it was locked to just raynor, kerrigan, and artanis, it also used to happen to all commanders. Thank you
Today random commander gave me Artanis, and I could confirm the bug was still there (got 0 exp because it’s “capped”).
And yet I played with some players that had Raynor level 10 and 107, and maybe others.
So it would seem some players may escape it.
Maybe the bug is acting differently this time?
Is there any update from the Blizzard team?
To be fair Shikamaru this started YEARS ago. Based on the Reddit posts you find when you look for info on this one, this started around over half a decade ago at least, and just keeps coming back. Blizz has had a long to time figure this one out.
I personally don’t expect an explanation of what is happening behind the scenes, I probably wouldn’t understand anyway. But some info on why such an old bug is taking so long to fix, or some feedback on an eta might help calm the swell a bit?
Indeed. It’s something that has been recurring. However, Shikamaru was referring to this most recent occurrence, which can give someone who doesn’t know any better the impression that Bliz is letting this recent occurrence linger. That’s not the case.
Two occurrences ago, they thought they had it figured out but they were wrong. The important point being, with each recurrence, they learn a little more on how to resolve it.
Understand that those who knew the code of SC2 and all its interacting parts are gone. In order to fix issues now, personnel have to be pulled from other places in the company to investigate and resolve them, all while not having intimate knowledge of SC2’s code.
The issue there is assuming that all bugs are easy to locate and fix and have a known, set path to resolution. But, not all bugs are easy to locate, or analyze, or fix without breaking something else, etc. All it takes is one uncertainty in the chain and an ETA could be impossible.
As for the engineers telling the TS agents to just keep telling us, “we’re still looking into it” over and over every few hours/days/etc, that’s no more informative than, "we’ll post again when we have something new ".
We appreciate the updates, we’re all frustrated as I’m sure customer support is too. I had sort of assumed that the folks who wrote the code were off on other things (or companies) and having new people come in cold adds to the wait time.
It’s a chance for everyone who’s waiting to find other ways to spend our time and check back when we’re ready.
sheeesh i sure hope this has nothing to do with the lay offs… XD but im pretty positive it has somewhat does… lmao
It’s the same damn bug, dude
I just started playing Starcraft 2 again and leveled up Raynor to lvl 5 and now it’s capped. It states that I need to purchase the game but I already have it purchased. Please fix 
Your post is EXACTLY what people are looking for Leviathan. Someone to explain what you did here.
It’s been hard to fix because the people who knew SC2 code are gone and people who don’t know the code are trying to fix something that has a degree of uncertainty as to it’s actual cause. The former culprit isn’t it this time.
That’s literally all most are asking for. A bit of communication. I know things are stretched at Blizz with the massive layoffs and so many quitting even before that, but a little message or two about the happenings goes such a long way!
If someone hops on and takes a minuet to post and tells us mere mortals: “Hey I know it looks like the same bug, but the cause is different, (complicated) and we’re trying to find out what it is with limited resources.”
Most (not all) would go: “Thanks for letting us know, best of luck with the fix.” and go back to playing with the other commanders for a while.
Yes, everyone, including Bliz, knows that. What most don’t know is the conditions surrounding it. Please read my next post after the one you replied to.
I’m with you there. Bliz has had terrible communication practices for a long time. Unfortunately, I don’t see Bliz changing that, even with MS now in the picture.
Just don’t blame the TS agents. They are only middlemen between the fixers and us. If the fixers don’t give anything to the TS agents, then the agents have nothing to pass on to us. That’s why you always see them saying, “If we get any updates, we’ll post them here.”
Just out of curiosity, historically has it always affected EVERYONE or is it piece-meal. Most I know are affected by it, especially the most recent two. HOWEVER, as I’m biding my time and leveling up other commanders, I keep getting matched with other Artanis, Raynors, and Kerrigans that are way past 15, prestige 1-3, and several mastery points. Including my most recent match…
Based off my observations and experience, it’s not everyone.
There’s usually 2 aspects to it. The first is that it affects one region at a time. The second is that it doesn’t affect everyone in the region. For example, I play on both AM and EU. During every outage so far, it hasn’t affected me on either one.
So that matches up with what you are seeing.
Ive had my first 3 commanders stuck on level 5 for the past 2 weeks and nothing seems to fix it. Ive tried deleting the game and signing in and out of my account but this problem continues. Ive had this in the past but logging out or doing a mission or 2 fixes it normally but this one is not going away. Do you have an idea of when this will be fixed?
Same here for all 3. Why hasn’t this been fixed yet?
Why has this not been fixed yet. I cannot play my favorite champion Artanis. He is free and locked out at level 5 55K for no reason. Please it has been a week already.
Probably due to the massive lay-offs that just happened. They cut like 2K employees across Blizz/Acti/MS. Likely a sh*t show over there rn.
I’m inclined to agree.
You got to pay you knowledge base a retainer… at this point then you got to stop defending them and work this logic up the chain. like I know you don’t want to make this your boss’ problem but when the ball has been dropped by them that is the only way to inspire change when bad decisions have been made.
What I don’t understand is that this is not the first (or second or third or etc.) time that this has happened. If there hasn’t been any change in code in forever, why is it happening again?