@@ -581,16 +581,16 @@ How to define container data
581
581
582
582
Container shape files (``.s ``) must be located in subfolders (or sub-subfolders) of the
583
583
``Trainset `` folder.
584
- Containers that can be managed must be provided with a Json ``.loa `` file. The ``.loa `` files
584
+ Containers that can be managed must be provided with a Json ``.load-or `` file. The ``.load-or `` files
585
585
must be located in a subfolder of the ``Trainset `` folder. It is warmly advised to keep all
586
- ``.loa `` file in a single folder: ``Common.ContainerData `` is suggested. It is also advised to name
587
- the ``.loa `` files in a consistent way: ``40HCtriton.loa `` is suggested, where ``40HC `` is the
586
+ ``.load-or `` file in a single folder: ``Common.ContainerData `` is suggested. It is also advised to name
587
+ the ``.load-or `` files in a consistent way: ``40HCtriton.load-or `` is suggested, where ``40HC `` is the
588
588
container type and ``triton `` the brand painted on the container.
589
589
590
- Format of the .loa file
590
+ Format of the .load-or file
591
591
'''''''''''''''''''''''
592
592
593
- Here below a sample of a ``.loa `` file::
593
+ Here below a sample of a ``.load-or `` file::
594
594
595
595
{
596
596
"Container":
@@ -704,8 +704,8 @@ shown here::
704
704
As can be seen, for each container loaded at startup a ``LoadData `` entry must be
705
705
present. The meaning of the parameters is as follows:
706
706
707
- - The first parameter is the name of the ``.loa `` file
708
- - The second parameter is the path (having ``Trainset `` as base path) where the ``.loa ``
707
+ - The first parameter is the name of the ``.load-or `` file
708
+ - The second parameter is the path (having ``Trainset `` as base path) where the ``.load-or ``
709
709
file resides
710
710
- The third parameter indicates where the container is allocated on the wagon.
711
711
@@ -1032,17 +1032,17 @@ its child stack location 10. Same applies to stack location 3 and its child stac
1032
1032
Population of container stations at game start
1033
1033
''''''''''''''''''''''''''''''''''''''''''''''
1034
1034
1035
- Container stations may be populated at game start. This occurs by inserting an ``.lsp ``
1036
- (load station population) in the ``Openrails `` subfolder of the "Activities" folder of the
1035
+ Container stations may be populated at game start. This occurs by inserting a ``.load-stations-loads-or ``
1036
+ file in the ``Openrails `` subfolder of the "Activities" folder of the
1037
1037
route, and inserting the following line at the bottom of the ``Tr_Activity_Header `` in
1038
1038
``.act `` files ::
1039
1039
1040
1040
ORTSLoadStationsPopulation ( BigContainerStationPopulation )
1041
1041
1042
- where ``BigContainerStationPopulation `` is the name of the ``.lsp `` file. At the moment population at
1042
+ where ``BigContainerStationPopulation `` is the name of the ``.load-stations-loads-or `` file. At the moment population at
1043
1043
game start is possible only in Activity mode.
1044
1044
1045
- The ``.lsp `` file is a Json file. An example is shown here below ::
1045
+ The ``.load-stations-loads-or `` file is a Json file. An example is shown here below ::
1046
1046
1047
1047
"ContainerStationsPopulation": [
1048
1048
{
@@ -1073,8 +1073,8 @@ The file can define the population at startup of many container stations.
1073
1073
1074
1074
- The ``LoadStationID `` contains the info needed to identify the container station.
1075
1075
- The ``LoadData `` array contains the data to populate the container station.
1076
- - The value of ``File `` is the name of the ``.loa `` file identifying the container.
1077
- - The value of ``Folder `` is the path where the ``.loa `` can be found, starting from the
1076
+ - The value of ``File `` is the name of the ``.load-or `` file identifying the container.
1077
+ - The value of ``Folder `` is the path where the ``.load-or `` can be found, starting from the
1078
1078
``TRAINSET ``.
1079
1079
- The value of ``StackLocation `` is the index of the Stack Location. If the index is equal
1080
1080
or higher than the number of stack locations defined in the extension ``.w `` file, the
0 commit comments