Skip to content

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#

  1. Reads your place. It checks StarterGui for existing screens so the new one fits in, and looks for sounds and any existing settings code.
  2. Looks things up when it needs to. Saving per-player settings means data stores, so expect a search of the documentation for DataStoreService and its limits, cited in the summary.
  3. Builds the screen. A ScreenGui with the button and a panel, laid out with UIListLayout and UIPadding, sized with scale rather than pixels and capped with UISizeConstraint so it holds up on small screens.
  4. Writes the scripts. A LocalScript drives the panel and the sliders; a server Script loads and saves the settings, with a RemoteEvent between them.
  5. 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.