Skip to content

v0.5.0 (stable!)

Compare
Choose a tag to compare
@LPGhatguy LPGhatguy released this 27 Aug 21:23
· 807 commits to master since this release
91caa67

This stable release has been in progress for a very long time.

If you're coming from the previous 0.5.0 alpha releases, not a whole lot has changed in this release except its name.

If you're coming from Rojo 0.4.x, check out the 0.5.x Migration Guide in the official docs to get yourself up to date. At this point, Rojo 0.4.x will no longer officially receive any further updates.

Upgrading

To install the Rojo CLI, either download rojo.exe attached here or run (requires Rust 1.34):

cargo install rojo --force

To install the plugin, either install it from Roblox (https://www.roblox.com/catalog/1997686364) or download Rojo.rbxm and put it into your Roblox Studio plugins folder.

The Rojo Visual Studio Code extension should automatically upgrade you from the 0.5.0 alphas onto the 0.5.0 stable release track.

Changes Since 0.4.x

  • Brand new project format, default.project.json instead of rojo.json
  • Added support for rbxm and rbxmx models as part of your project
  • Added new commands: rojo build, rojo upload, rojo init
  • Added support for csv localization tables
  • New plugin that's more efficient and more beautiful!

Changes Since 0.5.0 Alpha 13

  • Changed .model.json naming, which may require projects to migrate ambiguous cases:
    • The file name now takes precedence over the Name field in the model, like Rojo 0.4.x.
    • The Name field of the top-level instance is now optional. It's recommended that you remove it from your models.
    • Rojo will emit a warning when Name is specified and does not match the name from the file.
  • Fixed Rect values being set to 0, 0, 0, 0 when synced with the Rojo plugin. (#201)
  • Fixed live-syncing of PhysicalProperties, NumberSequence, and ColorSequence values

Known Issues

  • #142: Rojo still does not support ref properties, this will be fixed as part of a refactor and release 0.6.0
  • #215, #214, #213, #193, #132: Various issues around changes being dropped that we weren't quite able to pinpoint. After #217 merges, we'll be working on fresh foundations, which means fresh bugs!