BergerHealer Wiki - User contributions [en]

TrainCarts/Train Spawn Chest

2026-03-07T13:04:55Z

Bergerkiller: Marked this version for translation

<languages/>
<translate>
== Introduction == 


[[File:Train_Spawn_Chest_Small.gif|thumb|Train spawn chest is used to pick up a train and spawn it again|link=File:Train_Spawn_Chest.gif]]
The '''Train spawn chest''' is a special item that can hold train information. While holding the item players can right-click on trains to ''suck up'' the train into the item. Then, by right-clicking on rails, players can spawn the train again. All train properties are preserved.


Spawning on rails close to another train will add additional connected carts to that train. The orientation of looking at the rails changes in what orientation the new train is spawned.

== Permissions & Security == 
The train spawn chest can be used to duplicate items by picking up a train with chests containing items and spawning it again multiple times. Make sure to revoke the '''train.command.chest.use''' permission so that if a spawn chest item falls in the hands of survival players they cannot do this. Alternatively, deny the '''train.spawner.storage''' and '''train.spawner.hopper''' permissions so that players cannot spawn trains that contain item storage.

== Usage == 
To get the item, you need to use the following command:


{{Command|train chest|Give the player a new empty train chest item|train.command.chest.create}}


You can then right-click on rails to spawn a train there, or right-click existing trains to suck them into the item.
For this you also need the '''train.command.chest.use''' permission.

=== Spawn Pattern === 
You can also specify a [[Special:MyLanguage/TrainCarts/Spawning|train spawn pattern]] for the train to put in the item, the same pattern as used on the [[Special:MyLanguage/TrainCarts/Signs/Spawner|spawn sign]]:


{{Command|train chest mytrain|Give the player a new empty train chest item with a pre-configured train inside|train.command.chest.create}}


To update the pattern stored in the spawn chest, hold the item to update and use:


{{Command|train chest set mytrain|Put a new train inside the item, [[Special:MyLanguage/TrainCarts/Spawning|spawn pattern syntax]]|train.command.chest.create}}

=== Special Commands === 
Hold the item to update and use:


{{Command|train chest clear|Makes the item empty|train.command.chest.create}}
{{Command|train chest lock|Locks the item, preventing it from picking up trains when clicked|train.command.chest.create}}
{{Command|train chest unlock|Unlocks the item so it can pick up trains again|train.command.chest.create}}
{{Command|train chest name My Train|Gives the item a human-readable name to identify it|train.command.chest.create}}
{{Command|train chest finite yes|Makes the chest item have finite (1) or infinite number of spawns|train.command.chest.create}}
{{Command|train chest speed 2.0|Makes the chest item spawn the train with an initial speed of 2 blocks/tick|train.command.chest.create}}

=== Giving to other players === 


You can give a completely configured item to other players. This command can also be executed from command blocks, and supports the @p syntax for that purpose.


{{Command|train chest give PlayerName|Gives a train chest item to a player|train.command.chest.create}}


This command supports all the same updating options but as flags.


{{Command|train chest give bergerkiller --finite --locked --train Intercity01|Gives a single-use spawn chest that spawns the Intercity01 train. Can not be used to pick up trains.|train.command.chest.create}}

</translate>

TrainCarts/Train Spawn Chest

2026-03-07T13:04:48Z

Bergerkiller:

<languages/>
<translate>
== Introduction == 


[[File:Train_Spawn_Chest_Small.gif|thumb|Train spawn chest is used to pick up a train and spawn it again|link=File:Train_Spawn_Chest.gif]]
The '''Train spawn chest''' is a special item that can hold train information. While holding the item players can right-click on trains to ''suck up'' the train into the item. Then, by right-clicking on rails, players can spawn the train again. All train properties are preserved.


Spawning on rails close to another train will add additional connected carts to that train. The orientation of looking at the rails changes in what orientation the new train is spawned.

== Permissions & Security ==
The train spawn chest can be used to duplicate items by picking up a train with chests containing items and spawning it again multiple times. Make sure to revoke the '''train.command.chest.use''' permission so that if a spawn chest item falls in the hands of survival players they cannot do this. Alternatively, deny the '''train.spawner.storage''' and '''train.spawner.hopper''' permissions so that players cannot spawn trains that contain item storage.

== Usage == 
To get the item, you need to use the following command:


{{Command|train chest|Give the player a new empty train chest item|train.command.chest.create}}


You can then right-click on rails to spawn a train there, or right-click existing trains to suck them into the item.
For this you also need the '''train.command.chest.use''' permission.

=== Spawn Pattern === 
You can also specify a [[Special:MyLanguage/TrainCarts/Spawning|train spawn pattern]] for the train to put in the item, the same pattern as used on the [[Special:MyLanguage/TrainCarts/Signs/Spawner|spawn sign]]:


{{Command|train chest mytrain|Give the player a new empty train chest item with a pre-configured train inside|train.command.chest.create}}


To update the pattern stored in the spawn chest, hold the item to update and use:


{{Command|train chest set mytrain|Put a new train inside the item, [[Special:MyLanguage/TrainCarts/Spawning|spawn pattern syntax]]|train.command.chest.create}}

=== Special Commands === 
Hold the item to update and use:


{{Command|train chest clear|Makes the item empty|train.command.chest.create}}
{{Command|train chest lock|Locks the item, preventing it from picking up trains when clicked|train.command.chest.create}}
{{Command|train chest unlock|Unlocks the item so it can pick up trains again|train.command.chest.create}}
{{Command|train chest name My Train|Gives the item a human-readable name to identify it|train.command.chest.create}}
{{Command|train chest finite yes|Makes the chest item have finite (1) or infinite number of spawns|train.command.chest.create}}
{{Command|train chest speed 2.0|Makes the chest item spawn the train with an initial speed of 2 blocks/tick|train.command.chest.create}}

=== Giving to other players === 


You can give a completely configured item to other players. This command can also be executed from command blocks, and supports the @p syntax for that purpose.


{{Command|train chest give PlayerName|Gives a train chest item to a player|train.command.chest.create}}


This command supports all the same updating options but as flags.


{{Command|train chest give bergerkiller --finite --locked --train Intercity01|Gives a single-use spawn chest that spawns the Intercity01 train. Can not be used to pick up trains.|train.command.chest.create}}

</translate>

TrainCarts/Signs/Skip

2026-03-03T09:23:22Z

Bergerkiller:

<languages/>
<translate>
== Introduction == 


Skip sign causes the train to skip one or more signs further up ahead based on statements similar to the switcher sign.
It can be used to make trains skip a station sign when a certain destination is not set, for example.

== Syntax == 

</translate>
{{sign|[train]|skip 2 1|<statement 1>|<statement 2>}}
<translate>


* First line: [train] or [cart]. When the sign to be skipped works on a per-cart basis, using [cart] instead of [train] can be better. In general [train] is all you'll need. Like with other signs, redstone power matters. This means the skip sign is only active when powered by redstone. You can use [+train] or [+cart] to always power it.
* Second line: ''skip'', which without further arguments will skip the very next sign the train crosses. When followed by one number, the number sets the number of signs the train has to cross until the sign is skipped. When followed by a second number, the second number sets the number of signs to skip. In the example, a single sign will be skipped after having crossed two signs. A non-numeric sign filter can also be specified.
* Third and fourth lines: [[Special:MyLanguage/TrainCarts/Signs/Statements|statements]] (AND-ed together) for when to activate the skip sign. It is possible to put | in front of the second statement so that the two are OR-ed together instead. Leaving both lines empty makes the skip sign activate all the time.

=== Filter === 
On the second line of the skip sign a filter can be added before any skip offsets/counts. This makes the skip mechanism only ignore signs whose second line starts with the filter specified. The filter is case-insensitive. For example, the following skip sign skips the very next station sign, but ignores non-station signs:


{{sign|[+train]|skip station 0 1|}}

== Example == 


[[File:Skip sign example.png|thumb|left|940px|Trains come from the left and first hit the powered ([+train]) skip sign. When the train does not have destination ''square_west'' set or ( ''<nowiki>|</nowiki>'' ) is empty, the skip sign is activated and skips the very next sign. In this case that's the station sign. As a result, trains not meant for this station will cross the station sign without being stopped for 5 seconds.]]
</translate>

TrainCarts/Attachments

2026-01-17T17:36:33Z

Bergerkiller: Marked this version for translation

<languages/>
<translate>


[[File:Attachment_editor_wooden_car.png|thumb|A customized minecart is being edited using the attachment editor]]
[[File:Rotating_attachments.gif|thumb|Two model attachments are animated, demonstrating the use of hierarchy]]

==Introduction== 
'''The Attachment Editor''' is an in-game interactive [[Special:MyLanguage/Map Display|Map Display]] with which individual carts of a train can be customized.
This menu is used to configure the appearance and behavior of carts, with a [[wikipedia:Tree structure|tree layout]]
showing the different attachments. Each attachment represents a part of the train, such as a moving entity or a seat designation.
Attachments added as a child to other attachments are positioned relative to the parent. This allows many attachments to be moved
and animated together as a whole.

==Basic usage== 

===Command=== 


To start using the attachment editor, players need to give themselves the map item:
</translate>
{{Command|train attachments|Give the player the attachment editor map item|train.command.editor}}
<translate>

===Editing=== 


To edit a single cart of a train, and make it visible in the editor, you need to select the cart first.


[[Special:MyLanguage/TrainCarts/Editing|» Editing]]

===Navigation=== 


Each attachment is displayed on a different row, with an indent to the right every time it is added to a new parent. To navigate between attachments, use the Up/Down (W/S) steering controls. For each attachment selected, different menus can be accessed by pressing Left/Right (A/D) and Jump (spacebar) afterwards. Once inside a menu, the sneak button (shift) can be used to exit it again. This behavior is the same for all other menus. To move around while still viewing the editor, it can be placed into the off-hand (''typically F'').


To add new attachments, duplicate them, change the position in the tree hierarchy, or to delete them, use the [[Special:MyLanguage/TrainCarts/Attachments/General|General menu]] denoted by three horizontal lines.

===Dropping items=== 


[[File:Attachments_Drop_Item_Small.gif|thumb|An item is dropped from the inventory, configuring the attachment|link=File:Attachments_Drop_Item.gif]]
Menus where an item is being configured can be set instantly by dropping an item from the player's inventory. With the menu open, simply open the inventory, pick the item to set, and click on the outside of the inventory to drop it. The drop will be cancelled and the item set in the menu.

===Numbers=== 


Number sliders are used to configure numeric values, such position coordinates. Pressing the Left/Right buttons once will increment/decrement a very small amount. Holding the buttons for a longer time causes the number to increment/decrement faster and faster the longer it is being held down.


By holding Spacebar a number field can be reset to its default, usually 0. By holding spacebar and then pressing left/right, a special action can be performed. Usually this means inverting the value (-5 -> 5) or changing an angle in 90 degree steps.

===Text=== 


Text is input using an anvil menu. After typing in the desired text, click on the emerald to proceed, or the barrier item to cancel the change.

===Setting using commands=== 
</translate>
{{Command|train menu set [value]|Set a numeric or text value for the currently selected menu|train.command.editor}}
<translate>

==Gotchas== 
* Make sure to use <code>/train save name</code> to save your train regularly! Only saved trains can be restored
* Make use of the [[Special:MyLanguage/TrainCarts/Train Spawn Chest|train storage chest]] to move your train around or to recombine the carts
* Change spacing between carts, and where wheels are positioned, in the [[Special:MyLanguage/TrainCarts/Attachments/Physical|Physical menu]]
* When animating, make sure your animation frames have a delta-T greater than 0. Otherwise animation speed will not function.
* The new Display Entities cannot be clicked by default:
** If you cannot click to edit a train, look at it and do <code>/train edit</code> to select it
** To allow players to click on the cart to enter a seat, make sure to add a '''Hitbox attachment'''.
* You can save a sub-tree of attachments in the [[Special:MyLanguage/TrainCarts/Attachments/Model#Model_Store|Model Store]] in the [[Special:MyLanguage/TrainCarts/Attachments/General|General menu]], and create it in multiple places using the [[Special:MyLanguage/TrainCarts/Attachments/Model|'''Model Attachment''']]. There is also a clipboard and import/export function.

==Menu== 
===Appearance===
The Appearance Menu contains a selector at the top where the attachment type is configured, with the remainder of the menu automatically filled with this type's configuration.


{| class="wikitable" style="margin:left"
|+Attachment Types
! Type !! Description
|-
| '''Empty''' || Displays nothing. Used as a marker attachment to easily position multiple other attachments, and as an anchor for animations
|-bgcolor="#dddddd"
| '''Hitbox''' || Creates an invisible box that can be clicked. Important for entering seats. Size is configured in the Position menu.
|-
| [[Special:MyLanguage/TrainCarts/Attachments/Entity|'''Entity''']] || Displays an Entity like a Minecart or Mob
|-bgcolor="#dddddd"
| [[Special:MyLanguage/TrainCarts/Attachments/Item|'''Item''']] || Displays an Item on an Armorstand or using a Display Entity
|-
| [[Special:MyLanguage/TrainCarts/Attachments/Block|'''Block''']] || Displays a Block using a Display Entity. Only available on Minecraft 1.20+.
|-bgcolor="#dddddd"
| [[Special:MyLanguage/TrainCarts/Attachments/Seat|'''Seat''']] || A seat where a single player or entity can sit
|-
| [[Special:MyLanguage/TrainCarts/Attachments/Model|'''Model''']] || Loads in a full attachment configuration from the model store
|-bgcolor="#dddddd"
| '''Text''' || Floating Text Balloon
|-
| '''Platform''' || A moving shulker box that players can stand on. Does not work moving up.
|-bgcolor="#dddddd"
| '''Schematic''' || Displays multiple blocks using a WorldEdit saved Schematic
|-
| '''Light''' || When [https://www.spigotmc.org/resources/lightapi-fork.48247/ LightAPI] is installed, spawns a moving light source at the attachment position
|-bgcolor="#dddddd"
| [[Special:MyLanguage/TrainCarts/Attachments/Sound|'''Sound''']] || Adds a sound effect played with effect signs, command or the sequencer
|-
| [[Special:MyLanguage/TrainCarts/Attachments/Sequencer|'''Sequencer''']] || Automatically plays effects. Used to create ambient sound loops, such as engine noises, or to activate particle effects on a loop, such as a smoke stack.
|}

===Physical=== 
The Physical Menu configures the length of the cart and where the rail-tracking wheels of the cart are positioned.


[[Special:MyLanguage/TrainCarts/Attachments/Physical|» Physical Menu]]

===Position=== 
The position menu configures the position and rotation of the attachment. Includes additional options for some types of attachments, such as scale and transform options for items.


[[Special:MyLanguage/TrainCarts/Attachments/Position|» Position Menu]]

===Animation=== 
Attachments can be animated, making them move or rotate around. This is especially useful for funfair rides, or animated doors.


[[Special:MyLanguage/TrainCarts/Attachments/Animation|» Animation Menu]]


Animations play using linear interpolation. To create more lively animations, you can use Silacide's interpolation tool: https://fantasiecraft.be/EXPOT/Interpolation-Tool-Lite/

===General=== 
The general menu is used to add new attachments, delete them, move them around, name them or load/save them from the [[Special:MyLanguage/TrainCarts/Attachments/Model#Model_Store|model store]].


[[Special:MyLanguage/TrainCarts/Attachments/General|» General Menu]]

==Effect Activation== 
Effect attachments such as the [[Special:MyLanguage/TrainCarts/Attachments/Sound|sound attachment]] must be activated. First, the attachment must be [[Special:MyLanguage/TrainCarts/Attachments/General#Name|named in the general menu]]. It can then be activated in multiple ways:
* Using the [[Special:MyLanguage/TrainCarts/Signs/Effect|effect sign]]
* Using the <code>/train effect <name></code> command
* Using the [[Special:MyLanguage/TrainCarts/Attachments/Sequencer|sequencer attachment]]

==Backlog== 

===Editor=== 


* [[Special:MyLanguage/TrainCarts/Attachments/Saving|Saving trains (needs a cross-link about import/export and the whole savedtrain logic)]]
-> Navigating the tree menu

===Position=== 


* [[Special:MyLanguage/TrainCarts/Attachments/TransformType|Transform type]]
* [[Special:MyLanguage/TrainCarts/Attachments/Anchor|Anchor]]

===Animations=== 


* [[Special:MyLanguage/TrainCarts/Animations/Overview|Overview]]
</translate>

TrainCarts/Attachments

2026-01-17T17:36:22Z

Bergerkiller:

<languages/>
<translate>


[[File:Attachment_editor_wooden_car.png|thumb|A customized minecart is being edited using the attachment editor]]
[[File:Rotating_attachments.gif|thumb|Two model attachments are animated, demonstrating the use of hierarchy]]

==Introduction== 
'''The Attachment Editor''' is an in-game interactive [[Special:MyLanguage/Map Display|Map Display]] with which individual carts of a train can be customized.
This menu is used to configure the appearance and behavior of carts, with a [[wikipedia:Tree structure|tree layout]]
showing the different attachments. Each attachment represents a part of the train, such as a moving entity or a seat designation.
Attachments added as a child to other attachments are positioned relative to the parent. This allows many attachments to be moved
and animated together as a whole.

==Basic usage== 

===Command=== 


To start using the attachment editor, players need to give themselves the map item:
</translate>
{{Command|train attachments|Give the player the attachment editor map item|train.command.editor}}
<translate>

===Editing=== 


To edit a single cart of a train, and make it visible in the editor, you need to select the cart first.


[[Special:MyLanguage/TrainCarts/Editing|» Editing]]

===Navigation=== 


Each attachment is displayed on a different row, with an indent to the right every time it is added to a new parent. To navigate between attachments, use the Up/Down (W/S) steering controls. For each attachment selected, different menus can be accessed by pressing Left/Right (A/D) and Jump (spacebar) afterwards. Once inside a menu, the sneak button (shift) can be used to exit it again. This behavior is the same for all other menus. To move around while still viewing the editor, it can be placed into the off-hand (''typically F'').


To add new attachments, duplicate them, change the position in the tree hierarchy, or to delete them, use the [[Special:MyLanguage/TrainCarts/Attachments/General|General menu]] denoted by three horizontal lines.

===Dropping items=== 


[[File:Attachments_Drop_Item_Small.gif|thumb|An item is dropped from the inventory, configuring the attachment|link=File:Attachments_Drop_Item.gif]]
Menus where an item is being configured can be set instantly by dropping an item from the player's inventory. With the menu open, simply open the inventory, pick the item to set, and click on the outside of the inventory to drop it. The drop will be cancelled and the item set in the menu.

===Numbers=== 


Number sliders are used to configure numeric values, such position coordinates. Pressing the Left/Right buttons once will increment/decrement a very small amount. Holding the buttons for a longer time causes the number to increment/decrement faster and faster the longer it is being held down.


By holding Spacebar a number field can be reset to its default, usually 0. By holding spacebar and then pressing left/right, a special action can be performed. Usually this means inverting the value (-5 -> 5) or changing an angle in 90 degree steps.

===Text=== 


Text is input using an anvil menu. After typing in the desired text, click on the emerald to proceed, or the barrier item to cancel the change.

===Setting using commands=== 
</translate>
{{Command|train menu set [value]|Set a numeric or text value for the currently selected menu|train.command.editor}}
<translate>

==Gotchas== 
* Make sure to use <code>/train save name</code> to save your train regularly! Only saved trains can be restored
* Make use of the [[Special:MyLanguage/TrainCarts/Train Spawn Chest|train storage chest]] to move your train around or to recombine the carts
* Change spacing between carts, and where wheels are positioned, in the [[Special:MyLanguage/TrainCarts/Attachments/Physical|Physical menu]]
* When animating, make sure your animation frames have a delta-T greater than 0. Otherwise animation speed will not function.
* The new Display Entities cannot be clicked by default:
** If you cannot click to edit a train, look at it and do <code>/train edit</code> to select it
** To allow players to click on the cart to enter a seat, make sure to add a '''Hitbox attachment'''.
* You can save a sub-tree of attachments in the [[Special:MyLanguage/TrainCarts/Attachments/Model#Model_Store|Model Store]] in the [[Special:MyLanguage/TrainCarts/Attachments/General|General menu]], and create it in multiple places using the [[Special:MyLanguage/TrainCarts/Attachments/Model|'''Model Attachment''']]. There is also a clipboard and import/export function.

==Menu== 
===Appearance===
The Appearance Menu contains a selector at the top where the attachment type is configured, with the remainder of the menu automatically filled with this type's configuration.


{| class="wikitable" style="margin:left"
|+Attachment Types
! Type !! Description
|-
| '''Empty''' || Displays nothing. Used as a marker attachment to easily position multiple other attachments, and as an anchor for animations
|-bgcolor="#dddddd"
| '''Hitbox''' || Creates an invisible box that can be clicked. Important for entering seats. Size is configured in the Position menu.
|-
| [[Special:MyLanguage/TrainCarts/Attachments/Entity|'''Entity''']] || Displays an Entity like a Minecart or Mob
|-bgcolor="#dddddd"
| [[Special:MyLanguage/TrainCarts/Attachments/Item|'''Item''']] || Displays an Item on an Armorstand or using a Display Entity
|-
| [[Special:MyLanguage/TrainCarts/Attachments/Block|'''Block''']] || Displays a Block using a Display Entity. Only available on Minecraft 1.20+.
|-bgcolor="#dddddd"
| [[Special:MyLanguage/TrainCarts/Attachments/Seat|'''Seat''']] || A seat where a single player or entity can sit
|-
| [[Special:MyLanguage/TrainCarts/Attachments/Model|'''Model''']] || Loads in a full attachment configuration from the model store
|-bgcolor="#dddddd"
| '''Text''' || Floating Text Balloon
|-
| '''Platform''' || A moving shulker box that players can stand on. Does not work moving up.
|-bgcolor="#dddddd"
| '''Schematic''' || Displays multiple blocks using a WorldEdit saved Schematic
|-
| '''Light''' || When [https://www.spigotmc.org/resources/lightapi-fork.48247/ LightAPI] is installed, spawns a moving light source at the attachment position
|-bgcolor="#dddddd"
| [[Special:MyLanguage/TrainCarts/Attachments/Sound|'''Sound''']] || Adds a sound effect played with effect signs, command or the sequencer
|-
| [[Special:MyLanguage/TrainCarts/Attachments/Sequencer|'''Sequencer''']] || Automatically plays effects. Used to create ambient sound loops, such as engine noises, or to activate particle effects on a loop, such as a smoke stack.
|}

===Physical=== 
The Physical Menu configures the length of the cart and where the rail-tracking wheels of the cart are positioned.


[[Special:MyLanguage/TrainCarts/Attachments/Physical|» Physical Menu]]

===Position=== 
The position menu configures the position and rotation of the attachment. Includes additional options for some types of attachments, such as scale and transform options for items.


[[Special:MyLanguage/TrainCarts/Attachments/Position|» Position Menu]]

===Animation=== 
Attachments can be animated, making them move or rotate around. This is especially useful for funfair rides, or animated doors.


[[Special:MyLanguage/TrainCarts/Attachments/Animation|» Animation Menu]]

Animations play using linear interpolation. To create more lively animations, you can use Silacide's interpolation tool: https://fantasiecraft.be/EXPOT/Interpolation-Tool-Lite/

===General=== 
The general menu is used to add new attachments, delete them, move them around, name them or load/save them from the [[Special:MyLanguage/TrainCarts/Attachments/Model#Model_Store|model store]].


[[Special:MyLanguage/TrainCarts/Attachments/General|» General Menu]]

==Effect Activation== 
Effect attachments such as the [[Special:MyLanguage/TrainCarts/Attachments/Sound|sound attachment]] must be activated. First, the attachment must be [[Special:MyLanguage/TrainCarts/Attachments/General#Name|named in the general menu]]. It can then be activated in multiple ways:
* Using the [[Special:MyLanguage/TrainCarts/Signs/Effect|effect sign]]
* Using the <code>/train effect <name></code> command
* Using the [[Special:MyLanguage/TrainCarts/Attachments/Sequencer|sequencer attachment]]

==Backlog== 

===Editor=== 


* [[Special:MyLanguage/TrainCarts/Attachments/Saving|Saving trains (needs a cross-link about import/export and the whole savedtrain logic)]]
-> Navigating the tree menu

===Position=== 


* [[Special:MyLanguage/TrainCarts/Attachments/TransformType|Transform type]]
* [[Special:MyLanguage/TrainCarts/Attachments/Anchor|Anchor]]

===Animations=== 


* [[Special:MyLanguage/TrainCarts/Animations/Overview|Overview]]
</translate>

TrainCarts/API/SignAction

2025-11-18T21:28:45Z

Bergerkiller: Marked this version for translation

<languages/>
<translate>

This TrainCarts API allows custom signs to be registered, so that the registered executor callback is automatically run when trains go past them. This makes it very easy to make trains perform unique actions using a third-party plugin.

== Example Template == 


To begin, create a new class in your plugin with the following code:
<pre>
import org.bukkit.entity.Player;


import com.bergerkiller.bukkit.tc.controller.MinecartMember;
import com.bergerkiller.bukkit.tc.events.SignActionEvent;
import com.bergerkiller.bukkit.tc.events.SignChangeActionEvent;
import com.bergerkiller.bukkit.tc.signactions.SignAction;
import com.bergerkiller.bukkit.tc.signactions.SignActionType;
import com.bergerkiller.bukkit.tc.utils.SignBuildOptions;


/**
* Displays a welcome message to the players in the train
*/
public class SignActionWelcome extends SignAction {


@Override
public boolean match(SignActionEvent info) {
// Checks that the second line starts with 'welcome' (case-insensitive)
return info.isType("welcome");
}


@Override
public void execute(SignActionEvent info) {
// When a [train] sign is placed, activate when powered by redstone when the train
// goes over the sign, or when redstone is activated.
if (info.isTrainSign()
&& info.isAction(SignActionType.GROUP_ENTER, SignActionType.REDSTONE_ON)
&& info.isPowered() && info.hasGroup()
) {
for (MinecartMember<?> member : info.getGroup()) {
sendGreetingForCart(info, member);
}
return;
}


// When a [cart] sign is placed, activate when powered by redstone when each cart
// goes over the sign, or when redstone is activated.
if (info.isCartSign()
&& info.isAction(SignActionType.MEMBER_ENTER, SignActionType.REDSTONE_ON)
&& info.isPowered() && info.hasMember()
) {
sendGreetingForCart(info, info.getMember());
return;
}
}


public void sendGreetingForCart(SignActionEvent info, MinecartMember<?> member) {
// Lines 3 and 4 configure the message to send
String message = info.getLine(2) + info.getLine(3);


// Send to all player passengers of the cart (could be multiple seats!)
for (Player passenger : member.getEntity().getPlayerPassengers()) {
passenger.sendMessage(message);
}
}


@Override
public boolean build(SignChangeActionEvent event) {
// This is executed when a player places down a sign matching this sign action
// Permissions are checked and then a message is displayed to the player
// For simplicity you can use the SignBuildOptions API for this.
// You are free to use your own code here that checks permissions/etc.
return SignBuildOptions.create()
.setName(event.isCartSign() ? "cart welcome greeter" : "train welcome greeter")
.setDescription("sends a welcome message to all players in the train")
.handle(event.getPlayer());
}
}
</pre>


This is a simple example of a sign that sends a message to all players in the train. By default signs will support the standard TrainCarts conventions for the first line, where redstone options can be configured. The second line is typically used to match the sign type, and the last two lines are free to be used for anything.


To register the above class, perform the following in your plugin's main class:
<pre>
import org.bukkit.plugin.java.JavaPlugin;


import com.bergerkiller.bukkit.tc.signactions.SignAction;


public class TCWelcomeSign extends JavaPlugin {
public final SignActionWelcome signActionWelcome = new SignActionWelcome();


@Override
public void onLoad() {
// Register the signs
SignAction.register(signActionWelcome);
}


@Override
public void onEnable() {
}


@Override
public void onDisable() {
// Unregister the signs to prevent problems during /reload
SignAction.unregister(signActionWelcome);
}
}
</pre>


It is important to both '''register''' and '''unregister''' the sign. That way, when the server is reloaded, or the plugin or reloaded using for example ''PlugMan'', things don't break.


Also, do your registration during onLoad instead of onEnable if possible. This ensures your custom sign is available when trains load in on startup.

== The Execute Method == 


Various events are sent to signs and can be handled by the sign. All events are handled through the '''execute(event)''' callback.

=== Cart/Train Enter and Leave === 


When each individual ''cart'' hits a piece of track with a sign matching the sign action, the '''MEMBER_ENTER''' event is fired. When they move off the track again, a '''MEMBER_LEAVE''' event is fired. Similarly, for entire trains, a '''GROUP_ENTER''' and '''GROUP_LEAVE''' is fired.

=== Redstone === 


When the sign becomes powered from an unpowered state, '''REDSTONE_ON''' and '''REDSTONE_CHANGE''' fire. In reverse, '''REDSTONE_OFF''' and '''REDSTONE_CHANGE''' fire. When the power state doesn't change, but other blocks nearby change redstone levels that might influence the sign behavior, just '''REDSTONE_CHANGE''' is fired. The event has helper methods to figure out the power state of the sign or a given direction of the sign.

=== Movement === 


Every tick, while the train is moving, a '''MEMBER_MOVE''' event is fired. By default through, this is disabled for performance reasons. To use this event, override '''isMemberMoveHandled(event)''' and return true there.

=== Updates === 


When players enter the train, leave it, properties change or other similar events occur, a '''MEMBER_UPDATE''' event fires. This is useful if the sign uses such information to, for example, toggle a lever.

== Loaded Changed Event == 


The '''loadedChanged(event, loaded)''' method can be overrided to get notified when a sign matching this sign action is loaded or unloaded on the server. A sign is loaded when placed, or when a chunk loads with the sign in it. A sign is unloaded when destroyed, or when a chunk unloads with the sign in it. Be careful not to load or unload chunks in this method. This is a useful method to cache data in memory while the sign is in use.

== Remote Control == 


Remote control enables the sign to be activated by redstone, to then operate on one or more trains by name pattern. To use remote control with the sign, override '''canSupportRC()''' and return true.

== Path Finding == 


Some advanced methods can be overrided to make the sign act as a node in the [[Special:MyLanguage/TrainCarts/PathFinding|path-finding]] network:
* ''isRailSwitcher(event)'' - Return true if this sign switches the rails from/to any direction
* ''getRailDestinationName(event)'' - Return non-null to provide a unique destination name
* ''isPathFindingBlocked(event, railState)'' - Return true to tell the path finding algorithm that in this direction no further movement is possible

</translate>

TrainCarts/API/SignAction

2025-11-18T21:28:40Z

Bergerkiller:

<languages/>
<translate>

This TrainCarts API allows custom signs to be registered, so that the registered executor callback is automatically run when trains go past them. This makes it very easy to make trains perform unique actions using a third-party plugin.

== Example Template == 


To begin, create a new class in your plugin with the following code:
<pre>
import org.bukkit.entity.Player;


import com.bergerkiller.bukkit.tc.controller.MinecartMember;
import com.bergerkiller.bukkit.tc.events.SignActionEvent;
import com.bergerkiller.bukkit.tc.events.SignChangeActionEvent;
import com.bergerkiller.bukkit.tc.signactions.SignAction;
import com.bergerkiller.bukkit.tc.signactions.SignActionType;
import com.bergerkiller.bukkit.tc.utils.SignBuildOptions;


/**
* Displays a welcome message to the players in the train
*/
public class SignActionWelcome extends SignAction {


@Override
public boolean match(SignActionEvent info) {
// Checks that the second line starts with 'welcome' (case-insensitive)
return info.isType("welcome");
}


@Override
public void execute(SignActionEvent info) {
// When a [train] sign is placed, activate when powered by redstone when the train
// goes over the sign, or when redstone is activated.
if (info.isTrainSign()
&& info.isAction(SignActionType.GROUP_ENTER, SignActionType.REDSTONE_ON)
&& info.isPowered() && info.hasGroup()
) {
for (MinecartMember<?> member : info.getGroup()) {
sendGreetingForCart(info, member);
}
return;
}


// When a [cart] sign is placed, activate when powered by redstone when each cart
// goes over the sign, or when redstone is activated.
if (info.isCartSign()
&& info.isAction(SignActionType.MEMBER_ENTER, SignActionType.REDSTONE_ON)
&& info.isPowered() && info.hasMember()
) {
sendGreetingForCart(info, info.getMember());
return;
}
}


public void sendGreetingForCart(SignActionEvent info, MinecartMember<?> member) {
// Lines 3 and 4 configure the message to send
String message = info.getLine(2) + info.getLine(3);


// Send to all player passengers of the cart (could be multiple seats!)
for (Player passenger : member.getEntity().getPlayerPassengers()) {
passenger.sendMessage(message);
}
}


@Override
public boolean build(SignChangeActionEvent event) {
// This is executed when a player places down a sign matching this sign action
// Permissions are checked and then a message is displayed to the player
// For simplicity you can use the SignBuildOptions API for this.
// You are free to use your own code here that checks permissions/etc.
return SignBuildOptions.create()
.setName(event.isCartSign() ? "cart welcome greeter" : "train welcome greeter")
.setDescription("sends a welcome message to all players in the train")
.handle(event.getPlayer());
}
}
</pre>


This is a simple example of a sign that sends a message to all players in the train. By default signs will support the standard TrainCarts conventions for the first line, where redstone options can be configured. The second line is typically used to match the sign type, and the last two lines are free to be used for anything.


To register the above class, perform the following in your plugin's main class:
<pre>
import org.bukkit.plugin.java.JavaPlugin;


import com.bergerkiller.bukkit.tc.signactions.SignAction;


public class TCWelcomeSign extends JavaPlugin {
public final SignActionWelcome signActionWelcome = new SignActionWelcome();


@Override
public void onLoad() {
// Register the signs
SignAction.register(signActionWelcome);
}

@Override
public void onEnable() {
}


@Override
public void onDisable() {
// Unregister the signs to prevent problems during /reload
SignAction.unregister(signActionWelcome);
}
}
</pre>


It is important to both '''register''' and '''unregister''' the sign. That way, when the server is reloaded, or the plugin or reloaded using for example ''PlugMan'', things don't break.

Also, do your registration during onLoad instead of onEnable if possible. This ensures your custom sign is available when trains load in on startup.

== The Execute Method == 


Various events are sent to signs and can be handled by the sign. All events are handled through the '''execute(event)''' callback.

=== Cart/Train Enter and Leave === 


When each individual ''cart'' hits a piece of track with a sign matching the sign action, the '''MEMBER_ENTER''' event is fired. When they move off the track again, a '''MEMBER_LEAVE''' event is fired. Similarly, for entire trains, a '''GROUP_ENTER''' and '''GROUP_LEAVE''' is fired.

=== Redstone === 


When the sign becomes powered from an unpowered state, '''REDSTONE_ON''' and '''REDSTONE_CHANGE''' fire. In reverse, '''REDSTONE_OFF''' and '''REDSTONE_CHANGE''' fire. When the power state doesn't change, but other blocks nearby change redstone levels that might influence the sign behavior, just '''REDSTONE_CHANGE''' is fired. The event has helper methods to figure out the power state of the sign or a given direction of the sign.

=== Movement === 


Every tick, while the train is moving, a '''MEMBER_MOVE''' event is fired. By default through, this is disabled for performance reasons. To use this event, override '''isMemberMoveHandled(event)''' and return true there.

=== Updates === 


When players enter the train, leave it, properties change or other similar events occur, a '''MEMBER_UPDATE''' event fires. This is useful if the sign uses such information to, for example, toggle a lever.

== Loaded Changed Event == 


The '''loadedChanged(event, loaded)''' method can be overrided to get notified when a sign matching this sign action is loaded or unloaded on the server. A sign is loaded when placed, or when a chunk loads with the sign in it. A sign is unloaded when destroyed, or when a chunk unloads with the sign in it. Be careful not to load or unload chunks in this method. This is a useful method to cache data in memory while the sign is in use.

== Remote Control == 


Remote control enables the sign to be activated by redstone, to then operate on one or more trains by name pattern. To use remote control with the sign, override '''canSupportRC()''' and return true.

== Path Finding == 


Some advanced methods can be overrided to make the sign act as a node in the [[Special:MyLanguage/TrainCarts/PathFinding|path-finding]] network:
* ''isRailSwitcher(event)'' - Return true if this sign switches the rails from/to any direction
* ''getRailDestinationName(event)'' - Return non-null to provide a unique destination name
* ''isPathFindingBlocked(event, railState)'' - Return true to tell the path finding algorithm that in this direction no further movement is possible

</translate>

File:Pathfinding.png

2025-10-29T15:43:22Z

Bergerkiller: Bergerkiller reverted File:Pathfinding.png to an old version

MediaWiki:Common.css

2025-10-13T18:13:55Z

Bergerkiller:

/* CSS placed here applies to all skins */
@import url("/fonts/include.css");

.mw-editfont-monospace {
font-family: Consolas, sans-serif;
}

.minecraft-font {
font-family: "Minecraft Seven", sans-serif;
font-weight: normal;
}

.sign-template-panel {
width: 200px;
height: 100px
}

.sign-template-line {
font-family: "Minecraft Seven", sans-serif;
font-weight: normal;
font-size: 20px;
height: 24px;
}

#t-print { display: none; }
#t-specialpages { display: none; }
#feedlinks { display: none; }
#t-recentchangeslinked { display: none; }
#t-upload { display: none; }
#ca-talk { display:none!important; }

MediaWiki:Common.css

2025-10-13T18:13:46Z

Bergerkiller:

MediaWiki:Common.css

2025-10-13T18:05:16Z

Bergerkiller:

/* CSS placed here applies to all skins */
@font-face {
font-family: "Minecraft Seven";
src: url("/fonts/Minecraft-Seven_v2.woff2") format("woff2");
font-weight: normal;
font-style: normal;
font-display: swap;
}

@font-face {
font-family: 'IBM Plex Mono';
src: url('/fonts/ibm-plex-mono/IBMPlexMono-Regular.ttf') format('truetype');
font-weight: normal;
font-style: normal;
font-display: swap;
}

@font-face {
font-family: 'IBM Plex Mono';
src: url('/fonts/ibm-plex-mono/IBMPlexMono-Bold.ttf') format('truetype');
font-weight: bold;
font-style: normal;
font-display: swap;
}

@font-face {
font-family: 'IBM Plex Mono';
src: url('/fonts/ibm-plex-mono/IBMPlexMono-Italic.ttf') format('truetype');
font-weight: normal;
font-style: italic;
font-display: swap;
}

.mw-editfont-monospace {
font-family: Consolas, sans-serif;
}

.minecraft-font {
font-family: "Minecraft Seven", sans-serif;
font-weight: normal;
}

.sign-template-panel {
width: 200px;
height: 100px
}

.sign-template-line {
font-family: "Minecraft Seven", sans-serif;
font-weight: normal;
font-size: 20px;
height: 24px;
}

#t-print { display: none; }
#t-specialpages { display: none; }
#feedlinks { display: none; }
#t-recentchangeslinked { display: none; }
#t-upload { display: none; }
#ca-talk { display:none!important; }

MediaWiki:Common.css

2025-10-13T17:49:58Z

Bergerkiller:

/* CSS placed here applies to all skins */
@font-face {
font-family: "Minecraft Seven";
src: url("/fonts/Minecraft-Seven_v2.woff2") format("woff2");
font-weight: normal;
font-style: normal;
font-display: swap;
}

@font-face {
font-family: 'IBM Plex Mono';
src: url('/fonts/ibm-plex-mono/IBMPlexMono-Regular.ttf') format('truetype');
font-weight: normal;
font-style: normal;
font-display: swap;
}

@font-face {
font-family: 'IBM Plex Mono';
src: url('/fonts/ibm-plex-mono/IBMPlexMono-Bold.ttf') format('truetype');
font-weight: bold;
font-style: normal;
font-display: swap;
}

@font-face {
font-family: 'IBM Plex Mono';
src: url('/fonts/ibm-plex-mono/IBMPlexMono-Italic.ttf') format('truetype');
font-weight: normal;
font-style: italic;
font-display: swap;
}

.mw-editfont-monospace {
font-family: 'IBM Plex Mono', monospace !important;
}

.minecraft-font {
font-family: "Minecraft Seven", sans-serif;
font-weight: normal;
}

.sign-template-panel {
width: 200px;
height: 100px
}

.sign-template-line {
font-family: "Minecraft Seven", sans-serif;
font-weight: normal;
font-size: 20px;
height: 24px;
}

#t-print { display: none; }
#t-specialpages { display: none; }
#feedlinks { display: none; }
#t-recentchangeslinked { display: none; }
#t-upload { display: none; }
#ca-talk { display:none!important; }

TrainCarts/Attachments/General

2025-10-12T09:48:27Z

Bergerkiller:

<languages/>
<translate>

[[File:general_menu.png|thumb|General menu opened in the attachment editor]]

== Introduction == 


The general menu houses all the options create, delete, move, save and load attachments. This is the first place you usually go to when configuring a new cart.

== Add Attachment == 


Adds a new attachment as a child to the currently selected attachment. The newly added attachment will be of a wooden block item and is automatically selected. You can then go into the appearance menu to change it to the type of attachment you want.

=== Dropdown === 


The dropdown button next to it allows adding multiple attachments from one of the following locations:
* Attachment configuration previously saved to the player's clipboard
* Attachment configuration downloaded from a paste server (https://paste.traincarts.net)
* Attachment configuration loaded from the [[TrainCarts/Attachments/Model#Model_Store|model store]] (previously saved under a name)

== Duplicate == 


Duplicates the currently selected attachment with all the same configurations. Can duplicate an entire tree of attachments. Identical in functionality as saving to clipboard and then adding from clipboard.

== Name == 


Attachments can be named. These names can then be used to target this attachment. This feature is used by:
* [[Special:MyLanguage/TrainCarts/Attachments/Sequencer|'''Sequencer attachment''']] to target the effect attachments and play their effects automatically
* [[Special:MyLanguage/TrainCarts/Signs/Effect|'''Effect sign''']] to play effect attachments with a given name
* The <code>/train effect <name></code> command to play effect attachments with a given name
* The <code>/train eject --seat <name></code> command to eject specific seat attachments with a given name

== Change Order == 


Use the change order button to change the position of the attachment in the tree hierarchy. This can be used to 'insert' an attachment as parent before another one, or to re-order them. Important when configuring animations.

== Delete == 


Deletes the attachment, including all child attachments. First asks to confirm deletion.

== Save/Load == 


[[File:save_attachments.png|thumb|Save Attachment dialog is opened in the attachment editor]]


Saves or loads the configuration of the current attachment and all child attachments. Can be used to copy/paste attachments between trains or servers. This feature supports three locations to load/save to:
* Player Clipboard
* Paste server (https://paste.traincarts.net)
* [[TrainCarts/Attachments/Model#Model_Store|Model Store]]. Configurations are saved persistently in YAML to disk, and can be retrieved again from anywhere. The [[Special:MyLanguage/TrainCarts/Attachments/Model|Model Attachment]] can load these in.
</translate>

TrainCarts/Attachments/Sequencer

2025-10-12T09:48:24Z

Bergerkiller:

<languages/>
<translate>

[[File:sequencer_attachment.png|thumb|Sequencer attachment being configured]]

== Introduction == 


The sequencer attachment is like the real-life equivalent of a music sequencer. It can be used to activate effects in sequence on a loop. It supports the engine start-loop-stop logic to allow for realistic train engine sounds to be played. The sequencer itself does not configure any sounds. It activates other [[TrainCarts/Attachments/General#Name|named]] effect attachments like the [[Special:MyLanguage/TrainCarts/Attachments/Sound|sound attachment]].


Like other effect attachments, the sequencer must be [[Special:MyLanguage/TrainCarts/Attachments#Effect_Activation|activated]]. It can also be set to [[#Autoplay|automatically play]].

== Categories == 
There are three categories, each with their own configuration and list of effects to play:
* '''Start''' - Plays once when the effect is first played
* '''Loop''' - Plays on a loop over and over after the start sequence finished playing
* '''Stop''' - Plays once when the effect is stopped after playing

=== Duration === 


For how long this category plays or loops. The category is enabled if the duration is set to more than 0 (off).

=== Playback Speed === 


Controls the rate of playback of all effects under this category. Can be tied with functions to inputs such as the train speed.

=== Interrupt Play === 


Whether to interrupt playback when playing state changes. For example, if enabled for Start, the playback is aborted when the sequencer is stopped moving straight to the stop sequence.

== Adding Sequences == 


[[File:sequencer_piano_roll.png|thumb|MIDI Sequence [[TrainCarts/Attachments/Sequencer/PianoRoll|Piano Roll]]]]


The '''[+]''' button can be used to add new effects to play under a category. The menu first asks for the [[Special:MyLanguage/TrainCarts/Attachments/General#Name|effect name]] to play. It then can add one of several sequence types:
* '''Simple''' - Simply plays the effect once, optionally with a delay
* '''MIDI''' - Allows for a melody to be configured using a [[Special:MyLanguage/TrainCarts/Attachments/Sequencer/PianoRoll|piano roll]]

== Configuration == 


After selecting a sequence, multiple options are available. From left to right:

=== Preview button === 


Plays the sequence. In the case of MIDI, plays the full melody.

=== Configure Type === 


Configures the [[Special:MyLanguage/TrainCarts/Attachments/Sequencer/PianoRoll|piano roll]] for MIDI, or opens a menu to configure the delay for the simple sequence.

=== Configure Effect === 


Configures the effect name activated by the sequence.

=== Configure Sequence === 


Opens a menu to configure three options:
* '''Active''' - Makes the effect conditionally play. You can use this with input functions to, for example, only play the sound when a player is in a seat, or when a certain tag is set on the train.
* '''Volume''' - Volume multiplier for the effect. Use this to have an effect volume controlled by, for example, the speed of the train.
* '''Pitch''' - Pitch (speed) multiplier for the effect. Use this to have an effect pitch controlled by, for example, the speed of the train.

=== Delete === 


Deletes the sequence. Asks to confirm first.

== Other Options == 


At the top of the menu several other options are available

=== Synchronous === 


Switch between async/sync playback. Asynchronous playback is not affected by server lag. However, this can cause it to go out of sync with for example redstone-timed effects. Asynchronous is preferred, as it allows for smooth uninterrupted sound loops.

=== Autoplay === 


Automatically play the sequencer based on a condition, or all the time. This allows effects to be automatically played when a certain condition is met. For example, you can make a sound play when a player steps into the cart, or when the train goes from not moving to moving.

=== Play === 


Override autoplay and play the sequencer, or stop it again. Use this to test the play/stop behavior
</translate>

TrainCarts/Attachments/Sound

2025-10-12T09:48:20Z

Bergerkiller:

<languages/>
<translate>

[[File:sound_attachment.png|thumb|Sound attachment being configured with number labels]]

== Introduction == 


The sound attachment plays sounds. It has many different options to configure what sounds play for what players.


To play the sound, it must be [[Special:MyLanguage/TrainCarts/Attachments#Effect_Activation|activated]].

== Appearance == 

=== 1. First person and third person mode === 


The top-left button configures whether a different sound is played in first person mode versus third person mode. If a sound should be played only to players in the cart/train, or only outside of it, activate the suitable mode. The default mode ('play same sound') only allows configuring a single sound name, and will play for all players in range.

=== 2. Auto-Resume === 


Toggles auto-resume on or off. When auto-resume is enabled, the sound is automatically played when players come in range of the cart. This also makes the sound automatically play when the player changes between first person and third person modes (gets in and out of the seat). Turn this option on for sound loops where it is important that a sound continues playing when players go in and out of the train. Especially important when used in combination with the [[Special:MyLanguage/TrainCarts/Attachments/Sequencer|sequencer attachment]].

=== 3. Play Position === 


Controls where the sound is played. If the sound should always have roughly the same volume, set this to ''play at player''. Otherwise, the default ''play at position'' is the best option.

=== 4. Play Preview === 


Use the play button to play the sound, or stop button to cancel playback. You can hold the play button to play on repeat, which is useful when testing a sound loop. These buttons have no effect on the sound configuration.

=== 5. Sound Names and Channel === 


Configure the name of the sound to play in first person / third person / both, and what 'audio channel' to play this through. The channel controls what client-configured volume sliders control the sound volume.


You can use the <code>/train menu sound <name></code> to configure the sound, which offers automatic auto-completion of (client resource pack) sound names.


'''Important note:''' custom sound names must be all-lowercased. Uppercase characters aren't supported by vanilla Minecraft, while Optifine makes it seem like it works.

=== 6. Volume === 


The volume and volume randomness sliders control the range of volumes the sound plays at.

=== 7. Speed === 


The speed (pitch) and speed randomness sliders control the range of pitch the sound plays at.
</translate>

TrainCarts/Attachments/Model

2025-10-12T09:48:17Z

Bergerkiller:

<languages/>
<translate>
== Introduction == 


The '''model attachment''' is used to show a single attachment or a group of attachments in more than one place. Editing the model attachment will simultaneously edit it everywhere it is used. This makes this useful for commonly reused attachments, like seats and wheels.


While called the same, Model refers to a configuration model for reusing attachments. '''This is not for showing custom models in resource packs.''' Use the [[TrainCarts/Attachments/Item|Item Attachment]] for that instead.


The model attachment loads an attachment configuration from the [[#Model_Store|''model store'']]. You can save attachments to be used in models in the [[Special:MyLanguage/TrainCarts/Attachments/General#Save.2FLoad|general menu]].

== Appearance == 


* The model name can be selected either through an anvil menu, or by selecting them in a dropdown menu.
* If a non-existing model name was selected (shown as red), the Load button can be used to load a new configuration. It can also overwrite existing configurations.
* The edit button edits the model configuration that is selected. This will modify the attachments in all places where it is used in a model attachment

=== Multi-Editing === 


If the same model name is used in multiple model attachments or even trains, making changes to the configuration in the model store will update all locations simultaneously.
</translate>

== Model Store ==
The Model Store is the full collection of attachments saved under a name:
* Resource packs loaded on the server can include read-only model configurations of train parts
* Models can be saved to the store in the [[Special:MyLanguage/TrainCarts/Attachments/General#Save.2FLoad|general menu]]
* Models are saved to <code>plugins/Train_Carts/SavedModels.yml</code> and separate module yml files in the <code>savedModelModules</code> folder, similar to saved trains

=== Commands ===
Commands for manipulating models are available under the <code>/train model config <name> <subcommand></code> set of commands. It is here you can configure a model to be saved to a separate module (its own yml file).

You can use <code>/train model config <name> edit</code> to edit an existing model configuration in the attachment editor.

TrainCarts/Attachments/Seat

2025-10-12T09:48:14Z

Bergerkiller:

<languages/>
<translate>

[[File:seat_attachment.png|thumb|A seat attachment is being configured]]

==Appearance== 


Seats are invisible points where players or mobs can sit inside the train. Typically these are added as a child to other attachments where the seat is visibly displayed, such as is the case with the default Minecart. For each seat, both 1st-person (the player sitting) and 3rd-person (other players viewing the player in the seat) appearance can be configured.

===First Person View=== 

====Mode==== 


{| class="wikitable"
! Mode !! Description
|-
| DEFAULT || Players see themselves sitting upright at all times
|-
| INVISIBLE || Players are made invisible and cannot see themselves
|-
| HEAD || Players can only see their own head
|-
| STANDING || Players see themselves standing/walking/flying as the train moves. Their movement is controlled by the server.
|-
| THIRD_P || A fake player entity is spawned, causing players to see their own head when they look vertically. The real player is made invisible.
|-
| DYNAMIC || Uses DEFAULT when upright, and THIRD_P when moving vertical/upside-down
|}

====Eye Position==== 


Instead of positioning the passenger by the butt, positions the player by the eyes/line of sight. If it is important that the player camera is positioned at a certain position in first person, this can be enabled to do exactly that. The position of the eyes are displayed using an arrow, and the menu also includes a preview button to see what the passenger would see.


Switching it back to 'automatic' disables this feature, positioning the passenger by the butt again.

====View Locking==== 


Some first-person view locking options are available. This restricts the player's ability to look around.
{| class="wikitable"
! Mode !! Description
|-
| No view locking || The player can look around freely
|-
| Move view when seat moves (choppy) || Sends relative movement packets to rotate the camera when the seat moves. This can be quite choppy.
|-
| Free look in spectator mode || Makes the player spectate another entity, while allowing (delayed) free movement. The camera moves when the seat moves.
|-
| View locked in spectator mode || Makes the player spectate another entity. Does not allow any player input. The camera moves when the seat moves.
|}

===Passenger Display=== 

====Mode==== 


{| class="wikitable"
! Mode !! Description
|-
| DEFAULT || Passenger is shown seated upright as a normal player
|-
| ELYTRA_SIT || Passenger is shown as flying an elytra in a sort-of sitting pose. Allows for functional pitch.
|-
| STANDING || Passenger is shown standing/walking/flying as the train moves.
|-
| HEAD || Only the passenger's head is shown
|-
| NO_NAMETAG || Same as DEFAULT, except the players nametag is hidden
|-
| INVISIBLE || Passenger is invisible
|}

====Item Display==== 
An item can be configured to be displayed when the seat is occupied. This can be used in combination with the invisible display modes to show a custom model of a passenger.

====Body Locking==== 
Controls whether the passenger body is locked into facing forwards. This is only visible in third person.

===Exit=== 
A relative exit offset can be configured for every seat. Players are teleported here when ejecting from the train.

===Permission=== 
A permission node to enter this particular seat can be configured in the anvil menu. To reset, enter an empty space.

==Smooth Coasters== 
The [https://www.curseforge.com/minecraft/mc-mods/smoothcoasters Smooth Coasters] mod can be installed on the client. TrainCarts will automatically detect players that use this mod and send smooth rotations of the passengers. This also enables the seat to roll, which is otherwise not supported.

== Hitbox == 
Display entities cannot be clicked, as they have no hitbox. To allow for players to get into the seat anyway, you must add a '''hitbox attachment'''.

</translate>

TrainCarts/Attachments/Item

2025-10-12T09:48:11Z

Bergerkiller:

<languages/>
<translate>

[[File:attachments_item_main.png|thumb|Main section of the item appearance menu, showing a 3d preview of the selected item]]


The '''Item Attachment''' is the main attachment in TrainCarts to display item models for trains. Besides showing Vanilla items, Resource Packs can be used to display custom models created in programs like Blockbench.

==Appearance== 


By pressing Jump (spacebar) a menu can be opened to select a different item or block. If a resource pack is configured, an inventory menu is opened with the custom models that exist in the resource pack. Otherwise, a grid of blocks and items is displayed.


Additional menus can be opened by pressing Up/Down (W/S). It is here that special properties such as ''Unbreakable'' and ''Custom Model Data'' can be set. This might be important for custom resource pack models. For some items, such as tools, the durability of the item is configurable using Left/Right (A/D) input.


Instead of using the in-map menus you can also drop an item from your inventory with this menu open to set an item.

===Item Model Dialog=== 


[[File:item_model_dialog.png|thumb|Item Model Dialog is opened to select an item model]]
When you have a resource pack configured in your <code>server.properties</code> an item model search dialog becomes available. This dialog has easier click navigation of the entire resource pack, and includes a search dialog. You can open this dialog anywhere as a creative menu using the <code>/train model search</code> command.

==Position== 


When the item type is selected, an additional "mode" and "transform" option is made available in the '''Position menu'''. This controls ''how'' the item is displayed. If the server version is below 1.20, then the mode option is unavailable and only display using armorstands is supported.

=== Mode === 


{| class="wikitable"
|-
! Mode !! Function
|-
| '''Hybrid''' || Uses a display entity for Minecraft clients on version 1.20 or later (viaversion support). Uses an armorstand for clients on versions before that. Display scale is not configurable.
|-
| '''Armorstand''' || Uses an armorstand to display the item. Rotation will be less smooth than with display entities.
|-
| '''Display''' || Uses a display entity to display the item. Rotation will be smooth, and scale can be configured in the '''Position menu'''.
|}

=== Transform === 


Sets what equipment slot the item is put in. In hybrid mode, shows a display or armorstand icon to represent how the item is positioned. This is important for smooth rotations. A yellow "S" means the armorstand is small, or, 'baby'. The available slots are head, left hand, right hand, chestplate, legs and feet. For the display mode, additional options are available such as GUI, ground and fixed (item frame).

=== Size === 


[[File:item_size.png|thumb|Item size of a display-mode item attachment is configured]]
If the mode is set to display, then the item scale size (x/y/z) can be set as well. Pressing down (S) on the z-axis selects all three to uniform-scale the item.

=== Clip === 


If the mode is set to display, then a clip size can be set. By default this is set to disabled, which disables view clipping entirely. It can help client performance to set this clip size to something roughly the size of the item. That way when players don't look at the item, it is not rendered.


Armorstands don't support this feature, and they have a problem with models disappearing when looking away. For this reason, stick to hybrid or display mode if you can.
</translate>

TrainCarts/Attachments/Entity

2025-10-12T09:48:06Z

Bergerkiller:

<languages/>
<translate>

[[File:entity_attachment.png|thumb|An entity attachment of a boat is being configured]]
The Entity Attachment displays entities. These can be mobs, minecarts, boats or some other types of entities in the game. Unlike items it is not possible to have custom models for these without a modded client.


Some entities support additional customization, such as the wood type of boats.

==Appearance== 

===Sitting=== 


It can be toggled whether the entity is shown seated (in an armorstand) or not. This changes mobs from a standing pose to a sitting pose.


This option can also be toggled on for Minecarts so that their movement has the same interpolation as that of other entities. If you want to create a cart that mixes item models with ordinary minecart entities, setting them as seated makes sure they move at the same rate. Without this enabled, they will seem to lag behind the other models.

===Nametag=== 


An invisible nametag can be used with [https://ftb.gamepedia.com/OptiFine Optifine] to display custom entity models. The nametag can be set as hidden or visible as well.
</translate>

TrainCarts/Attachments/Physical

2025-10-12T09:47:01Z

Bergerkiller:

<languages/>
<translate>

[[File:physical_editing.png|thumb|The physical properties of a custom cart are being edited]]
[[File:physical_turning.gif|thumb|A train of custom carts going around in circles, the cart length controlling spacing and the wheel positions controlling how the cart turns]]


The physical menu, available at the top (root) attachment, configures the length of the cart and where the wheels are positioned. This controls the '''spacing between carts''' and '''how the cart rotates''' in turns. The menu shows a bounding box preview of the current dimensions of the cart.

== Cart Length == 


This controls the length of the cart. Multiple connected carts maintain distance between each other with a gap between them. This length controls the spacing this cart takes up in this linked chain.

== Wheel Distance == 


This controls how far from the center of the cart the front and back wheels are positioned. Further-spaced wheels turn more smoothly. If your custom train includes actual wheels, it helps to position the wheels in roughly the same place for realistic tracking on the rails. The wheel positions are displayed using ender pearls.

== Wheel Offset == 


If your wheels are not exactly centered, the offset allows for adjusting this. Usually this should be left 0.
</translate>

TrainCarts/Attachments/Appearance

2025-10-12T09:46:41Z

Bergerkiller:

Page Removed. There are now separate pages for every type of attachment, instead.

TrainCarts/Attachments

2025-10-12T09:44:51Z

Bergerkiller: Marked this version for translation

<languages/>
<translate>

[[File:Attachment_editor_wooden_car.png|thumb|A customized minecart is being edited using the attachment editor]]
[[File:Rotating_attachments.gif|thumb|Two model attachments are animated, demonstrating the use of hierarchy]]

==Introduction== 
'''The Attachment Editor''' is an in-game interactive [[Special:MyLanguage/Map Display|Map Display]] with which individual carts of a train can be customized.
This menu is used to configure the appearance and behavior of carts, with a [[wikipedia:Tree structure|tree layout]]
showing the different attachments. Each attachment represents a part of the train, such as a moving entity or a seat designation.
Attachments added as a child to other attachments are positioned relative to the parent. This allows many attachments to be moved
and animated together as a whole.

==Basic usage== 

===Command=== 


To start using the attachment editor, players need to give themselves the map item:
</translate>
{{Command|train attachments|Give the player the attachment editor map item|train.command.editor}}
<translate>

===Editing=== 


To edit a single cart of a train, and make it visible in the editor, you need to select the cart first.


[[Special:MyLanguage/TrainCarts/Editing|» Editing]]

===Navigation=== 


Each attachment is displayed on a different row, with an indent to the right every time it is added to a new parent. To navigate between attachments, use the Up/Down (W/S) steering controls. For each attachment selected, different menus can be accessed by pressing Left/Right (A/D) and Jump (spacebar) afterwards. Once inside a menu, the sneak button (shift) can be used to exit it again. This behavior is the same for all other menus. To move around while still viewing the editor, it can be placed into the off-hand (''typically F'').


To add new attachments, duplicate them, change the position in the tree hierarchy, or to delete them, use the [[Special:MyLanguage/TrainCarts/Attachments/General|General menu]] denoted by three horizontal lines.

===Dropping items=== 


[[File:Attachments_Drop_Item_Small.gif|thumb|An item is dropped from the inventory, configuring the attachment|link=File:Attachments_Drop_Item.gif]]
Menus where an item is being configured can be set instantly by dropping an item from the player's inventory. With the menu open, simply open the inventory, pick the item to set, and click on the outside of the inventory to drop it. The drop will be cancelled and the item set in the menu.

===Numbers=== 


Number sliders are used to configure numeric values, such position coordinates. Pressing the Left/Right buttons once will increment/decrement a very small amount. Holding the buttons for a longer time causes the number to increment/decrement faster and faster the longer it is being held down.


By holding Spacebar a number field can be reset to its default, usually 0. By holding spacebar and then pressing left/right, a special action can be performed. Usually this means inverting the value (-5 -> 5) or changing an angle in 90 degree steps.

===Text=== 


Text is input using an anvil menu. After typing in the desired text, click on the emerald to proceed, or the barrier item to cancel the change.

===Setting using commands=== 
</translate>
{{Command|train menu set [value]|Set a numeric or text value for the currently selected menu|train.command.editor}}
<translate>

==Gotchas== 
* Make sure to use <code>/train save name</code> to save your train regularly! Only saved trains can be restored
* Make use of the [[Special:MyLanguage/TrainCarts/Train Spawn Chest|train storage chest]] to move your train around or to recombine the carts
* Change spacing between carts, and where wheels are positioned, in the [[Special:MyLanguage/TrainCarts/Attachments/Physical|Physical menu]]
* When animating, make sure your animation frames have a delta-T greater than 0. Otherwise animation speed will not function.
* The new Display Entities cannot be clicked by default:
** If you cannot click to edit a train, look at it and do <code>/train edit</code> to select it
** To allow players to click on the cart to enter a seat, make sure to add a '''Hitbox attachment'''.
* You can save a sub-tree of attachments in the [[Special:MyLanguage/TrainCarts/Attachments/Model#Model_Store|Model Store]] in the [[Special:MyLanguage/TrainCarts/Attachments/General|General menu]], and create it in multiple places using the [[Special:MyLanguage/TrainCarts/Attachments/Model|'''Model Attachment''']]. There is also a clipboard and import/export function.

==Menu== 
===Appearance===
The Appearance Menu contains a selector at the top where the attachment type is configured, with the remainder of the menu automatically filled with this type's configuration.


{| class="wikitable" style="margin:left"
|+Attachment Types
! Type !! Description
|-
| '''Empty''' || Displays nothing. Used as a marker attachment to easily position multiple other attachments, and as an anchor for animations
|-bgcolor="#dddddd"
| '''Hitbox''' || Creates an invisible box that can be clicked. Important for entering seats. Size is configured in the Position menu.
|-
| [[Special:MyLanguage/TrainCarts/Attachments/Entity|'''Entity''']] || Displays an Entity like a Minecart or Mob
|-bgcolor="#dddddd"
| [[Special:MyLanguage/TrainCarts/Attachments/Item|'''Item''']] || Displays an Item on an Armorstand or using a Display Entity
|-
| [[Special:MyLanguage/TrainCarts/Attachments/Block|'''Block''']] || Displays a Block using a Display Entity. Only available on Minecraft 1.20+.
|-bgcolor="#dddddd"
| [[Special:MyLanguage/TrainCarts/Attachments/Seat|'''Seat''']] || A seat where a single player or entity can sit
|-
| [[Special:MyLanguage/TrainCarts/Attachments/Model|'''Model''']] || Loads in a full attachment configuration from the model store
|-bgcolor="#dddddd"
| '''Text''' || Floating Text Balloon
|-
| '''Platform''' || A moving shulker box that players can stand on. Does not work moving up.
|-bgcolor="#dddddd"
| '''Schematic''' || Displays multiple blocks using a WorldEdit saved Schematic
|-
| '''Light''' || When [https://www.spigotmc.org/resources/lightapi-fork.48247/ LightAPI] is installed, spawns a moving light source at the attachment position
|-bgcolor="#dddddd"
| [[Special:MyLanguage/TrainCarts/Attachments/Sound|'''Sound''']] || Adds a sound effect played with effect signs, command or the sequencer
|-
| [[Special:MyLanguage/TrainCarts/Attachments/Sequencer|'''Sequencer''']] || Automatically plays effects. Used to create ambient sound loops, such as engine noises, or to activate particle effects on a loop, such as a smoke stack.
|}

===Physical=== 
The Physical Menu configures the length of the cart and where the rail-tracking wheels of the cart are positioned.


[[Special:MyLanguage/TrainCarts/Attachments/Physical|» Physical Menu]]

===Position=== 
The position menu configures the position and rotation of the attachment. Includes additional options for some types of attachments, such as scale and transform options for items.


[[Special:MyLanguage/TrainCarts/Attachments/Position|» Position Menu]]

===Animation=== 
Attachments can be animated, making them move or rotate around. This is especially useful for funfair rides, or animated doors.


[[Special:MyLanguage/TrainCarts/Attachments/Animation|» Animation Menu]]

===General=== 
The general menu is used to add new attachments, delete them, move them around, name them or load/save them from the [[Special:MyLanguage/TrainCarts/Attachments/Model#Model_Store|model store]].


[[Special:MyLanguage/TrainCarts/Attachments/General|» General Menu]]

==Effect Activation== 
Effect attachments such as the [[Special:MyLanguage/TrainCarts/Attachments/Sound|sound attachment]] must be activated. First, the attachment must be [[Special:MyLanguage/TrainCarts/Attachments/General#Name|named in the general menu]]. It can then be activated in multiple ways:
* Using the [[Special:MyLanguage/TrainCarts/Signs/Effect|effect sign]]
* Using the <code>/train effect <name></code> command
* Using the [[Special:MyLanguage/TrainCarts/Attachments/Sequencer|sequencer attachment]]

==Backlog== 

===Editor=== 


* [[Special:MyLanguage/TrainCarts/Attachments/Saving|Saving trains (needs a cross-link about import/export and the whole savedtrain logic)]]
-> Navigating the tree menu

===Position=== 


* [[Special:MyLanguage/TrainCarts/Attachments/TransformType|Transform type]]
* [[Special:MyLanguage/TrainCarts/Attachments/Anchor|Anchor]]

===Animations=== 


* [[Special:MyLanguage/TrainCarts/Animations/Overview|Overview]]
</translate>

TrainCarts/ActionBlocks

2025-10-12T09:44:27Z

Bergerkiller:

<languages/>
<translate>
==Depreciated== 


<big>The ActionBlocks addon is depreciated and no-longer supported. It is not compatible with the latest versions of Traincarts.</big>

==Introduction == 


In an attempt to fully support Minecart Mania's features, action blocks are introduced. Action blocks is an add-on for TrainCarts, which is included in the download. It is not a requirement to run TrainCarts, but the add-on does require TrainCarts.


Action blocks are dumbed-down versions of the Sign systems in the official TrainCarts. Instead of using [https://minecraft.wiki/w/Sign signs], it is a certain block that behaves in certain ways. What [https://minecraft.wiki/w/Block block] material performs what can be configured in the configuration of TrainCartsBlocks:


<pre>plugins/TrainCarts/blocks.yml</pre>

== The blocks == 


It currently supports several [https://minecraft.wiki/w/Block blocks], all working in both directions and all working with on/off [https://minecraft.wiki/w/Redstone_mechanics redstone physics]. You can configure some action blocks to invert redstone power, just in case you want something to work without having to power the block. Permissions from the main TrainCarts are used as well, so you can deny players from building stations. This permission is active once the player tries to place a [https://minecraft.wiki/w/Minecart minecart] track on top of an action block.

=== Station block === 


By default [https://minecraft.wiki/w/Obsidian obsidian], it can stop trains when left unpowered. When powered again, it will launch trains into the previous direction, acting like the 'continue' of the sign version. If a train enters a powered station block, it will receive a boost.

=== Ejector block === 


By default [https://minecraft.wiki/w/Block_of_Iron iron], it can eject [https://minecraft.wiki/w/Minecart minecarts] when powered. If unpowered, nothing happens.

=== Elevator === 


By default [https://minecraft.wiki/w/Block_of_Gold gold], it can teleport trains up and down to another elevator block. It favors teleporting upwards above downwards. When powered, it will teleport the train, if not, nothing happens.
</translate>

TrainCarts/Lag

2025-10-12T09:44:24Z

Bergerkiller:

<languages/>
<translate>

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 == 


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 == 


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}}
<translate>


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>
<pre>
trainname:
collision:
block: CANCEL
</pre>
<translate>

== 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.

== Keep chunks loaded == 


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.


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 == 


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>
# Limits of the amount of carts on the server
cartLimits:
# Maximum number of TrainCarts minecarts allowed per world
# If there are more than this number, no more minecarts can be placed/spawned
# A value of -1 disables this limit (default)
maxCartsPerWorld: -1


# Whether to include unloaded trains/carts in the maxCartsPerWorld limit
countUnloaded: false


# Maximum number of carts that can be joined together in a train
# Linking does not happen when it would exceed this limit,
# and trains longer than this cannot be spawned
# A value of -1 disables this limit, allowing any length (default)
maxCartsPerTrain: -1
</pre>

== 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>.


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>

TrainCarts/Attachments

2025-10-12T09:44:20Z

Bergerkiller:

<languages/>
<translate>
[[File:Attachment_editor_wooden_car.png|thumb|A customized minecart is being edited using the attachment editor]]
[[File:Rotating_attachments.gif|thumb|Two model attachments are animated, demonstrating the use of hierarchy]]

==Introduction== 
'''The Attachment Editor''' is an in-game interactive [[Special:MyLanguage/Map Display|Map Display]] with which individual carts of a train can be customized.
This menu is used to configure the appearance and behavior of carts, with a [[wikipedia:Tree structure|tree layout]]
showing the different attachments. Each attachment represents a part of the train, such as a moving entity or a seat designation.
Attachments added as a child to other attachments are positioned relative to the parent. This allows many attachments to be moved
and animated together as a whole.

==Basic usage== 

===Command=== 


To start using the attachment editor, players need to give themselves the map item:
</translate>
{{Command|train attachments|Give the player the attachment editor map item|train.command.editor}}
<translate>

===Editing=== 


To edit a single cart of a train, and make it visible in the editor, you need to select the cart first.


[[Special:MyLanguage/TrainCarts/Editing|» Editing]]

===Navigation=== 


Each attachment is displayed on a different row, with an indent to the right every time it is added to a new parent. To navigate between attachments, use the Up/Down (W/S) steering controls. For each attachment selected, different menus can be accessed by pressing Left/Right (A/D) and Jump (spacebar) afterwards. Once inside a menu, the sneak button (shift) can be used to exit it again. This behavior is the same for all other menus. To move around while still viewing the editor, it can be placed into the off-hand (''typically F'').


To add new attachments, duplicate them, change the position in the tree hierarchy, or to delete them, use the [[Special:MyLanguage/TrainCarts/Attachments/General|General menu]] denoted by three horizontal lines.

===Dropping items=== 


[[File:Attachments_Drop_Item_Small.gif|thumb|An item is dropped from the inventory, configuring the attachment|link=File:Attachments_Drop_Item.gif]]
Menus where an item is being configured can be set instantly by dropping an item from the player's inventory. With the menu open, simply open the inventory, pick the item to set, and click on the outside of the inventory to drop it. The drop will be cancelled and the item set in the menu.

===Numbers=== 


Number sliders are used to configure numeric values, such position coordinates. Pressing the Left/Right buttons once will increment/decrement a very small amount. Holding the buttons for a longer time causes the number to increment/decrement faster and faster the longer it is being held down.


By holding Spacebar a number field can be reset to its default, usually 0. By holding spacebar and then pressing left/right, a special action can be performed. Usually this means inverting the value (-5 -> 5) or changing an angle in 90 degree steps.

===Text=== 


Text is input using an anvil menu. After typing in the desired text, click on the emerald to proceed, or the barrier item to cancel the change.

===Setting using commands=== 
</translate>
{{Command|train menu set [value]|Set a numeric or text value for the currently selected menu|train.command.editor}}
<translate>

==Gotchas== 
* Make sure to use <code>/train save name</code> to save your train regularly! Only saved trains can be restored
* Make use of the [[Special:MyLanguage/TrainCarts/Train Spawn Chest|train storage chest]] to move your train around or to recombine the carts
* Change spacing between carts, and where wheels are positioned, in the [[Special:MyLanguage/TrainCarts/Attachments/Physical|Physical menu]]
* When animating, make sure your animation frames have a delta-T greater than 0. Otherwise animation speed will not function.
* The new Display Entities cannot be clicked by default:
** If you cannot click to edit a train, look at it and do <code>/train edit</code> to select it
** To allow players to click on the cart to enter a seat, make sure to add a '''Hitbox attachment'''.
* You can save a sub-tree of attachments in the [[Special:MyLanguage/TrainCarts/Attachments/Model#Model_Store|Model Store]] in the [[Special:MyLanguage/TrainCarts/Attachments/General|General menu]], and create it in multiple places using the [[Special:MyLanguage/TrainCarts/Attachments/Model|'''Model Attachment''']]. There is also a clipboard and import/export function.

==Menu== 
===Appearance===
The Appearance Menu contains a selector at the top where the attachment type is configured, with the remainder of the menu automatically filled with this type's configuration.


{| class="wikitable" style="margin:left"
|+Attachment Types
! Type !! Description
|-
| '''Empty''' || Displays nothing. Used as a marker attachment to easily position multiple other attachments, and as an anchor for animations
|-bgcolor="#dddddd"
| '''Hitbox''' || Creates an invisible box that can be clicked. Important for entering seats. Size is configured in the Position menu.
|-
| [[Special:MyLanguage/TrainCarts/Attachments/Entity|'''Entity''']] || Displays an Entity like a Minecart or Mob
|-bgcolor="#dddddd"
| [[Special:MyLanguage/TrainCarts/Attachments/Item|'''Item''']] || Displays an Item on an Armorstand or using a Display Entity
|-
| [[Special:MyLanguage/TrainCarts/Attachments/Block|'''Block''']] || Displays a Block using a Display Entity. Only available on Minecraft 1.20+.
|-bgcolor="#dddddd"
| [[Special:MyLanguage/TrainCarts/Attachments/Seat|'''Seat''']] || A seat where a single player or entity can sit
|-
| [[Special:MyLanguage/TrainCarts/Attachments/Model|'''Model''']] || Loads in a full attachment configuration from the model store
|-bgcolor="#dddddd"
| '''Text''' || Floating Text Balloon
|-
| '''Platform''' || A moving shulker box that players can stand on. Does not work moving up.
|-bgcolor="#dddddd"
| '''Schematic''' || Displays multiple blocks using a WorldEdit saved Schematic
|-
| '''Light''' || When [https://www.spigotmc.org/resources/lightapi-fork.48247/ LightAPI] is installed, spawns a moving light source at the attachment position
|-bgcolor="#dddddd"
| [[Special:MyLanguage/TrainCarts/Attachments/Sound|'''Sound''']] || Adds a sound effect played with effect signs, command or the sequencer
|-
| [[Special:MyLanguage/TrainCarts/Attachments/Sequencer|'''Sequencer''']] || Automatically plays effects. Used to create ambient sound loops, such as engine noises, or to activate particle effects on a loop, such as a smoke stack.
|}

===Physical=== 
The Physical Menu configures the length of the cart and where the rail-tracking wheels of the cart are positioned.


[[Special:MyLanguage/TrainCarts/Attachments/Physical|» Physical Menu]]

===Position=== 
The position menu configures the position and rotation of the attachment. Includes additional options for some types of attachments, such as scale and transform options for items.


[[Special:MyLanguage/TrainCarts/Attachments/Position|» Position Menu]]

===Animation=== 
Attachments can be animated, making them move or rotate around. This is especially useful for funfair rides, or animated doors.


[[Special:MyLanguage/TrainCarts/Attachments/Animation|» Animation Menu]]

===General=== 
The general menu is used to add new attachments, delete them, move them around, name them or load/save them from the [[Special:MyLanguage/TrainCarts/Attachments/Model#Model_Store|model store]].


[[Special:MyLanguage/TrainCarts/Attachments/General|» General Menu]]

==Effect Activation== 
Effect attachments such as the [[Special:MyLanguage/TrainCarts/Attachments/Sound|sound attachment]] must be activated. First, the attachment must be [[Special:MyLanguage/TrainCarts/Attachments/General#Name|named in the general menu]]. It can then be activated in multiple ways:
* Using the [[Special:MyLanguage/TrainCarts/Signs/Effect|effect sign]]
* Using the <code>/train effect <name></code> command
* Using the [[Special:MyLanguage/TrainCarts/Attachments/Sequencer|sequencer attachment]]

==Backlog== 

===Editor=== 


* [[Special:MyLanguage/TrainCarts/Attachments/Saving|Saving trains (needs a cross-link about import/export and the whole savedtrain logic)]]
-> Navigating the tree menu

===Position=== 


* [[Special:MyLanguage/TrainCarts/Attachments/TransformType|Transform type]]
* [[Special:MyLanguage/TrainCarts/Attachments/Anchor|Anchor]]

===Animations=== 


* [[Special:MyLanguage/TrainCarts/Animations/Overview|Overview]]
</translate>

TrainCarts/TrainProperties

2025-10-12T09:44:15Z

Bergerkiller:

<languages/>
<translate>
== Introduction == 


In DefaultTrainProperties.yml and TrainProperties.yml, you can set important properties for trains or carts, like what happens when they collide. DefaultTrainProperties.yml is the config for every new train, whilst TrainProperties.yml are for trains which already exist.


DefaultTrainProperties.yml has three types of properties: default, admin and spawner. These property lists can set in the following ways:


By '''permissions''': 
Give people with a permission that create the trains certain properties (train.property.**** -> train.property.default),


By '''sign''': 
</translate>
{{sign|[+train]|property|setdefault|<name>}}
<translate>


By '''command''': 
Select the train (by punching it) and typing "/train setdefault default|admin|spawner"


If using the below table as a reference for values, all cart properties will be a part of the default train properties as well.


You can also set an individual property of a train or cart using /train <propertyname> <value>. A list of these property names are described below.

== Properties == 


{| class="wikitable"
|+Train Properties
!Property
!Type
!Description
|-
|soundEnabled
|boolean
|Sets whether ambient minecart sounds are enabled
|-
|displayName
|string
|Sets the display name of the train
|-
|allowPlayerTake
|boolean
|Sets whether the train supports players taking minecarts with them when they leave
|-
|requirePoweredMinecart
|boolean
|Sets whether the train needs a powered minecart to function
|-
|trainCollision
|boolean
|Sets whether the train can collide with other entities
|-
|collisionDamage
|double
|Sets the amount of damage the train does when colliding with entites
|-
|keepChunksLoaded
|boolean
|Sets whether this train keeps nearby chunks loaded
|-
|speedLimit
|double
|Sets the maximum speed of the train in blocks per tick
|-
|wait.distance wait.delay wait.acceleration wait.deceleration
|double values
|Distance sets the distance the train will wait to maintain a distance between itself and a train ahead
Delay sets the time the train waits when stopped completely
Acceleration/deceleration sets the maximum change of speed at which it maintains distance (speeds up/slows down)
|-
|suffocation
|boolean
|Sets whether passengers inside this train can sustain suffocation damage
|-
|killMessage
|string
|Sets the message displayed when a player or named entity<ref>Use %0% to display the player or entity's name when entering the string. For example, "%0% was crushed by a rolling minecart"</ref> dies to a minecart collision.
|-
|banking.strength
banking.smoothness
|double
|Sets how much a cart will bank sideways with strength when cornering and how long it will take to return to normal with smoothness
|-
|slowDown
|boolean
|Sets whether a minecart will experience friction and gravity
|-
|allowManualMovement
|boolean
|Sets whether minecart passengers can manually move the train they are in with W and S
|-
|tickets
|string[]
|Used internally
|-
|collision:
players:
passive:
neutral:
hostile:
tameable:
pet:
animal:
monster:
jockey:
killer_bunny:
npc:
utility:
boss:
train:
|string
|Sets a collision mode for the train.
Allowed modes are default, push, cancel, kill, killnodrops, enter, link, damage, damagenodrops, skip
|-
|allowPlayerEnter
|boolean
|Sets whether players can enter the train
|-
|allowPlayerExit
|boolean
|Sets whether players can exit the train
|-
|invincible
|boolean
|Sets whether the train is invincible
|-
|isPublic
|boolean
|Sets whether non-owners of the train can enter
|-
|pickUp
|boolean
|Sets whether storage minecarts in the train can pick up items
|-
|exitOffset
==: vector
x:
y:
z:
|double
|Sets the offset relative to the train in which players will teleport to when they exit the train
|-
|exitYaw
|double
|Sets the yaw of the player's view when they exit the train
|-
|exitPitch
|double
|Sets the pitch of the player's view when they exit the train
|-
|destination
|string
|Sets the destination of the train
|-
|enterMessage
|string
|Sets a message to display when entering the train
|-
|spawnItemDrops
|boolean
|Sets whether broken blocks should drop items
|}
{| class="wikitable"
|+Cart Properties
!Property
!Type
!Description
|-
|owners
|string[]
|Sets a list of owners' names of the
|-
|ownerPermissions
|string[]
|Used internally
|-
|tags
|string[]
|Sets a list of tags the train has
|-
|driveSound
|strring
|Sets the sound that plays when the cart rolls
|-
|blockBreakTypes
|string[]
|Sets an array of block types the cart will break which are one block directly to the left and right of the rails when it passes them
Example usage:
- DIRT
- COBBLE
|}
</translate>

TrainCarts/Tickets

2025-10-12T09:44:11Z

Bergerkiller:

<languages/>
<translate>
== Introduction == 


[[Image:Traincarts_ticket_item.png|thumb|right|Ticket item held in a player's hand]]


Ticket items are Minecraft Map items used as traditional train tickets to gain access to trains as a passenger.

== Usage == 

=== Creating, editing and renaming a ticket === 

==== Notes ==== 


* Leaving out a ticket name during creation will assign a random, free name
* Creating a new ticket automatically makes the player edit that ticket

==== Commands ==== 

</translate>
{{Command|train ticket create (name)|Creates a new ticket with the name specified|train.ticket.manage}}
<translate>
</translate>
{{Command|train ticket edit [name]|Edits the ticket with the given name|train.ticket.manage}}
<translate>
</translate>
{{Command|train ticket rename [new_name]|Renames the last-edited ticket|train.ticket.manage}}
<translate>
</translate>
{{Command|train ticket remove|Deletes the last-edited train ticket|train.ticket.manage}}
<translate>

=== Assigning or unassigning a ticket to a train === 

==== Commands ==== 


No auto-completion here, will be improved in the future

</translate>
{{Command|train addticket [name]|Assigns a ticket to a train|train.property.tickets}}
<translate>
</translate>
{{Command|train remticket [name]|Un-assigns a ticket from a train|train.property.tickets}}
<translate>
</translate>
{{Command|train clrticket|Clears all tickets set for a train|train.property.tickets}}
<translate>

==== Property sign ==== 

</translate>
{{sign|[+train]|property|addticket|myticket}}
<translate>

 
</translate>
{{sign|[+train]|property|remticket|myticket}}
<translate>

 
</translate>
{{sign|[+train]|property|clrticket|}}
<translate>

=== Giving ticket items to players === 


The ticket properties can later be updated without having to re-give the ticket item. The @p selector can be used (in command blocks) to give to players nearby.
</translate>
{{Command|train ticket give [name] [player/@p]|Gives a ticket item to a Player|train.ticket.manage}}
<translate>

=== Ticket item configuration === 


Tickets can be further configured to restrict the number of uses and more.

</translate>
{{Command|train ticket maximumuses [amount/unlimited]|Set the amount of times ticket items can be used|train.ticket.manage}}
<translate>

</translate>
{{Command|train ticket destination [destination]|Set what destination to set on the train when used|train.ticket.manage}}
<translate>

</translate>
{{Command|train ticket tags [tags]|Set what tags to add to the train when used|train.ticket.manage}}
<translate>

=== Ticket background image === 


The background image of the item can be changed on a per-ticket basis. Background images need to be put in the ''plugins/Train_Carts/images'' folder and must be 128x128 in resolution.
</translate>
{{Command|train ticket background [filename]|Assigns a background image|train.ticket.manage}}
<translate>

=== Realms === 


Tickets can be assigned to a realm, a common name that can be assigned to trains. This makes it easier to create multiple different tickets that can be used for the same trains. To use this feature, assign the realm name (instead of the ticket name) to the train tickets property, and now tickets part of this realm can be used.

</translate>
{{Command|train ticket realm [realm]|Sets the ticket realm|train.ticket.manage}}
<translate>
</translate>

TrainCarts/PathFinding

2025-10-12T09:44:07Z

Bergerkiller:

<languages/>
<translate>
== Introduction == 


[[Image:Pathfinding.png|thumb|right|Setup of 3 destinations and a switcher sign to route trains between them]]


Trains can be routed to different locations in the Minecraft world by automatically switching the track. By placing signs the track network topology is configured, which pre-configured trains will follow to reach their destination.


Locations trains can go to are known as ''Destinations'', which are designated using [[Special:MyLanguage/TrainCarts/Signs/Destination|destination signs]]. Locations where track is being switched, as well as the end-locations, are known as ''Nodes'' in the network, which are designated using [[Special:MyLanguage/TrainCarts/Signs/Switcher|switcher signs]]. To enforce a single direction on the tracks, [[Special:MyLanguage/TrainCarts/Signs/Blocker|blocker signs]] can be employed, which disables routes that go against the flow of traffic.

== Getting Started == 

=== Designate the destinations === 


Start by placing down destination signs with a name for the destination on the third line. The fourth line can be used to set a new destination to go to once a train goes over the sign, but can be left empty.
<gallery mode="slideshow">
File:Pathfinding_Destination.png|Station with destination sign. Trains can go here, are stopped for 30 seconds, then move on to the right.
</gallery>

=== Designate the switched nodes === 


Places where the track should be switched need to have an always-powered switcher sign placed. Now when a train moves over it that has a destination set, a route will be calculated and then the track is switched.
<gallery mode="slideshow">
File:Pathfinding_Switcher.png|Switcher sign will automatically switch the track to go from/to any of the 3 directions.
</gallery>

=== Enforce one direction === 


When it is desirable that trains only ever go in one direction over a piece of track, an always-powered blocker sign can be used. This is useful when having two tracks side-by-side, each going in opposing directions. The path finding system will automatically ignore paths that are blocked by blocker signs.
<gallery mode="slideshow">
File:Pathfinding_Blocker.png|With ''[+train:left]'' trains coming from the left are blocked, only allowing movement from right to left. Similarly, ''[+train:right]'' and other directions can be used.
</gallery>

=== Test it out === 


Place down a minecart on the track, and use the [[Special:MyLanguage/TrainCarts/Commands#Destination|Destination command]] to set a destination:
<pre>/train destination [name]
/train destination output</pre>
Now give the minecart a push towards the switcher sign, and observe how it will automatically switch the track to send the train towards the destination. You can change the destination again and send it to the switcher again. Continue to experiment with multiple switchers, blockers and destinations.


If you run into a problem where the switcher appears to make a mistake, use the [[Special:MyLanguage/TrainCarts/Commands#Reroute|Reroute command]] to force a recalculation of all routing information:
<pre>/train reroute</pre>


It is also possible to use the property sign to set a destination:
</translate>
{{sign|[+train]|property|destination|outpost}}
<translate>

== Advanced == 


Once the basic system is understood, there are some more complicated features to discuss.

=== Useful Side-Features === 

==== Keep Chunks Loaded ==== 
Prevent trains unloading when no player is nearby or in the train, by enabling the train [[Special:MyLanguage/TrainCarts/Signs/Property#Keep_Chunks_Loaded|keep chunks loaded property]].


You can use this property sign to set it:
{{sign|[+train]|property|keepchunksloaded|true}}


Or you can create your train, use <code>/train keeploaded true</code> and save it under a saved train name using <code>/train save name</code>. You can then automatically spawn it by this name using the [[Special:MyLanguage/TrainCarts/Signs/Spawner#Automated_spawning|spawner sign]].

==== Wait Distance ==== 
To maintain distance between trains and avoid collisions over long stretches, use the [[Special:MyLanguage/TrainCarts/Signs/Property#Wait_Property|wait distance property]].

==== Mutex Zones ==== 
Protects intersections against collisions with [[Special:MyLanguage/TrainCarts/Signs/Mutex|mutex zones]].

==== Station Routing ==== 
[[Special:MyLanguage/TrainCarts/Signs/Station|Station signs]] can launch the train into the direction of the next destination.


{{sign|[!train]|station||route}}

=== Debugger === 


[[File:Pathfinding Debug Destinations.png|thumb|Displays the destinations with a distance to them]]
The plugin offers a ''debug stick'' with which path finding information can be displayed. Use the stick item to click on rails to show information about the route(s) that can be taken. Sneak (shift) while clicking performs a ''reroute'', which recalculates the track reachable from where you clicked. If you have multiple smaller rail networks, this can be more efficient than executing the global reroute command.

==== All destinations ==== 


Use the following command to get a stick item that displays all destinations reached from a given track:
<pre>/train debug destination</pre>
The track clicked is followed until a ''node'' of the track network is found, after which all routeable destinations are listed. For every destination the total distance to it is listed, and particles are displayed leading into it. If you find that a certain destination is not listed that should be, you can move further along the track clicking occasionally to find where the break is.

==== A single destination ==== 


[[File:Pathfinding_Debug_Destination_Specific_One.png|thumb|Displays the precise route to one destination]]
Use the following command to debug a specific destination:
<pre>/train debug destination [destination]</pre>
Now when you click on the track, particles are displayed what route is taken to reach the destination. This is useful when debugging a specific destination so no particles are displayed for routes and destinations that aren't relevant to you.

=== Route Manager === 


Normally only one destination is set at a time. It is possible to set the next destination to go to on the destination sign itself, but that means you can only have one possible route. With the route manager a list of destinations to visit can be configured, and then applied to trains. Trains will then go down this list, advancing it every time they pass by a destination on it.

==== Commands ==== 


First, edit a train, then use the following commands to set a list of destinations:
<pre>/train route set [destination1] ([destination2] [destination3...])
/train route set outpost hillfort dungeon</pre>
[[File:Pathfinding_routes_set.png|File:Pathfinding_routes_set.png]]


To add additional destinations to the existing route, or to remove them, use these commands:
<pre>/train route add [destination1] ([destination2] [destination3...])
/train route remove [destination1] ([destination2] [destination3...])</pre>


You can then use the destination command or property to start the route at a desired destination. Otherwise, the route is started from the beginning the moment the train hits a destination sign. To inspect the route of a train, use the base route command. The current destination the train has is highlighted green.
<pre>/train route</pre>
[[File:Pathfinding_route_info.png|File:Pathfinding_route_info.png]]

==== Persistence ==== 


The route of a train can be saved globally under a name so it can later be applied to other trains instantly.
<pre>/train route save [name]</pre>
To load a saved route, this command can be used:
<pre>/train route load [name]</pre>
Alternatively, it can be done using a property sign as well:
</translate>
{{sign|[+train]|property|loadroute|myroute}}
<translate>
</translate>

TrainCarts/Commands/Selectors

2025-10-12T09:44:04Z

Bergerkiller:

<languages/>
<translate>
== Introduction == 


Traincarts adds command selectors that can be used to target trains, or passengers of trains, similar to how vanilla minecraft's [https://minecraft.wiki/w/Target_selectors @e selector] works. Besides the usual position-based selector filters, other train properties can be used to select trains that match specific criteria. These selectors can be used with '''other plugins'''. If a selector targets more than one player/train, then the entire command is repeated for every player/train result.


Two selectors exist: <code>@train</code> and <code>@ptrain</code>. Both accept identical selector conditions, which will be discussed on the rest of this page.


To quickly view what conditions are available in-game, use a Traincarts command like <code>/train info --train @ptrain[</code> which will then auto-complete and show suggestions of supported conditions.

=== Quick Command Examples === 


{| class="wikitable"
|-
! Example
! Description
|-
| /say hello @ptrain[distance=..5]
| Message "hello" to the passengers of all trains 5 blocks away or less
|-
| /kick @ptrain[name=train23]
| Kicks players inside train with name 'train23'
|-
| /train destroy --train @train[destination=InterState5]
| Destroy the trains heading for InterState5
|-
| /train eject --train @train[dx=-2..2,dy=-3..3,dz=-2..2]
| Eject the trains within a cuboid range of the sender
|-
| /train launch 0.5 --options 2 --train @train[tag=express]
| Launches the train with tag 'express' to a speed of 0.5 over 2 blocks distance
|}

== Conditions == 


Multiple conditions can be specified, which are all AND-ed together. All number-based conditions support Minecraft range syntax: <code>a..b</code>. For example, <code>-5..5</code> (-5 to 5), <code>..6</code> (6 or less) and <code>12..</code> (12 or more). Prefixing the condition value with <code>!</code> will make it evaluate as 'not'.


In all examples below <code>@train</code> can be substituted with <code>@ptrain</code> to instead target the player passengers of the trains.

=== Position Cuboid === 


The <code>x/y/z</code> conditions specify where on the world trains should be selected. This specifies a cuboid range. The <code>dx/dy/dz</code> can also be specified to grow this cuboid. If only dx/dy/dz are specified, then the x/y/z of the sender is used. The <code>world</code> condition can optionally be specified to operate on other worlds, or to run from a server terminal where no world can be inferred.


{| class="wikitable"
|-
| @train[x=10..12,y=23..56,z=-100..-80]
| All trains in cuboid (10, 23, -100) -> (12, 56, 80)
|-
| @train[x=10,y=23,z=-100,dx=2,dy=33,dz=20]
| Same as above, but specified with dx/dy/dz to 'grow' the cuboid
|-
| @train[x=10,y=10,z=10,dx=-2..2,dy=-10..10,dz=-2..2]
| Complex use: grows the cuboid from point (10, 10, 10) in both directions. This becomes cuboid (8, 0, 8) -> (12, 20, 12)
|-
| @train[dx=-10..10,dy=-5..5,dz=-10..10]
| Selects a cuboid around the sender (command block / player) of the command
|-
| @train[world=world_the_end,x=10,y=89,z=-20,dx=-10..10,dy=-10..10,dz=-10..10]
| The world name to target can be used to target trains on other worlds
|}

=== Distance === 


The <code>distance</code> condition filters trains based on distance to the sender, or a cuboid specified. This is a spherical distance.


{| class="wikitable"
|-
| @train[distance=..10]
| All trains 10 blocks or less away from the sender
|-
| @train[distance=1000..]
| All trains 1000 blocks away or more from the sender
|-
| @train[x=100,y=50,z=-100,distance=..5]
| All trains 5 blocks or less away from coordinate (100, 50, -100)
|-
| @train[x=10,y=10,z=10,dx=50,dz=50,distance=..10]
| All trains 10 blocks or less away from cuboid (10, 10, 10) -> (60, 10, 60)
|}

=== Sort and Limit === 


The <code>sort</code> and <code>limit</code> conditions can be used to pick a single result from many based on distance, or to pick limited results at random. '''Sort''' supports conditions <code>nearest</code>, <code>furthest</code> and <code>random</code>. '''Limit''' must be a natural integer.


{| class="wikitable"
|-
| @train[distance=..100,sort=random,limit=1]
| Picks a single random train 100 blocks away or less
|-
| @train[distance=..100,sort=nearest,limit=2]
| Picks at most 2 nearest trains, 100 blocks away or less
|-
| @train[distance=1000..,sort=furthest,limit=10]
| Picks at most 10 trains furthest away, 1000 blocks distance away or more
|}

=== Train Name === 


The <code>name</code> condition can be used to select trains by name, or a name pattern. Supports the same wildcard pattern rules as the [[Special:MyLanguage/TrainCarts/Signs#Remote_Control|remote control]] syntax.


{| class="wikitable"
|-
| @train[name=train12]
| Selects train with name 'train12'
|-
| @train[name=Intercity*Express]
| Selects trains with name starting with "Intercity" and ending with "Express"
|-
| @train[name=*]
| Selects all trains on the world
|}

=== Train Tags === 


The <code>tag</code> condition, which can be specified multiple times, can be used to select the tags assigned to trains and filter on those. Like the ''name'' condition, this supports a wildcard pattern. This only checks that a particular tag is or isn't present, not that it is the only tag present.


{| class="wikitable"
|-
| @train[tag=mytag]
| Selects trains that have tag 'mytag'
|-
| @train[tag=*fast,tag=!express]
| Selects trains that have a tag ending with 'fast', but do not have tag 'express'
|}

=== Passenger Count === 


The <code>passengers</code> and <code>playerpassengers</code> conditions select the trains that meet a certain number of (player) passengers. This supports the range command to check for 'at least' a number of passengers, such as <code>@train[passengers=5..]</code>

=== Derailed === 


The <code>derailed</code> condition selects trains that have derailed. For example: <code>@train[derailed=1]</code> or <code>@train[derailed=true]</code>

=== Unloaded === 
The <code>unloaded</code> condition selects trains that are inside unloaded chunks and are therefore no longer simulated. Example: <code>@train[unloaded=1]</code> or <code>@train[unloaded=true]</code>.
Trains that keep chunks loaded do not unload.

=== Speed === 


The <code>speed</code> condition (alias: <code>velocity</code>) selects trains that move at a certain speed. This is the actual movement speed, which is at most the speed limit set for the train. Example: <code>@train[speed=0]</code> for trains that are not moving.

=== Miscellaneous Properties === 


More might be added in the future, but the additional properties can be used to filter the selection


{| class="wikitable"
|-
| destination
| [[Special:MyLanguage/TrainCarts/PathFinding|Destination]] set for the train
|-
| friction
| Friction modifier of the train (default: 1)
|-
| gravity
| Gravity modifier of the train (default: 1)
|-
| keepchunksloaded
| Whether the train keeps nearby chunks loaded
|-
| speedlimit
| Speed limit set for the train
|-
| ticket
| Same checks as for tags, but for [[Special:MyLanguage/TrainCarts/Tickets|ticket names]] instead
|-
|}
</translate>

TrainCarts/Commands

2025-10-12T09:44:01Z

Bergerkiller:

<languages/>
<translate>
== Introduction == 


Commands are used to control trains or single carts through chat commands. They can also be used to perform routine tasks, such as removing all trains from a world.

=== Syntax basics === 


To perform a command, either use '''/train ''' or '''/cart '''. When using the train version, you want to operate on the entire train or perform a global train command. When using the cart version, you want to operate on a single cart.

=== Selecting === 
Commands that target a specific train (''/train'') or cart (''/cart'') require the player to select the train or cart first. This can be done by:
* Entering the cart
* Sneaking and damaging the cart, so it doesn't break (creative)
* Spawning a new train with the [[Special:MyLanguage/TrainCarts/Train Spawn Chest|train spawn chest]]
* Looking at the cart, and running command <code>/train edit</code>
* Listing trains with <code>/train list</code> and clicking on a train name, or specifying the name of the train in the <code>/train edit [name]</code> command

=== Targeting Flags === 
Instead of first selecting a cart to modify, you can use any of the following flags to target trains directly. These also work in Command Blocks.
{| class="wikitable"
|-
! style="width: 15%" | Flag
! style="width: 25%" | Example
! Description
|-
| --train <name>
| /train maxspeed 0.0 --train train12 /train maxspeed --train @train[name=intercity*]
| Selects a train by name. Supports the [[Special:MyLanguage/TrainCarts/Commands/Selectors|''@train'' selector]] in place of the name, with which you can target more than one train at a time.
|-
| --nearest
| /train maxspeed 0.0 --nearest
| Selects the nearest train to the sender. At most 128 blocks away.
|-
| --near <x> <y> <z> <distance>
| /train maxspeed 0.0 --near ~ ~ ~ 5
| Selects the nearest train near to the coordinates specified, at most distance away
|-
| --cart <index or entity_uuid>
| /cart destroy --nearest --cart 0
| Selects a single cart from the front. Index 0 is the front, 1 second from front, etc. The words 'head' and 'tail' can also be used to select the first or last cart. The train of which to select the carts can be selected with the other flags, otherwise the train the player is currently editing is used.
|-
| --world <worldname>
| /train destroy --world world_nether --near 2 66 -134 1.5
| By default flags only target the world the sender is on. With this, a different world can be specified. Is required when running commands from the server terminal.
|}

== Global commands == 


The below commands only work on ''/train'' and don't require a selection to function.

=== List === 


<pre>/train list
/cart list</pre>
Lists the number of stationary and moving trains in the world. It also lists the total number of cart entities (as part of those trains) and lists the trains that belong to you.

=== Reroute === 


<pre>/train reroute [--lazy]</pre>
If the path finding system is failing because the track got changed, you can use this command to force the plugin to re-calculate all destination paths.


The '--lazy' -Parameter: 
Normally the command takes all previous nodes which known existed and schedules them for routing. 
With the '--lazy' parameter, this happens once a cart goes towards a switcher sign, and only from that node.

=== Destroy all === 


<pre>/train destroyall
/train removeall</pre>
Destroys all minecarts and trains on the server. Can be useful to re-set the plugin.

=== Fix bugged === 


<pre>/train fixbugged</pre>
Destroys all minecarts that are not managed by the plugin. Useful for is the server was shut down unexpectedly, leaving orphaned trains on the track.

== Train - only commands == 


The below commands work only for ''/train''.

=== Rename === 


<pre>/train setname [name]
/train name [name]
/train rename [name]</pre>
Sets the name of the train, the name may not be assigned to another train already

=== Set display name === 


<pre>/train setdname [name]
/train displayname [name]
/train setdisplayname [name]</pre>
Sets the display name of the train, may be double-assigned. This name is displayed on SignLink-variable signs when using trigger signs.

== Train and Cart commands == 


The below commands work for both ''/train'' and ''/cart''.

=== Information === 


<pre>/train info
/train i</pre>
Shows train or cart related information, such as the name and set properties.

==== Ownership ==== 


<pre>/train claim</pre>
Sets you as the only owner of this train.
<pre>/train setowner [names...]
/train setowners [names...]
/train setowners</pre>
Sets the owner names of this train. Use no names to clear the owners.
<pre>/train addowner [names...]
/train addowners [names...]</pre>
Adds the owner names to this train.


To change ownership of a single minecart, use the '/cart' command instead of '/train'. When setting train owners, you set owners on all minecarts simultaneously. If no owners are set for a minecart, it can be freely edited and destroyed by everyone else.

==== Tags ==== 


<pre>/train settags [tags...]
/train settag [tags...]
/train tags [tags...]
/train tag [tags...]
/train settags</pre>
Sets the tags of this train. Use no tags to clear the tags.
<pre>/train addtags [tags...]
/train addtag [tags...]</pre>
Add tags to this train.


Tags can be used in combination with switcher or detector signs. For example, you can set a tag to order a train to be destroyed. Every minecart has a separate set of tags, setting tags on a train sets it for all minecarts simultaneously.

==== Destination ==== 


<pre>/train destination [destination]
/train dest [destination]</pre>
Sets the destination for this train.


You can also set a destination on a single minecart in the train, this way letting switcher signs split trains up in multiple carriages.

==== Player enter ==== 


<pre>/train playerenter [bool]</pre>
Sets if players can enter the train or minecart.

==== Player exit ==== 


<pre>/train playerexit [bool]
/train playerleave [bool]</pre>
Sets if players can exit the train or minecart.

==== Pick up ==== 


<pre>/train pickup [bool]</pre>
Sets if the storage minecart(s) (in the train) pick up nearby items from the ground.

==== Collision ==== 


<pre>/train collision mobs enter
/train collision player push
/train collision train cancel
/train collision block cancel</pre>
Set collision rules. This can be used to allow mobs to enter the train when they collide with it, disable trains linking or push players aside when they are in the way. Setting collision with blocks to cancel will make the train no longer check for collisions with blocks, which can help with performance.

</translate>

TrainCarts/Signs/Launcher

2025-10-12T09:42:27Z

Bergerkiller: Marked this version for translation

<languages/>
<translate>
== Introduction == 


The launcher sign, similar to the [[Special:MyLanguage/TrainCarts/Signs/Station|station]] sign, can launch trains and make them reach a certain speed. The distance over which the train slows down/speeds up and the direction to launch can all be specified. Launching at a speed of 0 will slowly put the train to a complete halt, similar to how stations stop trains. Note that the speed is not locked after launching is completed: you can still push the train around or stop it entirely.

== Syntax == 

</translate>
{{sign|[train]|launch 10|0.4|continue}}
<translate>

=== First line === 


There is no difference between using ''[cart]'' or ''[train]''. [[Special:MyLanguage/TrainCarts/Signs#Remote Control|Remote control]] can also be used in combination with this sign.

=== Second line === 


''launch'' or ''launcher'', followed up by the launch configuration. Launching can be done over a set distance, a set time, or at a constant acceleration. The launch function can be configured as [[wikipedia:Linear function|linear]] or [[wikipedia:Bezier curve|bezier]]. A bezier curve will accelerate slower towards the beginning and end of the launch.


{| class="wikitable"
|-
! Syntax
! Meaning
|-
| launch
| Automatically computes a suitable distance to launch at, by looking for the first bend in the rails up ahead.
The maximum distance calculated this way is 100 blocks.
|-
| launch 20.0
| Launches the train to the target speed over 20 blocks (meters)
|-
| launch 20.0s
| Launches the train to the target speed in 20 seconds
|-
| launch 1m
| Launches the train to the target speed in 1 minute
|-
| launch 500ms
| Launches the train to the target speed in 500 milliseconds
|-
| launch 100t
| Launches the train to the target speed in 100 ticks (5 seconds)
|-
| launch 2.2G
| Launches the train to the target speed at a constant acceleration based on a G-force of 2.2 (0.2406m/t2)
|-
| launch 10km/h/s
| Launches the train to the target speed at a constant acceleration. See the [[Special:MyLanguage/TrainCarts/Acceleration|TrainCarts/Acceleration]] page for more information.
Must have a slash somewhere to be considered an acceleration expression.
|-
| launch 20l launch 20sl launch 10km/h/sl
| By appending a ''l'' at the end of the expression, the launch follows a linear curve.
|-
| launch 20b launch 20sb launch 10km/h/sb
| By appending a ''b'' at the end of the expression, the launch follows a bezier curve.
|}

=== Third line === 


The speed to launch at. If left empty, it will launch at the speed specified in the configuration (''launchForce''). To put the train to a complete halt, use 0.


Absolute speeds use a positive or zero number with no sign; to launch the train to a speed of 1.25 blocks per tick (25 blocks per second, or 90 km/h), use "1.25". Relative speeds require a sign even when positive; to launch the train to a speed 0.5 higher than it was before, write "+0.5"; to decrease the speed by 0.5, write "-0.5".


When only a value is specified, the unit is blocks/tick. For all other supported units, see [[Special:MyLanguage/TrainCarts/Velocity|TrainCarts/Velocity]]

==== Speed limit ==== 
Normally trains will never speed up beyond what the speed limit property is set to. To overcome this, you will need to set a new speed limit, but setting the speed limit property may result in an instant speed-up. To fix this, it is possible to specify two numbers on the launcher sign to update both. It will smoothly launch to a new speed limit speed, and set the remainder as 'energy' that will slowly go down.

==== Speed limit syntax ==== 
Set a new speed limit of 2.0 and launch the train to this speed over a distance of 20 blocks. Once reached, give the train 10 'energy'.
{{sign|[train]|launch 20|2.0 10.0|}}

=== Fourth line === 


Optionally you can specify the [[Special:MyLanguage/TrainCarts/Signs/Direction|direction]] to launch here. The default parameter, if blank, is "continue" – it will launch the train in the same direction from which it came.
</translate>

TrainCarts/Permissions

2025-10-12T09:41:18Z

Bergerkiller:

<languages/>
<translate>
==Permissions== 


On this page all permissions used in Traincarts are listed. You can also find these by opening <code>plugins/Train_Carts/PermissionDefaults.yml</code>. That file might be more up-to-date than this page. [[Special:MyLanguage/BKCommonLib/PermissionDefaults|See also this page about Permission Defaults.]]

=== General === 


{| class="wikitable" style="margin:left"
! Node !! Description
|-
| train.place.minecart || The player can place minecarts. See also: [[Special:MyLanguage/TrainCarts/VanillaMinecarts|Vanilla Minecarts]]
|-bgcolor="#dddddd"
| train.place.traincart || The player can place TrainCarts minecarts. See also: [[Special:MyLanguage/TrainCarts/VanillaMinecarts|Vanilla Minecarts]]
|-
| train.break.self || The player can break their own minecarts
|-bgcolor="#dddddd"
| train.break.any || The player can break all minecarts, also ones the player does not own
|-
| train.ticket.manage || The player can edit the details of existing tickets or create new tickets
|}

=== Commands === 


{| class="wikitable" style="margin:left"
! Node !! Description
|-
| train.command.globalproperties || The player can edit the properties of all carts using commands
|-bgcolor="#dddddd"
| train.command.properties || The player can edit the properties of carts he owns using commands
|-
| train.command.destroy || The player can destroy owned carts through commands
|-bgcolor="#dddddd"
| train.command.destroyall || The player can destroy all trains on the server
|-
| train.command.fixbugged || The player can destroy all bugged minecarts on the server
|-bgcolor="#dddddd"
| train.command.upgradesavedtrains || The player can upgrade all saved trains model positions to the new TC version
|-
| train.command.reroute || The player can force path finding to re-calculate
|-bgcolor="#dddddd"
| train.command.reload || The player can reload the configuration
|-
| train.command.break || The player can set blocks the cart can break from a set list
|-bgcolor="#dddddd"
| train.command.breakblock.admin || The player can set blocks the cart can break, any type
|-
| train.command.setpublic || The player can make his owned carts open for the public
|-bgcolor="#dddddd"
| train.command.setowners || The player can set the owners of his owned carts
|-
| train.command.settags || The player can set the tags of his owned carts
|-bgcolor="#dddddd"
| train.command.setdestination || The player can set destinations for his owned carts
|-
| train.command.playerenter || The player can set if players can enter his owned carts
|-bgcolor="#dddddd"
| train.command.playerexit || The player can set if players can exit his owned carts
|-
| train.command.pickup || The player can set if his owned storage carts pick up items
|-bgcolor="#dddddd"
| train.command.setlinking || The player can set if his owned trains can link to other trains
|-
| train.command.keepchunksloaded || The player can set if his owned trains keep nearby chunks loaded
|-bgcolor="#dddddd"
| train.command.invincible || The player can set if his owned trains are invincible
|-
| train.command.pushing || The player can set if his owned trains push away certain entities
|-bgcolor="#dddddd"
| train.command.slowdown || The player can set if his owned trains slow down over time
|-
| train.command.setcollide || The player can set if his owned trains can collide
|-bgcolor="#dddddd"
| train.command.setspeedlimit || The player can set the maximum speed for his trains
|-
| train.command.setpoweredcartrequirement || The player can set if a powered minecart is needed for his train to stay alive
|-bgcolor="#dddddd"
| train.command.default || The player can apply default settings to his owned trains
|-
| train.command.rename || The player can rename his owned trains
|-bgcolor="#dddddd"
| train.command.displayname || The player can change the display name of his owned trains
|-
| train.command.manualmove || Whether the player can change if trains can be moved by damaging them
|-bgcolor="#dddddd"
| train.command.saveall || Whether the player can save all TrainCarts stored information to file
|-
| train.command.message || Whether the player can add message shortcuts
|-bgcolor="#dddddd"
| train.command.pathinfo || Whether the player can view the route the train is following to reach the destination
|-
| train.command.playertake || Whether the player can change if players take Minecarts with them when they leave
|-bgcolor="#dddddd"
| train.command.soundenabled || Whether the player can turn Minecart sound on or off
|-
| train.command.teleport || Whether the player can teleport to where trains are
|-bgcolor="#dddddd"
| train.command.changeblock || Whether the player can alter the type of block displayed in a minecart
|-
| train.command.changetick || Whether the player can alter the global update tick rate of TrainCarts (debug!)
|-bgcolor="#dddddd"
| train.command.issue || Whether the player can report problems with TrainCarts
|-
| train.command.editor || Whether the player can use commands to give himself editors for trains (models) and signs
|-bgcolor="#dddddd"
| train.command.chest || Whether the player can use a chest item that can store and spawn trains
|-
| train.command.save || Whether the player can use a command to save a train under a name
|-bgcolor="#dddddd"
| train.command.savedtrain.reverse || Whether the player can reverse a saved train, so that back becomes front when spawning
|-
| train.command.savedtrain.rename || Whether the player can rename a saved train to a new name
|-bgcolor="#dddddd"
| train.command.savedtrain.delete || Whether the player can delete a previously saved train
|-
| train.command.savedtrain.claim || Whether the player can change who has claimed a saved train
|-bgcolor="#dddddd"
| train.command.savedtrain.global || Whether the player can modify, delete or claim saved trains claimed by other players
|-
| train.command.savedtrain.import || Whether the player can import saved trains from online using hastebin
|-bgcolor="#dddddd"
| train.command.savedtrain.export || Whether the player can export (paste) saved trains to online using hastebin
|-
| train.command.enter || Whether the player can use a command to enter the train/cart being edited
|-bgcolor="#dddddd"
| train.command.launch || Whether the player can use a command to launch the train being edited
|-
| train.command.animate || Whether the player can use a command to play an animation
|-bgcolor="#dddddd"
| train.command.gravity || Whether the player can use a command to change the gravity factor of a train
|}


-----

=== Building Action Signs === 


Allows placing down [[Special:MyLanguage/TrainCarts/Signs|TrainCarts Signs]].
{| class="wikitable" style="margin:left"
! Node !! Description
|-
| train.build.feature.remotecontrol || The player can place down signs that use [[Special:MyLanguage/TrainCarts/Signs#Remote_Control|remote control]]
|-bgcolor="#dddddd"
| train.build.station || The player can build train stations
|-
| train.build.spawner || The player can build train spawners
|-bgcolor="#dddddd"
| train.spawner.automatic || The player can build spawners which automatically create carts
|-
| train.spawner.regular || The player can build spawners which create regular minecarts
|-bgcolor="#dddddd"
| train.spawner.powered || The player can build spawners which create powered minecarts
|-
| train.spawner.storage || The player can build spawners which create minecarts with chests
|-bgcolor="#dddddd"
| train.spawner.tnt || The player can build spawners which create minecarts with TNT
|-
| train.spawner.hopper || The player can build spawners which create minecarts with hoppers
|-bgcolor="#dddddd"
| train.spawner.command || The player can build spawners which create minecarts with command blocks
|-
| train.spawner.spawner || The player can build spawners which create minecarts with spawners
|-bgcolor="#dddddd"
| train.build.trigger || The player can build train triggers
|-
| train.build.destination || The player can build destinations
|-bgcolor="#dddddd"
| train.build.switcher || The player can build track switchers
|-
| train.build.destructor || The player can build train destructors
|-bgcolor="#dddddd"
| train.build.detector || The player can build train detectors
|-
| train.build.ejector || The player can build train ejectors
|-bgcolor="#dddddd"
| train.build.ejector.absolute || The player can build train ejectors that teleport to absolute world coordinates
|-
| train.build.property || The player can build train property setter signs
|-bgcolor="#dddddd"
| train.build.collector || The player can build systems to let trains collect from storage blocks
|-
| train.build.depositor || The player can build systems to fill storage blocks with items from trains
|-bgcolor="#dddddd"
| train.build.elevator || The player can build systems to teleport trains vertically
|-
| train.build.teleporter || The player can build train teleporters (portals)
|-bgcolor="#dddddd"
| train.build.blocker || The player can build train blockers
|-
| train.build.wait || The player can build train wait signs
|-bgcolor="#dddddd"
| train.build.crafter || The player can build item crafter signs
|-
| train.build.ticket || The player can build a sign that will charge money or ejects a player if he can't pay
|-bgcolor="#dddddd"
| train.build.announcer || The player can build a sign that sends a message to all the players in a train
|-
| train.build.effect || The player can build a sign that can play an effect
|-bgcolor="#dddddd"
| train.build.sound || The player can build a sign that can play a sound
|-
| train.build.blockchanger || The player can build a sign that alters the block displayed in minecarts
|-bgcolor="#dddddd"
| train.build.jumper || The player can build a sign that can cause a train to jump in a certain direction
|-
| train.build.launcher || The player can build a sign that can launch trains
|-bgcolor="#dddddd"
| train.build.enter || The player can build a sign that can make nearby players/mobs enter a train
|-
| train.build.skipper || The player can build a sign that can tell a train or minecart to skip upcoming signs
|-bgcolor="#dddddd"
| train.build.mutex || The player can build a sign that defines a mutual exclusion zone, where only one train can be at
|-
| train.build.flip || The player can build a sign that flips the orientation of a Minecart 180 degrees
|-bgcolor="#dddddd"
| train.build.animator || The player can build a sign that plays train animations
|}

=== Properties === 


Multiple permissions are checked when players want to change the properties (''maximum speed'', ''keep chunks loaded'', etc.) of a train. There are permissions for the different methods of changing them, permissions per property name and permissions that control the [[Special:MyLanguage/TrainCarts/TrainProperties|default properties]] applied to newly placed minecarts.


The per-property permissions are checked for:
* Commands that change a property
* Placing a [[Special:MyLanguage/TrainCarts/Signs/Property|Property Sign]] that changes a property
* Importing saved trains (<code>/savedtrain [name] import [path/url]</code>)
* Spawning train configurations with the [[Special:MyLanguage/TrainCarts/Train Spawn Chest|train storage chest]]
* Placing a [[Special:MyLanguage/TrainCarts/Signs/Spawner|Spawn Sign]] to spawn a saved train using certain properties

==== Permissions for different methods ==== 


{| class="wikitable" style="margin:left"
! Node !! Description
|-
| train.command.globalproperties || The player can edit the properties of all carts using commands
|-bgcolor="#dddddd"
| train.command.properties || The player can edit the properties of carts he owns using commands
|-
| train.build.property || The player can build train property setter signs
|}

==== Permissions per property name ==== 


{| class="wikitable" style="margin:left"
! Node !! Description
|-
| train.property.maxspeed || The player can alter the maximum speed of trains
|-bgcolor="#dddddd"
| train.property.slowdown || The player can change whether trains slow down due to gravity or friction
|-
| train.property.collision || The player can change what happens when trains collide with entities or blocks
|-bgcolor="#dddddd"
| train.property.playerenter || The player can change whether players can enter carts or not
|-
| train.property.playerexit || The player can change whether players can exit from carts or not
|-bgcolor="#dddddd"
| train.property.keepchunksloaded || The player can change whether the train keeps nearby chunks and itself loaded
|-
| train.property.gravity || The player can change the gravity multiplier of the train
|-bgcolor="#dddddd"
| train.property.banking || The player can change the way trains bank in curves
|-
| train.property.destination || The player can change what destination a train is path-finding to
|-bgcolor="#dddddd"
| train.property.tags || The player can add or remove tags to trains or carts, used by switchers and detectors
|-
| train.property.name || The player can change the name of the train
|-bgcolor="#dddddd"
| train.property.applydefaults || The player can apply defaults from DefaultTrainProperties.yml to trains
|-
| train.property.onlyownerscanenter || The player can change whether only owners or all players can enter a train
|-bgcolor="#dddddd"
| train.property.pickupitems || The player can change whether storage carts pick up items off the ground
|-
| train.property.soundenabled || The player can change whether a train makes sound while moving, or is quiet
|-bgcolor="#dddddd"
| train.property.invincible || The player can change whether a train is invincible to damage or can be destroyed
|-
| train.property.allowplayertake || The player can change whether the players take carts with them when they leave the server
|-bgcolor="#dddddd"
| train.property.spawnitemdrops || The player can change whether carts drop items when destroyed
|-
| train.property.requirepoweredcart || The player can change whether a train must have a furnace minecart to exist, or unlink
|-bgcolor="#dddddd"
| train.property.displayname || The player can change the display name of a train, which is used with the trigger sign
|-
| train.property.allowmobmanualmovement || The player can allow a train to be set in motion by mob passengers
|-bgcolor="#dddddd"
| train.property.allowplayermanualmovement || The player can allow player passengers to control the train using steering controls
|-
| train.property.owners || The player can change who has ownership of carts and can edit them
|-bgcolor="#dddddd"
| train.property.breakblocks.normal || The player can configure a train to automatically break blocks from a whitelist for farming setups
|-
| train.property.breakblocks.admin || The player can configure a train to break any type of block at all
|-bgcolor="#dddddd"
| train.property.route || The player can change what sequence of destinations a train follows
|-
| train.property.realtime || The player can configure that a train updates in realtime, adjusting for server tick lag and jitter
|-bgcolor="#dddddd"
| train.property.friction || The player can change the friction multiplier of the train
|-
| train.property.tickets || The player can assign tickets required for entering the train
|-bgcolor="#dddddd"
| train.property.viewdistance || The player can change the player view distance set for passengers of a train
|-
| train.property.entermessage || The player can change the message displayed to players when they enter the train
|-bgcolor="#dddddd"
| train.property.exitoffset || The player can change where players are ejected relative to the train
|-
| train.property.trackingrange || The player can change the range from which the train is visible to players
|-bgcolor="#dddddd"
| train.property.wait || The player can change the wait distance, acceleration and deceleration of trains
|}

==== Automatic Properties ==== 


When players place down minecarts, it can be set to automatically apply certain properties from <code>plugins/Train_Carts/DefaultTrainProperties.yml</code>. By default only the extra '''admin''' permissions exists, which is applied with:
<pre>train.properties.admin</pre>
Additional ones can be configured, and by giving the named permission to players, those players will then place down Minecarts using these properties. This mechanism can be used to, for example, create special roles that make it so minecarts these players place down keep chunks loaded, or makes the minecarts invincible.
</translate>

TrainCarts/Signs/Waiter

2025-10-12T09:41:13Z

Bergerkiller:

<languages/>
<translate>
== Introduction == 


Waiters are used to help prevent trains from colliding. Trains will look at the tracks ahead and wait at the sign until the track is clear.

== Syntax == 

</translate>
{{sign|[train]|waiter 7}}
<translate>


'''First line:''' Train/Cart You can use +train/cart to act as always-powered, or !train/cart to invert the power


'''Second line:''' waiter The optional number separated by a space (optional) determines how many blocks ahead the sign will look. Default is set in the server properties file.


'''Third line:''' ''(optional) A delay before the train is released when the track ahead is empty.''
</translate>

TrainCarts/Signs/Ticket

2025-10-12T09:41:10Z

Bergerkiller:

<languages/>
<translate>
== Description == 


The ticket sign is a simple money transfer and display system. It uses Vault to work on the account(s) of passenger(s) in a train.

== Syntax == 

</translate>
{{sign|[train]|ticket|add|1.5}}
<translate>

=== Second line === 


ticket, no other arguments.

=== Third line === 


''add'' to add money to the account, ''check'' to display the current money value to the player, ''buy'' to let the player buy a ticket and ''pay'' to let the user pay the owner(s) of the train. In the case of buying or paying, if the player can't buy a ticket, they are ejected from the train. To prevent the player re-entering the train, make sure player enter is disabled using a property sign as well.

=== Fourth line === 


In the case of add, buy or pay, the money value to add or the money value of the train ticket.
</translate>

TrainCarts/Signs/Trigger

2025-10-12T09:41:06Z

Bergerkiller:

<languages/>
<translate>
== Introduction == 


This sign is used to show train information on signs. It can also show a countdown of the time remaining for the train to arrive at a station, and comes with an internal stopwatch to measure this duration. Do not forget to power the sign, as it is inactive when not powered by redstone. To activate it all the time, use ''[+train]''.

== Syntax == 

</translate>
{{sign|[train]|trigger|trigger1|00:26}}
<translate>


'''Second line: ''' ''trigger''

=== Third line === 


Sets the trigger name. The name is used to show the gathered information on signs later on. For the syntax example above, the following things can be displayed on signs, which will be updated by SignLink automatically:
{| class="wikitable"
|-
! Variable on sign
! What is displayed
|-
| %trigger1%
| The count-down from the time set on the fourth line
|-
| %trigger1T%
| The same as the above
|-
| %trigger1D%
| The destination of the train
|-
| %trigger1N%
| The train name
|-
| %trigger1V%
| The speed of the train
|}

=== Fourth line === 


It sets the count-down time that is used when a train activates the trigger. You can use the common ':'-notation to make hour:minute:seconds, or minute:seconds, or just seconds. If you leave it empty, it will go into 'record mode'.

== Record mode == 


This means that the plugin is going to calculate the duration itself. As soon as one minecart activates the trigger, it keeps track of this minecart while measuring the time. As soon as the minecart stops or is destroyed, the time is stopped and put on the sign.
</translate>

TrainCarts/Signs/Transfer

2025-10-12T09:41:03Z

Bergerkiller:

<languages/>
<translate>
== Introduction == 


[[File:TrainCarts Item Transfer header.png|thumb|Multiple transfer signs lined up]]
TrainCarts allows you to transfer items from carts to blocks and the other way around. For example, if you want to pick up items from a chest or want to put items back into a chest. This is called 'item transferring', it is done through a single sign. It can target chests, furnaces and dispensers, also multiple at once. There are several syntax rules active for this sign.

== Syntax == 


The second line sets exactly what to perform and at what radius to look for furnaces, chests and/or dispensers. The third and fourth lines set what items to transfer.

</translate>
{{sign|[train]|collect chest|wood;64 stone|64 cobble}}
<translate>


 
This example would look in a radius of 3 and deposit all items into the chest (the default distance set in the config.yml file is 2).

</translate>
{{sign|[train]|chest in 3}}
<translate>

=== Second line === 


It can target furnaces, chests and dispensers and transfer both ways. The second line sets exactly what to perform: 


{| cellspacing="1" cellpadding="1" border="1" style="width: 480px; height: 501px"
|-
! scope="col" | Text 
! scope="col" colspan="2" | Result 
|-
| width="80" bgcolor="#cccccc" | chest in 
| width="200" bgcolor="#cccccc" rowspan="3" | Items from the train are put into nearby chests 
| bgcolor="#cccccc" rowspan="3" | [[Image:Minecart with Chest.png|50px]][[Image:Arrow icon.png|50px]][[Image:Chest.png|50px]] 
|-
| bgcolor="#cccccc" | deposit chest 
|-
| bgcolor="#cccccc" | deposit c 
|-
| chest out 
| rowspan="3" | Items from nearby chests are put into the train 
| rowspan="3" | [[Image:Chest.png|50px]][[Image:Arrow icon.png|50px]][[Image:Minecart with Chest.png|50px]] 
|-
| collect chest 
|-
| collect c 
|-
| bgcolor="#cccccc" | dispenser in 
| bgcolor="#cccccc" rowspan="3" | Items from the train are put into nearby dispensers 
| bgcolor="#cccccc" rowspan="3" | [[Image:Minecart with Chest.png|50px]][[Image:Arrow icon.png|50px]][[Image:Dispenser.png|50px|Dispenser.png]] 
|-
| bgcolor="#cccccc" | deposit disp 
|-
| bgcolor="#cccccc" | deposit d 
|-
| dispenser out 
| rowspan="3" | Items from nearby dispensers are put into the train 
| rowspan="3" | [[Image:Dispenser.png|50px|Dispenser.png]][[Image:Arrow icon.png|50px]][[Image:Minecart with Chest.png|50px]] 
|-
| collect disp 
|-
| collect d 
|-
| bgcolor="#cccccc" | furnace in 
| bgcolor="#cccccc" rowspan="3" | Fuel and cookable items from the train are put into nearby furnaces 
| bgcolor="#cccccc" rowspan="3" | [[Image:Minecart with Chest.png|50px]][[Image:Arrow icon.png|50px]][[Image:Furnace.png|50px|Furnace.png]] 
|-
| bgcolor="#cccccc" | deposit furn 
|-
| bgcolor="#cccccc" | deposit f 
|-
| furnace out 
| rowspan="3" | Items from nearby furnaces are put into the train
| rowspan="3" | [[Image:Furnace.png|50px|Furnace.png]][[Image:Arrow icon.png|50px]][[Image:Minecart with Chest.png|50px]] 
|-
| collect furn 
|-
| collect f 
|-
| bgcolor="#cccccc" | deposit cfd 
| bgcolor="#cccccc" rowspan="2" | Items from the train are first put into chests, then furnaces and then dispensers 
| bgcolor="#cccccc" rowspan="2" |
[[Image:Minecart with Chest.png|30px]] [[Image:Arrow icon.png|30px]] [[Image:Chest.png|30px]] [[Image:Furnace.png|30px|Furnace.png]] [[Image:Dispenser.png|30px|Dispenser.png]] 


|-
| bgcolor="#cccccc" | deposit
|-
| collect cfd 
| rowspan="2" | Items are put into the train, first from chests. then furnaces and then dispensers 
| rowspan="2" |
[[Image:Chest.png|30px]] [[Image:Furnace.png|30px|Furnace.png]] [[Image:Dispenser.png|30px|Dispenser.png]] [[Image:Arrow icon.png|30px]] [[Image:Minecart with Chest.png|30px]] 


|-
| collect
|-
| bgcolor="#cccccc" | deposit fc 
| bgcolor="#cccccc" | Items from the train are first put into furnaces, then into chests 
| bgcolor="#cccccc" |
[[Image:Minecart with Chest.png|40px]] [[Image:Arrow icon.png|40px]] [[Image:Furnace.png|40px|Furnace.png]] [[Image:Chest.png|40px]] 


|-
| fuel 
| rowspan="2" | Coal from nearby chests is put into the powered minecarts. 
| rowspan="2" |
[[Image:Chest.png|50px]] [[Image:Coal.png|15px]] [[Image:Arrow icon.png|50px]] [[Image:Minecart with Furnace.png|50px]] 


|}

=== Third and fourth lines === 


You can set the items to transfer on these lines, delimited by ;-signs. You can set the item type name and id, an optional data value and an optional amount to transfer. Both lines are read as one row of items. Leaving these lines blank will cause it to transfer all items. These lines are not used for the ''fuel'' system, which takes only coal to fuel powered minecarts.


[[Special:MyLanguage/TrainCarts/Signs/Items|TrainCarts/Signs/Items]] item format
</translate>

TrainCarts/Signs/Teleporter

2025-10-12T09:40:59Z

Bergerkiller:

<languages/>
<translate>
== Introduction == 


[[File:TrainCarts-Teleport.png|thumb|Trains are teleported from T1 to T2 and vice versa]]
The teleporter sign can teleport trains large distances and between worlds. It uses the [[Special:MyLanguage/MyWorlds/Portals|My Worlds portal]] as the sign, which has to be placed underneath the tracks like all other signs. It requires redstone power for it to teleport the train at all. All permissions of MyWorlds are taken into account and players that are not allowed to enter the world or portal will get ejected as the train vanishes. Trains are teleported into the direction the sign faces.

== Syntax == 

</translate>
{{sign|[portal]|World1TCE|World2TCE|World 2}}
<translate>


For the general syntax rules, see the [[Special:MyLanguage/MyWorlds/Portals|MyWorlds page about the portal format]].
</translate>

TrainCarts/Signs/Switcher

2025-10-12T09:40:55Z

Bergerkiller:

<languages/>
<translate>
== Introduction == 


Switcher signs can read information from the train or cart above and toggle a lever and rails based on that. It also marks the switchable nodes of the [[Special:MyLanguage/TrainCarts/PathFinding|path finding]] routing network. This makes this multi-purpose sign important for routing trains to their destinations, whether using path finding or otherwise.


Levers connected to the base block of the sign are toggled down when conditions match. When the sign is powered, the track above is also switched towards the statement-assigned direction when the condition matches. When the switcher sign is powered by redstone, or by using [+train], then it will switch the track based on the statements on the sign. This can cause trains to reverse on straight rail sections. If the sign is used primarily to toggle a lever when the statement conditions match, then [-train] should be used so this does not happen.


By default only powered switcher signs switch the track using [[Special:MyLanguage/TrainCarts/PathFinding|path finding]] logic. This can be changed in Traincart's ''config.yml'' as part of legacy support, as in past versions this was not the case.

== Syntax == 


'''First line:''' ''[-train]'' to toggle only the lever based on the conditions, ''[+train]'' or other modes for switching the track


'''Second line:''' ''switcher'' or ''tag''


'''Third line:''' ''The [[Special:MyLanguage/TrainCarts/Signs/Statements|statement]] for when to switch the track left (if no direction prefix is specified)''


'''Fourth line:''' ''The [[Special:MyLanguage/TrainCarts/Signs/Statements|statement]] for when to switch the track right (if no direction prefix is specified)''

</translate>
{{sign|[train]|switcher|t@mytag|r:default}}
<translate>


For [[Special:MyLanguage/TrainCarts/Signs/Statements|statements]] it can read cart tags, destination, passengers, items and several other states. It is also possible to sort the carts when using numeric values on the last two lines. This way you can make 1 train or cart go left out of every 3 trains or carts. The ''default'' statement is unique, in that it will only be true if no other statement on the sign is true, regardless of order. They are evaluated top to bottom.

=== Direction Prefixes === 
Statements can include a direction prefix to the left, such as ''l:'' or ''f:'', to define where to send the train when the statement condition is true.

=== Statements === 


On the third and fourth lines you can put the statements to evaluate. You can insert a [[Special:MyLanguage/TrainCarts/Signs/Direction|direction]] followed up by ''':''' and then the statement to set the direction to switch to. For example:

</translate>
{{sign|[!train]|switcher|1:<trainsize>|r:i@wood}}
<translate>


Will send all trains larger than 5 carts to the left, and trains with wood in storage minecarts to the right. It parses the statements from top to bottom, so wood-bearing trains larger than 5 carts are also sent to the left.


Switcher signs currently support wildcards only when matching to tags and player names (but not, for example, to train names).

=== Statement Continuation === 
Statements continue on signs below, provided they are all prefixed by a direction. Otherwise they will be ignored by the switcher sign. If you are not switching the track and only want a lever to be toggled, then you can use any direction prefix here, such as ''f:'' - it will have no effect in that case. The [[#Redstone powered switcher|Redstone powered switcher]] example down below uses this feature.

== Functions == 
=== As a detector ===
The switcher sign toggles a lever in addition to switching track. By using [-train] track switching can be disabled so that the switcher sign only toggles the lever. This can then be used to automatically detect changes in the train above, for example, when players enter the train.

</translate>
{{sign|[-train]|switcher|passengers|}}
<translate>

=== Switching without train === 


To change the rails when triggered by redstone, without requiring a train to enter the rails first, both from and to directions can be specified. For example:

</translate>
{{sign|[+train]|switcher|n-e:redstone|n-w:default}}
<translate>


Will switch the rails north-east when powered by redstone, and north-west otherwise. This also works with TC-Coasters, by specifying the junction names ( 1-2:redstone )

=== Path finding === 

</translate>
{{sign|[+train]|switcher}}
<translate>


The switcher sign is also used during [[Special:MyLanguage/TrainCarts/PathFinding|path finding]]. If a train or cart has a destination set, and no statements on the sign match (or no statements were set), it will toggle the rails to make the train go to the requested destination. If you need to force an alternative route or need to send 'passing through' trains around, add a statement on this sign to do so.

=== Sorter === 


If you need to sort carts onto multiple tracks, you can use an internal counter:

</translate>
{{sign|[+train]|switcher|3|4}}
<translate>


Right now it will send 3 trains to the left and then 4 trains to the right direction, after which the cycle repeats itself. You can put multiple switcher signs in line to equally divide the trains onto multiple tracks. This is shown in the video below:


https://www.youtube.com/watch?v=8KCfenk3Vi8

=== Splitting trains === 
A train can be split at an arbitrary cart using a [+cart] switcher. This will switch halfway the train sending each section of the train in a different direction. Instead of fixed number (1 cart left, 1 cart right) a percentage can be used (50%) which will split the train in half, regardless of train cart count.
{{sign|[+cart]|switcher|50%|50%}}

== Examples == 
=== Redstone powered switcher ===


By using the redstone statements on the sign, you can completely control what direction to send the train to:


[[File:TrainCarts Redstone Switcher.png|600px|3-way redstone switcher]]

=== Automatic launching === 
By using a <code>[-train]</code> passengers switcher sign, the lever is automatically toggled down once a player enters the train. This signal activates an inverted station sign, causing the train to launch into the opposite side that is powered. In this setup this launches the train left once a player enters. A redstone repeater delay can be used to debounce this.


[[File:Tc_switcher_station.png|600px|Switcher sign lever powers the station to automatically launch the train]]

=== Cart splitter === 
By using a <code>[+cart]</code> switcher sign using the counter syntax, a long train can be split into individual carts. Each cart is sent onto one of three tracks, equally. The extra sign below the cart switcher sign extends the number of switching rules. Statements: <code>l:1 r:1 f:1</code>


[[File:Tc_cart_switcher_sorter.png|600px|Cart switcher sign splits a train into individual carts onto three lanes]]

</translate>

TrainCarts/Signs/Station

2025-10-12T09:40:52Z

Bergerkiller:

<languages/>
<translate>
== Introduction == 


[[File:TrainCarts station centred.png|thumb|A train is idling above a station sign]]
Stations are used to stop and launch trains, optionally using a set delay in seconds. It can use redstone to set the direction to launch to, but when both sides are powered it can perform an automated action.

== Syntax == 

</translate>
{{sign|[train]|station|5|continue}}
<translate>

=== First line === 


When ''[train]'' is used, the train is centered above the sign. This means that the middle cart of the train will stop above the sign. When ''[cart]'' is used, the train will stop immediately, the first cart centered above the sign.

=== Second line === 


''Station'' followed up by an optional number. This number sets the distance to launch the trains at. The higher this number, the slower it will launch. Use only ''station'' to make the plugin calculate this distance automatically. Then it launches the train towards the first curved track piece up to 100 blocks away.


You can also specify a 'center offset' value, which changes where the train will stop on the station. This is done by specifying '''<distance>m''', for example ''''20.5m''''.


The below station sign will launch a train 30 blocks away, and center the train with a 12.5 block offset above the sign. The train waits for 10 seconds and then continues:
{{sign|[+train]|station 30 12.5m|10|continue}}

=== Third line === 


'''
An optional delay in seconds. This delay is used when launching. For example, when the right side is powered and a delay of 3 seconds is set, and a train enters, the train will wait for 3 seconds and then launch into the powered direction.'''

=== Fourth line === 


Sets the mode used when both sides are powered. The station sign will launch trains into the direction that is powered. If the sign receives no power whatsoever, it is not active and trains will travel right through. The inverted redstone option ([!train]) is still active here, so if power is inverted and the sign receives no power, it is as if all sides a powered.


The station will hold the train forever if both sides are powered, unless one of the below four types is set on the fourth line:
{| class="wikitable"
|-
! scope="col" | Sign
! scope="col" | Result
|-
| [[File:Sign 1.png|thumb]]
| [[Image:TrainCarts station left.gif|Image:TrainCarts station left.gif]]
|-
| [[File:Sign 2.png|thumb]]
| [[Image:TrainCarts station right.gif|Image:TrainCarts station right.gif]]
|-
| [[File:Sign 3.png|thumb]]
| [[Image:TrainCarts station continue.gif|Image:TrainCarts station continue.gif]]
|-
| [[File:Sign 4.png|thumb]]
| [[Image:TrainCarts station reverse.gif|Image:TrainCarts station reverse.gif]]
|}

==== Auto Routing ==== 
Instead of specifying a fixed direction, <code>route</code> can be put instead. This will make the station sign part of the [[Special:MyLanguage/TrainCarts/PathFinding|path finding network]], and launches the train into the most appropriate direction to reach its destination.


This will route the train to its destination, if set. Otherwise, resumes the train in the same direction it was approaching the station.
{{sign|[train]|station||route continue}}

==== Launch Speed ==== 
A number can also be put on the fourth line to set the launch speed of the station sign.
</translate>
{{sign|[train]|station||0.4}}

{{sign|[train]|station|5|continue 0.4}}
<translate>

== Lever Output == 
While a train is waiting on the station, the station toggles levers attached to the same block the station sign is attached to. This can be used to, for example, change the [[Special:MyLanguage/TrainCarts/Signs/Property|player exit property]], open doors or [[Special:MyLanguage/TrainCarts/Signs/Ejector|automatically eject]] the players inside.


<gallery widths=300px heights=250px>
File:Tc_station_lever_one.png|Lever is toggled while a train waits on a station|alt=alt language
File:Tc_station_lever_two.png|Alternative setup with a wall sign|alt=alt language
File:Tc_station_enterexit.png|Station output is used to automatically enable/disable players entering and exiting the train
</gallery>

== Examples == 

=== Shuttle-run === 


[[File:TrainCarts-Shuttle-run.gif|File:TrainCarts-Shuttle-run.gif]]
</translate>

TrainCarts/Signs/Sound

2025-10-12T09:40:48Z

Bergerkiller:

<languages/>
<translate>
== Description == 


This sign can play a sound effect, specified by name, when a train enters or power is supplied.

== Syntax == 

</translate>
{{sign|[+train]/[+cart]|sound|<soundname>|<soundname>}}
<translate>

</translate>
{{sign|[+train]|sound|block.beacon.|power_select}}
<translate>

</translate>
{{sign|[+train]|sound 0.56 0.5|block.note_block.bell|}}
<translate>

=== First line === 


When [train] is used, the sound is played in all the minecarts of the train. When [cart] is used, the sound is only played at the minecart that is currently above the sign. When no minecarts are near when the sign is powered, the sound is played above the sign. (at the rails)

=== Second line === 


''sound'', followed up by an optional pitch and volume.
Values of 1.0 are the defaults.The range of volume is from 0.0 to 1.0.
The range of pitch in note_block is from 0.5 (2^(-12/12) ) to 2.0 (2^(12/12) )
A full list of pitch value can be found on the Minecraft Wiki: [https://minecraft.wiki/w/Note_Block Note Block]
Pitch can be applied to any sound effect(some effects will be accelerated）
Use ''msound'' to play the sound every tick while a train is moving on top of it.
Use ''sound in'' to play the sound only to player passengers of the train.

=== Third and fourth lines === 


The name of the sound to play. Both lines are concatenated together, so that longer sound names can be specified. For example, you can put 'block.beacon.' on the third line and 'deactivate' on the fourth line, to play the 'block.beacon.deactivate' sound effect.


A full list of sound names can be found on the Minecraft Wiki: [https://minecraft.wiki/w/Sounds.json/Java_Edition_values Sounds.json/Java Edition values] or https://www.digminecraft.com/lists/sound_list_pc.php
</translate>

TrainCarts/Signs/Skip

2025-10-12T09:40:45Z

Bergerkiller:

<languages/>
<translate>
== Introduction == 


Skip sign causes the train to skip one or more signs further up ahead based on statements similar to the switcher sign.
It can be used to make trains skip a station sign when a certain destination is not set, for example.

== Syntax == 

</translate>
{{sign|[train]|skip 2 1|<statement 1>|<statement 2>}}
<translate>


* First line: [train] or [cart]. When the sign to be skipped works on a per-cart basis, using [cart] instead of [train] can be better. In general [train] is all you'll need. Like with other signs, redstone power matters. This means the skip sign is only active when powered by redstone. You can use [+train] or [+cart] to always power it.
* Second line: ''skip'', which without further arguments will skip the very next sign the train crosses. When followed by one number, the number sets the number of signs the train has to cross until the sign is skipped. When followed by a second number, the second number sets the number of signs to skip. In the example, a single sign will be skipped after having crossed two signs. A non-numeric sign filter can also be specified.
* Third and fourth lines: [[Special:MyLanguage/TrainCarts/Signs/Statements|statements]] (AND-ed together) for when to activate the skip sign. It is possible to put | in front of the second statement so that the two are OR-ed together instead. Leaving both lines empty makes the skip sign activate all the time.

=== Filter === 
On the second line of the skip sign a filter can be added before any skip offsets/counts. This makes the skip mechanism only ignore signs whose second line starts with the filter specified. The filter is case-insensitive. For example, the following skip sign skips the very next station sign, but ignores non-station signs:


{{sign|[+train]|skip station 0 1|}}

== Example == 


[[File:Skip sign example.png|thumb|1220x1220px|Trains come from the left and first hit the powered ([+train]) skip sign. When the train does not have destination ''square_west'' set or ( ''<nowiki>|</nowiki>'' ) is empty, the skip sign is activated and skips the very next sign. In this case that's the station sign. As a result, trains not meant for this station will cross the station sign without being stopped for 5 seconds.]]
</translate>

TrainCarts/Signs/Mutex

2025-10-12T09:40:38Z

Bergerkiller:

<languages/>
<translate>
== Introduction == 
[[File:Mutexworking.png|thumb|A mutex sign prevents a train from entering the intersection while another train is inside]]


The mutex sign handles mutual exclusion: it blocks trains entering a zone while another train is already inside. Once the zone is freed up again, the waiting trains are allowed to continue movement. This sign is useful in combination with switcher signs to avoid crashing trains. Levers attached to the base block are toggled while a train is inside the mutex zone.


Multiple mutex signs can be combined by naming them the same, combining the cuboid areas of effect they occupy. This way more complex zones can be created.

== Syntax == 

</translate>
{{sign|[train]|mutex}}
<translate>

</translate>
{{sign|[train]|mutex 1/2/1}}
<translate>

</translate>
{{sign|[train]|mutex 1/2}}
<translate>

</translate>
{{sign|[train]|mutex 2}}
<translate>

</translate>
{{sign|[train]|mutex 2|name|d@Station 12}}
<translate>


* First line: [train]. The sign does not have to be powered.
* Second line: ''mutex'', which without further arguments will create a cuboid zone around the sign of 1x2x1 (x/y/z). When followed by one number, the number sets all cuboid x/y/z-radius values at once. When followed by a second number, the first number sets the x/z-radius and the second number the y-radius. With 3 parameters, each x/y/z radius can be specified.
* Third line: Name (optional), multiple mutex signs with the same name form a single combined mutex zone
* Fourth line: [[Special:MyLanguage/TrainCarts/Signs/Statements|Statement]] (optional), each sign with the same name adds to a list of statements. Prepend & or | to switch between AND and OR logic.

=== Smart Mutex === 
[[File:Smartmutex.png|thumb|Smart Mutex allows two trains to pass while blocking two others]]
The Smart Mutex is a mutex sign that checks the paths trains (will) take through the mutex zones, allowing trains to pass that don't have a path intersecting with one another. This allows multiple trains to cross an intersection at the same time provided they can safely pass each other.

</translate>
{{sign|[train]|smartmutex 2}}
<translate>

</translate>
{{sign|[train]|smutex 5/6/8}}
<translate>

==== Prediction ==== 
When checking the path a train will take through the smart mutex zone, switchers are taken into account. The current switched state of the rails is then not important.

=== Pathing Mutex === 
[[File:Pathingmutex.png|thumb|Pathing Mutex creates a path that prevents another train from crossing at the same time]]
The pathing mutex attempts to replace the [[Special:MyLanguage/TrainCarts/Signs/Waiter|waiter sign]] in a more reliable fashion. When trains activate the pathing mutex sign, a path is predicted that the train will take from that point. All rails visited along this path become part of a temporary mutex zone. Other trains are blocked from entering this path, and if a train is already on it, the train is stopped in front of the pathing mutex sign.

</translate>
{{sign|[train]|pathmutex 100}}
<translate>

</translate>
{{sign|[train]|pmutex 100}}
<translate>

</translate>
{{sign|[train]|spmutex 100 3}}
<translate>

==== Syntax ==== 
'''pathmutex / pmutex''': Creates a standard mutex zone using the path ahead


'''spmutex''': Creates a smart mutex zone using the path ahead


First number is the path distance ahead to create as a mutex zone. Second number (optional) sets the width, or, distance that trains keep from the path. Setting this to a higher number avoids trains colliding with each other.

== Slowing down on approach == 
By setting the [[Special:MyLanguage/TrainCarts/Signs/Property#Wait_Property|train wait acceleration property]], trains will automatically slow down approaching an occupied mutex zone, instead of stopping instantly.

== Debug == 
[[File:Debugmutex.png|thumb|Smart Mutex boundaries displayed using the /train debug mutex command]]
Use '''/train debug mutex''' to temporarily display the exact boundaries of nearby mutex zones.

</translate>

TrainCarts/Signs/Launcher

2025-10-12T09:40:34Z

Bergerkiller:

<languages/>
<translate>
== Introduction == 


The launcher sign, similar to the [[Special:MyLanguage/TrainCarts/Signs/Station|station]] sign, can launch trains and make them reach a certain speed. The distance over which the train slows down/speeds up and the direction to launch can all be specified. Launching at a speed of 0 will slowly put the train to a complete halt, similar to how stations stop trains. Note that the speed is not locked after launching is completed: you can still push the train around or stop it entirely.

== Syntax == 

</translate>
{{sign|[train]|launch 10|0.4|continue}}
<translate>

=== First line === 


There is no difference between using ''[cart]'' or ''[train]''. [[Special:MyLanguage/TrainCarts/Signs#Remote Control|Remote control]] can also be used in combination with this sign.

=== Second line === 


''launch'' or ''launcher'', followed up by the launch configuration. Launching can be done over a set distance, a set time, or at a constant acceleration. The launch function can be configured as [[wikipedia:Linear function|linear]] or [[wikipedia:Bezier curve|bezier]]. A bezier curve will accelerate slower towards the beginning and end of the launch.


{| class="wikitable"
|-
! Syntax
! Meaning
|-
| launch
| Automatically computes a suitable distance to launch at, by looking for the first bend in the rails up ahead.
The maximum distance calculated this way is 100 blocks.
|-
| launch 20.0
| Launches the train to the target speed over 20 blocks (meters)
|-
| launch 20.0s
| Launches the train to the target speed in 20 seconds
|-
| launch 1m
| Launches the train to the target speed in 1 minute
|-
| launch 500ms
| Launches the train to the target speed in 500 milliseconds
|-
| launch 100t
| Launches the train to the target speed in 100 ticks (5 seconds)
|-
| launch 2.2G
| Launches the train to the target speed at a constant acceleration based on a G-force of 2.2 (0.2406m/t2)
|-
| launch 10km/h/s
| Launches the train to the target speed at a constant acceleration. See the [[Special:MyLanguage/TrainCarts/Acceleration|TrainCarts/Acceleration]] page for more information.
Must have a slash somewhere to be considered an acceleration expression.
|-
| launch 20l launch 20sl launch 10km/h/sl
| By appending a ''l'' at the end of the expression, the launch follows a linear curve.
|-
| launch 20b launch 20sb launch 10km/h/sb
| By appending a ''b'' at the end of the expression, the launch follows a bezier curve.
|}

=== Third line === 


The speed to launch at. If left empty, it will launch at the speed specified in the configuration (''launchForce''). To put the train to a complete halt, use 0.


Absolute speeds use a positive or zero number with no sign; to launch the train to a speed of 1.25 blocks per tick (25 blocks per second, or 90 km/h), use "1.25". Relative speeds require a sign even when positive; to launch the train to a speed 0.5 higher than it was before, write "+0.5"; to decrease the speed by 0.5, write "-0.5".


When only a value is specified, the unit is blocks/tick. For all other supported units, see [[Special:MyLanguage/TrainCarts/Velocity|TrainCarts/Velocity]]

==== Speed limit ====
Normally trains will never speed up beyond what the speed limit property is set to. To overcome this, you will need to set a new speed limit, but setting the speed limit property may result in an instant speed-up. To fix this, it is possible to specify two numbers on the launcher sign to update both. It will smoothly launch to a new speed limit speed, and set the remainder as 'energy' that will slowly go down.

==== Speed limit syntax ====
Set a new speed limit of 2.0 and launch the train to this speed over a distance of 20 blocks. Once reached, give the train 10 'energy'.
{{sign|[train]|launch 20|2.0 10.0|}}

=== Fourth line === 


Optionally you can specify the [[Special:MyLanguage/TrainCarts/Signs/Direction|direction]] to launch here. The default parameter, if blank, is "continue" – it will launch the train in the same direction from which it came.
</translate>

TrainCarts/Signs/Enter

2025-10-12T09:40:31Z

Bergerkiller:

<languages/>
<translate>
== Introduction == 


The enter sign lets nearby players and/or mobs into a train. It overrides the ''allowenter'' property on trains, which means you can deny players from entering the train manually while still allowing this sign to function.

== Syntax == 

</translate>
{{sign|[train]|enter 3s|player mob|no}}
<translate>


'''First line:''' ''[train]'' to enter into all minecarts of the train, ''[cart]'' to enter into minecarts individually

=== Second line === 


''enter'', followed up by the radius to look for players or mobs in blocks. When an ''s'' is added after the radius, the radius is fully spherical, otherwise it is cylindrical with height 1. So, if you do not want players/mobs above or below the minecart(s) to enter, leave out the s. If you do need this, add the s.

=== Third line === 


What type of entities this sign operates on. By adding ''mob'' mobs will enter, by adding ''player'' players will enter. ''misc'' will let in other types of entities, like armor stands. When this line is left empty only players enter the minecarts. You can allow both mobs and players by appending them, for example ''player mob''

=== Fourth line === 


Sets whether to look around the sign for players/mobs to enter, or whether to look around each individual minecart. By specifying 'yes/true' it will look around the sign, by specifying 'no/false' or by leaving the line empty it will look around each minecart.

=== Remote Control === 


You can remotely make trains take in passengers. Say your train is called ''train01'', then you use the following on the sign:

</translate>
{{sign|[train train01]|enter 5|player|yes}}
<translate>


Then it will teleport all players near the enter sign into the train named ''train01''. Note that long-distance teleportation (between worlds or far away) will likely fail, so keep the RC sign near the train when using this.
</translate>

TrainCarts/Signs/Elevator

2025-10-12T09:40:28Z

Bergerkiller:

<languages/>
<translate>

[[Image:TCElevators.png|thumb|right|Elevator signs teleporting up and down]]
The elevator sign can teleport trains up and down to another elevator sign. Note that it doesn't teleport to [[Special:MyLanguage/TrainCarts/ActionBlocks#Elevator|Elevator Blocks]], as that is another system. You can set on the sign to what direction to teleport, as well as which number elevator to take.

== Syntax == 

</translate>
{{sign|[train]|elevator|up 2}}
<translate>


'''Second line''': ''elevator''

=== Third line === 


''up'' or ''down'', optionally followed up by the number of elevator to take. For example, ''up 2'' would take the second elevator above this one. Note that if there is no available elevator at that location, nothing happens.
</translate>

TrainCarts/Signs/Ejector

2025-10-12T09:40:24Z

Bergerkiller:

<languages/>
<translate>
== Introduction == 


The ejector sign can eject (let exit) passengers of minecarts. You can place it at a station to eject the entire train in one go, or do it for carts individually.


The sign requires power to work.

== Syntax == 

</translate>
{{sign|[train]|eject|0/12/12|90/0}}
<translate>


'''First line:''' ''[train]'' to eject all minecarts in the train, ''[cart]'' to eject minecarts individually


'''Second line:''' ''eject'' to teleport relative to the minecarts, ''eject at'' to teleport at absolute world coordinates

=== Third line === 


When '''eject''' is used on the second line: 
Optional offset to eject players, relative to the minecarts. Offset 'axis' are delimited by '/'-signs. The first value sets the forward/backward offset, the second up/down and the third left/right. 
Example (left of the train): '''0/0/4'''


When '''eject at''' is used on the second line: 
The exact x/y/z world coordinates to teleport the players to 
Example: '''154/67/-2442'''

=== Fourth line === 


Optional angle players look to after being ejected. The first value sets the 'yaw', the angle to look left and right (90 is straight ahead, 180 is to the right, 0 to the left and 270 is facing backwards). The second sets the 'pitch', the angle to look up (negative) and down (positive).

=== Remote Control === 


You can remotely eject trains too. Say your train is called ''train01'', then you use the following on the sign:

</translate>
{{sign|[train train01]|eject|0/2/0}}
<translate>
</translate>

TrainCarts/Signs/Effect

2025-10-12T09:40:19Z

Bergerkiller:

<languages/>
<translate>
== Description == 


This sign can be used to activate an effect configured in the train's [[Special:MyLanguage/TrainCarts/Attachments|attachments]] when a train enters or redstone power is supplied.

== Syntax == 

</translate>
{{sign|[+train]/[+cart]|effect|<name>|<name>}}
<translate>

=== First line === 


When [train] is used, the effect is played in all the minecarts of the train. When [cart] is used, the effect is only played at the minecart that is currently above the sign. When no minecarts are near when the sign is powered, the effect is played above the sign. (at the rails)

=== Second line === 


''effect'', followed up by an optional '''playback speed''' (''pitch'') and '''intensity''' (''volume''). Values of 1.0 are the defaults. Specifying '''effect stop''' will abort playback of the effect if possible.

=== Third and fourth lines === 


One or two '''names''' of effect [[Special:MyLanguage/TrainCarts/Attachments|attachments]] to activate. In the Attachment Editor, go to the [[Special:MyLanguage/TrainCarts/Attachments/General|general menu]] (''hamburger'') and name the effect attachment. You can then put that name here to activate it.


Examples of supported attachments:
* [[Special:MyLanguage/TrainCarts/Attachments/Sound|Sound Attachment]]
* Particle Attachment
* [[Special:MyLanguage/TrainCarts/Attachments/Sequencer|Sequencer Attachment]]

== Legacy == 


An old version of this sign still exists which can only play (some) Bukkit effects. For this, use ''beffect'' on the second line. ''peffect'' plays the effect at the player, and ''meffect'' every tick as a train drives over the sign.

</translate>
{{sign|[+train]/[+cart]|beffect|note|}}
<translate>


These effects can be played:
* A sound effect (See: [https://hub.spigotmc.org/javadocs/spigot/org/bukkit/Sound.html Available Sounds])
* A particle effect (See: [https://hub.spigotmc.org/javadocs/spigot/org/bukkit/Effect.html Available Effects])
* ''link'', to play the fizz and smoke effects at once (link effect)
</translate>

TrainCarts/Signs/Detector

2025-10-12T09:40:15Z

Bergerkiller:

<languages/>
<translate>
== Introduction == 


Detector signs are very similar to switcher signs, only difference being that:
* They do not switch the tracks
* They detect multiple tracks


You can use detector signs to detect certain trains on a very long piece of track. You can use it, for example, to stop spawning trains if the track is currently in use. You can also use it to make trains take alternative routes if a certain track is in use.

== Syntax == 


'''First line:''' ''Whether to detect trains or single carts''


'''Second line:''' ''detector (name)''


'''Third line:''' ''Statement 1''


'''Fourth line:''' ''Statement 2''

</translate>
{{sign|[train]|detector (name)|o@player1|tag1}}
<translate>


If the third and fourth lines are kept empty, it will toggle the lever whenever it finds a train. A name can optionally be put after the word ''detector'', to make sure two detector signs can only find each other.

== Placement == 


[[File:TrainCarts-detector.png|thumb|Two detector signs in operation]]
Placement is rather difficult, since you need to use pairs of detector signs, one on both ends of the track to detect. The detector signs have to face each other, or they will have a hard time finding each other. Both signs are operated simultaneously, so you can use both ends to toggle a lever, using 4 statements in total. By adding multiple detector signs underneath one track you can expand the amount of statements.

== Statements == 


On the third and fourth lines you can put the statements to evaluate.


[[Special:MyLanguage/TrainCarts/Signs/Statements|Statements]]
</translate>

TrainCarts/Signs/Destroyer

2025-10-12T09:40:10Z

Bergerkiller:

<languages/>
<translate>

{{Sign Info|line1=[train]|line2=destroy|description=Destroys either a single cart or a train}}

== Introduction == 


The destroy sign can, simply put, destroy trains or single carts in a train. Nothing more nothing less.

== Syntax == 


Sign:

</translate>
{{sign|[train]|destroy}}
<translate>


'''First line''': ''Whether to destroy one cart or the entire train''


'''Second line''': ''destroy''

=== Remote Control === 


You can remotely destroy trains too. Say your train is called ''train01'', then you use the following on the sign:

</translate>
{{sign|[train train01]|destroy}}
<translate>

=== Destroy Empty Train === 


You need two signs and a lever, as well as access to two sides of the block on which the train is which to be destroyed, which we will call the 'destroy' block, as well as the block below that one, which we will call the 'underlying block.'


I placed a sign on the side of the destroy block that stated

</translate>
{{sign|[train]|switcher|empty}}
<translate>


I then put a lever on the face of that block (under the track leading to the destroy block).


Finally, I put this sign below the lever

</translate>
{{sign|[train]|destroy}}
<translate>


The whole thing looks like this


[[File:destroy empty train.png|File:destroy empty train.png|600px]]
</translate>

TrainCarts/Signs/Destination

2025-10-12T09:40:04Z

Bergerkiller:

<languages/>
<translate>
== Introduction == 


Destination signs map destinations under a name, which are used in the [[Special:MyLanguage/TrainCarts/PathFinding|path finding]] logic. When a train tries to reach a certain destination and it has this name set, the plugin knows what tracks to switch. Other than a marker, it can also set a new destination on the train when clicked, powered by redstone or when a train enters the sign.

== Syntax == 

</translate>
{{sign|[train]|destination|centralstation|subway_1}}
<translate>


'''Second line:''' ''destination''


'''Third line:''' ''Case-sensitive destination name''


'''Fourth line:''' ''Case-sensitive destination name to set on the train''


In the example above, the destination is <code>centralstation</code>, and any train with a destination of <code>centralstation</code> will find a path to the sign. Any train that passes over the sign will also have its destination set as <code>subway_1</code>.


You can leave the third line blank to only let the sign set a new destination on the train. You can leave the fourth line blank to only use this sign for path finding. The destination is set on the train only if:
* The train has no destination set
* The destination sign is itself no destination
* The destination sign is activated using Redstone power
* The destination sign name is the same as the destination set on the train

=== Remote Control === 


[[Special:MyLanguage/TrainCarts/Signs#Remote_Control|Remote Control]]
You can remotely set destinations on trains. Say your train is called ''train01'', then you use the following on the sign:

</translate>
{{sign|[train train01]|destination|subway|bridge}}
<translate>
</translate>