TrainCarts/Lag - Revision history

Bergerkiller at 09:44, 12 October 2025

2025-10-12T09:44:24Z

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

	<!--T:2-->		<!--T:2-->
	Using the plugin in some way may cause server or client lag. This page details causes of lag, and how to deal with them.		Using the plugin in some way may cause server or client lag. This page details causes of lag, and how to deal with them.

Bergerkiller: Marked this version for translation

2025-06-30T17:15:57Z

Marked this version for translation

← Older revision		Revision as of 17:15, 30 June 2025
Line 20:		Line 20:
	<translate>		<translate>

			<!--T:20-->
	You can also configure this for all minecarts placed by Players, or for existing saved trains. Edit this for the train configuration in <code>DefaulTrainProperties.yml</code> or <code>SavedTrainProperties.yml</code>:		You can also configure this for all minecarts placed by Players, or for existing saved trains. Edit this for the train configuration in <code>DefaulTrainProperties.yml</code> or <code>SavedTrainProperties.yml</code>:
	</translate>		</translate>

Bergerkiller at 17:15, 30 June 2025

2025-06-30T17:15:51Z

@@ Line 19: / Line 19: @@
 {{Command|train collision block cancel|Turns off block collisions, trains will fall through the ground|train.property.collision}}
 <translate>
 == Large wait distance == <!--T:7-->

Bergerkiller: Marked this version for translation

2025-01-19T13:20:11Z

Marked this version for translation

← Older revision		Revision as of 13:20, 19 January 2025
Line 32:		Line 32:
	Generally a single train keeping chunks loaded is not a big deal, it's no different from a player moving from one location to another. But having hundreds of them on far reaches of the server could cause problems.		Generally a single train keeping chunks loaded is not a big deal, it's no different from a player moving from one location to another. But having hundreds of them on far reaches of the server could cause problems.

			<!--T:19-->
	You can improve performance by lowering the radius trains keep loaded, or configuring it to not simulate the chunks they keep loaded. This should be done for when the train is traveling long distances.		You can improve performance by lowering the radius trains keep loaded, or configuring it to not simulate the chunks they keep loaded. This should be done for when the train is traveling long distances.

Bergerkiller at 13:20, 19 January 2025

2025-01-19T13:20:04Z

← Older revision		Revision as of 13:20, 19 January 2025
Line 27:		Line 27:

	<!--T:10-->		<!--T:10-->
	Trains can keep chunks loaded, but too many loaded chunks may also hurt server performance. They consume RAM, which might cause an out-of-memory situation. They may also contain entities or redstone contraptions that all contribute to a worsened TPS. As trains move, they load and unload chunks continuously, which might also cause problems.		Trains can [[TrainCarts/Signs/Property#Keep_Chunks_Loaded\|keep chunks loaded]], but too many loaded chunks may also hurt server performance. They consume RAM, which might cause an out-of-memory situation. They may also contain entities or redstone contraptions that all contribute to a worsened TPS. As trains move, they load and unload chunks continuously, which might also cause problems.

	<!--T:11-->		<!--T:11-->
	Generally a single train keeping chunks loaded is not a big deal, it's no different from a player moving from one location to another. But having hundreds of them on far reaches of the server could cause problems.		Generally a single train keeping chunks loaded is not a big deal, it's no different from a player moving from one location to another. But having hundreds of them on far reaches of the server could cause problems.

			You can improve performance by lowering the radius trains keep loaded, or configuring it to not simulate the chunks they keep loaded. This should be done for when the train is traveling long distances.

	== Limit the number of trains == <!--T:12-->		== Limit the number of trains == <!--T:12-->

Bergerkiller: Marked this version for translation

2024-09-03T12:31:28Z

Marked this version for translation

← Older revision		Revision as of 12:31, 3 September 2024
Line 1:		Line 1:
	<languages/>		<languages/>
	<translate>		<translate>
			<!--T:1-->
	[[Special:MyLanguage/TrainCarts\|« Go back]]		[[Special:MyLanguage/TrainCarts\|« Go back]]

			<!--T:2-->
	Using the plugin in some way may cause server or client lag. This page details causes of lag, and how to deal with them.		Using the plugin in some way may cause server or client lag. This page details causes of lag, and how to deal with them.

	== Complex 3D models ==		== Complex 3D models == <!--T:3-->

			<!--T:4-->
	Minecraft is not very good at rendering complicated voxel models. If you use a custom resource pack on the server that has far too complicated models, it can cause the FPS of the client to drop. Always review models before you use them on a live server. The model JSON filesize is a strong indicator.		Minecraft is not very good at rendering complicated voxel models. If you use a custom resource pack on the server that has far too complicated models, it can cause the FPS of the client to drop. Always review models before you use them on a live server. The model JSON filesize is a strong indicator.

	== Large carts ==		== Large carts == <!--T:5-->

			<!--T:6-->
	When configuring the [[Special:MyLanguage/TrainCarts/Attachments/Physical\|physical]] attributes of a cart in the [[Special:MyLanguage/TrainCarts/Attachments\|attachment editor]], the cart size can be set very large. This changes the bounding box of the entity itself, which may result in worsened TPS on the server. The main cause is the block collision calculations the server does. To prevent this problem, disable block collisions entirely		When configuring the [[Special:MyLanguage/TrainCarts/Attachments/Physical\|physical]] attributes of a cart in the [[Special:MyLanguage/TrainCarts/Attachments\|attachment editor]], the cart size can be set very large. This changes the bounding box of the entity itself, which may result in worsened TPS on the server. The main cause is the block collision calculations the server does. To prevent this problem, disable block collisions entirely
	</translate>		</translate>
	{{Command\|train collision block cancel\|Turns off block collisions, trains will fall through the ground\|train.property.collision}}		{{Command\|train collision block cancel\|Turns off block collisions, trains will fall through the ground\|train.property.collision}}
	<translate>		<translate>
	== Large wait distance ==		== Large wait distance == <!--T:7-->

			<!--T:8-->
	The [[Special:MyLanguage/TrainCarts/Signs/Property#Wait_Property\|wait distance property]] can be set for a train, so that it will keep distance to trains up ahead. This does require tracking all the rails the full distance in front of the train. Setting this distance too high can therefore result in worsened TPS on the server.		The [[Special:MyLanguage/TrainCarts/Signs/Property#Wait_Property\|wait distance property]] can be set for a train, so that it will keep distance to trains up ahead. This does require tracking all the rails the full distance in front of the train. Setting this distance too high can therefore result in worsened TPS on the server.

	== Keep chunks loaded ==		== Keep chunks loaded == <!--T:9-->

			<!--T:10-->
	Trains can keep chunks loaded, but too many loaded chunks may also hurt server performance. They consume RAM, which might cause an out-of-memory situation. They may also contain entities or redstone contraptions that all contribute to a worsened TPS. As trains move, they load and unload chunks continuously, which might also cause problems.		Trains can keep chunks loaded, but too many loaded chunks may also hurt server performance. They consume RAM, which might cause an out-of-memory situation. They may also contain entities or redstone contraptions that all contribute to a worsened TPS. As trains move, they load and unload chunks continuously, which might also cause problems.

			<!--T:11-->
	Generally a single train keeping chunks loaded is not a big deal, it's no different from a player moving from one location to another. But having hundreds of them on far reaches of the server could cause problems.		Generally a single train keeping chunks loaded is not a big deal, it's no different from a player moving from one location to another. But having hundreds of them on far reaches of the server could cause problems.

	== Limit the number of trains ==		== Limit the number of trains == <!--T:12-->

			<!--T:13-->
	You can edit <code>plugins/Train_Carts/config.yml</code> to limit how many individual TrainCarts Minecart entities can exist per world. This prevents an out of control spawner sign or player abuse lagging the server to a halt.		You can edit <code>plugins/Train_Carts/config.yml</code> to limit how many individual TrainCarts Minecart entities can exist per world. This prevents an out of control spawner sign or player abuse lagging the server to a halt.
	<pre>		<pre>
Line 36:		Line 44:
	maxCartsPerWorld: -1		maxCartsPerWorld: -1

	# Whether to include unloaded trains/carts in the maxCartsPerWorld limit		<!--T:14-->
			# Whether to include unloaded trains/carts in the maxCartsPerWorld limit
	countUnloaded: false		countUnloaded: false

	# Maximum number of carts that can be joined together in a train		<!--T:15-->
			# Maximum number of carts that can be joined together in a train
	# Linking does not happen when it would exceed this limit,		# Linking does not happen when it would exceed this limit,
	# and trains longer than this cannot be spawned		# and trains longer than this cannot be spawned
Line 46:		Line 56:
	</pre>		</pre>

	== Saved Train Spawn Limits ==		== Saved Train Spawn Limits == <!--T:16-->

			<!--T:17-->
	Besides a global limit, it is possible to configure a spawn limit per saved train. After having saved a train with <code>/train save name</code>, you can configure a spawn limit with <code>/savedtrain name spawnlimit <limit></code>.		Besides a global limit, it is possible to configure a spawn limit per saved train. After having saved a train with <code>/train save name</code>, you can configure a spawn limit with <code>/savedtrain name spawnlimit <limit></code>.

			<!--T:18-->
	Spawn signs and train chests configured with the train name will stop spawning trains when this limit is reached. This is particularly useful with [[Special:MyLanguage/TrainCarts/Signs/Spawner\|auto-spawning spawn signs]] that populate a train network, combined with setting <code>destroyAllOnShutdown</code> to true in '''config.yml'''.		Spawn signs and train chests configured with the train name will stop spawning trains when this limit is reached. This is particularly useful with [[Special:MyLanguage/TrainCarts/Signs/Spawner\|auto-spawning spawn signs]] that populate a train network, combined with setting <code>destroyAllOnShutdown</code> to true in '''config.yml'''.
	</translate>		</translate>

Bergerkiller at 12:31, 3 September 2024

2024-09-03T12:31:23Z

← Older revision		Revision as of 12:31, 3 September 2024
Line 15:		Line 15:
	{{Command\|train collision block cancel\|Turns off block collisions, trains will fall through the ground\|train.property.collision}}		{{Command\|train collision block cancel\|Turns off block collisions, trains will fall through the ground\|train.property.collision}}
	<translate>		<translate>

	== Large wait distance ==		== Large wait distance ==

Bergerkiller at 12:31, 3 September 2024

2024-09-03T12:31:12Z

← Older revision		Revision as of 12:31, 3 September 2024
Line 4:		Line 4:

	Using the plugin in some way may cause server or client lag. This page details causes of lag, and how to deal with them.		Using the plugin in some way may cause server or client lag. This page details causes of lag, and how to deal with them.


	== Complex 3D models ==		== Complex 3D models ==

	Minecraft is not very good at rendering complicated voxel models. If you use a custom resource pack on the server that has far too complicated models, it can cause the FPS of the client to drop. Always review models before you use them on a live server. The model JSON filesize is a strong indicator.		Minecraft is not very good at rendering complicated voxel models. If you use a custom resource pack on the server that has far too complicated models, it can cause the FPS of the client to drop. Always review models before you use them on a live server. The model JSON filesize is a strong indicator.


	== Large carts ==		== Large carts ==
Line 17:		Line 15:
	{{Command\|train collision block cancel\|Turns off block collisions, trains will fall through the ground\|train.property.collision}}		{{Command\|train collision block cancel\|Turns off block collisions, trains will fall through the ground\|train.property.collision}}
	<translate>		<translate>


	== Large wait distance ==		== Large wait distance ==

	The [[Special:MyLanguage/TrainCarts/Signs/Property#Wait_Property\|wait distance property]] can be set for a train, so that it will keep distance to trains up ahead. This does require tracking all the rails the full distance in front of the train. Setting this distance too high can therefore result in worsened TPS on the server.		The [[Special:MyLanguage/TrainCarts/Signs/Property#Wait_Property\|wait distance property]] can be set for a train, so that it will keep distance to trains up ahead. This does require tracking all the rails the full distance in front of the train. Setting this distance too high can therefore result in worsened TPS on the server.


	== Keep chunks loaded ==		== Keep chunks loaded ==
Line 29:		Line 25:

	Generally a single train keeping chunks loaded is not a big deal, it's no different from a player moving from one location to another. But having hundreds of them on far reaches of the server could cause problems.		Generally a single train keeping chunks loaded is not a big deal, it's no different from a player moving from one location to another. But having hundreds of them on far reaches of the server could cause problems.


	== Limit the number of trains ==		== Limit the number of trains ==
Line 51:		Line 46:
	maxCartsPerTrain: -1		maxCartsPerTrain: -1
	</pre>		</pre>


	== Saved Train Spawn Limits ==		== Saved Train Spawn Limits ==

Bergerkiller: Prepared the page for translation

2024-09-03T12:23:23Z

Prepared the page for translation

← Older revision		Revision as of 12:23, 3 September 2024
Line 1:		Line 1:
	[[TrainCarts\|« Go back]]		<languages/>
			<translate>
			[[Special:MyLanguage/TrainCarts\|« Go back]]

	Using the plugin in some way may cause server or client lag. This page details causes of lag, and how to deal with them.		Using the plugin in some way may cause server or client lag. This page details causes of lag, and how to deal with them.


	== Complex 3D models ==		== Complex 3D models ==

	Minecraft is not very good at rendering complicated voxel models. If you use a custom resource pack on the server that has far too complicated models, it can cause the FPS of the client to drop. Always review models before you use them on a live server. The model JSON filesize is a strong indicator.		Minecraft is not very good at rendering complicated voxel models. If you use a custom resource pack on the server that has far too complicated models, it can cause the FPS of the client to drop. Always review models before you use them on a live server. The model JSON filesize is a strong indicator.


	== Large carts ==		== Large carts ==
	When configuring the [[TrainCarts/Attachments/Physical\|physical]] attributes of a cart in the [[TrainCarts/Attachments\|attachment editor]], the cart size can be set very large. This changes the bounding box of the entity itself, which may result in worsened TPS on the server. The main cause is the block collision calculations the server does. To prevent this problem, disable block collisions entirely
			When configuring the [[Special:MyLanguage/TrainCarts/Attachments/Physical\|physical]] attributes of a cart in the [[Special:MyLanguage/TrainCarts/Attachments\|attachment editor]], the cart size can be set very large. This changes the bounding box of the entity itself, which may result in worsened TPS on the server. The main cause is the block collision calculations the server does. To prevent this problem, disable block collisions entirely
			</translate>
	{{Command\|train collision block cancel\|Turns off block collisions, trains will fall through the ground\|train.property.collision}}		{{Command\|train collision block cancel\|Turns off block collisions, trains will fall through the ground\|train.property.collision}}
			<translate>


	== Large wait distance ==		== Large wait distance ==
	The [[TrainCarts/Signs/Property#Wait_Property\|wait distance property]] can be set for a train, so that it will keep distance to trains up ahead. This does require tracking all the rails the full distance in front of the train. Setting this distance too high can therefore result in worsened TPS on the server.
			The [[Special:MyLanguage/TrainCarts/Signs/Property#Wait_Property\|wait distance property]] can be set for a train, so that it will keep distance to trains up ahead. This does require tracking all the rails the full distance in front of the train. Setting this distance too high can therefore result in worsened TPS on the server.


	== Keep chunks loaded ==		== Keep chunks loaded ==

	Trains can keep chunks loaded, but too many loaded chunks may also hurt server performance. They consume RAM, which might cause an out-of-memory situation. They may also contain entities or redstone contraptions that all contribute to a worsened TPS. As trains move, they load and unload chunks continuously, which might also cause problems.		Trains can keep chunks loaded, but too many loaded chunks may also hurt server performance. They consume RAM, which might cause an out-of-memory situation. They may also contain entities or redstone contraptions that all contribute to a worsened TPS. As trains move, they load and unload chunks continuously, which might also cause problems.

	Generally a single train keeping chunks loaded is not a big deal, it's no different from a player moving from one location to another. But having hundreds of them on far reaches of the server could cause problems.		Generally a single train keeping chunks loaded is not a big deal, it's no different from a player moving from one location to another. But having hundreds of them on far reaches of the server could cause problems.


	== Limit the number of trains ==		== Limit the number of trains ==

	You can edit <code>plugins/Train_Carts/config.yml</code> to limit how many individual TrainCarts Minecart entities can exist per world. This prevents an out of control spawner sign or player abuse lagging the server to a halt.		You can edit <code>plugins/Train_Carts/config.yml</code> to limit how many individual TrainCarts Minecart entities can exist per world. This prevents an out of control spawner sign or player abuse lagging the server to a halt.
	<pre>		<pre>
Line 37:		Line 51:
	maxCartsPerTrain: -1		maxCartsPerTrain: -1
	</pre>		</pre>


	== Saved Train Spawn Limits ==		== Saved Train Spawn Limits ==

	Besides a global limit, it is possible to configure a spawn limit per saved train. After having saved a train with <code>/train save name</code>, you can configure a spawn limit with <code>/savedtrain name spawnlimit <limit></code>.		Besides a global limit, it is possible to configure a spawn limit per saved train. After having saved a train with <code>/train save name</code>, you can configure a spawn limit with <code>/savedtrain name spawnlimit <limit></code>.

	Spawn signs and train chests configured with the train name will stop spawning trains when this limit is reached. This is particularly useful with [[TrainCarts/Signs/Spawner\|auto-spawning spawn signs]] that populate a train network, combined with setting <code>destroyAllOnShutdown</code> to true in '''config.yml'''.		Spawn signs and train chests configured with the train name will stop spawning trains when this limit is reached. This is particularly useful with [[Special:MyLanguage/TrainCarts/Signs/Spawner\|auto-spawning spawn signs]] that populate a train network, combined with setting <code>destroyAllOnShutdown</code> to true in '''config.yml'''.
			</translate>

Bergerkiller at 13:20, 29 December 2023

2023-12-29T13:20:58Z

← Older revision		Revision as of 13:20, 29 December 2023
Line 39:		Line 39:

	== Saved Train Spawn Limits ==		== Saved Train Spawn Limits ==
	Besides a global limit, it is possible to configure a spawn limit per saved train. After having saved at train with <code>/train save name</code>, you can configure a spawn limit with <code>/savedtrain name spawnlimit <limit></code>.		Besides a global limit, it is possible to configure a spawn limit per saved train. After having saved a train with <code>/train save name</code>, you can configure a spawn limit with <code>/savedtrain name spawnlimit <limit></code>.

	Spawn signs and train chests configured with the train name will stop spawning trains when this limit is reached. This is particularly useful with [[TrainCarts/Signs/Spawner\|auto-spawning spawn signs]] that populate a train network, combined with setting <code>destroyAllOnShutdown</code> to true in '''config.yml'''.		Spawn signs and train chests configured with the train name will stop spawning trains when this limit is reached. This is particularly useful with [[TrainCarts/Signs/Spawner\|auto-spawning spawn signs]] that populate a train network, combined with setting <code>destroyAllOnShutdown</code> to true in '''config.yml'''.