Roblox Settings Menu: Audio, Graphics, and Controls

# www.prompthubai.com.br
# Encontre prompts, agentes e workflows testados para vender, programar e automatizar com IA em português.

# Roblox Settings Menu: Audio, Graphics, and Controls

## Cabecalho
- Tipo: Conteudo
- Categoria: Games
- Modulos: 0
- Agentes: 0

## Escopo
Create a professional settings menu for Roblox, aimed at experiences that need to give players autonomy without compromising the game architecture. The system covers music volume, effects and master volume, graphics quality, visual effects reduction, and keyboard control remapping.

The prompt guides the AI to adapt the code to the real hierarchy in your Explorer, the interface names, and the RemoteEvents already in use. The requested output is a complete, commented, resilient Luau LocalScript that handles missing references and is ready to paste into Roblox Studio.

Ideal for developers who already have an interface built — or want to define a clear structure for it — and need a scalable implementation using ContextActionService, UserInputService, SoundService, and correct client-server security practices.

## Prompt Principal
Act as a senior Roblox developer, specialized in Luau, client-server architecture, responsive interfaces, and input systems. Generate a complete Luau LocalScript for a Settings Menu with Audio, Graphics, and Controls sections, strictly adapted to the context of my project provided below.

SCRIPT TYPE AND LOCATION: the main file must be a LocalScript placed in StarterPlayer > StarterPlayerScripts, because audio, graphics, and control preferences are local to the player. It must find and control the existing ScreenGui in PlayerGui. Do not use a server Script as the main solution. If I have provided a RemoteEvent to persist preferences, implement only the client-side call; make it explicit that any saving, validation, limits, and application of persistent data must happen on the server through a separate, server-authoritative Script. Never treat the client as a trusted source for currency, inventory, damage, progression, permissions, or any competitive data.

Before writing the code, analyze this context and use exactly the paths and names provided. If any essential item is blank, use a CONFIG section at the top of the script with paths and names that are easy to edit, without inventing RemoteEvents or unnecessary complex hierarchies:

[PASTE MY GAME CONTEXT HERE]
- Name/path of the settings ScreenGui:
- Main Frame and tab buttons (Audio, Graphics, Controls):
- Button to open, button to close, and button to restore defaults:
- Existing audio controls (sliders, text boxes, +/- buttons, or labels):
- SoundGroups in SoundService and their names (e.g., Master, Music, SFX):
- Existing graphics controls (dropdown, buttons, toggles, and labels):
- Visual effects that can be enabled/disabled (Bloom, ColorCorrection, particles, etc.):
- Control remapping rows/buttons and game actions:
- Default keys per action:
- Existing RemoteEvents/RemoteFunctions and their paths, if any:
- Existing save system, Player attributes, or server DataStore, if any:
- Target platforms (PC, mobile, console):
- Additional design, performance, or compatibility constraints:
[END OF CONTEXT]

REQUIRED FEATURES:
1. Implement navigation between the Audio, Graphics, and Controls tabs, ensuring that only the selected panel is visible and that the visual state of the active button is updated.
2. In Audio, control SoundService and the provided SoundGroups. Support master, music, and effects volume, with normalized values from 0 to 1, appropriate rounding, label/slider updates, and protection against missing references. Do not alter sounds individually if SoundGroups are configured.
3. In Graphics, offer at least Low, Medium, and High presets. Adjust strictly local and safe preferences, such as local graphics quality when supported, visibility/Enabled of the provided local effects, and reduction of particles/cosmetic effects. Do not attempt to enforce server-wide settings. Preserve original values of altered instances to allow proper restoration.
4. In Controls, use ContextActionService and UserInputService to remap keys for previously defined actions. When clicking an action, enter capture mode; accept only appropriate keyboard inputs, cancel with Escape, block invalid keys, prevent duplicate keys across actions, and update the UI. Do not capture input when a TextBox is focused. Keep actions and keys in a central configuration table.
5. Include a “Restore Defaults” button, simple confirmation, and full reapplication of the default audio, graphics, and control settings.
6. Keep all preferences in a local state table during the session. If I provide a persistence RemoteEvent, send only allowed preference data, structured and serializable, with debounce/rate limiting on the client. Document in a comment that the server must validate type, numeric range, allowed actions, and request frequency before saving. Do not use RemoteFunction or RemoteEvent without confirming it exists in the context.
7. Use WaitForChild with a timeout when appropriate, FindFirstChild for optional elements, organized connections, clear names, useful comments, and error handling via warn without stopping the entire menu. Avoid infinite loops, unnecessary polling, and obsolete APIs.

DELIVERY: first reply with a short list of adopted assumptions. Then provide only one markdown code block identified as ```lua containing the full LocalScript, with no pseudocode, no omitted excerpts, and no use of “...”. The code must be ready to paste into StarterPlayerScripts, with a CONFIG section at the beginning for all editable paths. After the code, provide concise instructions to test it in Roblox Studio using Play Solo and Start Server/Start Player, including tests for sliders, tab switching, reset, remapping, duplicate key, Escape, absence of optional objects, and RemoteEvent security.