@@ -141,22 +141,29 @@ This example has a base package for the Kuju stock stuff, an XTracks package and
141141 ...
142142
143143## Paths and References
144- Files in a package can contain references to files in the same or other packages. For example:
144+ Files in a package can contain references to files in the same or other packages. For example,
145+ a reference from one OR content package to another:
145146
146- /OR/SomePackage/Shapes/bungalow.s
147+ /OR/SomePackage/Shapes/bungalow.shape-or
147148
148- refers to file
149+ which might refer to physical file:
149150
150- C:\Users\Ryan\Open Rails\SomePackage.zip\SomePackage\Shapes\bungalow.s
151+ C:\Users\Ryan\Open Rails\SomePackage.zip\SomePackage\Shapes\bungalow.shape-or
151152
152- Files in the MSTS-organised packages can continue to use legacy references such as:
153+ A reference from one MSTS content package to another:
154+
155+ /MSTS/SomePackage/Shapes/bungalow.s
156+
157+ This also works as a reference from an OR content package to an MSTS one.
158+
159+ References from one MSTS content package to another may also use a legacy reference such as:
153160
154161 ..\..\SomePackage\Shapes\bungalow.s
155162
156- but files in the OR-organised packages must start from the /OR root and may not use ".."
163+ but files in the OR content packages must start from the /OR root and may not use ".."
157164
158165
159166### For OR assets that are inextricably linked with other assets (paths and activities vis-a-vis routes)
160- An activity must be linked to a route. In OR packages, this will be achieved with a more restrictive reference:
167+ An activity must be linked to a route. In OR packages, this constraint will be achieved with a more restrictive reference, such as :
161168
162169 "Route": "/OR/SomePackage/Routes/SomeRoute.route-or"
0 commit comments