Quick start guide.

01Get access

Vivid is in closed beta and is not for sale yet. Keys are issued in the Discord. A key is a lifetime key tied to one Discord account.

1. Join the Discord and ask for a key.
2. Redeem it with the bot. Your Discord account is your login, so there is no password to keep.
3. Open your account page and sign in with the same Discord account.

02Install

Vivid runs on Roblox for Windows 10 and 11. You install the launcher, and the launcher fetches the client for you and keeps itself current.

1. Sign in on the account page. The download is at the top of the dashboard.
2. Choose Download for Windows and run the launcher.
3. Sign in with Discord in the launcher.

After a Roblox update you do not reinstall anything. Offsets are served from our side, so expect the occasional gap while a patch is handled.

03First run

With the launcher signed in, join a game in Roblox. Vivid attaches from outside the game process and shows a hint with the key that opens the menu.

The first time you open Vivid on an account, a short intro tour walks through the basics, including your accent color and your menu key. It shows once per account. You can replay it from Settings > General with Show intro again.

The menu is grouped into Combat, Visuals, Movement, Player list and Settings. The search at the top of the menu finds any setting.

04The menu key

Press the menu key at any time to show or hide the menu. The default is Insert. You can pick another key during the intro or later in Settings > General > Hotkeys.

The same Hotkeys section has a Panic key and an Unload key, and a Pause while typing toggle so your binds do not fire while you chat. Unload Vivid on the same page removes it from the game.

05Configs and sharing

Open Settings > Configs to manage saved setups. Configs are stored in the cloud, so they follow your account.

• Save the current game's settings under a name.
• Load a saved config into the game you are in. Loading asks first, because it overwrites that game's current settings.
• Share with a code. The share code for this game's settings is copied to your clipboard, and anyone can paste it into Import code to load it.
• Search and sort your list by name or by when it was modified.

You can also open a support ticket in the Discord and say what you want changed. The assistant edits your config and the running client refreshes live.

06Per-game settings

Each game keeps its own settings and saves them on its own. You do not have to save anything by hand for a game to remember its setup. If a cloud save fails, it is retried.

A game you have not played before starts with every feature off, instead of carrying over the toggles from the last game. Loading a saved config or importing a code replaces the settings of the game you are in.

07Unsafe mode

By default Vivid is external: it reads the game from outside its process and writes nothing into the game's files. A few features need to hook the game itself. They stay locked, and show Requires unsafe mode, until you turn it on.

What it unlocks

• Native chams, drawn by the game itself, including the hidden-parts color.
• World chams and the custom sky.
• The Raycast hit method for silent aim.
• Lua scripts that write to game memory.

Find the switch in Settings > General > App > Unsafe mode. Turn it off in the same place.

08Lua editor

Vivid has a built-in script editor and runtime for Luau. Open it from Settings > Tools with the Script editor switch, which can also have its own key.

• Tabs. Each script gets a tab. The plus button opens a new one, and a dot marks unsaved changes.
• Execute and Stop. Run the active script and stop it again. The status shows Not attached, Attached or Running.
• Save, Open file, Delete manage scripts, and Scripts lists the ones you have.
• Output. Detach output moves script output into its own window, and Dock output puts it back.
• Assistant. A pane next to the editor that helps with scripts.

The Explorer browses the game, and Script API docs lists every scripting function and its tier. A runaway script cannot freeze the overlay, and its changes are undone when it stops. Writing to game memory from Lua needs unsafe mode.

09Get help

The Discord is the place to ask. Open a support ticket there for account, key or config problems, and say what you were doing and which game you were in.

Check the FAQs and the changelog first. A problem you hit may already be fixed in a newer build.