TrainCarts/Signs/Property - Revision history

Bergerkiller at 09:37, 12 October 2025

2025-10-12T09:37:25Z

← Older revision		Revision as of 09:37, 12 October 2025
Line 1:		Line 1:
	<languages/>		<languages/>
	<translate>		<translate>
	~~<!--T:1-->~~
	~~[[Special:MyLanguage/TrainCarts/Signs\|« Go back]]~~


	== Introduction == <!--T:2-->		== Introduction == <!--T:2-->

Bergerkiller: Marked this version for translation

2025-01-19T13:18:00Z

Marked this version for translation

← Older revision		Revision as of 13:18, 19 January 2025
Line 227:		Line 227:


	=== Keep Chunks Loaded ===		=== Keep Chunks Loaded === <!--T:21-->
	Trains can keep chunks around them loaded like players do. This allows them to move through the world without unloading when there are no players nearby. This feature can be enabled per train using the <code>keepchunksloaded</code> or <code>keeploaded</code> property. This can be set with a legacy ''true/false'' value, or a load mode and radius.		Trains can keep chunks around them loaded like players do. This allows them to move through the world without unloading when there are no players nearby. This feature can be enabled per train using the <code>keepchunksloaded</code> or <code>keeploaded</code> property. This can be set with a legacy ''true/false'' value, or a load mode and radius.

			<!--T:22-->
	On modern versions of Minecraft a [https://minecraft.wiki/w/Chunk#Level_and_load_type chunk load type] is also active, which can be <code>full</code>, <code>redstone</code> or <code>minimal</code>. Full will tick entities in the chunks loaded, redstone will not tick entities but will simulate redstone physics, and minimal will not run either. To [[TrainCarts/Lag\|improve server performance]] it can help to switch the mode to <code>minimal</code> with a lower radius when the train is driving long distances that don't require world simulation.		On modern versions of Minecraft a [https://minecraft.wiki/w/Chunk#Level_and_load_type chunk load type] is also active, which can be <code>full</code>, <code>redstone</code> or <code>minimal</code>. Full will tick entities in the chunks loaded, redstone will not tick entities but will simulate redstone physics, and minimal will not run either. To [[TrainCarts/Lag\|improve server performance]] it can help to switch the mode to <code>minimal</code> with a lower radius when the train is driving long distances that don't require world simulation.

			<!--T:23-->
	{\| class="wikitable"		{\| class="wikitable"
	\|-		\|-
Line 253:		Line 255:
	\|}		\|}

	==== Examples ====		==== Examples ==== <!--T:24-->
	<code>/train keepchunksloaded true</code>		<code>/train keepchunksloaded true</code>
	</translate>		</translate>

Bergerkiller at 13:17, 19 January 2025

2025-01-19T13:17:51Z

← Older revision		Revision as of 13:17, 19 January 2025
Line 262:		Line 262:
	{{sign\|[train]\|property\|keeploaded\|minimal 0}}		{{sign\|[train]\|property\|keeploaded\|minimal 0}}
	<translate>		<translate>


	=== Wait Property === <!--T:18-->		=== Wait Property === <!--T:18-->

Bergerkiller: /* Keep Chunks Loaded */

2025-01-19T13:17:38Z

Keep Chunks Loaded

← Older revision		Revision as of 13:17, 19 January 2025
Line 250:		Line 250:
	\|-		\|-
	\| full 10		\| full 10
	\| Enables the chunk loader, loading a 21x21 area of chunks and simulating entities inside. ~~In addition loads a~~ layer around it ~~that~~ is block ticked, and ~~a non-~~simulated ~~layer as well~~. So this is actually loading 25x25 chunks. If you're looking for a chunk loader that acts like a Player, this is it.		\| Enables the chunk loader, loading a 21x21 area of chunks and simulating entities inside. A 23x23 layer around it is block-ticked, and another 25x25 layer around that is not simulated. So this is actually loading 25x25 chunks. If you're looking for a chunk loader that acts like a Player, this is it.
	\|}		\|}

Line 262:		Line 262:
	{{sign\|[train]\|property\|keeploaded\|minimal 0}}		{{sign\|[train]\|property\|keeploaded\|minimal 0}}
	<translate>		<translate>


	=== Wait Property === <!--T:18-->		=== Wait Property === <!--T:18-->

Bergerkiller at 13:14, 19 January 2025

2025-01-19T13:14:14Z

@@ Line 219: / Line 219: @@
 | Loads a previously saved [[Special:MyLanguage/TrainCarts/PathFinding#Route_Manager|route]] by name.
 |}
 === Set name === <!--T:15-->
@@ Line 224: / Line 225: @@
 <!--T:16-->
 The name property alters the name of the train. To account for multiple trains being renamed, and because every train needs a unique name, the # value is added as a counter-based replacement. For example, the first train passing over the property sign with name value: ''Intercity#A'' would be named ''Intercity1A'' and the second ''Intercity2A'', and so on. You can use this in combination with the spawner sign to spawn trains with a fixed naming system. This naming system can then be used for remote control to control all trains of a certain spawner or category.
 === Wait Property === <!--T:18-->

Bergerkiller at 15:13, 23 September 2024

2024-09-23T15:13:42Z

← Older revision		Revision as of 15:13, 23 September 2024
Line 29:		Line 29:
	=== Boolean Statements === <!--T:17-->		=== Boolean Statements === <!--T:17-->
	[[File:Tc_property_statement.png\|thumb\|300px\|Property 'playerenterexit' is controlled using the lever]]		[[File:Tc_property_statement.png\|thumb\|300px\|Property 'playerenterexit' is controlled using the lever]]
	Boolean properties like playerenter and slowdown can be set using a [[TrainCarts/Signs/Statements\|statement]] to evaluate true/false. This makes it much easier to toggle something on or off with redstone, or based on another property of the train.		Boolean properties like playerenter and slowdown can be set using a [[Special:MyLanguage/TrainCarts/Signs/Statements\|statement]] to evaluate true/false. This makes it much easier to toggle something on or off with redstone, or based on another property of the train.

	=== Remote Control === <!--T:8-->		=== Remote Control === <!--T:8-->
Line 213:		Line 213:
	\| route add<br>route set<br>route remove<br>route clear		\| route add<br>route set<br>route remove<br>route clear
	\| destination_name		\| destination_name
	\| Adds/removes/clears/sets the destinations of the [[TrainCarts/PathFinding#Route_Manager\|route]] set for a train. Destinations are added at the end.		\| Adds/removes/clears/sets the destinations of the [[Special:MyLanguage/TrainCarts/PathFinding#Route_Manager\|route]] set for a train. Destinations are added at the end.
	\|-		\|-
	\| route load<br>loadroute		\| route load<br>loadroute
	\| my_saved_route		\| my_saved_route
	\| Loads a previously saved [[TrainCarts/PathFinding#Route_Manager\|route]] by name.		\| Loads a previously saved [[Special:MyLanguage/TrainCarts/PathFinding#Route_Manager\|route]] by name.
	\|}		\|}

Line 228:		Line 228:
	The wait properties control when a train will automatically slow down. This can be used to slow a train down when obstacles are ahead of the train. This feature largely replaces the older [[Special:MyLanguage/TrainCarts/Signs/Waiter\|waiter sign]], and is a lot more intelligent:		The wait properties control when a train will automatically slow down. This can be used to slow a train down when obstacles are ahead of the train. This feature largely replaces the older [[Special:MyLanguage/TrainCarts/Signs/Waiter\|waiter sign]], and is a lot more intelligent:
	* Maintain distance with other trains up ahead		* Maintain distance with other trains up ahead
	* Slow down approaching [[TrainCarts/Signs/Mutex\|occupied mutex zones]]		* Slow down approaching [[Special:MyLanguage/TrainCarts/Signs/Mutex\|occupied mutex zones]]
	* Slow down approaching a [[TrainCarts/Signs/Blocker\|blocker sign]] that will block the train		* Slow down approaching a [[Special:MyLanguage/TrainCarts/Signs/Blocker\|blocker sign]] that will block the train

	<!--T:19-->		<!--T:19-->
Line 245:		Line 245:
	\| waitacceleration		\| waitacceleration
	\| 20kmh/s		\| 20kmh/s
	\| The [[TrainCarts/Acceleration\|rate of acceleration]] at which trains slow down or speed up when obstacles ahead appear or disappear. When specifying two numbers, the first number is the rate speeding up, the second number the rate slowing down. This can be set without the waitdistance, and will be used to slow down when approaching blockers or mutexes.		\| The [[Special:MyLanguage/TrainCarts/Acceleration\|rate of acceleration]] at which trains slow down or speed up when obstacles ahead appear or disappear. When specifying two numbers, the first number is the rate speeding up, the second number the rate slowing down. This can be set without the waitdistance, and will be used to slow down when approaching blockers or mutexes.
	\|-		\|-
	\| waitdelay		\| waitdelay
Line 253:		Line 253:
	\| waitpredicted		\| waitpredicted
	\| false		\| false
	\| Controls whether the path the train will take is predicted. By default on. When enabled, this will take into account [[TrainCarts/Signs/Switcher\|switcher signs]] and where the train will be routed to when checking for obstacles.		\| Controls whether the path the train will take is predicted. By default on. When enabled, this will take into account [[Special:MyLanguage/TrainCarts/Signs/Switcher\|switcher signs]] and where the train will be routed to when checking for obstacles.
	\|}		\|}

Bergerkiller: Marked this version for translation

2024-09-02T06:11:00Z

Marked this version for translation

← Older revision		Revision as of 06:11, 2 September 2024
Line 225:		Line 225:
	The name property alters the name of the train. To account for multiple trains being renamed, and because every train needs a unique name, the # value is added as a counter-based replacement. For example, the first train passing over the property sign with name value: ''Intercity#A'' would be named ''Intercity1A'' and the second ''Intercity2A'', and so on. You can use this in combination with the spawner sign to spawn trains with a fixed naming system. This naming system can then be used for remote control to control all trains of a certain spawner or category.		The name property alters the name of the train. To account for multiple trains being renamed, and because every train needs a unique name, the # value is added as a counter-based replacement. For example, the first train passing over the property sign with name value: ''Intercity#A'' would be named ''Intercity1A'' and the second ''Intercity2A'', and so on. You can use this in combination with the spawner sign to spawn trains with a fixed naming system. This naming system can then be used for remote control to control all trains of a certain spawner or category.

	=== Wait Property ===		=== Wait Property === <!--T:18-->
	The wait properties control when a train will automatically slow down. This can be used to slow a train down when obstacles are ahead of the train. This feature largely replaces the older [[Special:MyLanguage/TrainCarts/Signs/Waiter\|waiter sign]], and is a lot more intelligent:		The wait properties control when a train will automatically slow down. This can be used to slow a train down when obstacles are ahead of the train. This feature largely replaces the older [[Special:MyLanguage/TrainCarts/Signs/Waiter\|waiter sign]], and is a lot more intelligent:
	* Maintain distance with other trains up ahead		* Maintain distance with other trains up ahead
Line 231:		Line 231:
	* Slow down approaching a [[TrainCarts/Signs/Blocker\|blocker sign]] that will block the train		* Slow down approaching a [[TrainCarts/Signs/Blocker\|blocker sign]] that will block the train

			<!--T:19-->
	The following 'wait' properties exist:		The following 'wait' properties exist:
	{\| class="wikitable"		{\| class="wikitable"
Line 255:		Line 256:
	\|}		\|}

			<!--T:20-->
	They can also be configured with the <code>/train wait <property> <value></code> set of commands.		They can also be configured with the <code>/train wait <property> <value></code> set of commands.
	</translate>		</translate>

Bergerkiller at 06:10, 2 September 2024

2024-09-02T06:10:55Z

← Older revision		Revision as of 06:10, 2 September 2024
Line 224:		Line 224:
	<!--T:16-->		<!--T:16-->
	The name property alters the name of the train. To account for multiple trains being renamed, and because every train needs a unique name, the # value is added as a counter-based replacement. For example, the first train passing over the property sign with name value: ''Intercity#A'' would be named ''Intercity1A'' and the second ''Intercity2A'', and so on. You can use this in combination with the spawner sign to spawn trains with a fixed naming system. This naming system can then be used for remote control to control all trains of a certain spawner or category.		The name property alters the name of the train. To account for multiple trains being renamed, and because every train needs a unique name, the # value is added as a counter-based replacement. For example, the first train passing over the property sign with name value: ''Intercity#A'' would be named ''Intercity1A'' and the second ''Intercity2A'', and so on. You can use this in combination with the spawner sign to spawn trains with a fixed naming system. This naming system can then be used for remote control to control all trains of a certain spawner or category.
	~~</translate>~~

	=== Wait Property ===		=== Wait Property ===
Line 257:		Line 256:

	They can also be configured with the <code>/train wait <property> <value></code> set of commands.		They can also be configured with the <code>/train wait <property> <value></code> set of commands.
			</translate>

MrTibo at 01:02, 24 December 2023

2023-12-24T01:02:05Z

← Older revision		Revision as of 01:02, 24 December 2023
Line 57:		Line 57:
	\| tag1<br>		\| tag1<br>
	\| Add a single tag<br>		\| Add a single tag<br>
	\|-
	~~\| addticket<br>~~
	~~\| expresstrain<br>~~
	~~\| Add a ticket that can be used for this train<br>~~
	\|-		\|-
	\| settag<br>		\| settag<br>
	\| taga<br>		\| taga<br>
	\| Set to a single tag<br>		\| Set to a single tag<br>
	\|-
	~~\| setticket<br>~~
	~~\| expresstrain<br>~~
	~~\| Set the train to only accept this ticket<br>~~
	\|-		\|-
	\| remtag		\| remtag
Line 74:		Line 66:
	\| Remove a single tag		\| Remove a single tag
	\|-		\|-
	\| remticket~~<br>~~		\| addticket
	\| expresstrain~~<br>~~		\| expresstrain
	\| Remove a ticket so it can no longer be used for this train~~<br>~~		\| Add a ticket that can be used for this train
			\|-
			\| setticket
			\| expresstrain
			\| Set the train to only accept this ticket
			\|-
			\| remticket
			\| expresstrain
			\| Remove a ticket so it can no longer be used for this train
	\|-		\|-
	\| addowner<br>		\| addowner<br>

MrTibo: tickets property should be documented lol

2023-12-24T01:00:27Z

tickets property should be documented lol

← Older revision		Revision as of 01:00, 24 December 2023
Line 57:		Line 57:
	\| tag1<br>		\| tag1<br>
	\| Add a single tag<br>		\| Add a single tag<br>
			\|-
			\| addticket<br>
			\| expresstrain<br>
			\| Add a ticket that can be used for this train<br>
	\|-		\|-
	\| settag<br>		\| settag<br>
	\| taga<br>		\| taga<br>
	\| Set to a single tag<br>		\| Set to a single tag<br>
			\|-
			\| setticket<br>
			\| expresstrain<br>
			\| Set the train to only accept this ticket<br>
	\|-		\|-
	\| remtag		\| remtag
	\| a		\| a
	\| Remove a single tag		\| Remove a single tag
			\|-
			\| remticket<br>
			\| expresstrain<br>
			\| Remove a ticket so it can no longer be used for this train<br>
	\|-		\|-
	\| addowner<br>		\| addowner<br>