What Revix Can See
After this page you will know exactly which parts of your place Revix has a picture of, which parts are locked, and how to phrase requests so they land somewhere it can reach.
The services it lists
While connected, the plugin builds a list of what is in your place — path and class name, nothing else — for these services and everything inside them:
- Workspace
- ReplicatedStorage
- ReplicatedFirst
- ServerScriptService
- ServerStorage
- StarterGui
- StarterPack
- StarterPlayer
- Lighting
- SoundService
- Teams
- Chat
- TextChatService
- MaterialService
- CollectionService
That list is what fills the @ menu in the composer, and it is capped at 5,000 entries. On a very large place some deeper items will not be listed — type the full path in your message instead of picking from the menu.
Separately, the text of every script in the place is uploaded, wherever it lives. So Revix can search code that sits outside the services above, even though those containers are not listed.
The one locked area: ServerStorage
ServerStorage appears in the list, and scripts inside it are searchable. But Revix cannot touch anything in it. Any attempt to read, create, edit, move or delete something inside ServerStorage comes back as a path it cannot find.
This is on purpose. It gives you a shelf inside your own place that an AI cannot reach.
Use it like this: anything you want protected — a finished system, a backup copy of a script, an asset you do not want rearranged — goes in ServerStorage. If you later want Revix to work on one of those scripts, drag it into ServerScriptService first, ask for the change, then drag it back.
Everything else is invisible
Services that are not on the list are simply not there as far as Revix is concerned — Players, Debris, TweenService, HttpService, TestService and the rest. There is nothing to browse and nothing to point at.
Two of those matter in practice.
Players and PlayerGui do not exist in edit mode. A player's screen only exists once someone joins a running game. So there is no such thing as "add a button to my PlayerGui" — the request is:
Add a Close button to the shop screen in StarterGui, top right, and wire it to hide the frameStarterGui is the template that gets copied into each player when they join. Building there is how you build a screen.
The other services are plumbing, not containers. TweenService and HttpService are things scripts call, not places things live. Revix uses them in the code it writes; there is just nothing to list.
Where to ask for things
Revix already knows Roblox's placement rules and follows them, but knowing them helps you ask precisely and helps you check its work afterwards.
| What you want | Where it belongs |
|---|---|
| Server logic — shops, data saving, round loops | ServerScriptService |
| Code that runs for each player — input, camera, screens | StarterPlayer, in StarterPlayerScripts |
| Shared modules and remote events | ReplicatedStorage |
| On-screen interfaces | StarterGui |
| A loading screen shown before the game appears | ReplicatedFirst |
| Tools a player spawns holding | StarterPack |
| The world itself — parts, models, terrain | Workspace |
If you ask for a script at a path that does not exist yet, Revix creates the folders and picks the right script type for where it lands.
What this means for what you can ask
- "Fix the bug in my ServerStorage script" will not work. Move the script out first.
- "Look at everything in my game" works, but is slow and expensive on a big place. Name a folder and you get a better answer for fewer credits.
- "Check what the player sees" cannot be answered from edit mode. Revix verifies a screen by reading the code back against the objects it built, then asks you to press Play. Anything that only happens for a live player is your check, not its check.
- "Read the output" does work — Revix can read what your running game printed to the Output window after you have played.