This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | |||
trains:signs [2024/07/11 21:44] – paul | trains:signs [2024/07/11 21:46] (current) – [Placement] paul | ||
---|---|---|---|
Line 42: | Line 42: | ||
===== Placement ===== | ===== Placement ===== | ||
- | {{: | + | {{: |
Empty minecarts are blocked | Empty minecarts are blocked | ||
+ | |||
+ | |||
{{: | {{: | ||
Line 52: | Line 54: | ||
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. | 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, 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): | For most signs the sign direction influences what happens, as also discussed earlier (Activation Direction): |