Support

Support scope

Roblox GUI Maker support is focused on the current editor, templates, generated UI code, and safe-use boundaries. This roblox gui maker support page is not official Roblox support, cannot help with Roblox account issues, and cannot troubleshoot private Roblox experiences that are not represented in the exported UI code. It exists to help visitors understand what the current tool can do and where to go next.

The supported workflow is straightforward: open a template, edit UI text and visual properties, preview the layout, copy generated Luau, and test the ScreenGui in Roblox Studio. If a problem is inside that workflow, the relevant next step is usually to check the editor, the template detail page, or the guide that explains the same screen type.

What the current editor supports

The editor supports visible Roblox UI structures such as frames, labels, buttons, image placeholders, scrolling areas, corner styling, stroke styling, padding, and layout-oriented properties. It is useful for first drafts of shops, inventories, HUDs, leaderboards, reward screens, settings menus, quest trackers, and level-up notifications.

Generated Luau is intended to create UI instances. It can help you get a visible screen into Roblox Studio faster, but it does not include full gameplay behavior. You still need to connect button clicks, player data, rewards, purchases, datastore logic, quest progress, and validation in your own Roblox project.

Current limits

The first version does not include cloud project saves, user accounts, paid plans, AI prompt-to-GUI generation, a Roblox Studio plugin, or direct rbxl or rbxm export. It also does not provide official Roblox documentation support or platform moderation support. Those limits should not be hidden because they shape realistic expectations for creators.

If a template does not match your game exactly, use it as a structure rather than a finished promise. Change names, copy, spacing, and colors before export. If the generated code creates visible UI but your buttons do not do anything, that is expected until you connect behavior in Roblox Studio.

Troubleshooting checklist

If the UI does not appear in Studio, confirm that the code runs in the right client context and that the ScreenGui is parented to PlayerGui. If a button is visible but inactive, confirm that you added a click handler after export. If text wraps badly, return to the editor and test with longer real labels. If a mobile layout feels cramped, review the mobile scaling guide before duplicating the same panel.

If the generated code contains names that are hard to script against, rename objects in the editor and export again. Script-friendly names make later LocalScript work easier. If a template feels too large, remove nonessential elements rather than shrinking every label until the UI becomes unreadable.

Safety boundaries

Roblox GUI Maker does not help create exploit GUIs, executor panels, bypass interfaces, external script loaders, hidden remote-code loaders, or loadstring-based tools. Support requests for those uses are outside the project boundary. The exporter is intentionally limited to safe UI instance code.

Support also cannot validate purchases, grant items, approve gamepasses, or decide whether a reward should be issued. Those actions require project-owned game logic and, in many cases, server-side checks. Treat the generated interface as the view layer and keep authority in trusted systems.

Where to go next

Use the template library if you need a different starting screen. Use the guide hub if you need to understand a concept before editing. Use the disclaimer if you need the independent-tool and trademark boundary. Use the privacy policy if your question is about local storage, analytics, or future contact data.

The best support outcome is not a hidden workaround. It is a clear path back to a visible template, a safe export, and deliberate Roblox Studio testing.

Maintenance expectation

This support page should change with the product. If the editor gains a new exporter, more templates, a Studio plugin, AI assistance, accounts, or cloud saves, support should explain the new workflow and the likely failure points. If a feature is not live, it should not appear as a support promise.

Support content should also keep users out of unsafe shortcuts. A fast answer that tells a creator to paste unreviewed code, trust client-side rewards, or use hidden loaders would damage the whole site. The safer answer is usually slower but clearer: inspect the generated UI, understand what it creates, then connect game behavior deliberately in Roblox Studio.

Navigation and review

This page should stay connected to the rest of the site without becoming a sales page. Visitors should be able to return to the editor, browse templates, read support notes, or review the disclaimer depending on the question that brought them here. Internal links should clarify the next step, not distract from the page duty.

Review this page after any product change that affects user expectations. If a feature is added, removed, delayed, or renamed, the utility copy should be updated at the same time as the product page. Keeping these pages current protects users from stale promises and keeps the site's SEO signals aligned with the real product.