Free text for the arrangement title.
The XML file containing all locomotives properties.
Optional routes XML file. When using connection it is probably not needed, but it can be used for defining routes which are not possible at the momentairy implementation of solving module routes.
This file is used before shutting down to store all block occupations.
Swap all switches at startup to get defined positions.
Allow saving the moduleplan file.
Allow saving the module files.
Free text for the module title.
Module ID which is a reference for all other modular actions. Be carefull to change this ID because it could make the module routes invalid.
XML File with the module definition.
Module position in the arrangement.
Which side of the module will be upper most is selected by the rotation option:
For an explanation see: Modular Connections
The side on which a module is connected.
Take care: This is the real side of the module, not the rotated one!
If the module is rotated to east, east side up, the connection side at the bottom of the module is west.
The module ID which connect to the selected side.
To create a modular layout from scratch the default scheme for the rocrail server, plan.xml, must contain this:
<modplan title="My Modular Layout"/>
The rocrail server will get the full qualified path for new modules from the rocgui so both must share the same file system. In future version the rocgui will send the content of the new module to the rocrail server.