Using mods

Mods change Roblox client files on disk before launch (sounds, textures, cursors, skyboxes, etc.). They do not reskin the Carbon launcher. That is themes.

Mods page layout

Section	Purpose
Installed	All built-in and community mods; toggle enable, expand settings
Cursor	Dedicated UI for Cursor Swapper (presets + custom PNG)
Settings	Mod-related app preferences (disk usage, install options)

Enable a built-in mod

1. Mods → Installed.
2. Toggle the mod on.
3. Expand the card to change dropdowns/toggles (theme, colors, etc.).
4. Launch Roblox again, mods do not hot-reload mid-session.

Built-in assets ship inside the app; your choices save to bin/configs/mods/<id>/config.json.

Install a community mod

1. Obtain a folder or .zip with a valid mod.yaml at the root.
2. Mods → Installed → Install folder or Install zip.
3. Carbon copies the pack into mods/<id>/ and validates the manifest.

Broken manifests show errors in the UI or logs. Compare with built-in examples.

Priority and conflicts

If two enabled mods touch the same file, higher priority in mod.yaml wins. Disable one mod to test conflicts.

Presets (menu icons, sounds, skybox, …)

Many built-ins use preset: shorthand instead of listing every Roblox path. See Preset operations for folder layouts and app workflow.

Authoring mods

Ready to ship your own pack? Start at Mod authoring and the mod.yaml reference.