RailSwitch: Difference between revisions

If the rail is set up, simply write <code>/dest place</code> where <code>place</code> is the place where you want to go. You can also chain destinations, and<code>/dest travelplace1 toplace2</code> them in order,etc. this can be useful for taking a route via specific junctions, RailSwitch will route players towards signs that contain either <code>place1</code> or <code>place2</code>.<ref name=":0">https://github.com/okx-code/RailSwitch/blob/master/README.md</ref> Stations where /dest has been set up will probably list possible destinations on signs, if you use normal direct rails between A and B /dest will do nothing.

A sign with the destination name on it must be placed over a detector rail and reinforced under the same group. The sign first line must be <code>[destination]</code>, then the other three lines can be destination names. They have to be placed before the T-junction. You may also use <code>[!destination]</code>, which will activate the rail if a player's destination is not on the signs.<ref name=":0" />

Upon passing on the detector rail, the redstone signal will activate only if the player on the minecart chose a direction written on the sign. If it's the case, the detector rail will send a signal which will allow the T-junction to change direction, thosethus allowing the player to chose a direction. In the exempleexample on the right, if the player had the mall set has their destination, the detector would send a redstone signal which would change the T-junction orientation, thosethus sending the player to the mall. If the player had an otheranother destination setup, the detector rail won't send a redstone signal, and the player would continue straight up as per the normal T-junction rules.