Data - Starcraft 2 Preparing Game

One player has a modified map file (even accidentally, due to disk corruption). The checksum fails, and the match aborts. This is why ladder forces a map re-download if verification fails.

Sometimes the percentage freezes at 0%, 50%, or 90%. Here are the most common culprits and their fixes.

This solves 60% of "Preparing game data" loops without requiring administrative access.

When you relaunch, Battle.net will rebuild its cache. The first "Preparing game data" may take 3–5 minutes. Subsequent launches should take seconds.

High-level players and speedrunners have learned to minimize “preparing game data” time:

Speedrunners aiming for campaign world records will even reboot their PC before a run to ensure a clean memory heap and no background processes fragmenting asset loads.

Go to Battle.net Settings → General → "When I launch a game" → Select "Exit Battle.net completely." This frees up system resources and prevents the launcher from re-running "Preparing" checks mid-game. starcraft 2 preparing game data

StarCraft II uses a deterministic lockstep network model. Every player’s simulation must be byte-for-byte identical. To achieve this:

Preparing game data here means building the command queue buffers, synchronizing system clocks (via ICMP or UDP timestamps), and performing a handshake that verifies all players have the same map checksum and data table hashes.

Before the orbital command descends, before the first probe warps in, before the zergling rush even crosses the mind—there is the screen. A splash of muted terran grey, the StarCraft II logo hovering like a distant starship, and that deceptively simple status bar: Preparing game data.

For the uninitiated, it’s a loading screen. For the veteran, it’s a ritual. A limbo between the frenetic ladder queue and the cold calculus of the match. The percentage crawls from 0% to 100% with the deliberate patience of a siege tank deploying. Sometimes it pauses at 50%. Sometimes it blinks to 90% and stays there, a taunt.

What is being prepared? Not just maps or assets. The game is aligning three asymmetrical nightmares: the swarm’s digestive creep, the Protoss’s psionic matrix, the Terran’s mechanical grind. It is verifying build orders not yet chosen, computing the exact second a reaper will peek over a cliff, pre-calculating the supply block that will inevitably hit at 36/36.

This screen is the last moment of calm. Here, there are no proxies, no cannon rushes, no 12-pool. There is only the whir of the hard drive (or the silent grace of an SSD) and the quiet dread of possibility. It is the antechamber of the ladder—a few seconds of virtual neutrality before the gloves come off and the GG is but a dream. One player has a modified map file (even

And then, the map loads. The data is ready. The game begins.

But for that fleeting, frozen moment, you are neither winning nor losing. You are simply… preparing.

The progress bar had been stuck at 64% for three hours. Outside, the neon signs of the Seoul district hummed in the rain, but inside the darkened apartment, the only sound was the frantic whirring of a cooling fan struggling against a decade-old processor.

Ji-Hoon stared at the screen. The text—Preparing Game Data—flickered like a pulse. For most, this was a technical hiccup. For Ji-Hoon, it was a ghost in the machine.

He wasn’t trying to play a ladder match. He was looking for a ghost. Ten years ago, his older brother, Min-ho, had been a rising star in the GSL circuit before disappearing into mandatory military service and, eventually, a quiet life abroad. He had left behind one thing: a custom map file titled “The Last Bridge.”

Ji-Hoon had finally found the old drive in a box of mothballed tech. But the modern Battle.net launcher didn’t recognize the architecture. It hung there, spinning, trying to bridge the gap between 2010’s code and 2026’s hardware. 65%. When you relaunch, Battle

The screen flashed white. Suddenly, the "Preparing" bar vanished, replaced by a command prompt that didn't belong to Blizzard. > REPLAY INITIALIZED.

The game didn't open to the main menu. It skipped straight into a match. Ji-Hoon’s hands moved instinctively to the mechanical keyboard. The clicks were loud in the empty room. He was playing Terran; his opponent was listed only as UNKNOWN.

But as the SCVs began to mine, Ji-Hoon realized this wasn't a game. The "Game Data" being prepared wasn't textures or sound files—it was a series of encrypted messages hidden in the build orders. Every time Ji-Hoon hotkeyed a group of Marines, a string of coordinates appeared in the sub-menu. Every time he dropped a Scanner Sweep, a pixelated image of a terminal map flickered in the fog of war. Min-ho hadn't just left a map. He’d left a trail.

The "Preparing Game Data" message reappeared, overlaying the match. > DATA COMPLETED.> DECRYPTING SECTOR 7.

The game crashed to desktop. In its place was a single text file and a blinking cursor. Ji-Hoon read the first line, his heart hammering against his ribs.

“I knew you’d eventually try to fix the lag, little brother. Now, look at the coordinates. I'm still waiting at the bridge.”

Ji-Hoon didn't relaunch the game. He grabbed his coat and the drive, the "Preparing" stage finally over. The real game was just beginning.