As always, this version is backwards compatible with older MC versions through BKCommonLib.

Changes:

• Switcher sign bug-out has been fixed
• Bugfixes related to keepChunksLoaded
• New ticket feature!

By popular demand, new train ticket system is now included in TrainCarts. Restrict access to trains by handing out train tickets, and automatically send trains to the right place based on the ticket used. I will make a proper tutorial video once I have the time, for now, this video will have to do for demonstration:



New commands:

• /train list destinations - see all destinations
• /train list tickets - see all tickets
• /train ticket create [name] - create a type of train ticket
• /train ticket edit [name] - edit an existing train ticket
• /train ticket clone [name] - clones the ticket currently being edited under a new name
• /train ticket rename [new_name] - rename the currently edited ticket
  
• /train ticket maxuses [num] - set the amount of times the ticket can be used before expiring
• /train ticket destination [name] - set a destination, applied to trains when entered with the ticket
• /train ticket tags [tags...] - set one or more tags added to the train when entered with the ticket
• /train ticket give [name] [players...] - give an instance of a ticket to a player
• /train ticket realm [realm] - set up a ticket realm (see below!)
  
• /train addticket [name] - adds a new ticket to a train. As soon as a single ticket is added, access is restricted unless the player possesses one of the tickets added.
• /train remticket [name] - removes a ticket
• /train setticket [name] - clears old tickets and sets a single new one

addticket/remticket/setticket also work on property signs.

Lacking commands right now, you can edit tickets.yml manually and set up an expire duration in milliseconds (real time) or mark tickets as player-bound, so only the player that was given the ticket can use the ticket. You can also let tickets define properties other than tags/destination that way.

Realms:
A complicated feature perhaps, so I'm giving it its own header. You can assign a realm to a ticket, which makes it easier to bundle multiple tickets together. Say, you have many tickets to apply to a train because you have dozens of destinations in your network. By setting a realm, and then assigning the realm name as a ticket name to the train, you simplify managing it.

For example, I have two tickets called 'TicketA' and 'TicketB'. For both tickets, I use /train ticket realm MyRealm. Then I assign it to the train using /train setticket MyRealm. Now players can use both TicketA and TicketB on the train. You can still put 'TicketA' as ticket for the train to only allow one.