Report a bug so it gets fixed fast
What to include, where to post it, and the details that make a bug easy to reproduce.
Updated November 8, 2026
Bricklayer is built by one person, so a clear report is the fastest route to a fix. A good report takes five minutes and saves days.
Before you report
- Update to the latest version (Ctrl+Shift+P → Bricklayer: Check for Updates). It may already be fixed.
- Run the troubleshooter (Bricklayer: Troubleshoot (Setup & Diagnostics)) and note anything red.
- Try it once more to see whether it happens every time.
What to include
- What you did, step by step: "Opened an existing game from a link, clicked Use this game, then…"
- What you expected to happen.
- What actually happened, with the exact error text. Copy and paste it rather than retyping.
- How often: every time, sometimes, once.
- Your setup: Windows version, which AI and model, and whether Studio's MCP server is on.
- A screenshot if it is visual.
Check screenshots and logs for API keys, tokens, and personal details before you post them anywhere public.
Where to report it
| Where | Best for |
|---|---|
| Help forum, category Bug report | Most bugs. Brick checks for a known fix first, and calls in the developer if it looks like a real bug. |
| GitHub issues | Detailed, reproducible bugs and feature requests. |
| Discord | Asking whether anyone else sees the same thing. |
| Contact form | Anything private. |
Did this answer your question?
Related articles
Still need help? or start a thread in the community forum.