Difference between revisions of "TrainCarts/ko"

From BergerHealer Wiki
Jump to navigation Jump to search
(Updating to match new version of source page)
(Updating to match new version of source page)
 
(6 intermediate revisions by the same user not shown)
Line 13: Line 13:
 
<div lang="en" dir="ltr" class="mw-content-ltr">
 
<div lang="en" dir="ltr" class="mw-content-ltr">
 
The first thing you will notice is that you can now connect carts together to form infinitely long trains. Every cart in this train is called a ''member'', all members combined are called a ''group''. Every member communicates with the group, so when the front cart hits a block, it stops the entire group. When someone pushes a cart, this pushing force is shared among all members. Therefore, long trains are less responsive than short trains.
 
The first thing you will notice is that you can now connect carts together to form infinitely long trains. Every cart in this train is called a ''member'', all members combined are called a ''group''. Every member communicates with the group, so when the front cart hits a block, it stops the entire group. When someone pushes a cart, this pushing force is shared among all members. Therefore, long trains are less responsive than short trains.
 +
</div>
 +
 +
<div lang="en" dir="ltr" class="mw-content-ltr">
 +
By default all minecarts placed by players become TrainCarts managed Minecarts. If you want to spawn Vanilla Minecarts that behave with original Minecraft Physics, you can do so through '''permissions''' or by spawning with a '''dispenser'''. [[TrainCarts/VanillaMinecarts|See this page for more information]].
 +
</div>
 +
 +
<div lang="en" dir="ltr" class="mw-content-ltr">
 +
Mobs no longer get into Traincarts Minecarts by default. If you want to change this, [[TrainCarts/MobEntering|see this page for more information]] or spawn vanilla minecarts instead.
 +
</div>
 +
 +
<div lang="en" dir="ltr" class="mw-content-ltr">
 +
== Spawning ==
 +
Trains can be spawned by players using Minecart items or the [[TrainCarts/Train Spawn Chest|Train Spawn chest]]. They can be spawned automatically using the [[TrainCarts/Signs/Spawner|spawn sign]].
 +
</div>
 +
 +
<div lang="en" dir="ltr" class="mw-content-ltr">
 +
[[Special:MyLanguage/TrainCarts/Spawning|» Spawning]]
 +
</div>
 +
 +
<div lang="en" dir="ltr" class="mw-content-ltr">
 +
[[Special:MyLanguage/TrainCarts/Train Spawn Chest|» Train Spawn Chest]]
 +
</div>
 +
 +
<div lang="en" dir="ltr" class="mw-content-ltr">
 +
== Properties ==
 +
Trains and individual carts of trains have properties. These can be set using commands (/train and /cart) or using the [[TrainCarts/Signs/Property|property sign]].
 +
</div>
 +
 +
<div lang="en" dir="ltr" class="mw-content-ltr">
 +
[[Special:MyLanguage/TrainCarts/Signs/Property|» Property Sign]]
 
</div>
 
</div>
  
Line 52: Line 82:
  
 
<div lang="en" dir="ltr" class="mw-content-ltr">
 
<div lang="en" dir="ltr" class="mw-content-ltr">
== Train Spawn Chest ==
+
== Command Selectors ==
 +
You can use command selectors like ''@train'' and ''@ptrain'' in all other commands (including non-traincarts commands) to perform actions on trains or player passengers of trains based on selector criteria. For tighter integration with other plugins like economies and status effects, this is the ideal mechanism.
 
</div>
 
</div>
  
 
<div lang="en" dir="ltr" class="mw-content-ltr">
 
<div lang="en" dir="ltr" class="mw-content-ltr">
A special item allows for trains to be picked up and spawned.
+
[[TrainCarts/Commands/SelectorsCommand Selectors]]
</div>
 
 
 
<div lang="en" dir="ltr" class="mw-content-ltr">
 
[[Special:MyLanguage/TrainCarts/Train_Spawn_ChestTrain Spawn Chest]]
 
 
</div>
 
</div>
  
Line 104: Line 131:
  
 
<div lang="en" dir="ltr" class="mw-content-ltr">
 
<div lang="en" dir="ltr" class="mw-content-ltr">
[[Special:MyLanguage/TrainCarts/Attachments|» Attachments]] (WIP)
+
The attachment editor is used to configure the appearance of your train. The interactive menu enables players to configure customized trains using item models, entities, seats, sounds and more. All of these can be animated to bring the train alive.
 +
</div>
 +
 
 +
<div lang="en" dir="ltr" class="mw-content-ltr">
 +
[[Special:MyLanguage/TrainCarts/Attachments|» Attachments]]
 
</div>
 
</div>
  
Line 148: Line 179:
 
<div lang="en" dir="ltr" class="mw-content-ltr">
 
<div lang="en" dir="ltr" class="mw-content-ltr">
 
*[https://www.spigotmc.org/resources/traincarts.39592/ Spigot Dev Page & Forum]
 
*[https://www.spigotmc.org/resources/traincarts.39592/ Spigot Dev Page & Forum]
*[https://discord.gg/q9gutsN Discord]
+
*[https://discord.gg/wvU2rFgSnw Discord]
 
</div>
 
</div>
  

Latest revision as of 16:09, 21 September 2024

Other languages:
Deutsch • ‎English • ‎Español • ‎Nederlands • ‎中文(中国大陆)‎ • ‎日本語 • ‎한국어
TrainCarts
TrainCarts train 1.gif
Minecarts redefined
Spigot: TrainCarts
GitHub: TrainCarts


« 뒤로 가기

TrainCarts는 Bergerkiller가 개발한 플러그인이고, 마인카트에 관련된 모든 것을 가지고 있는 플러그인이다. (이후 번역 필요) It was initially developed to link multiple carts together, creating a moving train. Over time the plugin grew to host many more features, such as action signs, commands, properties, attachments and a broad API other plugins can implement to add their own features.

The first thing you will notice is that you can now connect carts together to form infinitely long trains. Every cart in this train is called a member, all members combined are called a group. Every member communicates with the group, so when the front cart hits a block, it stops the entire group. When someone pushes a cart, this pushing force is shared among all members. Therefore, long trains are less responsive than short trains.

By default all minecarts placed by players become TrainCarts managed Minecarts. If you want to spawn Vanilla Minecarts that behave with original Minecraft Physics, you can do so through permissions or by spawning with a dispenser. See this page for more information.

Mobs no longer get into Traincarts Minecarts by default. If you want to change this, see this page for more information or spawn vanilla minecarts instead.

Spawning

Trains can be spawned by players using Minecart items or the Train Spawn chest. They can be spawned automatically using the spawn sign.

Properties

Trains and individual carts of trains have properties. These can be set using commands (/train and /cart) or using the property sign.

New physics

Trains can travel on top of pressure plates and alongside ladders, and also upside-down below vanilla rails placed on a ceiling.

Signs

Loads of different signs are available to automate stations, eject trains, put players in trains or update train configuration.

Command

The plugin has lots of commands you can use to alter the behavior of trains and minecarts.

Command Selectors

You can use command selectors like @train and @ptrain in all other commands (including non-traincarts commands) to perform actions on trains or player passengers of trains based on selector criteria. For tighter integration with other plugins like economies and status effects, this is the ideal mechanism.

Path finding

Trains can have a destination set, after which switcher signs will automatically switch the track to lead the train towards it with the shortest route possible. This can be used to automate a large train network, sending trains to different stations fully automatically. It is also possible to configure a list of destinations the train should visit and have the train automatically go from one destination to the next.

Tickets

Train ticket items can be used to restrict who can enter trains. They can also be used to assign properties to trains when used, such as assigning a destination to go to.

Configuration

TrainCarts can be configured in the config.yml file. All setting nodes have a header to help you understand what that particular node adjusts. Other than that, you can set the default train properties (properties applied to new trains) in the DefaultTrainProperties.yml file. The nodes should speak for themselves. Try not to touch the other files, as it can cause corrupted save data, or the plugin getting out of sync. Deleting the files should re-set TrainCarts completely, may one of the files get corrupted. The plugin automatically generates all configuration needed.

Attachments

The attachment editor is used to configure the appearance of your train. The interactive menu enables players to configure customized trains using item models, entities, seats, sounds and more. All of these can be animated to bring the train alive.

Permissions

Like in all plugins that use BKCommonLib as a base, all permissions can be found in PermissionDefaults.yml in the plugin folder. There they are all listed together with a description and permission default, which you can alter as well.

Performance

Some features by this plugin may result in server or client lag. There are ways to prevent them.

API and Add-ons

TrainCarts has a flexible API which allows other plugins to implement custom track, signs, attachments and more.

Useful Links

Traincarts Spigot Jenkins GitHub

BKCommonLib Spigot Jenkins GitHub

TC Coasters Spigot Jenkins GitHub

Depreciated Addons

(No longer supported in current versions of Traincarts)

ActionBlocks, added block-based systems to the game. They were dumbed-down versions of the sign systems mentioned above.