Searching Your Game
Revix can search across every script in your game and find instances by name. The two tools are grep (search inside script contents) and list_descendants (find instances by name or class).
Searching script contents with grep
grep searches the source of every script in your synced services. It supports:
- Regex patterns — full POSIX/PCRE-style regex
- Context lines — show N lines before and after each match
- Scope — limit the search to a subtree (e.g. only ServerScriptService)
Grep for "DataStore" across the whole game.Grep for "GetService\(\"HttpService\"\)" with 3 lines of context, only in ServerScriptService.Find every place we call ":FireAllClients" inside ReplicatedStorage.Each match comes back with the script path, line number, and surrounding context — so the AI (and you) can navigate fast.
Finding instances by name
list_descendants walks the data model and returns instances matching a name pattern or class.
List every Part in Workspace whose name contains "Spawn".Find all RemoteEvents anywhere in the game.Show me every ModuleScript under ReplicatedStorage.Modules.This is the right tool for "where is X?" questions about instances, not their contents.
When to use which
| Question | Tool |
|---|---|
| "Where in code do we read the leaderstats?" | `grep` |
| "Which script handles damage?" | `grep` for `Humanoid.Health` or similar |
| "Find the Part named SpawnPoint" | `list_descendants` |
| "How many ModuleScripts do we have?" | `list_descendants` |
| "Show me every place we call DataStore:GetAsync" | `grep` |
| "List every ScreenGui in StarterGui" | `list_descendants` |
grep is for what scripts say. list_descendants is for what instances exist.
Synced scope
Both tools run over Revix's synced services:
| Synced |
|---|
| Workspace, ReplicatedStorage, ReplicatedFirst |
| ServerScriptService |
| StarterGui, StarterPack, StarterPlayer |
| Lighting, SoundService |
| Teams, Chat, TextChatService |
| MaterialService, CollectionService |
ServerStorage is not synced, so its contents won't show up in either tool.
Tips
- Use regex when patterns matter.
Player(s|sInstance)is faster than three separate searches. - Scope your search when you know roughly where the code lives. Searching only
ServerScriptServiceis much faster than the whole game. - Ask for context lines. Five lines of surrounding code is usually enough for the AI to understand the call site without re-reading the file.
Troubleshooting
- Zero results: double-check spelling and try a broader regex (e.g.
damageinstead ofDamageHandler). - Too many results: narrow the scope, or add more specific terms.
- Searching the toolbox: that's a different tool —
search_toolbox. Ask for "toolbox assets" instead. - For reading the matching scripts in detail, see Editing Scripts.