The Revix Plugin

After this page you will know what the Revix plugin does inside Roblox Studio, exactly what it sends to Revix, and what it can never touch.

What it is

The Revix plugin is a Roblox Studio plugin. It is the link between the chat at /dashboard and the place you have open in Studio. Without it Revix has nothing to look at and nowhere to put the work — sending a message with no plugin connected opens the connect guide instead of sending.

Get it from the Roblox Creator Store: create.roblox.com/store/asset/122070500639295. That is the only place it is published. The current version is 7.2, shown as v7.2 in the bottom-right corner of the plugin window.

Revix builds for Roblox and nothing else. There is no player-side part to it — the plugin exists only in Studio, on whatever computer runs Studio.

What it does

Connects the place you have open to your Revix account
Sends up your scripts and a list of what is in the place, so Revix knows what it is working with
Carries out the changes Revix makes — new parts, new scripts, changed properties — as ordinary Studio edits
Puts each change on Studio's undo stack, so Ctrl+Z walks it back one step at a time

Everything happens in your open place. There is no cloud copy of your game being built somewhere else.

What it sends

Two things, and only while you are connected.

Script text. The source of every Script, LocalScript and ModuleScript in the place. This is what lets Revix search your code and answer questions about it.
A list of what exists. A flat map of path to class name — Workspace/Tower/Base is a Part, and that is all it says. No property values, no code, and no more than 5,000 entries.

The list covers a fixed set of services, written out in What Revix Can See.

What it never sends

Your place file
Meshes, textures, images, audio, or any other asset file
Property values in the routine background sync — Revix asks for a specific property only when it needs one
Your Studio settings
Anything at all while the plugin is disconnected

When you press Disconnect, the copy is thrown away: the uploaded scripts and the instance list are deleted on the Revix side, along with any work that was still queued for Studio.

What it cannot touch

ServerStorage is a protected area. Revix cannot read, create, edit, move or delete anything inside it. If you ask, you get a plain "path not found" back. Anything you want kept entirely out of reach belongs there.

Revix also cannot see anything that only exists while a game is running — no player objects, no PlayerGui, no camera. And it never sees your screen; there are no screenshots.

The trust story, in plain terms

No password and no key live in the plugin. There is no login window. It reads the Roblox account you are already signed into in Studio and matches that username against the Roblox account linked to your Revix account. If they do not match, it will not connect.
Studio holds the permissions, not Revix. Studio asks you before the plugin may reach the network, and asks again before it may write script code. You grant both, and you can review them later under File, then Advanced, then Manage Plugins.
Every change is a normal edit. Nothing is applied through a back door. If you can undo a change you made by hand, you can undo the same change made by Revix.
Nothing is saved or published for you. Revix edits the open place. Deciding when to save and when to publish stays entirely with you.