KIND Industry

Revision as of 17:52, 25 January 2014

Industry data types

KIND Industry provides the basis for interactive assets such as factories, grain silos and passenger stations, or any other activity that involves loading to, or unloading from, a train. Industries use processes and queues to manage the loading and unloading activity.

KIND Hierarchy

Parent Classes

• KIND SceneryWithTrack —Industries without track attached nor interactive behaviour are just buildings, a scenery categorized asset. When made into a dynamic programmable interactive industry, the parent type is SceneryWithTrack.

Child Classes

• KIND Product — without this type, which includes passengers, there would be no reason for carrying anything, nor need of railways.

Sister Class

• KIND Traincar — On a railroad simulation, industries need rolling stock to move product and feedstock into and out of the plant. Both rolling stock and industries are thereby tied by the daughter level data type KIND Product, for it is difficult to unclog the pipes emptying a tank car when it is filled with Coal chunks, and fuel oil and acids spill off the odd flat car.

Supported Tags

KIND Industry supports all of the KIND SceneryWithTrack tags, and adds the following tags.

 processes
 {
 }

processes

Type: Processes container

Desc: The input and output settings of the industry. You can specify the amount of input and output for each queue referenced product as well as the duration (or rate) in seconds for that process to take place. All queues and processes are linked through the industry assets script file.

Process Name: Each process is identified by a name. This name must also be recognised in the asset script. If using a standard script then that name must be used by that script. See the example below.

Example Config.txt

Below is a sample config.txt file for an industry asset, with the standard tags excluded for brevity. This particular example is for a simple coal mine which takes in diesel fuel and outputs coal.

Tags of the TrainzBaseSpec would be included here in a config.txt file, then …

 processes
 {
   coal_production
   {
     start-enabled                       1
     duration                            30
     
     inputs
     {
       0
       {
         amount                          6465
         queue                           "diesel_in"
       }
     }
     
     outputs
     {
       0
       {
         amount                          22620
         queue                           "coal_out"
       }
     }
   }
 }
 
 queues
 {
   coal_out
   {
     size                                1357500
     product-kuid                        <kuid:44179:60013>
     initial-count                       543000
     
     allowed-products
     {
       0                                 <kuid:44179:60013>
     }
   }
   
   diesel_in
   {
     size                                310400
     product-kuid                        <kuid:-3:10011>
     initial-count                       155200
     
     allowed-products
     {
       0                                 <kuid:-3:10011>
     }
   }
 }
 

Categories