v0.5.0 Alpha 3

This is the fourth alpha for Rojo 0.5.0!

This release features one major bugfix for files not syncing into Studio, and changes the name of the default project format. Rojo will automatically let you know that you need to upgrade your project file name when you launch it!

Installing the 0.5.x Plugin

A new plugin has been uploaded to Roblox in order to let existing users of Rojo continue using 0.4.x.

You can install the plugin from one of two places:

• The new Roblox.com plugin page
• Downloading the attached rbxm file and putting it into your Studio 'plugins' folder

Installing the 0.5.x Server

If you're on Windows, you can download the attached Windows executable, rojo.exe.

If you're not on Windows, or you'd rather install via Cargo, you can do that with:

cargo install rojo --version 0.5.0-alpha.3

If you already have Rojo installed, you'll need to add the --force flag to overwrite your current version.

Migrating Your Project to 0.5.x

There's a brand new set of docs for 0.5.x available that includes basic instructions on how to get started with 0.5.x. As we get closer to release, these docs will be updated and fleshed out.

If you're coming from 0.4.x, check out Migrating from 0.4.x to 0.5.x for a crash course in how to upgrade your project.

Changes Since 0.5.0-alpha.2

• Changed default project file name from roblox-project.json to default.project.json (#120)
  • The old file name will still be supported until 0.5.0 is fully released.
• Added warning when loading project files that don't end in .project.json
  • This new extension enables Rojo to distinguish project files from random JSON files, which is necessary to support nested projects.
• Added new (empty) diagnostic page served from the server
• Added better error messages for when a file is missing that's referenced by a Rojo project
• Added support for visualization endpoints returning GraphViz source when Dot is not available
• Fixed an in-memory filesystem regression introduced recently (#119)