Since 16 September, StarCraft: Remastered players in Korea have been opening the game and finding no profile. Not a corrupted one – none. The client offers to create a new one, and creating one fails with an error.
The natural reading is that the account was deleted. It almost certainly was not, and the gap between what the screen says and what is actually happening is the interesting part.
What players are reporting
Blizzard’s Korean StarCraft technical support forum has filled with threads over the past two days, and the titles are the clearest summary available: profiles gone, cannot connect to the server, cannot delete or create an ID, and one simply asking what error 3:13 is.
The sequence matters. Ladder complaints started on the 16th and 17th. By the 18th they had become login failures, missing profiles and failed profile creation – which is the shape of a problem widening rather than several unrelated ones.
As of writing there is no official Blizzard statement. The one substantive reply in the profile thread came from a forum moderator, explaining that profiles do not disappear unless the user deletes them or signs in on the wrong account – a correct statement about normal operation that does not describe what is happening here.
Why the message says the wrong thing
StarCraft: Remastered profiles live on Blizzard’s servers, not in a file on your machine. The client asks for the list of profiles attached to your account and then draws whatever comes back.
If the answer is an empty list, the client shows an empty list. If the request fails entirely and the client treats the failure as an empty result, it shows the same thing. From the UI’s point of view those two states are identical, and the only screen it has for “no profiles” is the one that asks you to make one.
So the message is not a claim that your data was deleted. It is the client’s default state when it has nothing to show, rendered by a game that has no separate screen for “I could not reach the service”.
The evidence for this reading is the second failure: creating a new profile also errors out. A working server that had genuinely lost your profile would happily accept a new one. A server that cannot answer either request produces exactly what players are seeing.
The error codes have history
Error 3:13 is not new. The same signature – 3:13 on login, then a failed attempt to create a profile as a workaround, then still no login – has appeared on Blizzard’s English StarCraft forum before, reported by players who found friends affected at the same time. Error 3:15 shows up the same way, specifically when creating a profile.
That recurrence is useful. It means this is a known failure mode of the service rather than a novel account problem, and it means the historical resolution was the service coming back rather than anything the player did.
What not to do
Three things are worth avoiding while this is ongoing, because they cost time and cannot help.
- Do not reinstall. Nothing about a server-side profile list is stored in the install. Players in these threads have reinstalled repeatedly and reported no change.
- Do not clear caches or hunt for local files. Same reason.
- Do not keep trying to create profiles. Each attempt fails anyway, and repeatedly firing account-level writes at a service that is already failing is the one action with any real downside.
The check worth doing instead is whether you are signed into the Battle.net account you actually used. That is the only self-inflicted cause of a missing profile, and it is worth ruling out once before concluding it is the server.
The broader failure pattern
StarCraft is a 1998 game with an online layer bolted on in 2017. The single-player game is entirely local and works perfectly right now. Everything that identifies you as a player – profile, ladder record, match history – lives somewhere else, and when that somewhere else is unreachable, the game does not degrade gracefully. It presents you as a new player.
This is not unique to StarCraft. It is the standard failure mode of any long-running online service attached to a game that predates the practice of designing for offline states. Modern titles show a connection error and keep your profile visible locally; older ones have no local copy to show.
Retrofitting an old game for online play tends to produce this pattern, and the honest version of the work is rarely a patch – it is a rewrite of how the client treats the network, which is the same lesson rollback netcode taught the fighting game scene.
The same fragility shows up wherever competitive infrastructure sits on top of an old client. Korean StarCraft has been running on this arrangement for years, which is part of why the professional scene has outlasted its own sequels – the game is durable and the service around it is not, and those are different things.
What to watch
Two places. The technical support board on the Korean StarCraft forum, where the volume of new threads is the most honest real-time indicator, and Blizzard’s Korean customer support account, which is where any acknowledgement would appear first.
The thing that would change the reading is a Blizzard statement describing account-level data loss rather than a service disruption. Nothing like that exists at the moment, and given that profile creation is also failing, it is unlikely to.
It is also worth noting how little visibility players have here. There is no public status page granular enough to confirm a StarCraft: Remastered service outage, which leaves a forum board as the primary source – an odd position for a game that a national sports policy conversation now takes seriously enough to discuss alongside professional leagues.
Short version
- Profiles are stored server-side. An empty profile list is what a failed request looks like.
- Profile creation failing too is the strongest sign this is the service, not your account.
- Error 3:13 and 3:15 are known server-side login failures with prior reports.
- Reinstalling does nothing. Waiting is the fix.
- No official Blizzard acknowledgement as of writing.
If your profile comes back and your ladder record does not, that is a different problem and worth reporting separately. But the missing-profile screen on its own is a symptom of an unreachable service, not evidence that anything was erased.
Images: Wvdp (CC0), Carl Lender (CC BY 2.0) and Kai Hendry (CC BY 2.0), via Wikimedia Commons.