Skip to main content
  • Pricing
Tutorials

A Roblox Studio Workflow With Rojo, VS Code, and Git

By Oakgen TeamPublished 1 min read

Share
A Roblox Studio Workflow With Rojo, VS Code, and Git

Rojo connects files on disk to Roblox instances in Studio. VS Code is where you edit those files, and Git records their history. Give each tool a clear job so your first successful sync also becomes a reproducible project state.

Sync one change from disk

  1. Follow the Rojo installation guide to make the Rojo executable and Studio plugin available. In a new project folder, run rojo init.
  2. Start rojo serve in that folder. Open the Studio plugin and connect to the address printed in your terminal.
  3. Locate one server script in the starter project. Change the text passed to a print call in VS Code, then save. Check the instance in Studio and start a local playtest to see the new text in Output.
  4. Initialize your Git repository if needed, then inspect git status and git diff. Commit the project configuration and relevant source files.

The first test gives you a specific observation to reproduce after sharing the repository. Someone can open the folder on another machine, serve it, and see the same text appear.

Decide what belongs in the repository

A local rojo build -o build.rbxlx creates a place file you can open or share. Decide with your team whether that file is a published artifact or a committed source file. Keep Studio-only assets documented if they need separate setup. When a sync looks wrong, compare the project's mappings with Explorer and make sure the script path on disk points to the intended service.

Continue with Oakgen Agent

Open in Oakgen Agent

Review the prefilled prompt before sending.

Open in Oakgen Agent

Sources

  1. Rojo โ€” Creating a New Game
  2. Rojo โ€” Sync Details
  3. Rojo โ€” Installation
Share