Skip to content

Releases: rojo-rbx/rojo

v0.5.0 Alpha 1

26 Jan 02:07
Compare
Choose a tag to compare
v0.5.0 Alpha 1 Pre-release
Pre-release

This is the second alpha (pardon the zero-based indexing) for Rojo 0.5.0!

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:

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.1

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.1

  • Changed plugin UI to be way prettier
    • Thanks to Reselim for the design!
  • Changed plugin error messages to be a little more useful
  • Removed unused 'Config' button in plugin UI
  • Fixed bug where bad server responses could cause the plugin to be in a bad state
  • Upgraded to rbx_tree, rbx_xml, and rbx_binary 0.2.0, which dramatically expands the kinds of properties that Rojo can handle, especially in XML.

v0.5.0 Alpha 0

15 Jan 02:33
Compare
Choose a tag to compare
v0.5.0 Alpha 0 Pre-release
Pre-release

This is the first alpha release of the up-and-coming 0.5.0 release!

It's a major breaking change from 0.4.x, but includes lots of improvements.

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:

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.0

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 from 0.4.x

  • "Epiphany" rewrite, in progress since the beginning of time
  • New live sync protocol
    • Uses HTTP long polling to reduce request count and improve responsiveness
  • New project format
    • Hierarchical, preventing overlapping partitions
  • Added rojo build command
    • Generates rbxm, rbxmx, rbxl, or rbxlx files out of your project
    • Usage: rojo build <PROJECT> --output <OUTPUT>.rbxm
  • Added rojo upload command
    • Generates and uploads a place or model to roblox.com out of your project
    • Usage: rojo upload <PROJECT> --cookie "<ROBLOSECURITY>" --asset_id <PLACE_ID>
  • New plugin
    • Only one button now, "Connect"
    • New UI to pick server address and port
    • Better error reporting
  • Added support for .csv files turning into LocalizationTable instances
  • Added support for .txt files turning into StringValue instances
  • Added debug visualization code to diagnose problems
    • /visualize/rbx and /visualize/imfs show instance and file state respectively; they require GraphViz to be installed on your machine.
  • Added optional place ID restrictions to project files
    • This helps prevent syncing in content to the wrong place
    • Multiple places can be specified, like when building a multi-place game
  • Added support for specifying properties on services in project files

v0.4.13

13 Nov 05:54
Compare
Choose a tag to compare

This release introduces a small change suggested by @osyrisrblx!

As always, download the latest plugin either from this release (the rbxm file) or from the Roblox plugin page.

You can grab the server portion from here if you're on Windows, or by running cargo install rojo. If you're upgrading from a previous server version, use cargo install rojo --force to tell Cargo to update your existing version.

Changes since 0.4.12

  • When rojo.json points to a file or directory that does not exist, Rojo now issues a warning instead of throwing an error and exiting

v0.4.12

21 Jun 18:24
Compare
Choose a tag to compare

This is a minor bugfix, and introduces a small new feature, a plugin action for syncing in!

As always, download the latest plugin either from this release (the rbxm file) or from the Roblox plugin page.

You can grab the server portion from here if you're on Windows, or by running cargo install rojo. If you're upgrading from a previous server version, use cargo install rojo --force to tell Cargo to update your existing version.

Changes since 0.4.11

  • Fixed obscure assertion failure when renaming or deleting files (#78)
  • Added a PluginAction for the sync in command, which should help with some automation scripts (#80)

v0.4.11

10 Jun 22:58
Compare
Choose a tag to compare

This is a bugfix update, trying to squish the last few duplication bugs. Notably, it fixes the (painful) duplication issue when syncing into an existing tree that would cause the first update after starting the plugin to cause a duplicate script insertion.

I'm aiming to get 0.4.x into a stable spot with as few bugs as possible. 0.5.0 is around the corner, with much stronger testing infrastructure that should prevent bugs like this from happening in the future.

I've been losing my mind trying to track these down and juggle the implementations of both 0.4.x and 0.5.0 while keeping a full-time programming job!

As always, download the latest plugin either from this release (the rbxm file) or from the Roblox plugin page.

You can grab the server portion from here if you're on Windows, or by running cargo install rojo. If you're upgrading from a previous server version, use cargo install rojo --force to tell Cargo to update your existing version.

Changes since 0.4.10

  • Defensively insert existing instances into RouteMap; should fix most duplication cases when syncing into existing trees.
  • Fixed incorrect synchronization from Plugin:_pull that would cause polling to create issues
  • Fixed incorrect file routes being assigned to init.lua and init.model.json files
  • Untangled route handling internals slightly

v0.4.10

02 Jun 06:53
Compare
Choose a tag to compare

This update brings a few bugfixes, and a new feature: init.model.json files!

As always, download the latest plugin either from this release (the rbxm file) or from the Roblox plugin page.

You can grab the server portion from here if you're on Windows, or by running cargo install rojo. If you're upgrading from a previous server version, use cargo install rojo --force to tell Cargo to update your existing version.

Changes since 0.4.9

  • Added support for init.model.json files, which enable versioning Tool instances (among other things) with Rojo. (#66)
  • Fixed obscure error when syncing into an invalid service.
  • Fixed multiple sync processes occurring when a server ID mismatch is detected

v0.4.9

27 May 00:04
Compare
Choose a tag to compare

This is a small quality-of-life and hotfix update.

As always, download the latest plugin either from this release (the rbxm file) or from the Roblox plugin page.

You can grab the server portion from here if you're on Windows, or by running cargo install rojo. If you're upgrading from a previous server version, use cargo install rojo --force to tell Cargo to update your existing version.

Changes since 0.4.8

  • Fixed warning when renaming or removing files that would sometimes corrupt the instance cache (#72)
  • JSON models are no longer as strict -- Children and Properties are now optional.

v0.4.8

26 May 06:44
Compare
Choose a tag to compare

This is a tiny release to fix an oversight from 0.4.6 that I missed for 0.4.7 yesterday.

As always, download the latest plugin either from this release (the rbxm file) or from the Roblox plugin page.

You can grab the server portion from here if you're on Windows, or by running cargo install rojo. If you're upgrading from a previous server version, use cargo install rojo --force to tell Cargo to update your existing version.

Changes since 0.4.7

  • Hotfix to prevent errors from being thrown when objects managed by Rojo are deleted

v0.4.7

26 May 06:33
Compare
Choose a tag to compare

Thanks to @Vorlias for creating an awesome set of icons, which is the highlight of this release!

As always, download the latest plugin either from this release (the rbxm file) or from the Roblox plugin page.

You can grab the server portion from here if you're on Windows, or by running cargo install rojo. If you're upgrading from a previous server version, use cargo install rojo --force to tell Cargo to update your existing version.

Changes since 0.4.6

  • Added icons to the Rojo plugin, made by @Vorlias! (#70)
  • Server will now issue a warning if no partitions are specified in rojo serve (#40)

v0.4.6

21 May 20:30
Compare
Choose a tag to compare

Thanks to @Quenty, @evaera, and some folks internally at Roblox for helping me track some of these issues down.

This release should finally close up the last of the script duplication bugs.

As always, download the latest plugin either from this release (the rbxm file) or from the Roblox plugin page.

You can grab the server portion from here if you're on Windows, or by running cargo install rojo. If you're upgrading from a previous server version, use cargo install rojo --force to tell Cargo to update your existing version.

Changes since 0.4.5

  • Rojo handles being restarted by Roblox Studio more gracefully (#67)
  • Folders should no longer get collapsed when syncing occurs.
  • Significant robustness improvements with regards to caching.
    • This should catch all existing script duplication bugs.
    • If there are any bugs with script duplication or caching in the future, restarting the Rojo server process will fix them for that session.
  • Fixed message in plugin not being prefixed with Rojo: .