Difference between revisions of "TrainCarts/Tickets"
Jump to navigation
Jump to search
Bergerkiller (talk | contribs) |
Bergerkiller (talk | contribs) (Marked this version for translation) |
||
| Line 1: | Line 1: | ||
<languages/> | <languages/> | ||
<translate> | <translate> | ||
| + | <!--T:1--> | ||
[[Special:MyLanguage/TrainCarts|« Go back]] | [[Special:MyLanguage/TrainCarts|« Go back]] | ||
| − | == Introduction == | + | == Introduction == <!--T:2--> |
| + | <!--T:3--> | ||
[[Image:Traincarts_ticket_item.png|thumb|right|Ticket item held in a player's hand]] | [[Image:Traincarts_ticket_item.png|thumb|right|Ticket item held in a player's hand]] | ||
| + | <!--T:4--> | ||
Ticket items are Minecraft Map items used as traditional train tickets to gain access to trains as a passenger. | Ticket items are Minecraft Map items used as traditional train tickets to gain access to trains as a passenger. | ||
| − | == Usage == | + | == Usage == <!--T:5--> |
| − | === Creating, editing and renaming a ticket === | + | === Creating, editing and renaming a ticket === <!--T:6--> |
| − | ==== Notes ==== | + | ==== Notes ==== <!--T:7--> |
| + | <!--T:8--> | ||
* Leaving out a ticket name during creation will assign a random, free name | * Leaving out a ticket name during creation will assign a random, free name | ||
* Creating a new ticket automatically makes the player edit that ticket | * Creating a new ticket automatically makes the player edit that ticket | ||
| − | ==== Commands ==== | + | ==== Commands ==== <!--T:9--> |
</translate> | </translate> | ||
| Line 39: | Line 43: | ||
| − | === Assigning or unassigning a ticket to a train === | + | === Assigning or unassigning a ticket to a train === <!--T:10--> |
| − | ==== Commands ==== | + | ==== Commands ==== <!--T:11--> |
| + | <!--T:12--> | ||
No auto-completion here, will be improved in the future | No auto-completion here, will be improved in the future | ||
| Line 57: | Line 62: | ||
| − | ==== Property sign ==== | + | ==== Property sign ==== <!--T:13--> |
</translate> | </translate> | ||
{{sign|[+train]|property|addticket|myticket}} | {{sign|[+train]|property|addticket|myticket}} | ||
<translate> | <translate> | ||
| + | <!--T:14--> | ||
<br> | <br> | ||
</translate> | </translate> | ||
{{sign|[+train]|property|remticket|myticket}} | {{sign|[+train]|property|remticket|myticket}} | ||
<translate> | <translate> | ||
| + | <!--T:15--> | ||
<br> | <br> | ||
</translate> | </translate> | ||
| Line 72: | Line 79: | ||
| − | === Giving ticket items to players === | + | === Giving ticket items to players === <!--T:16--> |
| + | <!--T:17--> | ||
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. | 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> | </translate> | ||
| Line 80: | Line 88: | ||
| − | === Ticket item configuration === | + | === Ticket item configuration === <!--T:18--> |
| + | <!--T:19--> | ||
Tickets can be further configured to restrict the number of uses and more. | Tickets can be further configured to restrict the number of uses and more. | ||
| Line 97: | Line 106: | ||
| − | === Ticket background image === | + | === Ticket background image === <!--T:20--> |
| + | <!--T:21--> | ||
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. | 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> | </translate> | ||
| Line 105: | Line 115: | ||
| − | === Realms === | + | === Realms === <!--T:22--> |
| + | <!--T:23--> | ||
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. | 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. | ||
Latest revision as of 12:30, 3 September 2024
Introduction
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
| Command: | /train ticket create (name) |
|---|---|
| Permission: | train.ticket.manage |
| Command: | /train ticket edit [name] |
|---|---|
| Permission: | train.ticket.manage |
| Command: | /train ticket rename [new_name] |
|---|---|
| Permission: | train.ticket.manage |
| Command: | /train ticket remove |
|---|---|
| Permission: | train.ticket.manage |
Assigning or unassigning a ticket to a train
Commands
No auto-completion here, will be improved in the future
| Command: | /train addticket [name] |
|---|---|
| Permission: | train.property.tickets |
| Command: | /train remticket [name] |
|---|---|
| Permission: | train.property.tickets |
| Command: | /train clrticket |
|---|---|
| Permission: | train.property.tickets |
Property sign
[+train]
property
addticket
myticket
[+train]
property
remticket
myticket
[+train]
property
clrticket
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.
| Command: | /train ticket give [name] [player/@p] |
|---|---|
| Permission: | train.ticket.manage |
Ticket item configuration
Tickets can be further configured to restrict the number of uses and more.
| Command: | /train ticket maximumuses [amount/unlimited] |
|---|---|
| Permission: | train.ticket.manage |
| Command: | /train ticket destination [destination] |
|---|---|
| Permission: | train.ticket.manage |
| Command: | /train ticket tags [tags] |
|---|---|
| Permission: | train.ticket.manage |
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.
| Command: | /train ticket background [filename] |
|---|---|
| Permission: | train.ticket.manage |
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.
| Command: | /train ticket realm [realm] |
|---|---|
| Permission: | train.ticket.manage |