The Game Map

After this page you can open a visual map of the game you have connected, see what Revix understands about it, and turn a feature idea into a chat message in one click.

Plan: every plan, including Free. Cost: the map has no fixed credit price, and nothing it shows you is sent to your game until you press send in the chat yourself. Needs: Roblox Studio open and connected before the map can read your place.

Opening it

The left rail of the dashboard, marked with a map icon: Game Map. It opens as a tall panel beside your chat, so the conversation stays visible - you are not leaving the chat to look at it.

If Studio is not connected you get a single node with a question mark on it, named after your game. Connect the plugin first and it fills in. See Plugin Connection.

What you are looking at

A mind map on a dot grid, not a floor plan. In the middle is your game. Around it are the features Revix has found, joined by lines back to the centre.

Drag anywhere on the grid to pan.
Zoom with the minus and plus controls in the corner. The current zoom shows as a live percentage.
Rename the centre node by clicking it and typing. The field is labelled "Game name". Useful when the place name in Studio is still "Baseplate".

Filling it in

The first time, press Import Game. It scans the connected place and builds the map from what is actually there, with a progress bar and a running status line while it works. The button only appears when Studio is connected.

Two things worth knowing while it runs:

Give it time on a big place. It is reading your whole game, not guessing.
You cannot switch to a different connected game mid-scan. Try it and you get: "Finish the current chat or Revix Ideas run before switching games." Wait for it to finish.

Re-import whenever you have built something substantial and want the map to catch up.

Getting ideas out of it

Hover any node and you get AI Mechanics Ideas for that part of your game - concrete features that would fit what is already there. It says "Brainstorming features..." while it thinks, and "No ideas found." when it has nothing useful to add for that node.

Click an idea and it goes into the composer. It does not send. That gap is the useful part: read what it wrote, then edit it before you press send.

text

Add a daily reward chest near spawn that gives coins on a 24 hour timer

Turn that into something specific to your game before sending:

text

Add a daily reward chest next to the spawn platform in Workspace.Lobby.
Give 100 coins, once every 24 hours per player, saved so it survives a rejoin.

Using it to aim Revix at one area

The map is best used as a starting point, then narrowed in the chat. Three habits make the difference:

Find the feature on the map, then name it in your message. "The shop" is vague; "the shop stand in Workspace.Village" is not.
Use `@` in the composer to point at an exact object. Typing @ opens a browser of your whole game tree - expand a folder, pick the thing, and Revix works on that instead of searching for it. This is the sharpest tool you have for a big place.
One area per message. A request that touches the shop, the leaderboard and the spawn at once gets a broad, shallow answer. Three messages get three good ones.

For more on narrowing a request down, see Finding Things in a Big Place.

What the map is not

It is not a live view. It reflects the last import, not the current state of Studio.
It is not a place editor. Nothing you do on the map changes your game - it fills the composer, and you decide what to send.
It is not a complete inventory of your game. It maps features, not every part. To ask what is actually inside a container, ask Revix directly in the chat.