The studio
The project window
The top bar, the tools on the left, the right panel and the status bar with Output, Problems and Tests.
Top bar
- Play starts the server and Player 1. When the server is already up, it starts only Player 1.
- Server with a state dot: grey (stopped), yellow (starting or stopping), green (running). The server restart is next to it.
- Player 1 and Player 2 open that player’s game window inside the studio.
- Search opens the command palette (Ctrl+Shift+P).
- The layout buttons hide the side panel and the right panel.
Left: Files, Scene and tools
At the top of the bar are Files (the project tree) and Scene (the objects the studio places in the world). Ctrl+B shows and hides the side panel.
Below them are the tools. Each opens as a tab at the top of the middle area, next to files and the players’ windows:
| Tool | What for |
|---|---|
| Map | The scene, zones, blips, places and players on the GTA map from above |
| Mechanics | What happens on objects: targeting, E nearby, zones, items |
| Catalog | Props, NPCs and vehicles to place in the scene |
| Resources | Start, stop, restart, settings, resources from GitHub, what the project can do |
| Database | Tables, SQL, snapshots and migrations |
| Items | The project’s inventory items |
| Attachments | A prop in the hand or on a bone, placed with a gizmo in the game |
| Clothing | Your own clothes on models from the game |
| Tattoos | Your own tattoos: an image, text or SVG on the body |
| Inspector | Entities, state bags, players, buckets and events |
| Docs | Natives, the API of the project’s resources and docs.fivem.net pages |
| Animations | The animation editor |
A tool the project cannot use, because no resource gives the capability it needs, does not show. Resources → What the project can do lists what the project has.
Right panel
- Selection: properties of the object picked in the scene, in the game or in a tool (an item, an attachment).
- Catalog: models to place.
- Session: Player 1 and 2, the character, time of day and weather, scenarios.
Status bar
At the bottom are Output (logs of the server, the players and the studio, with the server console), Problems (script errors with file and line), Tests and Claude (what Claude did over MCP). A click opens the panel above the bar.
Further along, the bar shows the server state, framework and gamebuild, who has control (the studio or Player N), the plan and the connection to Claude.