Hi guys
I built Console Blast — an editor plugin that turns the Unreal console into a dockable board of one-click buttons.
The problem it solves: We all know the console is powerful, but the workflow is painful. You forget the cvar name, you paste commands from a 2019 forum thread, you apply three variables to calm Lumen and can’t remember which ones, and you have no idea whether the engine actually accepted the change. Console Blast fixes all of that.
How it works:
- 66 ready-made recipes across 5 columns: Rendering, Debug, Lighting, Performance, and Virtual Production — plus a Custom column for your own.
- Named after the symptom, not the cvar. Search for “flicker”, “lag”, or “nanite” instead of memorizing variable paths.
- Click to apply, click to restore. Every button captures what the engine looked like before you pressed it. The second click puts those exact values back — not the default, not zero.
- Honest feedback. Green edge = accepted. Dashed green = partially applied. Amber = the engine ignored it (read-only or overridden by a device profile). Hover for the reason.
- Build your own buttons. Title, tooltip, tags, On/Off command lines, colour marks. The command picker reads your live console registry — every cvar, show flag, and view mode in your engine.
- Value chip on single-number recipes with an inline slider.
- Keep after restart writes to
DefaultEngine.iniso the values survive editor restarts. Off by default — your team sees the change in source control. - Export/Import the full board as JSON. Hand your studio setup to the rest of the team in one file.
Supports: UE 5.5 – 5.8 · Editor-only · No engine source changes · Nothing ships in your packaged game.
Product page: blastplugins.com/consoleblast
Documentation: blastplugins.com/docs/consoleblast
Fab Marketplace: fab.com/sellers/NEW VISION PRODUCTION
Would love to hear your thoughts. If there’s a recipe you think should ship by default, let me know — I’m actively building new columns.
