Rojo is a flexible multi-tool designed for creating robust Roblox projects. It's in early development, but is still useful for many projects.
It's designed for power users who want to use the best tools available for building games, libraries, and plugins.
This is the main Rojo repository, containing the binary server component. For the source for the Roblox plugin, see the rojo-plugin repository.
Rojo has a number of desirable features right now:
Soon, Rojo will be able to:
Rojo has two components: * The command line tool, written in Rust * The Roblox Studio plugin, written in Lua
To install the command line tool, there are two options:
* Cargo, if you have Rust installed
* Use cargo install rojo -- Rojo will be available with the rojo command
* Download a pre-built Windows binary from the GitHub releases page
For more help, use rojo help.
Just create a new folder and tell Rojo to initialize it!
```sh mkdir my-new-project cd my-new-project
rojo init ```
Rojo will create an empty project in the directory.
The default project looks like this:
json
{
"name": "my-new-project",
"servePort": 8000,
"partitions": {}
}
To create a server that allows the Rojo Dev Plugin to access your project, use:
sh
rojo serve
The tool will tell you whether it found an existing project. You should then be able to connect and use the project from within Roblox Studio!
Coming soon!
In order to sync code into Roblox, you'll need to add one or more "partitions" to your configuration. A partition tells Rojo how to map directories to Roblox objects.
Each entry in the partitions table has a unique name, a filesystem path, and the full name of the Roblox object to sync into.
For example, if you want to map your src directory to an object named My Cool Game in ReplicatedStorage, you could use this configuration:
json
{
"name": "rojo",
"servePort": 8000,
"partitions": {
"game": {
"path": "src",
"target": "ReplicatedStorage.My Cool Game"
}
}
}
The path parameter is relative to the project file.
The target starts at game and crawls down the tree. If any objects don't exist along the way, they'll be created as Folder instances.
Run rojo serve in the directory containing this project, then press the "Sync In" or "Toggle Polling" buttons in the Roblox Studio plugin to move code into your game.
The structure of files and folders on the filesystem are preserved when syncing into game.
Creation of Roblox instances follows a simple set of rules. The first rule that matches the file name is chosen:
| File Name | Instance Type | Notes |
| -------------- | -------------- | ----------------------------------------- |
| *.server.lua | Script | Source will contain the file's contents |
| *.client.lua | LocalScript | Source will contain the file's contents |
| *.lua | ModuleScript | Source will contain the file's contents |
| * | StringValue | Value will contain the file's contents |
Any folders on the filesystem will turn into Folder objects unless they contain a file named init.lua, init.server.lua, or init.client.lua. Following the convention of Lua, those objects will instead be whatever the init file would turn into.
For example, this file tree:
Will turn into this tree in Roblox:
my-game (LocalScript with source from my-game/init.client.lua)
foo (ModuleScript with source from my-game/foo.lua)There are lots of other tools that sync scripts into Roblox, or otherwise work to improve the development flow outside of Roblox Studio.
Here are a few, if you're looking for alternatives or supplements to Rojo: * Studio Bridge by Vocksel * RbxRefresh by Osyris * RbxSync by evaera * CodeSync and rbx-exteditor by MemoryPenguin * rbxmk by Anaminus
I also have a couple tools that Rojo intends to replace: * rbxfs, which has been deprecated by Rojo * rbxpacker, which is still useful
Rojo is available under the terms of the MIT license. See LICENSE.md for details.