StarCraft II: Best Variables.txt for Zero Delay Micro

To achieve professional-grade micro, you need the highest possible Frame Rate Stability. In StarCraft II, input lag is tied to your frame-time. If your FPS fluctuates during a 200-supply battle, your “click-to-action” time changes, ruining your muscle memory for Blink-Stalkers or Split-Marines. This configuration locks the engine into a low-latency state.

File Path

StarCraft II stores its core variables in your Windows user profile. Editing this file allows you to access “Hybrid” settings not available in the in-game menu.

%USERPROFILE%\Documents\StarCraft II\Variables.txt

Technical Note: Always close the game and the Battle.net launcher before editing. In 2026, the game may attempt to “sync” settings from the cloud; if your edits are reverted, set the file to Read-only after saving.

Optimized “Zero Delay” Configuration Block

Search for these keys in your Variables.txt and adjust the values. If a line doesn’t exist, simply paste it at the bottom of the document.

Parameter	Recommended Value	Technical Purpose
frameratecap	[Refresh Rate]	Match your monitor (e.g., 144/240). Prevents GPU overheating and input lag spikes.
frameratecapGlue	60	Caps the menu FPS to reduce coil whine and system heat during lobby wait.
GraphicsOptionShadowQuality	0	Completely removes shadows. Shadows are the #1 cause of CPU-bound micro-stutter.
lighting	0	Forces “Low” lighting mode, which makes cloaked units much easier to see.
creepQuality	0	Disables creep animations. High-quality creep can hide widow mine burrows.
shadowmapsize	1	Reduces the shadow buffer to the absolute minimum to free up VRAM.

# Zero Delay Micro Config
frameratecap=240
frameratecapGlue=60
GraphicsOptionShadowQuality=0
lighting=0
shadowmapsize=1
creepQuality=0
creepnormalmap=0
creeptrans=0
foliagedensity=0.000000
GraphicsOptionPhysicsQuality=0
GraphicsOptionPostProcessing=0

HowTo: Engineering the Ultimate Professional Micro Setup

Beyond the text file, follow these GameEngineer.net engineering steps to eliminate input delay:

1. The “Hybrid Settings” Hack: In the Variables.txt, set GraphicsOptionModelQuality=1 (Medium) while keeping everything else at 0 (Low). This creates the “Pro” look where unit models are sharp and distinct, but the environment is flat and non-distracting.
2. Mouse Sensitivity (Windows): Ensure “Enhance Pointer Precision” is OFF in Windows mouse settings. In StarCraft II, you want a 1:1 raw input. Use the in-game sensitivity slider only if “Enable Mouse Sensitivity” is checked; otherwise, it uses your OS settings.
3. Reduce Mouse Lag Toggle: In the in-game Graphics menu, check “Reduce Mouse Lag.” This forces the game to prioritize mouse coordinate updates over frame rendering, which is essential for target-firing Banelings.
4. Display Mode: Use “Fullscreen” rather than “Windowed (Fullscreen).” Exclusive fullscreen allows the game to bypass the Windows Desktop Window Manager (DWM) composition, saving $\approx 10–15 \text{ ms}$ of input delay.
5. Sound Channels: Set Sound Channels to Low (16-32). Like many RTS titles, SC2 processes sound on the CPU. In massive battles, calculating 128 simultaneous sound effects can cause “Physics-like” lag.

Technical Explanation: Render Latency vs. Simulation Ticks

In StarCraft II, the Simulation Tick occurs every $0.0625$ seconds (on Faster speed). However, your Input Sampling is tied to your frame rate. If you are running at 60 FPS, the game only checks your mouse position every $16.6 \text{ ms}$. At 240 FPS, it checks every $4.1 \text{ ms}$.

By disabling lighting and shadows in the Variables.txt, you reduce the GPU-Busy time. When the GPU is under-loaded, it can finish drawing the frame faster, allowing the engine to start the next input-sampling cycle sooner. This is why “Zero Delay” configs look “ugly”—they are designed to make the GPU finish its work as quickly as possible so the CPU can focus on the $1 \text{ ms}$ reaction times required for high-level micro.