TrainCarts/Signs/ko

TrainCarts에서는 표지판을 활용해 기차를 조종할 수 있다.

표지판의 구조

표지판 형식 한눈에 보기

모든 표지판의 첫번째 줄은 cart나 train을 포함한다. 첫 번째 줄이 cart인 표지판은 기차의 각 칸에 독립적으로 적용되며, train인 표지판은 기차 전체에 한번에 작용한다. 또한, 첫번째 줄에 특수 문법을 활용해 레드스톤 신호에 따른 표지판의 작동 여부를 설정할 수 있으며, 기차가 오는 방향에 따라 표지판이 다르게 작동하도록 명시할 수도 있다.

레드스톤 신호

TrainCarts에서 사용하는 표지판은 레드스톤 신호가 주어져야지 작동한다. 즉, 표지판 옆에 레드스톤 토치나 레버와 같은 레드스톤 신호를 주는 장치를 통해 표지판의 활성화 여부를 조절할 수 있다. 또한, 첫 번째 줄에 특수 문법을 활용해준다면 레드스톤 신호와 상관없이 표지판을 활성화한 상태로 유지할 수 있다. (일반적으로 [+train]을 많이 쓴다.)

TrainCarts 표지판 활성화 모드

첫번째 줄	설명
[train]	기본값. 레드스톤 신호가 주어졌을 때만 표지판이 활성화됨
[+train]	항상 활성화. 레드스톤 신호와 상관없이 표지판이 항상 활성화된 상태로 유지됨.
[!train]	레드스톤 신호 반전. [train]과는 정 반대로 레드스톤 신호가 주어지지 않을 때만 표지판이 활성화되고, 레드스톤 신호가 주어지면 표지판이 비활성화됨. (레드스톤 신호가 없으면 [+train]와 똑같음.)
[-train]	항상 비활성화. 레드스톤 신호와 상관없이 표지판이 항상 비활성화된 상태로 유지됨. switcher 표지판 말고는 쓸 일 없음.
[/train]	On-pulse power mode. Signs only activate once when redstone power goes from off to on, and don't respond to trains riding over it
[\train]	Off-pulse power mode. Signs only activate once when redstone power goes from on to off, and don't respond to trains riding over it
[/\train]	Redstone change power mode. Signs only activate once when redstone power switches state, and don't respond to trains riding over it

표지판의 레드스톤 신호 출력

표지판이 부착된 블럭에 레버를 달면, 일부 표지판은 레드스톤 신호를 출력할 수도 있다. 예를 들어, station(역) 표지판은 위에 열차가 정차하였을 때 레드스톤 신호를 출력한다.

Activation Direction

By default signs only activate when the train sees the front or sides of the sign. This means you should place signs facing the direction of train movement. To override this behavior you can set these activation directions by adding a colon (:) followed by one or more directions. If you want the sign to always respond, just use [train:*].

For example, [-train:lr] on a switcher sign would activate a lever when a train enters from either the sign-relative left or right direction and doesn't for the remaining ones. It uses -train so that it does not switch the track.

Remote Control

A few sign systems support remote control: the ability to control trains by name. You then use the [train <name>] format, or the shorter alias [t <name>]. Remotely controlled signs only respond to redstone changes, thus where you place them is not important. The signs that support this feature are listed in the Types table down below.

Remote control can also affect multiple trains. Just like the tag system, remote control uses *-signs to identify the trains to affect. For example, the following remote control sign will set the destination to home for all intercity trains:

[train Intercity*]

property

destination

interhome

You can use this to recall all your trains easily. If you use tags to navigate trains, you can also add a tag saying that the train should return.

Placement

Empty minecarts are blocked

Trains are switched left and right using a 1:1 counter

Each sign targets a certain track piece above. Signs attached to walls take the block they are attached to and look up until they find a piece of track. That track is then used for that sign. Sign posts look up until they find a piece of track. There may not be blocks without signs between the bottom sign and the tracks.

You can make a pillar of blocks below a single track piece and attach signs to it, to make a bundle of actions on a single track piece. Trains look down when they enter a new track piece to check for signs, so make sure you put the output signs above the signs that use this output for correct results.

A noticeable exception would be add-ons for the TrainCart plugin, which may change the (relative) position a sign would need to be placed on in order to work for the track. For example, would the TC Hang Rail add-on require you to add the signs above the Hang rail track to work, while the TCC (TrainCarts Coasters) add-on uses the block of a node for the sign, which can be moved to any other block.

For most signs the sign direction influences what happens, as also discussed earlier (Activation Direction):

• The train has to face the text on the sign to make the sign respond
• Signs with the same alignment as the tracks (faces to or away from the tracks) always respond
• The train is spawned in the direction the sign faces

Types

Sign	Description	Remote Control
Animate	play an animation configured in the train's attachments	Yes
Announce	sends a message to players in the cart and/or train above	Yes
Blocker	blocks trains coming from a certain direction	No
Block Changer	change the block types displayed in a minecart	Yes
Craft	crafts items inside the storage minecarts of a train using a nearby workbench	No
Destination	marks a destination for the path finding and sets the next destination for the train	Yes
Destroy	destroy trains	Yes
Detector	detect trains on a set region of rails	No
Effect	plays a particle or sound effect at the minecart, train or sign	Yes
Eject	eject trains (let passengers exit)	Yes
Elevator	teleports trains including passengers up and down to another elevator	No
Enter	lets nearby players and/or mobs enter the train	Yes
Flip	Lets you flip a cart 180 degrees	Yes
Launcher	launch or brake trains to start moving at a desired speed	Yes
(Smart) Mutex	prevents train collisions at intersections by blocking multiple trains from entering the same area	No
Property	set properties on the train such as tags, destinations, enter/exit toggle and more	Yes
Skip	skips execution of signs up ahead based on statements	Yes
Sound	plays a named sound effect	Yes
Spawn	spawn an entire train, cart types can be set	No
Station	stop and launch trains	No
Switcher	switch levers and rails based on properties on the train	No
Teleport	teleport trains including passengers (requires MyWorlds)	Yes
Transfer	transfer items between trains and chests/furnaces/dispensers	No
Trigger	display train information and a countdown of the arrival time of trains on signs (requires SignLink)	No
Ticket	let passengers pay for a ride (requires Vault)	No
Waiter	waits the train until the track is clear of other trains	No

Permissions

Each sign has a separate build permission. See the main permissions page. For using remote control, the player requires the train.build.feature.remotecontrol permission which is OP-only by default.