Blueprint-Enabled Overlays
Some overlays include a configuration file that powers a dynamic GUI editor. These overlays are often created via Quick Cast or by manually defining a config using meta.json.
This makes the overlay customizable via a visual editor — no code required.
What Blueprint Overlays Look Like
When viewing an overlay with a configuration schema:
- A Template Settings panel appears on the left side
- All fields defined in the config will be rendered as interactive controls (text inputs, checkboxes, sliders, dropdowns, etc.)
- Users can upload assets (e.g. images), adjust behavior (e.g. duration), and modify text fields live
- All changes are saved and reflected in real time inside the preview window
The specific layout and controls shown depend entirely on the structure of the config file used in the overlay.
Typical Use Cases
Blueprint overlays are ideal when:
- You want to let collaborators or non-coders customize the overlay
- You're distributing a template for reuse
- You want to expose frequently edited values without editing HTML/CSS/JS
Example Fields You Might See
- Event Trigger – what type of Streamer.bot event triggers the overlay
- Alert Duration – how long the overlay stays on screen
- Alert Image – upload and preview a visible graphic
- Main Message – formatted text, often with placeholders like
{user}
These inputs directly affect the overlay’s behavior via your script.js logic or HTML placeholders.
Customizing the Blueprint
Blueprints are powered by a config schema. For details on how to create or edit one, see: