CONSOLE BLAST
PLUG IN
Click the problem. Not the cvar name.
66 one-click console recipes for Unreal, named after what actually went wrong. Click to apply. Click again to restore. Amber tells you when the engine ignored it.
66 one-click console recipes for Unreal, named after what actually went wrong. Click to apply. Click again to restore. Amber tells you when the engine ignored it.
The Unreal console is one of the most powerful tools in the editor. It is also one of the worst places to work.
You type a command. You forget the name. You apply three cvars to calm Lumen, then you cannot remember which ones. The viewport looks wrong and you have no idea whether the engine even accepted the last line. That is not a skill issue. That is a bad interface for a good system.
Console Blast is the interface. A dockable board of one-click recipes, grouped by the problem in front of you — the editor is slow, the GI is noisy, the shadows crawl, Nanite pops, bloom is too much. Each click applies a known recipe. The next click puts the previous values back.
Hours in Unreal are lost in repetition: the same five commands, every session, every level. Console Blast turns that ritual into a click, and the click into a button you designed yourself.
A new button is a title, an On list, and an optional Off list. Paste a command or pick from the engine's own list, filtered to the column you are in. Tag it so search finds it when you type "flicker" instead of the exact cvar path. Mark it with a quiet colour so it is not lost in a stack of grey.
Lighting and rendering artists who live in the viewport. Technical artists who already know the cvars. Anyone who has typed the same stat line two hundred times and is done with it. Editor-only, Unreal Engine 5.5–5.8, no engine source changes.