Skip to content
You're reading the docs for Railroader 0.6 (the MoW Update), currently available on the Experimental branch.

Migrating Mods to 0.6

In 2025.1.x and earlier, modding via asset packs was available but unofficially supported. For the MoW Update (0.6), this system was revamped.

  • Asset Pack changes:
    • All asset packs must have an Info.json file. See Asset Packs.
    • Catalog.json is no longer used and should be removed.
    • Asset packs must be installed in either Documents\Railroader\Mods or, for mods in development, Documents\Railroader\ModDev. Asset packs are no longer loaded from %APPDATA%\LocalLow\Giraffe Lab LLC\Railroader\AssetPacks. Mods in Documents\Railroader\ModDev override other mods sharing the same identifier regardless of source; the directory name doesn’t need to match the pack’s identifier. See Installing Mods for the full picture of load locations.
  • Car definitions:
    • The archetype field has been removed. Gameplay classification is now determined automatically from the carType prefix. See Car Types.
  • Car coloring:
    • The Colorizer component is now RendererGroup. Rename the kind field; material carries over unchanged.
    • Its hexColors list is gone. Colors are no longer baked into the component — give the group a styleClass ("body", "trim", and so on) and let a Style supply the color by matching a selector such as Renderer.body. See Colorable Components for how the pieces fit together.
  • Decals:
    • Decals can display an image now, not just text. Set content to Image and point image at a texture — heralds, logos, and the like. If the texture is a sprite atlas, uvRect picks out a single cell.
  • Identifier Domains:
    • Identifiers have been namespaced with an added domain prefix: domain/item. For example, the built-in pack ls-280-c46 is now rr/ls-280-c46. A definition’s domain is typically the same as its pack’s domain, but this is not required — see Identifiers for details.
    • You should select a meaningful domain to represent your work, preferably your name or handle, and use this domain for your creations. This will help avoid conflicts with other mods.

Map mods weren’t officially supported in 2025.1.x and earlier. They worked through third party DLL mods that read JSON data files and built the track graph and scenery objects at runtime. The MoW Update replaces that with a first-party format, so a map mod written for 2025.1.x won’t load without modifications.

The data is a similar shape, so this is mostly a translation rather than a rebuild. See Map Modding for the new format. We plan to provide a tool that makes a best-effort conversion of 2025.1-era map data.