Guides
Build an interface
Menus, shops, HUDs and settings screens that work on desktop, phone and console.
Interfaces are a good first project: you see the result as soon as you press Play, and it is easy to say what you want changed. This guide builds a settings menu end to end.
The request#
Add a settings menu opened by a gear button in the top right corner.
It has sliders for music and sound effects volume and a toggle for
camera shake. Save the settings so they come back next time the
player joins. Keep it readable on phones.What the agent does#
- Reads your place. It checks
StarterGuifor existing screens so the new one fits in, and looks for sounds and any existing settings code. - Looks things up when it needs to. Saving per-player settings means data stores, so expect a search of the documentation for
DataStoreServiceand its limits, cited in the summary. - Builds the screen. A
ScreenGuiwith the button and a panel, laid out withUIListLayoutandUIPadding, sized with scale rather than pixels and capped withUISizeConstraintso it holds up on small screens. - Writes the scripts. A
LocalScriptdrives the panel and the sliders; a serverScriptloads and saves the settings, with aRemoteEventbetween them. - Summarises what it made, where, and how to test it.
Check it#
Press Play. Open the menu, move the sliders, leave and rejoin a test server. Use Studio's Device emulator to check a phone-sized screen.
Refine it#
Reply in the same chat:
- "Match the font and colours of the main menu."
- "Animate the panel sliding in from the right, 0.2 seconds."
- "Add a reset to defaults button."
Tips#
- Name the screen you want to match, or select it before sending.
- Say which devices matter. "Mostly mobile" changes the button sizes the agent chooses.
- If you already have a design, describe it in words: layout, colours, corner radius, font.