v0.5.0 Alpha 4

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

This release features increased flexibility in the project format that should make it more feasible to use Rojo for versioning an entire game. The documentation site has received a huge upgrade to go along with this release.

Changes Since 0.5.0-alpha.3

• Added support for nested partitions (#102)
• Added support for 'transmuting' partitions (#112)
• Added support for aliasing filesystem paths (#105)
• Changed Windows builds to statically link the CRT (#89)

Nested Partitions

Previously, Rojo only allowed defining instance children if $path wasn't specified. Since 0.5.0-alpha.4 however, Rojo can handle projects that you'd expect to work, like:

{
    "name": "nested-as-heck",
    "tree": {
        "$path": "src",

        "Modules": {
            "$path": "Modules"
        }
    }
}

Transmuting Partitions

Instances defined in projects can now have $path as well as other options like $properties and $className, which can be used to put stuff directly into Roblox services:

{
    "name": "nested-as-heck",
    "tree": {
        "$className": "DataModel",
        
        "ReplicatedStorage": {
            "$className": "ReplicatedStorage",
            "$path": "ReplicatedStorage"
        }
    }
}

Aliasing File Paths

Rojo used to have bugs if you had multiple $path values pointing into the same place on the filesystem. Now it doesn't!

Static CRT

This fixes the need for installing any Microsoft Visual Studio Redistributibles! On the flipside, future releases will all be a little larger.