Internal Menu

Search instances, jump through the hierarchy, use runtime suggestions and inspect thread values inside Roblox.

The Internal Menu runs inside the connected Roblox client. It includes the editor, Scripts, Explorer, thread inspection and decompiler windows. Press your Menu Key, Insert by default, to open it. Configure the key and menu visibility under Settings → Client in the desktop app.

Open Explorer and type an instance name in the search field. Search includes descendants of collapsed branches, so you can find an object without opening its parents first.

The status reads Searching descendants... while the catalogue is being captured, then All descendants when it is complete. Results refresh as the hierarchy changes. Clear the search field to return to the normal expandable tree.

Jump to an instance

  1. Find the instance in Explorer and right-click its row.
  2. Choose Jump to from the context menu.
  3. Explorer clears the search, expands the instance's ancestors, selects the row and scrolls it into view horizontally and vertically.

Runtime property suggestions

The Internal Menu editor combines live child names with runtime property names, including inherited properties. Type workspace. or game:GetService("Players").LocalPlayer. to request suggestions for the current object. Known instance references such as Parent and Players.LocalPlayer can continue the chain.

Suggestions follow the connected client's current hierarchy and class metadata. The list refreshes as you edit; changing games replaces the old client context.

Read Stack and Environment

Open a script's thread list from Scripts and select a thread to inspect its Stack and Environment. Expand a table or userdata value's Metatable entry to inspect its captured fields.

Anonymous functions found in actual metatables receive labels such as __index (metamethod). A shared function can show several roles, such as __index / __call (metamethod). Existing function names remain visible. Metamethod labels are searchable, and refreshed captures rebuild the labels after methods or metatables change.

Compact script paths

Explorer's Copy path action and decompiler titles use compact paths when the names allow it:

game:GetService("ReplicatedStorage").ClientModules.Game.PetEntities

Names that need escaping use bracket access. Names that collide with instance members keep an explicit child lookup, and duplicate sibling names use an indexed child lookup to identify the selected instance.

Decompiler windows

Choose Decompile for a script to open its recovered source. The title fits the available window or tab width by shortening the beginning of a long path. Hover over a shortened title to read the full path.

Use Copy Code to copy the recovered source or Open new Tab to open it in an editor tab. Resizing or docking the source window keeps its identity and full script path.