From BergerHealer Wiki
Jump to navigation Jump to search
This page is a translated version of the page TrainCarts and the translation is 6% complete.
Other languages:
Deutsch • ‎English • ‎Español • ‎Nederlands • ‎中文 • ‎中文(简体)‎ • ‎日本語 • ‎한국어
TrainCarts train 1.gif
Minecarts redefined
Spigot: TrainCarts
GitHub: TrainCarts

« 뒤로 가기

TrainCarts는 Bergerkiller가 개발한 플러그인이고, 마인카트에 관련된 모든 것을 가지고 있는 플러그인이다. (이후 번역 필요) It was initially developed to link multiple carts together, creating a moving train. Over time the plugin grew to host many more features, such as action signs, commands, properties, attachments and a broad API other plugins can implement to add their own features.

The first thing you will notice is that you can now connect carts together to form infinitely long trains. Every cart in this train is called a member, all members combined are called a group. Every member communicates with the group, so when the front cart hits a block, it stops the entire group. When someone pushes a cart, this pushing force is shared among all members. Therefore, long trains are less responsive than short trains.


Trains and individual carts of trains have properties. These can be set using commands (/train and /cart) or using the property sign.

New physics

Trains can travel on top of pressure plates and alongside ladders, and also upside-down below vanilla rails placed on a ceiling.


Loads of different signs are available to automate stations, eject trains, put players in trains or update train configuration.


The plugin has lots of commands you can use to alter the behavior of trains and minecarts.

Command Selectors

You can use command selectors like @train and @ptrain in all other commands (including non-traincarts commands) to perform actions on trains or player passengers of trains based on selector criteria. For tighter integration with other plugins like economies and status effects, this is the ideal mechanism.

Train Spawn Chest

A special item allows for trains to be picked up and spawned.

Path finding

Trains can have a destination set, after which switcher signs will automatically switch the track to lead the train towards it with the shortest route possible. This can be used to automate a large train network, sending trains to different stations fully automatically. It is also possible to configure a list of destinations the train should visit and have the train automatically go from one destination to the next.


Train ticket items can be used to restrict who can enter trains. They can also be used to assign properties to trains when used, such as assigning a destination to go to.


TrainCarts can be configured in the config.yml file. All setting nodes have a header to help you understand what that particular node adjusts. Other than that, you can set the default train properties (properties applied to new trains) in the DefaultTrainProperties.yml file. The nodes should speak for themselves. Try not to touch the other files, as it can cause corrupted save data, or the plugin getting out of sync. Deleting the files should re-set TrainCarts completely, may one of the files get corrupted. The plugin automatically generates all configuration needed.



Like in all plugins that use BKCommonLib as a base, all permissions can be found in PermissionDefaults.yml in the plugin folder. There they are all listed together with a description and permission default, which you can alter as well.


Some features by this plugin may result in server or client lag. There are ways to prevent them.

API and Add-ons

TrainCarts has a flexible API which allows other plugins to implement custom track, signs, attachments and more.

Useful Links

Traincarts Spigot Jenkins GitHub

BKCommonLib Spigot Jenkins GitHub

TC Coasters Spigot Jenkins GitHub

Depreciated Addons

(No longer supported in current versions of Traincarts)

ActionBlocks, added block-based systems to the game. They were dumbed-down versions of the sign systems mentioned above.