KIND Industry - Revision history

Pcas1986: Added sort criterion

2014-02-14T04:55:21Z

Added sort criterion

← Older revision		Revision as of 04:55, 14 February 2014
Line 81:		Line 81:

	== Categories ==		== Categories ==
	[[Category:Asset KIND]]		[[Category:Asset KIND\|I]]
	{{ORP-bot\|Industry,KIND}}		{{ORP-bot\|Industry,KIND}}

Pcas1986 at 05:30, 26 January 2014

2014-01-26T05:30:18Z

← Older revision		Revision as of 05:30, 26 January 2014
Line 18:		Line 18:
	====processes====		====processes====

	:Type: [[~~Processes_container~~\|Process element container]]		:Type: [["processes-element" container\|Process element container]]
	:Desc: Contains one or more process elements. Each process element provides information about the process, including duration, start status, and the input and output queues associated with that process.		:Desc: Contains one or more process elements. Each process element provides information about the process, including duration, start status, and the input and output queues associated with that process.

Pcas1986: Changes to the processes tag format to align with other similar pages.

2014-01-26T04:46:16Z

Changes to the processes tag format to align with other similar pages.

← Older revision		Revision as of 04:46, 26 January 2014
Line 16:		Line 16:
	[[KIND Industry]] supports all of the [[KIND SceneryWithTrack]] tags, and adds the following tags.		[[KIND Industry]] supports all of the [[KIND SceneryWithTrack]] tags, and adds the following tags.

	processes		====processes====
	{
	}		:Type: [[Processes_container\|Process element container]]
			:Desc: Contains one or more process elements. Each process element provides information about the process, including duration, start status, and the input and output queues associated with that process.

	~~== Processes ==~~
	~~:Type: [[Processes_container\|Processes container]]~~
	~~:Desc: Each process container provides information about the process including duration, start status and the input and out queues.~~
	: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 ==		== Example Config.txt ==

Pcas1986: Updated Processes section to enable help links and also added information about the process name.

2014-01-25T08:04:37Z

Updated Processes section to enable help links and also added information about the process name.

← Older revision		Revision as of 08:04, 25 January 2014
Line 20:		Line 20:
	}		}

	==~~== processes ==~~==		== Processes ==
	:Type: [[Processes_container\|Processes container]]		:Type: [[Processes_container\|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~~.		:Desc: Each process container provides information about the process including duration, start status and the input and out queues.
	: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.		: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.

Pcas1986: /* processes */

2014-01-25T07:52:54Z

processes

← Older revision		Revision as of 07:52, 25 January 2014
Line 23:		Line 23:
	:Type: [[Processes_container\|Processes container]]		:Type: [[Processes_container\|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.		: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 ==		== Example Config.txt ==

Pcas1986: /* Industry data types */ Rewording of description to better describe an industry. Removed comments about MSTS and popularity of Trainz due to industries since it is irrelevant.

2014-01-25T07:48:01Z

Industry data types: Rewording of description to better describe an industry. Removed comments about MSTS and popularity of Trainz due to industries since it is irrelevant.

← Older revision		Revision as of 07:48, 25 January 2014
Line 1:		Line 1:
	{{ORP-top}}		{{ORP-top}}
	==Industry data types==		==Industry data types==
	'''KIND Industry''' provides the basis for interactive ~~[[industry]] objects~~ such as ~~a factory~~, ~~docks~~, or ~~passenger station. Industry assets provide queues for~~ loading ~~and~~ unloading ~~product~~, ~~and automated functionality for processing product~~. ~~Interactive industries~~ and ~~rolling stock were introduced in TRS2004 in 2003, and are one thing which has made Trainz a success compared~~ to ~~other simulators like {{wp\|Microsoft Train Simulator}} (released~~ the ~~same year as Trainz 1.0) which have never had the popularity~~ and ~~longevity.~~.		'''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 ==		== KIND Hierarchy ==

Fabartus: /* Categories */ pipetrick

2013-07-27T02:47:40Z

Categories: pipetrick

← Older revision		Revision as of 02:47, 27 July 2013
Line 84:		Line 84:
	== Categories ==		== Categories ==
	[[Category:Asset KIND]]		[[Category:Asset KIND]]
	{{ORP-bot}}		{{ORP-bot\|Industry,KIND}}

Fabartus: fmt, new user notes

2013-07-26T18:08:56Z

fmt, new user notes

← Older revision		Revision as of 18:08, 26 July 2013
Line 1:		Line 1:
	[[KIND Industry]] provides the basis for interactive industry objects such as a factory, docks, or passenger station. Industry assets provide queues for loading and unloading product, and automated functionality for processing product.		{{ORP-top}}
			==Industry data types==
			'''KIND Industry''' provides the basis for interactive [[industry]] objects such as a factory, docks, or passenger station. Industry assets provide queues for loading and unloading product, and automated functionality for processing product. Interactive industries and rolling stock were introduced in TRS2004 in 2003, and are one thing which has made Trainz a success compared to other simulators like {{wp\|Microsoft Train Simulator}} (released the same year as Trainz 1.0) which have never had the popularity and longevity..

	== KIND Hierarchy ==		== KIND Hierarchy ==
	=== Parent Classes ===		=== Parent Classes ===
	* [[KIND SceneryWithTrack]]		* [[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 ===		=== Child Classes ===
	* ''~~none~~.''		* '''[[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 {{wp\|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 ==		== Supported Tags ==
Line 21:		Line 27:
	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.		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		processes
	{		{
Line 77:		Line 84:
	== Categories ==		== Categories ==
	[[Category:Asset KIND]]		[[Category:Asset KIND]]
	~~[[Category:TBD]]~~		{{ORP-bot}}

Pw3r at 12:47, 12 February 2013

2013-02-12T12:47:18Z

← Older revision		Revision as of 12:47, 12 February 2013
Line 8:		Line 8:

	== Supported Tags ==		== Supported Tags ==
	~~Each industry asset~~ supports the following tags.		[[KIND Industry]] supports all of the [[KIND SceneryWithTrack]] tags, and adds the following tags.

	processes		processes

Pw3r at 12:46, 12 February 2013

2013-02-12T12:46:30Z

← Older revision		Revision as of 12:46, 12 February 2013
Line 3:		Line 3:
	== KIND Hierarchy ==		== KIND Hierarchy ==
	=== Parent Classes ===		=== Parent Classes ===
	* [[KIND ~~Buildable~~]]		* [[KIND SceneryWithTrack]]
	=== Child Classes ===		=== Child Classes ===
	* ''none.''		* ''none.''