Minecraft插件百科 - 用户贡献 [zh-cn]

EssentialsX/发布页

2020-09-14T09:55:42Z

Minedx：

{{待翻译}}
=== 关于 EssentialsX ===
EssentialsX 是一个用于 Spigot 服务端的基础整合插件, 全方位覆盖服务端所需的超过 130 个指令与其他特性!

EssentialsX is a fork of the original Essentials 2 plugin for Bukkit servers, adding support for the latest Minecraft versions. EssentialsX also includes several performance enhancements and fixes on top of the original Essentials, as well as plenty of new useful features for servers.

You can view major differences and learn how to set EssentialsX up over at the EssentialsX [https://essentialsx.net/wiki/Improvements.html wiki].

=== Requirements ===
* EssentialsX is designed to use modern permissions plugins - we strongly recommend [https://luckperms.net/ LuckPerms]. You also need [https://www.spigotmc.org/resources/vault.34315/ Vault] for prefix/suffix support.
* EssentialsX currently supports '''CraftBukkit''', '''Spigot''' and [https://papermc.io/ Paper] '''(recommended)'''. Other server implementations may work, but we don't recommend them as they may cause compatibility issues.

=== Support ===
Looking for help with EssentialsX? You can join the MOSS Discord Server for support:

https://discord.gg/casfFyh

You can also report bugs on the GitHub issue tracker: https://github.com/EssentialsX/Essentials/issues/new/choose

'''Note: please use MOSS or GitHub for support, not Spigot private messages or the review section. You'll get a much faster answer on Discord or GitHub than on SpigotMC.'''

=== Donate ===
EssentialsX is provided completely free-of-charge. If you'd like to support the EssentialsX project, you can make a recurring donation on Patreon:

https://patreon.com/essentialsx

If you'd prefer to make a one-off donation, you can support us on Ko-fi:

https://ko-fi.com/essentialsx

If you're not able to donate, we'd really appreciate if you could take the time to write a review below, or give us a star on [https://github.com/EssentialsX/Essentials GitHub]. Every little helps!

=== Metrics collection ===
EssentialsX collects anonymous server statistics through bStats, an open-source Minecraft statistics service.

https://bstats.org/plugin/bukkit/EssentialsX

If you'd like to disable metrics collection via bStats, you can edit the '''plugins/bStats/config.yml''' file.

=== Contributing ===
EssentialsX is an open source project released under the '''GPLv3''' license, and we welcome code contributions on our [https://github.com/EssentialsX/Essentials GitHub]. Our translations are also crowd sourced, so if you'd like to help bring EssentialsX to your language, you can do so on [https://crowdin.com/project/essentialsx-official Crowdin].

EssentialsX/发布页

2020-09-14T09:54:13Z

Minedx：发布页完整搬运

{{待翻译}}
=== About EssentialsX ===
EssentialsX is the essential plugin suite for Spigot servers, including over 130 commands and many features for servers of all size and scale!

EssentialsX is a fork of the original Essentials 2 plugin for Bukkit servers, adding support for the latest Minecraft versions. EssentialsX also includes several performance enhancements and fixes on top of the original Essentials, as well as plenty of new useful features for servers.

You can view major differences and learn how to set EssentialsX up over at the EssentialsX [https://essentialsx.net/wiki/Improvements.html wiki].

=== Requirements ===
* EssentialsX is designed to use modern permissions plugins - we strongly recommend [https://luckperms.net/ LuckPerms]. You also need [https://www.spigotmc.org/resources/vault.34315/ Vault] for prefix/suffix support.
* EssentialsX currently supports '''CraftBukkit''', '''Spigot''' and [https://papermc.io/ Paper] '''(recommended)'''. Other server implementations may work, but we don't recommend them as they may cause compatibility issues.

=== Support ===
Looking for help with EssentialsX? You can join the MOSS Discord Server for support:

https://discord.gg/casfFyh

You can also report bugs on the GitHub issue tracker: https://github.com/EssentialsX/Essentials/issues/new/choose

'''Note: please use MOSS or GitHub for support, not Spigot private messages or the review section. You'll get a much faster answer on Discord or GitHub than on SpigotMC.'''

=== Donate ===
EssentialsX is provided completely free-of-charge. If you'd like to support the EssentialsX project, you can make a recurring donation on Patreon:

https://patreon.com/essentialsx

If you'd prefer to make a one-off donation, you can support us on Ko-fi:

https://ko-fi.com/essentialsx

If you're not able to donate, we'd really appreciate if you could take the time to write a review below, or give us a star on [https://github.com/EssentialsX/Essentials GitHub]. Every little helps!

=== Metrics collection ===
EssentialsX collects anonymous server statistics through bStats, an open-source Minecraft statistics service.

https://bstats.org/plugin/bukkit/EssentialsX

If you'd like to disable metrics collection via bStats, you can edit the '''plugins/bStats/config.yml''' file.

=== Contributing ===
EssentialsX is an open source project released under the '''GPLv3''' license, and we welcome code contributions on our [https://github.com/EssentialsX/Essentials GitHub]. Our translations are also crowd sourced, so if you'd like to help bring EssentialsX to your language, you can do so on [https://crowdin.com/project/essentialsx-official Crowdin].

EssentialsX/发布页

2020-09-14T09:49:09Z

Minedx：添加模板

{{待搬运}}
=== About EssentialsX ===
EssentialsX is the essential plugin suite for Spigot servers, including over 130 commands and many features for servers of all size and scale!

EssentialsX is a fork of the original Essentials 2 plugin for Bukkit servers, adding support for the latest Minecraft versions. EssentialsX also includes several performance enhancements and fixes on top of the original Essentials, as well as plenty of new useful features for servers.

You can view major differences and learn how to set EssentialsX up over at the EssentialsX [https://essentialsx.net/wiki/Improvements.html wiki].

=== Requirements ===
EssentialsX is designed to use modern permissions plugins - we strongly recommend [https://luckperms.net/ LuckPerms]. You also need [https://www.spigotmc.org/resources/vault.34315/ Vault] for prefix/suffix support.
EssentialsX currently supports '''CraftBukkit''', '''Spigot''' and [https://papermc.io/ Paper] '''(recommended)'''. Other server implementations may work, but we don't recommend them as they may cause compatibility issues.

=== Support ===
Looking for help with EssentialsX? You can join the MOSS Discord Server for support:
https://discord.gg/casfFyh

EssentialsX

2020-09-14T09:48:37Z

Minedx：

EssentialsX/发布页

2020-09-14T09:48:08Z

Minedx：创建页面，内容为“=== About EssentialsX === EssentialsX is the essential plugin suite for Spigot servers, including over 130 commands and many features for servers of all size and sca…”

=== About EssentialsX ===
EssentialsX is the essential plugin suite for Spigot servers, including over 130 commands and many features for servers of all size and scale!

EssentialsX is a fork of the original Essentials 2 plugin for Bukkit servers, adding support for the latest Minecraft versions. EssentialsX also includes several performance enhancements and fixes on top of the original Essentials, as well as plenty of new useful features for servers.

You can view major differences and learn how to set EssentialsX up over at the EssentialsX [https://essentialsx.net/wiki/Improvements.html wiki].

=== Requirements ===
EssentialsX is designed to use modern permissions plugins - we strongly recommend [https://luckperms.net/ LuckPerms]. You also need [https://www.spigotmc.org/resources/vault.34315/ Vault] for prefix/suffix support.
EssentialsX currently supports '''CraftBukkit''', '''Spigot''' and [https://papermc.io/ Paper] '''(recommended)'''. Other server implementations may work, but we don't recommend them as they may cause compatibility issues.

=== Support ===
Looking for help with EssentialsX? You can join the MOSS Discord Server for support:
https://discord.gg/casfFyh

EssentialsX

2020-09-14T09:47:57Z

Minedx：切换到子页面

EssentialsX

2020-09-14T09:46:43Z

Minedx：

{{Bukkit Plugin Infobox
|插件名=EssentialsX
|版本=2.18.1
|前置插件=Vault
|兼容服务端版本=1.8 - 1.16
|網址=https://www.spigotmc.org/resources/essentialsx.9089/
}}
{{待搬运}}
[[Category:管理]]
=== About EssentialsX ===
EssentialsX is the essential plugin suite for Spigot servers, including over 130 commands and many features for servers of all size and scale!

EssentialsX is a fork of the original Essentials 2 plugin for Bukkit servers, adding support for the latest Minecraft versions. EssentialsX also includes several performance enhancements and fixes on top of the original Essentials, as well as plenty of new useful features for servers.

You can view major differences and learn how to set EssentialsX up over at the EssentialsX [https://essentialsx.net/wiki/Improvements.html wiki].

=== Requirements ===
EssentialsX is designed to use modern permissions plugins - we strongly recommend [https://luckperms.net/ LuckPerms]. You also need [https://www.spigotmc.org/resources/vault.34315/ Vault] for prefix/suffix support.
EssentialsX currently supports '''CraftBukkit''', '''Spigot''' and [https://papermc.io/ Paper] '''(recommended)'''. Other server implementations may work, but we don't recommend them as they may cause compatibility issues.

=== Support ===
Looking for help with EssentialsX? You can join the MOSS Discord Server for support:
https://discord.gg/casfFyh

EssentialsX

2020-09-14T09:43:06Z

Minedx：

EssentialsX

2020-09-14T09:41:00Z

Minedx：创建页面，内容为“{{Bukkit Plugin Infobox |插件名=EssentialsX |版本=2.18.1 |前置插件=Vault |兼容服务端版本=1.8 - 1.16 |網址=https://www.spigotmc.org/resources/essent…”

Towny

2016-08-12T09:11:18Z

Minedx：

{{待翻译}}

== 介绍 ==
Towny Advanced is a versatile, player-controlled land management plugin for use with Bukkit/Tekkit/Spigot/Libigot. Towny offers solutions for pvp, griefing, chat, inflated economies and monsters to minecraft server admins. Towny allows players to work together and against each other as they see fit.

== 特性 ==

Towny includes a wide variety of features to offer instant enhancements to your traditional Minecraft server.

*Allows players to own and manage land based on a pre-set grid layout.
**Players join towns and purchase plots of land.
**Players decide who can build, destroy, use “switchs” and use items on every plot they control.
**Towns can join together into nations, further structuring a server into teams.
**Towns grant protection from monsters, pvp, fire, explosions and greifing.
*Wilderness Rules (Optional)
**Area between towns is wilderness, with its own build permissions.
**Limit players’ interaction with the wild to just harvest-able blocks, keeping the wild pristine.
**Roll-back tnt, creeper, wither explosions, dragon damage and endermen block-moving.
**Block explosions and fire.
*PVP Enhancements
**Server with a strong PVP aspect will find Towny’s grouping of players to be invaluable.
**Prevent friendly-fire. (Optional)
**Nations split players into larger teams.
**Nations can declare other nations to be allies or enemies, further splitting players into even larger teams.
**PVP can be turned on/off in wilderness, towns and worlds. (Optional)
*Teleporting/Warping and Spawning (Optional)
**Players can spawn to their town upon death.
**Players can spawn to their town or a town that is within their nation/allied with their nation.
**Use of beds can be limited to personally-owned land and players can spawn there.
*Customized modified chat. (Optional)
**Colours, group prefixes and suffixes, nation, town, towny titles.
**Channels for general, local, town, nation, moderator, admin and custom channels.
**Anti-spam feature.
*Shop plugin support. (Optional)
**Limit shops to special Shop Plots, enhancing realism.
*Economy plugin interaction. (Optional)
**Supports all economy plugins.
**Charge money for plots, towns, nations.
**Flexible tax system.
**Upkeep to remove money from the economy, stopping rampant inflation.
*All Permissions Plugins supported. (Optional)
**Perms 2/3, GroupManager, BukkitPermissions, bPermissions, PermissionsEx, etc.
*Multiworld Support
**Flexible settings for every world.
**Enable/disable Towny in as many worlds as you like.

== 重要信息 ==

=== Towny 安装指南 ===

:Here are instructions to install Towny for the first time. There are a few steps so follow them all carefully. 

:'''Step One – Preparing your server.''' 

:#Stop your server completely.
:#Download the following and copy to your Plugins folder (Place .jar files in the plugins folder, not the actual .zip):
:::*Download Towny Advanced.zip (Includes Towny, TownyChat and Questioner.)
:::**Towny.jar is required at all times,
:::**TownyChat.jar is required if you want to have Towny modify chatting in any way. (Adding prefixes and suffixes from your permissions plugin to chat, adding town/nation/world to chat, adding chat channels.)
:::**Questioner.jar is required if you want players to receive invites to towns, instead of being added automatically.
:::*If you use any economy plugin other than iConomy 5.01 you will be required to download Register.jar or Vault and put it in your plugins folder.
:::**If your economy plugin is supported by Vault, do not use Register.jar, instead use only Vault.
:#Start your server.
:#Stop your server.

=== Towny 升级向导 ===

:Here are instructions for performing a Towny Upgrade from a previous version:

:'''Towny Upgrade Instructions'''

:*Stop your server completely.
:*Backup your entire server!
:*Download Towny_Advanced.zip and extract the 4 .jar files into your plugins folder (Register is not required if your server already uses Vault.jar).
:*Start your server.
:*Stop your server.
:*Upgrade from pre-0.79.0.0
:**The chat section of config.yml has been move to a new file, channels.yml. Edit the new channels.yml to your liking.
:*Upgrade from pre-0.82.0.0
:::*Towny has had TownyPerms added. This new file located at townysettingstownyperms.yml will be generated when you first start your server using Towny 0.82.0.0 or higher.
:::*TownyPerms adds town/nation ranks so server admins can specify what each rank can do (nomads, residents, mayors, kings, etc) Admins can also create custom ranks with custom permission sets. Any existing players set as assistants will lose their rank and need to have it re-assigned.
:*Start your server.

=== Towny 的工作方式 ===

Use this page to learn how Towny works, how various settings affect the gameplay, what you can do to customize Towny to your liking.

----
==== <big>The Hierarchy</big> ====

===== Nomads =====

:Nomads are simply players who are not part of any town. They are landless and their permission nodes are configurable via TownyPerms.yml. Nomads can purchase Embassy plots if they have been given towny.command.plot.claim in the Townyperms.yml

===== Residents =====

:Every person who joins your server can become a resident (the are given the towny.town.resident permission node in townyperms.yml’s nomad section.) Residents have their own command /resident which used by itself outputs a Resident Screen, displaying Money, Town, Plots owned and Friends.

:Residents can join towns or choose to start a town of their own. Residents can also be put into one town automatically when they join the server for the first time by setting default_town_name: '' in config.yml.

:Residents who join towns can claim plots that the Mayor of the town has set for sale. When a resident owns 1 or more plots, they will see a new line on their Resident Screen, showing plots owned and a perm line showing the plot perms given on all plots that resident owns.

:Residents have their permission nodes configurable via TownyPerms.yml.

===== Towns =====

:A town is a collection of residents (or just one resident) with one resident as the mayor. A town also has a bank which the mayor can withdraw from. A mayor can also have assistants who have the same powers as him/herself. Towns can have taxes that will be taken at the end of each day interval.

:Towns usually grow outwards from their home block, the townblock the mayor stood in during town creation. Townblocks need to be claimed beside other townblocks, unless the mayor claims an outpost in the wilderness.

===== Mayors =====

:Mayors run towns and with the help of their assistants, manage a town and its residents. Mayors have their permission nodes configurable via TownyPerms.yml.

:Mayors can decide which ranks their residents fall into, in their town. This can be a Town Assistant or any other custom ranks created by the server admin in the townyperms.yml file. Mayors can see the available ranks using ‘/town ranklist’ command. Players are ranked using ‘/town rank {add|remove} {playername} {rankname}’. A player can have more than one rank assigned, allowing admins to create diverse town-roles such as bankers, builders, inviters for the mayor to choose for their trusted residents.

:It is not possible to run two towns unless you are also an admin. An admin can do the following to manage two or more towns:

Example: Admin Bob
Admin Bob wants to have a server-town, and his own town. Bob would start by creating his Server Town and setting up taxes, plotprices, permissions. This sort of town should not give residents, allies or outsiders permissions in the
Server Town.
When Bob finished making his town the way he wants he uses /townyadmin set mayor {townname} npc to place a fake 'npc' resident as mayor of the Server Town.
Then Bob leaves Server Town and creates his own town. Using the /townyadmin set mayor {townname} npc command Bob can flip back and forth between towns.
Bob doesn't have to leave his town to add players to the Server Town though! He can use /townyadmin town {townname} add {playername} to add players to the Server Town or set default_town_name: 'Server_Town' in config.yml.
Bob can also add the NPC town into a nation using /ta nation {nation} add {town}.

===== Nations =====

:A nation is a collection of towns (or just one town) with one town as the capital. The mayor of that capital is the king. A nation can join the war event, as well as ally other nations. A nation also has it’s own bank. It can also tax the towns that belong to it.

:Two nations can decide to join in an alliance, which allows them to be protected from friendly fire, help on each others plots (if the plot’s perm line allows allies,) and to help each other in war.

:As of 0.91.0.0, you may restrict nation alliances to be 2-way only. So that Nation A cannot consider Nation B an ally unless the Nation B also considers Nation A an ally. You may turn this setting on in the config: war.disallow_one_way_alliance, which defaults to false.

:Also, as of 0.91.0.0, you may restrict who can create, join and maintain a nation by requiring a minimum number of residents. See the Global Town Settings section of the config.yml.

===== Kings =====

:Kings lead Nations and are the mayor of the capital city. Kings have their permission nodes configurable via TownyPerms.yml.

:Kings can decide which ranks their residents fall into, in their nation. This can be a Nation Assistant or any other custom ranks created by the server admin in the townyperms.yml file. Kings can see the available ranks using ‘/nation ranklist’ command. Players are ranked using ‘/nation rank {add|remove} {playername} {rankname}’. A player can have more than one rank assigned, allowing admins to create diverse nation-roles such as bankers, inviters for the king to choose for their trusted residents.

:Kings have the ability to set titles (prefixes) and surnames (postfixes) to the residents of the towns they have in their nation. This is done with:

:*/nation set title {name} titlegoeshere
:*/nation set surname {name} surnamegoeshere
:Typing the commands with nothing after the player’s name resets the title or surname to blank.

===== Configuring Townyperms.yml and the Roles of the Ranks Within =====

:New to Towny 0.82.0.0 and onwards towny has a new configuration file, TownyPerms.yml, located in the towny\settings\ folder.

:This system pushes permissions directly to Bukkit and works along side all other perms plugins. It allows you to define sets of permissions based upon a players status (nomad/resident/mayor/king). You can also assign additional permissions based upon any assigned town/nation ranks (assistant/vip etc). This system is not limited to Towny permission nodes. You can assign any permissions for any plugins in it’s groups.

:This file allows admins to decide what each player-rank can do. Some ranks are assigned automatically:

::*Players without towns are Nomads.
::*Players in towns are Residents.
::*Owners of towns are Mayors.
::*Owners of nations are Kings.

:Some ranks are assigned by Mayors or Kings, and supplement the ranks the players already have:

::*Mayors can make a resident a Town Assistant.
::*Kings can make a resident a Nation Assistant.
::*Mayors and kings can grant admin-created ranks, allowing for diverse customization.
:::*A player can attain many Supplemental ranks from their mayor or king, allowing for diverse nation/town-roles.
:::*Examples of this would be town-builders, town-bankers, nation-bankers, town-inviters, etc.

:A resident of a town can see the ranks within their town using ‘/town ranklist’. A mayor can use ‘/town rank {add|remove} {playername} {rankname}’ to give a player a new rank within their town. A king can use ‘/nation rank {add|remove} {playername} {rankname}’ to give a player a new rank within their nation.

===== Configuring Mayor and King Titles, Town and Nation Names =====

:Towny gives you the ability to customize the naming scheme applied to Mayors, Kings, Towns, Capital Cities and Nations.

:This is done with two sections in the config.yml

::*town_level:
::**The basic layout of the townLevel lines are as follows:

- upkeepModifier: 1.0
namePostfix: ' (Settlement)'
mayorPrefix: 'Hermit '
mayorPostfix: ''
townBlockLimit: 16
namePrefix: ''
numresidents: 1
- upkeepModifier: 1.0
namePostfix: ' (Hamlet)'
mayorPrefix: 'Chief '
mayorPostfix: ''
townBlockLimit: 32
namePrefix: ''
numResidents: 2

:*These are read as follows:
:*upkeepModifier: 1.0 – Use a higher multiplier to increase the upkeep as towns get more residents (unless you use town_plotbased_upkeep:true in which case it is based off of plot-count rather than resident-count.)
:*namePostfix: ‘ (Settlement)’ – This is added to the end of the town name.
:*mayorPrefix: ‘Hermit ‘ – This is added to the front of the mayor’s name.
:*mayorPostfix: ” – This is added to the end of the mayor’s name.
:*townBlockLimit: 16 – This decides how many townblocks a town gets, it is only used if town_block_ratio: ‘0’ is set in the config.yml.
:*namePrefix: ” – This is added to the front of the town name.
:*numresidents: 1 – This is how many residents a town needs to have in order to attain the prefixes/postfixes of the townlevel.
:*The two levels above are for towns of 1 and 2 residents. When a town is created the mayor’s new town has (Settlement) added to the end of his townname and he is given the prefix of Hermit. When the mayor gets a second resident his town becomes Townname (Hamlet) and he receives the prefix of Chief.
:*nation_level:
:**The basic layout of the nationLevel lines are as follows:

- capitalPostfix: ''
upkeepModifier: 1.0
namePostfix: ' (Nation)'
kingPrefix: 'Count '
townBlockLimitBonus: 10
namePrefix: 'Federation of '
numResidents: 10
capitalPrefix: ''
kingPostfix: ''
nationTownUpkeepModifier: 1.0
- capitalPostfix: ''
upkeepModifier: 1.0
namePostfix: ' (Nation)'
kingPrefix: 'Duke '
townBlockLimitBonus: 20
namePrefix: 'Dominion of '
numResidents: 20
capitalPrefix: ''
kingPostfix: ''
nationTownUpkeepModifier: 1.0

:*These are read as follows:
:*capitolPostfix: ” – This is added to the end of the capital city of the nation.
:*upkeepModifier: 1.0 – Use a higher multiplier to increase the upkeep as nations get more residents (unless you use town_plotbased_upkeep:true in which case it is based off of plot-count rather than resident-count.)
:*namePostfix: ‘ (Nation)’ – This is added to the end of the nation name.
:*kingPrefix: ‘Count ‘ – This is added to the front of the nation-leader.
:*townBlockLimitBonus: 10 – This is the number of bonus townblocks given to a town when they join a nation.
:*namePrefix: ‘Federation of ‘ – This is added to the front of the nation name.
:*numResidents: 10 – This is how many residents a nation must have to receive the prefixes and postfixes of the nation level.
:*capitalPrefix: ” – This is added to the front of the capital city of the nation.
:*kingPostfix: ” – This is added to the end of the nation-leader’s name.
:*nationTownUpkeepModifier: 1.0 – Joining a nation will lower/raise how much town upkeep your town pays. This multiplier is calculated after all other multipliers have their effect on the town upkeep cost. When set at 1.0, there is no :*change to upkeep.

----
==== <big>How Towns Grow</big> ====

===== Starting a Town =====

:Mayors start towns using the command /town new {townname}. The townblock they are standing in will be the home block for the town, the exact spot/position will be the spawn point for the town. 

:More townblocks can be claimed using /town claim. These townblocks need to be directly adjacent to already claimed townblocks.

===== Joining Towns =====

:There are two ways to join towns, the first is by being invited by a Mayor or a Town assistant. The second it by joining an open town.

:Mayors and assistants can add players to their town with the command /town add {playername}. If the server has Questioner.jar and using_questioner: true in the Towny config.yml then the player will receive a prompt to either /accept or /deny the invitation.

:Mayors can set their towns to open using /town toggle open. A player who isn’t in a town already can use the command /town join {townname} to join open towns.

:When residents join towns they increase the number of townblocks accessible to the mayor for claiming.

----
==== <big>Plot System of Land Ownership</big> ====

===== Town Blocks =====

:Towny provides a server admin a hands-off approach to block-protection. Block protection is broken down into plots of land, called townblocks, which by default are 16x16x128 (the full height of the world.)
:Townblocks are claimed by town mayors who can then sell/give individual plots to their town’s residents.

====== Town Block Size ======

:You change the townblock size in config.yml at ''town_block_size: 16.'' '''Changing this value is suggested only when you first install Towny.'''a
:Doing so after entering data will shift things unwantedly. Using smaller value will allow higher precision,at the cost of more work setting up. Also, extremely small values will render the caching done useless.
:Each cell is (town_block_size x town_block_size x 128) in size, with 128 being from bedrock to clouds.

====== Setting How Many Towny Blocks A Town Receives ======

:You can change how many town blocks a town gets to claim. This is done in two places.
:Towny checks first in the config.yml at ''town_block_ratio: 8'' and by default gives a town 8 townblocks per resident.
:You can override this by setting ''town_block_ratio: 0'' and using the townLevel section of the config.yml
:More information on the townLevel line and how to configure it is here.

====== Buying Townblocks ======

:Mayors can buy townblocks using /town buy bonus {amount}. An admin can set a maximum limit on how many townblocks a town can buy in the config.yml at max_purchased_blocks: '0'. The price of a bought townblock is also set in the config.yml at price_purchased_bonus_townblock: '25.0'.
:Using this feature, mayors can grow their town without needing new residents.

===== Plot Types =====

:Towny post-0.75 has added plot types besides the default. This is to give mayors more control over their towns.

:As of now there are:

====== Default Plots ======

:These plots do not need any specific command to be designated.
:They are put up for sale with /plot forsale {$$}.
:A plot which is not of default type can be reset to a default plot with /plot set reset.

====== Shop Plots ======

:Shop plots are designated with /plot set shop
:A mayor can use /town set shopprice {$$} to set how much shop plots are sold at by default. This can be overriden when a mayor puts the actual plot up for sale with /plot forsale {$$}.
:A mayor can also charge an additional shoptax with /town set shoptax {$$}. This tax is charged in addition to the normal plottax.

====== Arena Plots ======

:Arena plots are designated with /plot set arena.
:PVP is on all the time in arena plots as well as friendly-fire damage. Town health regen is also disabled in arena plots.

====== Embassy Plots ======

:Embassy plots are designated with /plot set embassy
:A mayor can use /town set embassyprice {$$} to set how much embassy plots are sold at by default. This can be overriden when a mayor puts the actual plot up for sale with /plot forsale {$$}.
:A mayor can also charge an additional embassytax with /town set embassytax {$$}. This tax is charged in addition to the normal plottax.
:An embassy plot can be bought by any player, whether they are in a town or not. The townblock remains owned by the host-town and a mayor from the host-town can take the plot from the owner at any time.
:Embassy plots can also be changed into shop plots, allowing for larger shop towns, where many different towns’ players can set up shops.
:When a player leaves a town they do not lose ownership of their plots if those plots are set to be Embassy plots.

====== Wilds Plots ======

:Wilds plots are designated with /plot set wilds
:A wilds plot allows residents to destroy the blocks found on the wild ignore ID list. This includes ores, trees, flowers, mushrooms and other harvestable blocks by default. It does not include stone, dirt, grass and other terrain blocks.
:It is useful for creating tree farms, and protecting the terrain around a town, while still allowing residents to cut trees and explore caves.
:Setting up wilds plots can be slightly complex, here are instructions.

# Navigate to your towny\data\worlds\WORLDNAME.txt file
# Set:
#* unclaimedZoneBuild=false
#* unclaimedZoneDestroy=false
#Configure the unclaimedZoneIgnoreIds line to include the blocks you would like players to break/build.
#Go to the Wilds plots you can set using /plot set wilds
#Use ‘/plot set perm resident build on’ and ‘/plot set perm resident destroy on’ to enable residents to break/build using only the blocks in the ignoreIDs list.

====== Inn Plots ======

:Inn plots are designated with /plot set inn
:An Inn plot allows anyone to use a bed to set their ‘/res spawn’ and spawn on death. The Inn plot will still deny a player who is in a nation declared as an enemy by your nation.
:For them to function deny_bed_use: ‘true’ must be set in the config.yml

====== Jail Plots ======

:Jail plots are designated with /plot set jail

:* Players can become jailed if
::*The player’s mayor/sheriffs send them to jail.
::*An attacker who attacks a town which considers him an Enemy (Nation-relationship) dies in that Town. He is sent to the first available Jail plot of the defending town.

:*Jailed players become unjailed if:
::*they leave their town and become a nomad,
::*the mayor/sheriff unjails them,
::*the player pays a bail amount to the town which jailed them, (using: /resident jail paybail)
::*they manage to escape the jail plot and the town and get into Wilderness.

:*Jailed players cannot teleport.
:*Jailed players cannot use Ender Pearls unless enabled in the config.
:*Jailed players who die are sent back to their prescribed jail plot.
:*Jailed players do not give monetary payouts when they are killed.
:*Jailed players show their jailed status in the /res [playername] screen, along with the town they are jailed in.
:*It is suggested you make a new town rank in the townyperms.yml called Sheriff, and give that rank the towny.command.town.toggle.jail node. Newly generated townyperms.yml files will contain this rank by default.

====== Farm Plots ======

:Farm plots are designated with /plot set farm

:A Farm plot players to only build/destroy blocks designated in the Towny Config.yml at global_town_settings.farm_plot_allow_blocks. By default this list includes “LONG_GRASS, DOUBLE_PLANT, YELLOW_FLOWER, RED_ROSE, PUMPKIN_STEM, MELON_STEM, BEETROOT_BLOCK, CARROT, POTATO, CROPS, MELON_BLOCK, PUMPKIN”.

::Who can build/destroy these blocks is still determined by the plot’s perm line seen in the /plot perm screen. This means that if B=rao, anyone can plant/place the allowed blocks in the plot. If the B=r– then only town residents can plant/place the allowed blocks.

:If admins want, they can add SOIL to the allowed blocks list, which will allow anyone allowed via the perm line to also make soil with a hoe. By default SOIL is not included and only admins/mayors/assistants will be able to create soil with a hoe. Towny already protects soil from being stomped into grass, so soil will only return to dirt if it is not irrigated.

:Farm plots also allow town residents to kill animals in the plot. The list of animals is set in the config at global_town_settings.farm_animals. By default this list includes “PIG,COW,CHICKEN,SHEEP,MOOSHROOM”.

===== Outposts =====

:Normally townblocks are claimed around the home block, always connected to the town. To claim a townblock out in the wilderness, a mayor or assistant must claim an outpost.

:In order for players to claim outposts, the config must be set to ''allow_outposts:'' true and players require towny.town.claim.outpost in their permission node group.

:An admin can configure how many outposts a player can claim, this is set in your permissions plugin’s info/option/meta node section using the towny_maxoutposts: {number} info node. [http://towny.palmergames.com/towny/towny-permission-nodes/ See here.]

:Outposts cannot be claimed too close to other home blocks, just like when a mayor starts a town they cannot be too close. The exact number is set in the [http://towny.palmergames.com/towny/towny-config-yml/ config.yml] at ''min_distance_from_town_homeblock: 5''. In the default setting an outpost cannot be claimed within 5 townblocks of any other homeblock.

:Outposts have two settings in [http://towny.palmergames.com/towny/towny-config-yml/ config.yml]

:*By setting ''allow_outposts: false'' you can disable outposts completely.
:*You can also set the cost of claiming an outpost with ''price_outpost: 500.0''

:Outposts can be teleported to, mayors set the spawn point of the outpost when they claim it or using ‘/town set outpost’. Players teleport to the outpost using ‘/town outpost x’ (with x being a number 1 – however many outposts the town has.)

===== Selling Land =====

Land is sold by Mayors to Residents that are a part of their town. using_iconomy: true must be set in [http://towny.palmergames.com/towny/towny-config-yml/ config.yml] in order for costs to be applied. Mayors have a command used in game to set the cost of all the plots that are set for sale hence-forth.

*''/town set plotprice {$}''
:*This sets the cost of newly-set-for-sale plots, already set-for-sale plots keep their costs. If it is not set, the plots will cost $0 by default.

:To put a plot up for sale a mayor, while standing in the plot, type /plot forsale {optional cost} The resident would then type /plot claim while standing in the plot to buy it.

===== Using the Maps =====

:The map in towny displays the grid system of plots. The map can be viewed once using /towny map one time or you can set the map to show every time you move from one block to another:

*Use ''/resident set mode map'' to turn it on.
*And use ''/resident set mode reset'' to turn it off.

:A large version of the map can be seen using /towny map big.

===== Plot Regeneration & Unclaimed Plots =====

There are 4 options for affecting townblocks/plots.

====== Reverting unclaimed townblocks to their original state on unclaim ======

:When a town plot is unclaimed (by a player or through upkeep) it will slowly begin to revert to a pre town state. Blocks will slowly change back to whatever blocks we’re present at the moment the town block was claimed. A townblock must revert completely before the snapshot of the townblock is removed. If townblock is reclaimed mid-revert, a new snapshot is not taken and if the townblock is unclaimed again it will revert to the original snapshot.

*Disabling this feature is done in the towny\data\worlds\worldname.txt @ 'usingPlotManagementRevert=false'
*or by using ‘/tw toggle revertunclaim’ while standing in the world you want to toggle it in.
*Disabling this feature for new worlds is done in the config at new_world_settings.plot_management.revert_on_unclaim.enabled

:You can configure certain block types you don’t want restored to prevent players exploiting regen for diamond ores.

*Block types to not restore are configured in block_ignore in the worlds txt file data/worlds/worldname.txt
*Defaults for new worlds are set in the config at new_world_settings.plot_management.revert_on_unclaim.block_ignore:

====== Deleting pre-defined blockIDs on unclaim ======

:When a town plot is unclaimed (by a player or through upkeep) block IDs matching a list will be deleted within that townblock. This can be useful for deleting all signs within a townblock, ensuring any chests locked with Lockette or Deadbolt signs are unlocked.

*Disabling this feature is done in the towny\data\worlds\worldname.txt @ ''usingPlotManagementdelete=false''
*Disabling this feature for new worlds is done in the config at new_world_settings.plot_management.block_delete.enabled

:You can configure the list of blockIDs to be removed on a per-world basis.

*The blockIDs listed in the towny\data\worlds\worldname.txt @ 'plotManagementDeleteIds=' will be removed from the townblock.
*Defaults for new worlds are set in the config at new_world_settings.plot_management.block_delete.unclaim_delete

====== Plot-Owners’ and Mayors’ /plot clear command ======

:A feature available only to Town Mayors on public town land: /plot clear. This command is meant to be used after a plot was personally owned by a resident, who either moved to another plot or left town. By default this list includes only signs, useful for mayors to remove sign-protection on doors, chests, furnaces, dispensers and trapdoors given via Lockette or Deadbolt.

*Disabling this feature is done in the in the towny\data\worlds\worldname.txt @ ''usingPlotManagementMayorDelete=false''
*Disabling this feature for new worlds is done in the config at new_world_settings.plot_management.mayor_plotblock_delete.enabled

:You configure the list of blockIDs to be removed when this command is used.

*The list of blockIDs is listed in the towny\data\worlds\worldname.txt @ ''plotManagementMayorDelete=WALL_SIGN,SIGN_POST''
*Defaults for new worlds are set in the config.yml at new_world_settings.plot_management.mayor_plotblock_delete.mayor_plot_delete

As of Towny 0.79.1.0, players can use this command within plots they personally own.

====== Wilderness Regeneration ======

:A simple wild_revert_on_mob_explosion option. Will regenerate explosions on a timer.
As of Towny 0.79.1.0 You can now add any entities here you want explosions to revent for in the wilderness (includes Creeper,EnderCrystal,EnderDragon,Fireball,SmallFireball,TNTPrimed).
These settings are copied to the individual world files, so you must make changes per world.

*Disabling this feature is done in the in the towny\data\worlds\worldname.txt @ ''usingPlotManagementWildRegen=true''
*or by using ‘/tw toggle revertexpl’ while standing in the world you want to toggle it in.
*Disabling this feature for new worlds is done in the config at new_world_settings.plot_management.wild_revert_on_mob_explosion.enabled

:You can configure how quickly the blocks will regenerate, specifically how much time in between each block being reverted.

*The timer is changed in the towny\data\worlds\worldname.txt @ ''usingPlotManagementWildRegenDelay=5''
*The default for new worlds is set in the config.yml at new_world_settings.plot_management.wild_revert_on_mob_explosion.delay

----
==== <big> How Towny Lets Players Protect Their Blocks </big> ====

:Towny’s genius is the way it lets players protect themselves. An admin doesn’t need to go around protecting land for players, and players can’t run rampant claiming massive amounts of land without working for it and building their towns.

:The first concept you need to digest are the 4 perm-types and 3 groups.

===== Towny Plot Perms =====

:There are 4 permission-type values, which can be set for personal plots and for town plots as well (town permissions can be set by the mayor and affect plots who are not owned by any player.) The basic command for this is either ''/resident set perm'' or ''/town set perm'' followed by the proper flags for each permission.

:Available in Towny 0.77.0.0 and onward are per-plot permissions. Plots start with the default settings for plot perms (be it a resident-owned or town-owned plot,) but the owner of the plots can set different perms to different plots. To view a plots perm type ''/plot perm'' and to set a plots’ perms use ''/plot set perm''.

:Default permissions are viewable by typing either ''/resident'' for personal plot perms or by typing ''/town'' for town permissions.

Towny

2016-08-09T07:25:31Z

Minedx：搬运自 http://palmergames.com/towny/

Towny

2016-08-09T06:42:20Z

Minedx：

Towny

2016-08-09T06:40:37Z

Minedx：创建页面，内容为“== 介绍 == Towny Advanced is a versatile, player-controlled land management plugin for use with Bukkit/Tekkit/Spigot/Libigot. Towny offers solutions for pvp, grief...”

== 介绍 ==
Towny Advanced is a versatile, player-controlled land management plugin for use with Bukkit/Tekkit/Spigot/Libigot. Towny offers solutions for pvp, griefing, chat, inflated economies and monsters to minecraft server admins. Towny allows players to work together and against each other as they see fit.

== 特性 ==

Towny includes a wide variety of features to offer instant enhancements to your traditional Minecraft server.

*Allows players to own and manage land based on a pre-set grid layout.
**Players join towns and purchase plots of land.
**Players decide who can build, destroy, use “switchs” and use items on every plot they control.
**Towns can join together into nations, further structuring a server into teams.
**Towns grant protection from monsters, pvp, fire, explosions and greifing.
*Wilderness Rules (Optional)
**Area between towns is wilderness, with its own build permissions.
**Limit players’ interaction with the wild to just harvest-able blocks, keeping the wild pristine.
**Roll-back tnt, creeper, wither explosions, dragon damage and endermen block-moving.
**Block explosions and fire.
*PVP Enhancements
**Server with a strong PVP aspect will find Towny’s grouping of players to be invaluable.
**Prevent friendly-fire. (Optional)
**Nations split players into larger teams.
**Nations can declare other nations to be allies or enemies, further splitting players into even larger teams.
**PVP can be turned on/off in wilderness, towns and worlds. (Optional)
*Teleporting/Warping and Spawning (Optional)
**Players can spawn to their town upon death.
**Players can spawn to their town or a town that is within their nation/allied with their nation.
**Use of beds can be limited to personally-owned land and players can spawn there.
*Customized modified chat. (Optional)
**Colours, group prefixes and suffixes, nation, town, towny titles.
**Channels for general, local, town, nation, moderator, admin and custom channels.
**Anti-spam feature.
*Shop plugin support. (Optional)
**Limit shops to special Shop Plots, enhancing realism.
*Economy plugin interaction. (Optional)
**Supports all economy plugins.
**Charge money for plots, towns, nations.
**Flexible tax system.
**Upkeep to remove money from the economy, stopping rampant inflation.
*All Permissions Plugins supported. (Optional)
**Perms 2/3, GroupManager, BukkitPermissions, bPermissions, PermissionsEx, etc.
*Multiworld Support
**Flexible settings for every world.
**Enable/disable Towny in as many worlds as you like.

== 重要信息 ==

=== Towny 安装指南 ===

Here are instructions to install Towny for the first time. There are a few steps so follow them all carefully. 

'''Step One – Preparing your server.''' 

#Stop your server completely.
#Download the following and copy to your Plugins folder (Place .jar files in the plugins folder, not the actual .zip):
::*Download Towny Advanced.zip (Includes Towny, TownyChat and Questioner.)
::**Towny.jar is required at all times,
::**TownyChat.jar is required if you want to have Towny modify chatting in any way. (Adding prefixes and suffixes from your permissions plugin to chat, adding town/nation/world to chat, adding chat channels.)
::**Questioner.jar is required if you want players to receive invites to towns, instead of being added automatically.
::*If you use any economy plugin other than iConomy 5.01 you will be required to download Register.jar or Vault and put it in your plugins folder.
::**If your economy plugin is supported by Vault, do not use Register.jar, instead use only Vault.
#Start your server.
#Stop your server.

=== Towny 升级向导 ===

Here are instructions for performing a Towny Upgrade from a previous version:

'''Towny Upgrade Instructions'''

Stop your server completely.
Backup your entire server!
Download Towny_Advanced.zip and extract the 4 .jar files into your plugins folder (Register is not required if your server already uses Vault.jar).
Start your server.
Stop your server.
Upgrade from pre-0.79.0.0
The chat section of config.yml has been move to a new file, channels.yml. Edit the new channels.yml to your liking.
Upgrade from pre-0.82.0.0
Towny has had TownyPerms added. This new file located at townysettingstownyperms.yml will be generated when you first start your server using Towny 0.82.0.0 or higher.
TownyPerms adds town/nation ranks so server admins can specify what each rank can do (nomads, residents, mayors, kings, etc) Admins can also create custom ranks with custom permission sets. Any existing players set as assistants will lose their rank and need to have it re-assigned.
Start your server.

Bukkit/插件开发教程

2015-08-27T10:57:11Z

Minedx：/* Bukkit Java文档 */ 更正API位置

{{模板:待翻译}}
本页面英文原文内容来源 [http://wiki.bukkit.org/Plugin_Tutorial]
== 介绍 ==

这篇内容丰富的教程旨在帮助你学会如何开发Bukkit插件.这一篇教程不可能完全涉及到Bukkit中所有的可能性,而是最基本的一般概述. 前提是你懂得Java这门语言,并在IDE中设置好你的工作区,此教程介绍了大多数Bukkit插件所必需的语法结构.

== 学习Java ==

'''理解这些教程需要具备Java这门编程语言的基本知识.'''如果你刚开始学习Java或者需要重温一下相关知识，下面有一个并不完整的网站列表可供参考.

<big>[http://docs.oracle.com/javase/tutorial/ Oracle's Java Tutorials]</big> - 官方教程
*[http://www.java2s.com/Tutorial/Java/CatalogJava.htm Java2s.com] - 教程
*[http://www.javacoffeebreak.com/java101/java101.html Java 101] - 教程
*[http://math.hws.edu/javanotes/ JavaNotes] - 免费的在线教科书
*[http://thenewboston.org/list.php?cat=31 TheNewBoston] - 视频教程.

== 开发环境 ==

在编写一个插件前 (或学习Java前) 你需要配置一个开发者环境，这个包括但不限于安装IDE (Integrated Development Environment，集成开发环境)。接下来的教程中有关于Eclipse上IDE的操作指南。

:: ''更多信息，请参见 [[Bukkit/插件开发教程-建立工作区|建立工作区]]''

你'''必须'''下载'''Java'''开发者使用的Eclipse构建版本, '''不是''' '''Java EE'''开发者的版本。 Java EE 开发者的版本不包含此教程需要的Maven支持。

== 新建插件开发项目 ==
=== 创建一个新的项目 ===

在开始工作之前，你需要先在Eclipse中配置好工作区和文件. 打开Eclipse,然后依次点击''File -> New -> Project:''来创建一个新的项目.

[[Image:Newproject.png]]

现在,打开''Maven''文件夹, 然后选择''Maven Project''.点击next,之后在下一个菜单中选择''Create a simple project'', 再次点击''Next'':
如果你看不到''Maven''文件夹, 那么你需要[http://eclipse.org/m2e/download/ 下载m2eclipse]

[[Image:Newproject2.png]]

现在，你需要给你的组用户命名，就像下面这样:
* 如果你拥有一个域名，package则填写逆转的域名地址.
** 例如: i-am-a-bukkit-developer.com 你的package地址即是com.i_am_a_bukkit_developer [http://docs.oracle.com/javase/tutorial/java/package/namingpkgs.html source]
** 避免使用一个不属于你自己的域名.
* 没有域名? 这里有几种方法可供选择。
*# 在资源管理站点创建一个用户，比如GitHub或是sourceforge
*#* 对于使用GitHub的用户, 请参照[http://pages.github.com/ 这里的说明] 之后你将获得一个子域名,所以你的package地址是io.github.<username> 
*# 使用你的邮箱. 例如: <username>@gmail.com格式的邮箱应输入com.gmail.<username> 
*# 最不济的方法.：使用独特的组名命名方式，这应当是你最后的解决方法。

以下几个地址不能作为package中的地址前缀:
* org.bukkit
* net.bukkit
* com.bukkit
* net.minecraft

完成基础的组名以后，你需要在最后加上插件的名称. 在这里用 GitHub页面作为讲解的实例. 如果你创建了一个名为 ''TestPlugin''的插件，那么完整的组名是''io.github.<username>'', 你的工程名也是 ''TestPlugin''. 至于版本，默认即可，稍后可以修改。
完成向导:

[[Image:Newproject3.png]]

如果这是你首次使用Eclipse, 点击右上角的"X" 来关闭Welcome提示页面. 现在，你的窗口视图看起来就像下面的图片这样:

[[Image:Eclipsemain.png]]

点击工程名称右边的箭头来进行下一步，现在我们正式开始。
=== 添加Bukkit API ===

在开发插件之前，你需要添加 Bukkit API库文件到你的项目，作为一个dependency, 你也可以添加其他你想实用的API.

找到项目文件夹中部的''pom.xml''并双击进行编辑. 点击''pom.xml''中部的 tab,你将会看到下图所示内容:

[[Image:Pomeditor.png]]

如果你想使用Java 6以上版本的语言特性,你需要指定搭建项目的Java版本.复制并粘贴以下内容(设定项目只能使用Java 7及以下的版本)到 ''</project>''之前:

<code>
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-compiler-plugin</artifactId>
<configuration>
<nowiki><</nowiki>source>1.7</source>
<target>1.7</target>
</configuration>
</plugin>
</plugins>
</build>
</code>

你或许想使用其他版本,例如 <code>1.8</code> 使用Java 8. 请注意 [http://mcstats.org/global/ 根据MCStats数据统计], 大多数服主选择了Java 7, 所以使用Java 8会使许多服务器无法运行你的插件. 如果你使用Java 1.7的特性, Eclipse将会在报错代码"error"中建议你更改语言版本.同意即可.

在位于代码中段的''</project>''之前粘贴以下内容(这段代码告诉Eclipse关于Bukkit's repository的地址):

<code>
<repositories>
<repository>
<id>bukkit-repo</id>
<url>http://repo.bukkit.org/content/groups/public/</url>
</repository>
</repositories>
</code>

然后继续在 ''</project>''前粘贴以下内容 (这段代码告诉Eclipse搭建插件的Bukkit版本):

<code>
<dependencies>
<dependency>
<groupId>org.bukkit</groupId>
<artifactId>bukkit</artifactId>
<version>1.7.2-R0.3</version>
<type>jar</type>
<scope>provided</scope>
</dependency>
</dependencies>
</code>

你也可以修改这里的Bukkit版本.你可以在[http://repo.bukkit.org/content/groups/public/org/bukkit/bukkit/ here]这里通过查看 maven-metadata.xml文件下的版本列表来获取可用的服务端版本号.

当你完成上述步骤后,''pom.xml''中的内容应该是这样:

[[Image:Finishedpom.png]]

通过菜单 ''File -> Save''或者按住 <code>Ctrl + S</code> 来保存''pom.xml''文件 . 之后, 右键项目标题，然后依次选择 ''Maven -> Update Project''.

=== Bukkit Java文档 ===

如果你曾经使用过Eclipse和Java，你会知道当你将鼠标准心移至class或者 method中的代码部分时，一个含有相关文档内容的黄色小框会弹出来. 这就是（Java的）Java文档。

你可以[http://download.oracle.com/javase/6/docs/api/ Oracle website 在线获取]它.。Bukkit同样拥有文档，这些文档内容包含了关于API中method和class的有用描述。

你可以在[http://jd.bukkit.org/ 这]找到它 (Beta版的Java文档在[http://jd.bukkit.org/ 这]找, 新开发出来的Java文档在

[http://jd.bukkit.org/ 这]) 。为了在Eclipse里使用Java文档,这样的话当你的鼠标停留在Bukkit的class和method上时，

（Bukkit的）Java文档就会冒出来。
JavaDoc in spigot [https://hub.spigotmc.org/javadocs/bukkit/ Click Here]

首先右键在侧边栏里的"Maven Dependencies"下面的Bukkit jar,选择"Properties".选中窗口左边的''Javadoc Location'', 并粘贴如下网址

'''http://jd.bukkit.org/''' (或者上面的测试版/最新版 Java文档链接也好) 到"Javadoc URL"下面的输入框内. 就像这样:

[[Image:Bukkitjavadocs.png]]

点击 "Validate",然后再点击"OK"就完成了.现在Bukkit Javadocs已经连接到Bukkit提供的资源,同时你也可以通过Eclipse来获得帮助类文档信息了.

=== 创建一个包 ===

现在你需要创建一个包，它将储存所有我们需要使用的Java类文件. 右键展开''src/main/java''折叠并选择 ''New > Package'':

[[Image:Newpackage.png]]

包名的话，先写上你的组名，然后加个点，再写上你的小写Artifact ID。举例, 如果你的组名是''io.github.name''，你的artifact名是 ''TestPlugin''。

你的包名就应该是''io.github.name.testplugin''.

=== 创建插件的类文件 ===

既然我们已经建立好了我们的项目，我们接下来可以开始添加类文件以及制作插件了. 插件的主类指的是拓展(extends)JavaPlugin的类文件. 在你的插件中只能有一个类文件拓展JavaPlugin，无论直接还是间接. 先创建你的主类文件并保持名称与插件名一致是个很好的习惯.右键你之前新建的包,并选择  ''New > Class''.你将会创建一个新的类文件，就像下面这样

package {$GroupName}.{$ArtifactName};

import org.bukkit.plugin.java.JavaPlugin;

public final class {$ArtifactName} extends JavaPlugin {

}

警告：插件绝对不应该调用自己的构造函数并实例化

=== 创建plugin.yml ===

你已经创建了项目和主类，如果你想要Bukkit能够加载你的插件，你还必须创建 '''[[Plugin YAML|plugin.yml]]''' 文件. 这个文件包含有基础的插件信息，如果缺失这个文件，你的插件也将会失效. 此时你需要右键''src/main/resources''. 选择''New > File''. 命名为"'''plugin.yml'''" 并右键完成新文件的创建.Eclipse会打开默认的文本编辑窗口来显示'''plugin.yml'''文件中空白的内容并提供编辑. ''(Hint: 如果你想要使得你的工作空间更加规整，关闭文本编辑器并将'''plugin.yml''' 文件拖到主工作空间(拖到文件目录的右边) 之后你就可以在eclipse中编辑文件了.)''

有三个基础的内容需要在plugin.yml写明.
: name: 插件名称.
: main: [http://docs.oracle.com/javase/specs/jls/se7/html/jls-6.html#jls-6.7 插件主类的完整，合法名称] .
: version: 插件当前版本号.

最简单的 '''plugin.yml''' 文件内就像这样 :

name: {插件名称}
main: {包名}.{主类}
version: {版本号}

PS:插件的包名经常会包括插件的名称，所以看到这个的时候不要感到惊讶。
你的主类是否是你的插件名取决于你之前的命名方式，时刻记住这一点很重要。

'''''更多例子''', 请看[[#Example_Files_and_Templates]]''

此时你的插件已经可以被Bukkit加载了,同时服务端日志也会开始记录你的插件. 不过它现在什么用都没有!

== onEnable()和onDisable()方法 ==

这些方法将在插件启用与卸载时生效. 默认情况下，你的插件在被加载时会调用这些方法，所以你可以在这里注册你需要用到的事件和提供一些调试信息. <code>onEnable()</code> 方法会在插件启用时被调用, 需要包含初始化插件的逻辑语句. <code>onDisable()</code> 方法会在插件卸载时被调用，需要包含清理(clean up)插件的逻辑语句和连接声明(associated state)。此外，插件可以重写 <code>onLoad()</code> 方法来在插件载入时执行附加的逻辑语句。

=== onEnable()和onDisable()方法介绍 ===

在前面的章节中，我们在主类创建了<code>onEnable()</code> 和 <code>onDisable()</code> 方法. 此时，这些代码看起来就像下面这样

package {$TopLevelDomain}.{$Domain}.{$PluginName};

import org.bukkit.plugin.java.JavaPlugin;

public final class {$PluginName} extends JavaPlugin {
@Override
public void onEnable() {
// 插件载入时要执行的代码（略）
}

@Override
public void onDisable() {
// 插件卸载时要执行的代码（略）
}
}

这些方法已经创建，但目前它们还没有任何作用.
注意: 不需要添加代码来实现输出信息"{$PluginName} has been enabled!" ，因为bukkit会自动输出此类信息
有关更多事件的信息请查看 [[Event_API_Reference|这里]].

=== 发送提示信息 ===

插件能够输出信息至控制台与服务器日志。这是通过调用插件记录器里正确的方法来实现的。首先我们必须调用 <code>getLogger()</code> 方法来检索该插件的记录器，

然后我们就可以开始记录信息了。

我们通过调用<code>onEnable()</code>方法可以实现输出信息。我们需要在<code>onEnable()</code>方法下面插入如下代码：

getLogger().info("onEnable has been invoked!");

在 <code>'''onDisable()'''</code>方法里面，你也可以做类似的事情，不过要改改输出信息。

此时你的主类文件就像这样:

package {$TopLevelDomain}.{$Domain}.{$PluginName};

import org.bukkit.plugin.java.JavaPlugin;

public final class {$PluginName} extends JavaPlugin {
@Override
public void onEnable() {
getLogger().info("onEnable has been invoked!");
}

@Override
public void onDisable() {
getLogger().info("onDisable has been invoked!");
}
}

=== 防止重载后插件失效 ===

你需要知道的是，插件并不只会伴随服务器关闭、启动而重载，你的插件也可能会被其他插件启用、关闭，或是在服务器运行时使用/reload命令.
假设服务器启动之后一会儿后，你的插件才被启用，这时便是危险的,因为服务器中可能已经有玩家在线、额外的世界被加载以及很多预想不到的不同之处(与"插件同服务器同时加载"的情况相比较).

举个例子来说:
* 你有一个用来储存HashMap中的玩家登入信息的插件
* 你希望该信息对所有玩家都可见
* 一名管理员使用/reload命令
* 你的插件被卸载，所有储存的数据都丢失了
* 你的插件被再次启用时，一些玩家已经在线
* 这些玩家在HashMap并没有储存的信息
* 你试图重新获得他们的信息，但是失败了!

为了插件重载以后能够正常工作, 你需要在插件启用时加载所有已经在线的玩家的信息并将之储存在HashMap中.

for (Player player : Bukkit.getServer().getOnlinePlayers()) {
playerList.put(player.getName(), playerData(player));
}

== 监听器 ==
监听器是一种方法被调用来对事件作出反应的类.所有的监听器使用 org.bukkit.event.Listener接口.更多有关监听器创建的细节,
:: '' 请查看: [[Event API Reference]]''

== 指令 ==

=== onCommand() 方法 ===

现在你已经知道如何注册一个事件并做出响应,但是如果你只是想要在命令输入之后做出响应呢? 你可以使用 <code>'''onCommand'''</code>方法.

这个代码的作用是当玩家输入“/”时，监听该操作并执行相关语句"/" . 举个例子来说.输入 "/do something" 将会执行 <code>'''onCommand'''</code>方法.

此种情况下，因为没有特定的行为被编程，所以并不会发生任何事情。

请避免使用和bukkit所提供的指令重名的指令, 然后深思你的指令名的唯一性。

例如.指令"give"已经被好几个插件使用了, 如果你执行了另外一个"give"指令, 你的插件将会和这些插件冲突。

你必须在插件的"plugins.yml"注册你的指令否则这个方法将不会被触发。

<code>'''onCommand'''</code>方法必须返回一个布尔值（true或false）。

如果返回值是true，你不会看到什么明显的事情发生。

但如果返回值是false，则会返回你的plugin.yml里的'usage:property'然后发送给命令使用者.

当使用 <code>'''onCommand'''</code>方法时, 你需要填写4个参数.

*<code>'''CommandSender sender'''</code> - 发送命令的对象

*<code>'''Command cmd'''</code> - 被执行的指令

*<code>'''String commandLabel'''</code> - 被执行指令的别名

*<code>'''String[] args'''</code> - 该指令的自变量数组。

例如.指令 ''/hello abc def'' 中， ''abc'' 会被存放进args[0]中, ''def'' 被存放进args[1]中。

==== 设置命令 ====
@Override
public boolean onCommand(CommandSender sender, Command cmd, String label, String[] args) {
if (cmd.getName().equalsIgnoreCase("basic")) { // 如果玩家输入了/basic则执行如下内容...
// 所需要执行的事（此处略）
return true;
} //如果以上内容成功执行，则返回true
// 如果执行失败，则返回false.
return false;
}

每当使用<code>'''onCommand'''</code>方法时，在每个方法后面都加上一个 return false; 是一个惯例。

返回false会显示在plugin.yml里设置的usage信息 (看下面). 用这种方法的话，一旦执行出错便会显示usage信息。

每当方法return一个值的时候，这个方法就会退出，所以return true的时候，在它下面的代码就会被跳过,

除非return语句在一个if的嵌套中，或者类似的嵌套情况。

<code>'''.equalsIgnoreCase("basic")'''</code>代表忽略英文大小写. 在这种情况下,字符串"BAsIc" 和 "BasiC"和 basic相同，代码会被照常执行。

和以前一样，加两行import在你的java文件头

import org.bukkit.command.Command;

import org.bukkit.command.CommandSender;

=== 在Plugin.yml中添加你的指令 ===

你需要添加你的指令到 '''plugin.yml''' 文件里. 如下是指令/basic添加到 '''plugin.yml'''的例子（请在plugins.yml的末尾添加如下代码）:

commands:
basic:
description: This is a demo command.
usage: /<command> [player]
permission: <plugin name>.basic
permission-message: You don't have <permission></source> </code> </blockquote>

*<code>'''basic'''</code> - 指令名称

*<code>'''description'''</code> - 指令描述

*<code>'''usage'''</code> - 在oncommand方法return false后显示的用法提示。尽量简洁, 使别人能够理解指令是什么以及如何使用它。

*<code>'''permission'''</code> - 被一些显示帮助信息的插件使用，用来决定向玩家显示哪个指令（完全不对劲吧！）。

*<code>'''permission-message'''</code> - 当玩家使用了这个指令而没有权限时输出的信息。

PS:yml文件使用两个空格作为制表符,使用tab键输入制表符会导致错误。

===控制台指令vs玩家指令===

你可能注意到了上文的<code>'''CommandSender sender'''</code>参数. <code>'''CommandSender'''</code> 是个Bukkit接口，

它有两个（对插件编写者）有用的子类：<code>'''Player'''</code> 和 <code>'''ConsoleCommandSender'''</code>.

所以当你编写插件的时候, 确定这个指令从控制台发出后能完全正常工作是十分必要的,

那些只能由在线玩家执行的指令 ''只能'' 由一个在线玩家执行。

有的插件在判断命令执行对象不是玩家时仅仅用return进行处理 (比如当有人从控制台发出指令),

即便这些指令能够在控制台完美运行（比如改变天气的指令）。

一个判断sender的方法:
@Override
public boolean onCommand(CommandSender sender, Command cmd, String label, String[] args) {
if (cmd.getName().equalsIgnoreCase("basic")) { //如果玩家输入了/basic则执行如下内容...
// 所需要执行的事（此处略）
return true;
} else if (cmd.getName().equalsIgnoreCase("basic2")) {
if (!(sender instanceof Player)) { //如果sender与Player类不匹配
sender.sendMessage("This command can only be run by a player.");
} else {
Player player = (Player) sender;
// 所需要执行的事（此处略）
}
return true;
}
return false;
}

在这个例子里，指令'''basic'''能由任何人发出 - 一个在线的玩家, 或者服务器后台的op.

但是指令'''basic2'''只能由一个在线的玩家发出.

大体上说,你应该允许尽可能多的指令在控制台和玩家聊天框里都正常执行.

需要在线玩家执行的指令可以使用以上例子中的机制来检测<code>'''CommandSender'''</code>是一个玩家.

很多指令广泛依靠于一些玩家的属性（例如可以被tp或被给予物品等等）。

如果你想更进一步, 你可以对你的指令的自变量做一些额外的检测，例如传送指令在提供玩家ID的情况下（也只有在这种情况下）可以在控制台被执行。

=== 使用独立的 CommandExecutor class ===

以上的例子必须把 <code>'''onCommand()'''</code> 方法放在插件的主类里。

对于小插件来说，这是极好的,但如果你要写一个大点的插件,把你的 <code>'''onCommand()'''</code>方法放在独立的类里将会很有意义。

幸运的是，这并不难:

*在你的包里创建一个新类. 命名为'''MyPluginCommandExecutor'''之类的 (当然，要把'''MyPlugin'''替换成你制作的插件的名字)。这个类 '''必须''' 继承Bukkit 的'''CommandExecutor'''接口。

*在你的插件的<code>'''onEnable()'''</code>方法中,你需要实例化你创建的命令执行类(CommandExecutor class), 然后做一个像下面一样的调用：<code>getCommand("basic").setExecutor(myExecutor);</code>
其中"basic"是我们需要操控的指令, <code>myExecutor</code> 是我们创建的实例.

废话少说直接吔我例子:

'''MyPlugin.java''' (插件的主类):
@Override
public void onEnable() {
// 如果你没有在plugins.yml注册过指令的话，此处会抛出空指针异常！
this.getCommand("basic").setExecutor(new MyPluginCommandExecutor(this));
}

'''MyPluginCommandExecutor.java'''（独立CommandExecutor类）:
public class MyPluginCommandExecutor implements CommandExecutor {
private final MyPlugin plugin;

public MyPluginCommandExecutor(MyPlugin plugin) {
this.plugin = plugin; // Store the plugin in situations where you need it.
}

@Override
public boolean onCommand(CommandSender sender, Command cmd, String label, String[] args) {
// 和以前一样执行就好…
}
}

请注意我们是如何把主类里的对象指向'''MyPluginCommandExecutor'''的. 这允许我们轻易的使用主类对象的方法（如果我们需要的话）。

这么做的话, 我们便能更好的组织代码 - 如果 <code>'''onCommand()'''</code> 方法又大又复杂, 它就能被划分为子类，从而不使插件的主类显得凌乱。

PS：如果你的插件含有多个指令的话, 你需要为每一个指令单独设立一个commandexecutor.

=== 写一个安全的指令 ===
当写一个指令的时候,别进行任何假设（很重要）, 例如假设执行者一定是个玩家. 请牢记以下原则:

==== 在命令执行前确定发出者是玩家 ====

使用简单的例子来进行检测:

@Override
public boolean onCommand(CommandSender sender, Command cmd, String label, String[] args) {
if (sender instanceof Player) {
Player player = (Player) sender;
// do something
} else {
sender.sendMessage("You must be a player!");
return false;
}
// do something
return false;
}

==== 检测自变量个数 ====

别老是认为玩家都能打对正确数量的自变量.

@Override
public boolean onCommand(CommandSender sender, Command cmd, String label, String[] args) {
if (args.length > 4) {
sender.sendMessage("Too many arguments!");
return false;
}
if (args.length < 2) {
sender.sendMessage("Not enough arguments!");
return false;
}
}

==== 在获取玩家之前先检测他们是否在线 ====

有时你想通过命令发出者打出的ID来获取其他玩家，请确保他们在线再说！

@Override
public boolean onCommand(CommandSender sender, Command cmd, String label, String[] args) {
Player target = (Bukkit.getServer().getPlayer(args[0]));
if (target == null) {
sender.sendMessage(args[0] + " is not online!");
return false;
}
return false;
}

如果你想对离线玩家进行操作，<code>'''OfflinePlayer'''</code>类提供了基础操作的方法.

== 插件的配置/设置 ==
Bukkit API 为插件提供了一种简便的方法，用来管理用户自定义的设置。同时，通过这种方法也可以储存数据。
:: ''详情请查看: [[Configuration API Reference]]''

== 权限 ==

利用新的Bukkit API来设置权限是再容易不过的事情. 检测玩家是否拥有权限，可以使用以下代码:
<blockquote><source lang="java">if (player.hasPermission("some.pointless.permission")) {
//执行此段代码(有权限)
} else {
//执行此段代码(无权限)
}</source> </blockquote>
你也可以检测一个权限节点是否被定义过，(等效于 Java 语言中的'''null''')，使用下面的方法:
<blockquote><source lang="java">boolean isPermissionSet(String name)</source></blockquote>
你或许对此抱有疑惑:为什么这段代码中没有任何用户群的信息？因为它们并不是必需的. 之前这段代码想要实现的主要功能之一就是根据用户群格式化聊天信息. 但其实使用权限就可以很容易地完成这项工作.你可以在聊天插件的配置文件中定义权限与前缀的对应关系. 举例来说，"someChat.prefix.admin" 权限可以对应前缀[Admin].当拥有此权限的玩家发出聊天信息时，聊天前缀便是[Admin].

另一个想要实现的主要功能则是给所有拥有权限的在线用户发一条信息.你可以这样做:
<blockquote><source lang="java">for (Player player: Bukkit.getServer().getOnlinePlayers()) {
if (player.hasPermission("send.receive.message")) {
player.sendMessage("You were sent a message");
}
}</source> </blockquote>
看到这里你可能会问，若是没有权限组我该如何配置玩家的 [[权限]] ？既然 [[Bukkit]] API 本身并没有提供用户组的预设, 你必须通过安装一款权限组插件，像 [[permissionsBukkit]] 这样的插件来帮助你配置用户群. '''API 只是提供接口而不是提供implementation.'''

=== 配置权限 ===

如果你想要更多地控制你的权限，例如设置权限的默认值或是子权限节点，不如将权限节点加入你的 ''[[plugin.yml]]''文件.这并不是必须的，但我们推荐你这样做. 下面是一个实例，显示了当你将权限添加在''plugin.yml''文件末尾时的样子:
<blockquote><code><source lang="yaml">permissions:
doorman.*:
description: Gives access to all doorman commands
children:
doorman.kick: true
doorman.ban: true
doorman.knock: true
doorman.denied: false
doorman.kick:
description: Allows you to kick a user
default: op
doorman.ban:
description: Allows you to ban a user
default: op
doorman.knock:
description: Knocks on the door!
default: true
doorman.denied:
description: Prevents this user from entering the door</source> </code> </blockquote>
Firstly, each permission your plugin uses is defined as a child node of the ''permissions'' node. Each permission can then optionally have a description, a default value, and children.

==== Defaults ====

By default when a permission isn't defined for a player ''hasPermission'' will return false. Inside your plugin.yml you can change this by setting the default node to be one of four values:

*'''true''' - The permission will be true by default.
*'''false''' - The permission will by false by default.
*'''op''' - If the player is an op then this will be true.
*'''not op''' - If the player is not an op then this will be true.

==== Children ====

Before now you will probably be used to the * permission to automatically assign all sub permissions. This has changed with the bukkit API and you can now define the child permissions. This allows for a lot more flexibility. Below is an example of how you do this:
<blockquote><source lang="yaml">permissions:
doorman.*:
description: Gives access to all doorman commands
children:
doorman.kick: true
doorman.ban: true
doorman.knock: true
doorman.denied: false</source> </blockquote>
Here the ''doorman.*'' permission has several child permissions assigned to it. The way child permissions work is when ''doorman.*'' is set to true, the child permissions are set to their values defined in the ''plugin.yml''. If however ''doorman.*'' was set to false then all child permissions would be inverted.

=== Setting your own permissions ===

If you wish to know about developing your own permissions plugins (Ones that actually set permissions) then check out the tutorial on [[Developing a permissions plugin]].

== Scheduling Tasks and Background Tasks ==

Currently, Minecraft servers operate nearly all of the game logic in one thread, so each individual task that happens in the game needs to be kept very short. A complicated piece of code in your plugin has the potential to cause huge delays and lag spikes to the game logic, if not handled properly.

Luckily, Bukkit has support for scheduling code in your plugin. You can submit a Runnable task to occur once in the future, or on a recurring basis, or you can spin off a whole new independent thread that can perform lengthy tasks in parallel with the game logic.

There is a separate [[Scheduler Programming]] tutorial which introduces the Scheduler, and gives more information on using it to schedule synchronous tasks, and on kicking off asynchronous tasks in Bukkit.

== 方块操控 ==

这是一个很容易的方法创建、获取或修改一个方块, 例如当你想要修改往你头上数第五格的方块时, 首先你需要做的是获取你当前的坐标点, 然后往你当前的坐标点的Y轴加上五, 获取目标方块后我们便能够很容易地修改它了, 例子如下:
<blockquote><source lang="java">
@EventHandler
public void onPlayerMove(PlayerMoveEvent event) {
// 得到玩家当前的坐标.
Location loc = event.getPlayer().getLocation();
// 设置目标坐标为玩家头顶 5 格处.
loc.setY(loc.getY() + 5);
// 得到目标坐标的方块
Block b = loc.getBlock();
// 将目标坐标的方块更改为岩石 (stone).
b.setType(Material.STONE);
}</source> </blockquote>
The above code gets the player's location, gets the block five above it, and sets it to stone. Note that once you have a <code>Block</code>, there are other things you can do besides set its type. Consult the JavaDocs for more information.

You can use a similar concept to generate buildings and individual blocks programmatically through the use of algorithms. For example, to generate a solid cube, you could use nested <code>for</code> loops to loop over an entire cube and fill it in.
<blockquote><source lang="java">
public void generateCube(Location loc, int length) {
// Set one corner of the cube to the given location.
// Uses getBlockN() instead of getN() to avoid casting to an int later.
int x1 = loc.getBlockX();
int y1 = loc.getBlockY();
int z1 = loc.getBlockZ();

// Figure out the opposite corner of the cube by taking the corner and adding length to all coordinates.
int x2 = x1 + length;
int y2 = y1 + length;
int z2 = z1 + length;

World world = loc.getWorld();

// Loop over the cube in the x dimension.
for (int xPoint = x1; xPoint <= x2; xPoint++) {
// Loop over the cube in the y dimension.
for (int yPoint = y1; yPoint <= y2; yPoint++) {
// Loop over the cube in the z dimension.
for (int zPoint = z1; zPoint <= z2; zPoint++) {
// Get the block that we are currently looping over.
Block currentBlock = world.getBlockAt(xPoint, yPoint, zPoint);
// Set the block to type 57 (Diamond block!)
currentBlock.setType(Material.DIAMOND_BLOCK);
}
}
}
}</source></blockquote>
This method will construct a 3D cube or cuboid with the given length and starting point. As for deleting blocks simply follow the same method for creating them but set the ID to 0 (air). 
<blockquote></blockquote>

== (Player) Inventory Manipulation ==

This section mostly covers player inventory manipulation, but the same applies to chest inventory manipulation as well if you find out how to get a chest's inventory :P. Here is a simple example of inventory manipulation:
<blockquote><source lang="java">public void onPlayerJoin(PlayerJoinEvent evt) {
Player player = evt.getPlayer(); // 当玩家加入游戏
PlayerInventory inventory = player.getInventory(); // 获取玩家背包列表
ItemStack itemstack = new ItemStack(Material.DIAMOND, 64); // 生成一组钻石

if (inventory.contains(itemstack)) {
inventory.addItem(itemstack); // 将一组钻石放到玩家的背包里
player.sendMessage("Welcome! You seem to be reeeally rich, so we gave you some more diamonds!"); //向玩家发送消息("你看起来很有钱的样子....balabala")
}
}</source> </blockquote>
So inside onPlayerJoin we first make a few variables to make our job easier: player, inventory and itemstack. Inventory is the player's inventory and itemstack is a ItemStack that has 64 diamonds. After that we check if the player's inventory contains a stack of diamonds. If the player has a stack of diamonds, we give him/her another stack with inventory.addItem(itemstack) and send a message. So inventory manipulation isn't actually that hard, if we wanted we could remove the stack of diamonds by simply replacing inventory.addItem(itemstack) with inventory.remove(itemstack) and change the message a little bit. Hopefully this helped!

== Item Manipulation ==

When dealing with items in the code, you use the ItemStack class for looking up and setting all information on that stack.

=== Enchantments ===

To enchant an item you must first know the [http://www.minecraftwiki.net/wiki/Data_values Item Code] and the [http://www.minecraftwiki.net/wiki/Talk:Enchanting#Effect_IDs Effect ID]. Enchantments themselves cannot be instantiated (new Enchantment() won't work) because they're abstract, so you must use an EnchantmentWrapper. If you want to enchant items that can't be enchanted inside normal SMP, use addUnsafeEnchantment() instead of addEnchantment()

<source lang="java">
int itemCode = 280; //use the item code you want here
int effectId = 20; //use the enchantment code you want here
int enchantmentLevel = 100;

ItemStack myItem = new ItemStack(itemCode); //new item of item code
Enchantment myEnchantment = new EnchantmentWrapper(effectId); //new enchantment of effect id
myItem.addEnchantment(myEnchantment, enchantmentLevel); //enchant the item
</source>

=== ItemMeta ===
You can set the display name of an item by doing this.
<source lang="java">
String myDisplayName = "Awesome Sword"; //这里是保存了你想要显示的名字

ItemStack myItem = new ItemStack(Material.DIAMOND_SWORD); //你要更改的方块
ItemMeta im = myItem.getItemMeta(); //得到方块的元数据
im.setDisplayName(myDisplayName); //设置它显示的名字
myItem.setItemMeta(im); //保存更改
</source>
You can also set the lores of an item. The lores are the small annotations on an item, like "+5 attack damage" on a stone sword.
<source lang="java">
List<String> lores = new ArrayList<String>();
lores.add("Example lore", "this one comes on line 2");

ItemStack myItem = new ItemStack(Material.DIAMOND_SWORD); //your item
ItemMeta im = myItem.getItemMeta(); //get the itemmeta of the item again
im.setLore(lores); //add the lores of course
myItem.setItemMeta(im); //give the item the new itemmeta
</source>

== Maps, and Sets, and Lists, Oh My! <ref>标题中Map,Set,List均为Java类集中的接口，故不翻译</ref> ==

除了Map类和HashMap类，Java中还提供了其它的数据结构类集。

他们提供这些不同的类，是因为有些时候，使用Map类并不合适。<nowiki>[[Java data structure classes]]</nowiki>在这个条目中，有对Java数据框架类集更深入的讲述。

<nowiki>=== HashMaps概览以及如何使用此接口 ===</nowiki>

<nowiki><big></nowiki>

<nowiki>'''</nowiki>Keep in mind to never use a player in a hashmap!<nowiki>'''</nowiki><ref>下面有讲解。</ref>

应在HashMap中使用字符串.，使用 "p.getName()" 来添加，移除或是检查列表中是否含有某个玩家.

将玩家当作object储存在HashMap中会造成大量内存泄漏.

<nowiki></big></nowiki>

When making a plugin you will get to a point where just using single variables to state an event has happened or a condition has been met will be insufficient, due to more than one player performing that action/event.

This was the problem I had with one of my old plugins, Zones, now improved and re-named to Regions. I was getting most of these errors because I didn't consider how the plugin would behave on an actual server with more than one on at any given time. I was using a single boolean variable to check whether players were in the region or not and obviously this wouldn't work as the values for each individual player need to be separate. So if one player was in a region and one was out the variable would constantly be changing which could/would/did cause numerous errors.

A HashMap is an excellent way of doing this. A HashMap is a way of mapping/assigning a value to a key. You could set up the HashMap so that the key is a player and the value could be anything you want, however the useful things with HashMaps is that one key can only contain one value and there can be no duplicate keys. So say for example I put "adam" as the key and assigned a value of "a" to it. That would work as intended, but then say afterwards I wanted to assign the value of "b" to key "adam" I would be able to and would get no errors but the value of "a" assigned to key "adam" in the HashMap would be overwritten because HashMaps cannot contain duplicate values.

<nowiki>==== Defining a HashMap ====</nowiki>

<nowiki><blockquote><source lang="java">public Map<KeyType, DataType> HashMapName = new HashMap<>(); //Example syntax</nowiki>

// Example Declaration

public Map<String, Boolean> pluginEnabled = new HashMap<>();

public Map<String, Boolean> isGodMode = new HashMap<>();

<nowiki></source></nowiki> <nowiki></blockquote></nowiki>

Keep that code in mind because we will be using it for the rest of the tutorial on HashMaps. So, for example lets create a simple function which will toggle whether the plugin has been enabled or not. Firstly, inside your on command function which I explained earlier you will need to create a function to send the player name to the function and adjust the players state accordingly.

So inside on command you'll need this, the function name can be different but for the sake of simplicity it's best if you keep it the same.

<nowiki><blockquote><source lang="java">Player player = (Player) sender;</nowiki>

togglePluginState(player);<nowiki></source></nowiki> <nowiki></blockquote></nowiki>

This code above will cast the value of sender to player and pass that argument to the function togglePluginState(). But now we need to create our togglePluginState() function.

<nowiki><blockquote><source lang="java">public void togglePluginState(Player player) {</nowiki>

// Notice how we use the player name as the key here,

// not the player object

String playerName = player.getName();

if (pluginEnabled.containsKey(playerName)) {

if (pluginEnabled.get(playerName)) {

pluginEnabled.put(playerName, false);

player.sendMessage("Plugin disabled");

} else {

pluginEnabled.put(playerName, true);

player.sendMessage("Plugin enabled");

}

} else {

pluginEnabled.put(playerName, true); //If you want plugin disabled by default change this value to false.

player.sendMessage("Plugin enabled");

}

}<nowiki></source></nowiki> <nowiki></blockquote></nowiki>

Now, what this code is doing is checking if the HashMap first contains the key player, so if it has been put into the HashMap, if it is then we check the value of the HashMap key by get(player); if this is true then set value to false and send the player a message, else if the value is false then do the opposite, set the value to true and send a message again. But if the HashMap does not contain the key player then we can assume that this is their first run/use so we change the default value and add the player to the HashMap.

<nowiki>==== More Ideas for HashMaps ====</nowiki>

A HashMap (or really any kind of Map in Java) is an association. It allows quick and efficient lookup of some sort of <nowiki>'''value''', given a unique '''key'''</nowiki>. Anywhere this happens in your code, a Map may be your solution.

Here are a few other ideas which are ideally suited to using Maps. As you will see, it doesn't have to be data that you store per player, but can be any kind of data that needs to be "translated" from one form to another.

<nowiki>===== Data Value Lookups =====</nowiki>

<nowiki><blockquote><source lang="java"></nowiki>

public Map<String, Integer> wool_colors = new HashMap<>();

// Run this on plugin startup (ideally reading from a file instead of copied out row by row):

wool_colors.put("orange", 1);

wool_colors.put("magenta", 2);

wool_colors.put("light blue", 3);

..

wool_colors.put("black", 15);

// Run this in response to user commands - turn "green" into 13

int datavalue = 0;

if (wool_colors.containsKey(argument)) {

datavalue = wool_colors.get(argument);

} else {

try { datavalue = Integer.parseInt(argument); }

catch (Exception e) {}

}

<nowiki></source></nowiki> <nowiki></blockquote></nowiki>

<nowiki>==== Saving/Loading a HashMap ====</nowiki>

Once you know how to work with HashMaps, you probably want to know how to save and load the HashMap data. Saving and loading HashMap data is appropriate if

<nowiki>*</nowiki>you don't want an administrator to edit the data manually

<nowiki>*</nowiki>you need to save data in binary format (too complex to organize for YAML)

<nowiki>*</nowiki>you want to avoid parsing block names and/or other objects from freeform text

This is very simple way how to save any HashMap. You can replace HashMap&lt;String, Integer&gt; with any type of HashMap you want. Let's take an example HashMap with code to save it:

<nowiki><blockquote><source lang="java"></nowiki>

HashMap<String, Integer> mapToSave = new HashMap<String,Integer>();

public void save(HashMap<String, Integer> map, String path) {

try {

ObjectOutputStream oos = new ObjectOutputStream(new FileOutputStream(path));

oos.writeObject(map);

oos.flush();

oos.close();

//Handle I/O exceptions

} catch(Exception e) {

e.printStackTrace();

}

}

// ...

save(mapToSave, getDataFolder() + File.separator + "example.bin");<nowiki></source></nowiki><nowiki></blockquote></nowiki>

You can see it's really easy. Loading works very very similar but we use ObjectInputStream instead of ObjectOutputStream ,FileInputStream instead of FileOutputStream,readObject() instead of writeObject() and we return the HashMap.

<nowiki><blockquote><source lang="java">public HashMap<String, Integer> load(String path) {</nowiki>

try {

ObjectInputStream ois = new ObjectInputStream(new FileInputStream(path));

Object result = ois.readObject();

//you can feel free to cast result to HashMap<String, Integer> if you know there's that HashMap in the file

return (HashMap<String, Integer>)result;

} catch(Exception e) {

e.printStackTrace();

}

}

// ...

HashMap<Integer, String> loadedMap;

String path = getDataFolder() + File.separator + "example.bin";

File file = new File(path);

if (file.exists()) { // check if file exists before loading to avoid errors!

loadedMap = load(path);

}<nowiki></source></nowiki><nowiki></blockquote></nowiki>

You can use this "API" for saving/loading HashMaps, ArrayLists, and all Objects which implement Serializable or Externalizable interface.

<nowiki><blockquote><source lang="java">/** SLAPI = Saving/Loading API</nowiki>

* API for Saving and Loading Objects.

* Everyone has permission to include this code in their plugins as they wish :)

* @author Tomsik68<tomsik68@gmail.com>

*/

public class SLAPI

{

public static <T extends Object> void save(T obj,String path) throws Exception

{

ObjectOutputStream oos = new ObjectOutputStream(new FileOutputStream(path));

oos.writeObject(obj);

oos.flush();

oos.close();

}

public static <T extends Object> T load(String path) throws Exception

{

ObjectInputStream ois = new ObjectInputStream(new FileInputStream(path));

T result = (T)ois.readObject();

ois.close();

return result;

}

}<nowiki></source></nowiki> <nowiki></blockquote></nowiki>

Example implementation of this API: <nowiki>'''</nowiki>I'm skipping some part of code in this source<nowiki>'''</nowiki>

<nowiki><blockquote><source lang="java">public class Example extends JavaPlugin {</nowiki>

private ArrayList<Object> list = new ArrayList<>();

@Override

public void onEnable() {

try {

list = SLAPI.load("example.bin");

} catch(Exception e) {

//handle the exception

e.printStackTrace();

}

}

@Override

public void onDisable() {

try {

SLAPI.save(list,"example.bin");

} catch(Exception e) {

e.printStackTrace();

}

}

}<nowiki></source></nowiki> <nowiki></blockquote></nowiki>

Note #1: This will work un-modified with almost all well-known Java types like Integer, String, HashMap. It will also work for some Bukkit types as well. If you're writing your own data object classes, and you may want to save their state using this technique, you should read about Java's Serializable or Externalizable interface. The only difference between Externalizable and Serializable is, that Serializable automatically takes all of class's fields and tries to serialize them, while Externalizable allows you to define method for reading and writing the Object. It's easy to add to your code, and it will make your data persistent with very little work required. No more parsing!

Note #2: This API doesn't support changes. Once you change something in the class, data files saved with older version of your plugin won't load correctly.

<nowiki>===== Tips & Examples =====</nowiki>

1.) Simplify your save structure

Try to use as much simple types as possible. E.g. if you want to save player, save their UUID instead. If you want to save world, save its UUID. If you want to save location, save x,y,z world UUID. DO NOT DIRECTLY SAVE BUKKIT TYPES!

2.) Save version number along with data

You should always remember, that you don't know what you'll be saving in the same file tomorrow. Will you ever migrate this file because of newer version of your plugin, bukkit, or minecraft? You don't know!

3.) Migrate older files

If your plugin finds older version of some file, it should update the file accordingly and change version number.

<references />

== Metadata ==

Bukkit is trying to make plugin development as easy as possible, so HashMaps with key of type Player, Entity, World or even a Block were replaced by Metadata. Metadata is some kind of alternative to HashMap. It allows you to add custom "fields" to Players, Entities, Worlds and Blocks. These things are all members of Metadatable class(check [http://jd.bukkit.org/doxygen/de/d59/interfaceorg_1_1bukkit_1_1metadata_1_1MetadataValue.html#ab49975fe013a0626dd29d3b85c63a82f])It works very simply. Everything that is Metadatable holds its own HashMap of Metadata which you have access to. That means, for example, if you're creating an economy plugin, you would need a HashMap of Player and Float or Double. With Metadata, you don't have to! You just attach to player new metadata value, and that's it! 

=== Why to use Metadata ===

* Metadata is all handled by Bukkit, which makes it a very good alternative to HashMaps.
* Metadata can be used to share information between plugins.

=== Why not use Metadata ===

* Slightly more difficult to get the value.
* It is not saved on shutdown (but then again, neither are any Maps that you create).

=== Getting & Setting Metadata ===

<source lang="java">
public void setMetadata(Metadatable object, String key, Object value, Plugin plugin) {
object.setMetadata(key, new FixedMetadataValue(plugin,value));
}

public Object getMetadata(Metadatable object, String key, Plugin plugin) {
List<MetadataValue> values = object.getMetadata(key);
for (MetadataValue value : values) {
// Plugins are singleton objects, so using == is safe here
if (value.getOwningPlugin() == plugin) {
return value.value();
}
}
return null;
}</source>

Note: If you're manipulating with numbers, booleans or strings, use convenient method to get the result. For example, you can use asInt(), asString() or asBoolean() instead of value to find out the value.

== Databases ==

Sometimes flat files aren't enough for what your looking to do, this is where databases come in. The most common database engines available on Linux/Mac/Windows machines typically run on some flavor of SQL (Structured Query Language).

Software offering SQL allow you to create databases with columns and header to identify to contents of each cell. Think of it as a spreadsheet on steroids, where every column you set up in your database can enforce rules to ensure integrity. Apart from being more organised than a simple custom data file, SQL provides faster access and better searching than flat files.

The SQL standard helps applications like Bukkit implement database storage for their data in a consistent way. Unfortunately, there's more than one SQL-ready database engine, and each has minor differences in how to configure and use it. Which one you choose may depend on your particular needs. (Some plugins even offer configurable options to connect to multiple database engines!)

=== SQLite ===

Alta189 has written a [http://forums.bukkit.org/threads/lib-tut-mysql-sqlite-bukkit-drivers.33849/ fantastic SQLite tutorial] which I suggest you watch if you're interested in using SQL in your plugins, included with the tutorials is a handy library you can download and import to make using SQL easier. Once you have watched these video tutorials I would suggest you go and learn some SQL syntax, it's very straightforward and shouldn't take you long to pick up. SQL Tutorials [http://www.w3schools.com/sql/default.asp @W3Schools] and [http://www.1keydata.com/sql/sql.html @1Keydata].

SQLite is great for very simple databases, because there's no server concerns to set up. Just make a few calls to create a new database and table. It's easy to back up: just copy the whole database file in one go. SQLite is a little bit weaker at data integrity, flexibility in data types, and it may not be something you would want to trust for huge databases of millions of rows. But for a new plugin in development, it's often easiest and fastest to get the SQL basics squared away with SQLite, even if you "graduate" to a more server-class database engine later.

=== MySQL ===

Another popular SQL database engine is called MySQL. It is closer to server-grade than SQLite, where many popular companies or websites depend on it for millions of webpage hits every day. With that security comes a little bit steeper learning-curve, because MySQL has more tunable parameters and capabilities.

The coding for plugins accessing MySQL is mostly the same as tiny SQLite or mega-sized Oracle, with only small differences in syntax here or there. But the administration has room to grow. You may want to set up accounts and privileges inside your MySQL setup. You may want to set up SQL scripts that organize your backups and rollback to previous states.

== 部署你的插件 ==

总之你写好的你的插件,如何把它变成一个可安装在服务端的jar文件呢?

首先我们需要建立一个水桶服务器。 [http://wiki.bukkit.org/Setting_up_a_server 在这里] 能找到开服相关信息.接下来你需要把插件导出为一个.jar文件，

这样你就能在你的服务器里运行它。在Eclipse里, 右键工程，点击''Run as > Maven install''即可:

[[Image:Maveninstall.png]]

将来呢, 当你对插件进行了改动后,在做上述操作之前，如果你想删除之前的.jar文件，你可以右键工程，点击 ''Run as > Maven clean'' 。

如果你在编译插件时遇到了问题, 请检查你的JDK是否正确安装，并浏览[[建立工作区]]条目。

如果你在Eclipse控制台看到了和JDK有关的错误，你可能需要手动调整JDK,因为Eclipse的检测可能发生了错误。

点击''Window -> Preferences'', 然后是''Java -> Installed JREs''。选中你最近安装的JDK作为Java运行环境（JRE）并添加, 并取消掉原来那个报错的JDK:

[[Image:Jrelocation.png]]

如果你的工程成功被编译,JAR文件会生产在 ''target'' 目录下，具体在Eclipse的工作空间里名字为工程名的文件夹中。

这个JAR文件就是一个能正常工作的Bukkit插件了。当然前提是你的plugin.yml里没出差错。

你可以把这个jar文件丢到服务器的plugins文件夹里,重载或重启服务器,就可以测试你的新插件啦。

为了连接上使用你自己的电脑开的服务器 ,在多人游戏的ip里填上你的本地ip即可。

如果出现了错误而你又不能解决的话, 试试这里[http://forums.bukkit.org/forums/plugin-development.5/ plugin development forum],

在这里提问[http://wiki.bukkit.org/IRC bukkitdev IRC channel],或者重新阅读wiki。

当你做完了一个实用的插件,可以考虑把它发表在这里[http://dev.bukkit.org/ dev.bukkit]（为了Bukkit社区的访问量）。

以上可知,JAR格式是默认压缩生成的(JAR文件基于ZIP文件的格式)。这么说来，在上传插件到Bukkit上时把JAR文件压缩成ZIP只会增加文件体积罢了。

而且呢, 放在JAR中的config文件可以在检测不到插件目录（插件自动生成的文件夹，名字与插件名相同，里面是该插件的配置）下的config文件时自动生成。

所以我们一般不把jar文件转换成其他格式。

== 导入其它插件 ==
你可能会希望编辑其它那些有源代码的插件. 如果插件在它的目录下有''pom.xml''(大多数知名插件,例如WorldEdit和Essentials都有),你可以通过点击''File -> Import''来把它作为一个工程导入, 然后打开''Maven''项并选择''Existing Maven Projects'':

[[Image:Importmaven.png]]

然后选择''pom.xml''所在的目录,这个工程就应该出现在你的侧边栏里了。就像平常一样编辑并编译它吧。

== 小贴士 ==

=== 使玩家着火 ===

Bukkit API有很多碉堡的功能。以下是实现一些功能的代码片段。

下面的代码运行一个玩家使另一个玩家着火。通过类似于'''/ignite Notch'''这样的指令，这个指令会让 Notch 着火。

@Override
public boolean onCommand(CommandSender sender, Command cmd, String label, String[] args) {
// 使用 equalsIgnoreCase() 来忽视大小写
if (cmd.getName().equalsIgnoreCase("ignite")) {
// 确保玩家只输入了一个自变量(要被点着的玩家名).
if (args.length != 1) {
// 当return false时，该指令的使用信息会显示出来。
return false;
}

// 确保命令发出者是个玩家.
if (!(sender instanceof Player)) {
sender.sendMessage("Only players can set other players on fire.");
sender.sendMessage("This is an arbitrary requirement for demonstration purposes only.");
return true;
}

// 获取那个要被点着的玩家. 请注意下标起始是0，不是1.
Player target = Bukkit.getServer().getPlayer(args[0]);

// 确保这个玩家在线。
if (target == null) {
sender.sendMessage(args[0] + " is not currently online.");
return true;
}

// 让这个玩家着火1000 ticks (一秒钟大概有20ticks,所以总共是50秒).
target.setFireTicks(1000);
return true;
}
return false;
}

=== 干掉玩家 ===

和标题一样.这里是要干掉某个玩家。

在你的onCommand方法里使用这个:

@Override
public boolean onCommand(CommandSender sender, Command cmd, String label, String[] args) {
if (cmd.getName().equalsIgnoreCase("KillPlayer")) {
Player target = sender.getServer().getPlayer(args[0]);
// 确保玩家在线.
if (target == null) {
sender.sendMessage(args[0] + " is not currently online.");
return true;
}
target.setHealth(0);
}
return false;
}

这里有个小扩展,会使用一个爆炸来杀死玩家:

float explosionPower = 4F; //爆炸等级 - TNT的爆炸等级默认是4F
Player target = sender.getWorld().getPlayer(args[0]);
target.getWorld().createExplosion(target.getLocation(), explosionPower);
target.setHealth(0);

=== 创造一个假爆炸 ===

这段代码会生产一个看起来和听起来与TNT/苦力怕产生的爆炸一样的效果。但是不会对实体和方块产生破坏。在保留爆炸的艺术的同时又削弱了爆炸的威力，真是太有用了（
@EventHandler
public void onExplosionPrime(ExplosionPrimeEvent event) {
Entity entity = event.getEntity();

// 如果事件和点燃的TNT有关,执行一些代码（又略）
if (entity instanceof TNTPrimed) {
entity.getWorld().createExplosion(entity.getLocation(), 0);
}
}

=== 使一个玩家对另外一个玩家隐形 ===

通过输入指令，能让指令执行者对特定的玩家隐形。然而其他人仍然能看到指令执行者。

@Override
public boolean onCommand(CommandSender sender, Command cmd, String label, String[] args) {
if (cmd.getName().equalsIgnoreCase("HideMe") && args.length == 1) {
if (!(sender instanceof Player)) {
sender.sendMessage("Only players can use this command!");
return true;
}
// 检测指令执行者是玩家后，我们便可以安全的进行强制转换类操作。
Player s = (Player) sender;

// 获取命令执行者指定的玩家
Player target = Bukkit.getServer().getPlayer(args[0]);
if (target == null) {
sender.sendMessage("Player " + args[0] + " is not online.");
return true;
}
// 将 s 从 target 的视野中隐藏起来.
target.hidePlayer(s);
return true;
}
return false;
}

=== 在玩家准星所指处生产闪电 ===

如下代码运行手持鱼竿的玩家通过点击来生成闪电 (当然要用准星瞄准)。真是个简单好玩的恶作剧（。

@EventHandler
public void onPlayerInteractBlock(PlayerInteractEvent event) {
Player player = event.getPlayer();
if (player.getItemInHand().getType() == Material.FISHING_ROD) {
// 在给定坐标中生成一道闪电. 在本例中, 这个坐标是玩家准星瞄准的地方.
// 只能指向200格以内的坐标.
player.getWorld().strikeLightning(player.getTargetBlock(null, 200).getLocation());
}
}

=== 自动格式 ===

Eclipse提供了将你的代码自动转成Oracle规定的格式, 修正了不符合常规的缩进, 空格等等。在侧边栏选中你的项目,然后选择''Source -> Format''即可对其进行更改。

== 插件需求专区 ==

http://forums.bukkit.org/forums/plugin-requests.13/

== 范例文件和样板 ==

*[https://github.com/Bukkit/SamplePlugin/ Bukkit/SamplePlugin on GitHub]

*[http://pastebin.com/wpeTPx7N Example.Java]

*[http://pastebin.com/MTwaAVCT ExamplePlayerListener.Java]

*[http://pastebin.com/6FLixfH3 ExampleBlockListener.Java]

*[http://pastebin.com/8UZ6pkWC ExampleEntityListener.Java]

If you have any more questions on this matter, don't hesitate to visit the BukkitDev [[IRC]] channel and ask!

[[Category:教程]]
[[Category:大篇幅条目]]

Help.yml

2015-08-11T16:06:57Z

Minedx：开头格式

'''help.yml是帮助文件，可以帮助新手服主们查看指令'''
本页文字全部带有#号为方便全部删除

This is the help configuration file for Bukkit.
By default you do not need to modify this file. Help topics for all plugin commands are automatically provided by
or extracted from your installed plugins. You only need to modify this file if you wish to add new help pages to
your server or override the help pages of existing plugin commands.
This file is divided up into the following parts:
-- general-topics: lists admin defined help topics
-- index-topics: lists admin defined index topics
-- amend-topics: lists topic amendments to apply to existing help topics
-- ignore-plugins: lists any plugins that should be excluded from help
Examples are given below. When amending command topic, the string <text> will be replaced with the existing value
in the help topic. Color codes can be used in topic text. The color code character is & followed by 0-F.
================================================================
Set this to true to list the individual command help topics in the master help.
command-topics-in-master-index: true
Each general topic will show up as a separate topic in the help index along with all the plugin command topics.
general-topics:
Rules:
shortText: Rules of the server
fullText: |
&61. Be kind to your fellow players.
&B2. No griefing.
&D3. No swearing.
permission: topics.rules

Each index topic will show up as a separate sub-index in the help index along with all the plugin command topics.
To override the default help index (displayed when the user executes /help), name the index topic "Default".
index-topics:
Ban Commands:
shortText: Player banning commands
preamble: Moderator - do not abuse these commands
permission: op
commands:
- /ban
- /ban-ip
- /banlist

Topic amendments are used to change the content of automatically generated plugin command topics.
amended-topics:
/stop:
shortText: Stops the server cold....in its tracks!
fullText: <text> - This kills the server.
permission: you.dont.have

Any plugin in the ignored plugins list will be excluded from help. The name must match the name displayed by
the /plugins command. Ignore "Bukkit" to remove the standard bukkit commands from the index. Ignore "All"
to completely disable automatic help topic generation.
ignore-plugins:
- PluginNameOne
- PluginNameTwo
- PluginNameThree

ChestShop

2015-08-11T08:33:10Z

Minedx：修改表格,格式,分类

http://dev.bukkit.org/bukkit-plugins/chestshop/
==使用商店==

*十分简单！右键来购买物品，左键来卖出物品（当然你也可以在配置文件中自定义按键用途！）

==如何创建一个商店==

===普通玩家商店===

*放置一个箱子在地上.
*放置一个在箱子周围一方格的牌子（例如，在箱子上）.
*在牌子上, 书写文字：
*第一行会被插件自动填充
*价格行是用来描述卖出和买进的价格的，你需要一个价格注释在价格的附近比如“B”来描述这是被玩家买的S来描述玩家卖出的，用冒号隔开，可用的序列有： "B 5:5 S", "B 5", "S free"，free指免费
*你可以通过使用/iteminfo命令来得到你手上物品的名字
*
*A person can buy 64 diamonds
*for 10 dollars and sell them back
*for 5 dollars from
*AcrobotPL
*
===管理员商店===
*有无限物品的商店
*确保你安装了插件后有 ChestShop.admin权限，在牌子上第一行加上Admin shop就可以了在config中可以配置。

==翻译==
*右边是玩家自制的翻译列表: [http://dev.bukkit.org/bukkit-plugins/chestshop/pages/translations/ 翻译列表]

==权限节点==
* ChestShop.shop.* 创造和使用商店
* ChestShop.shop.create.* 创造所有商店
* ChestShop.shop.buy 卖任何物品到商店
* ChestShop.shop.sell 从商店买任何物品
* ChestShop.mod 打开和破坏商店箱子
* ChestShop.admin 开启任何商店，破坏，创造管理员商店

==对玩家们有用的提示==

*[http://dev.bukkit.org/bukkit-plugins/chestshop/tickets/629-a-new-technique-for-not-going-bankrupt/ 如何不破产]
*[http://www.mediafire.com/download/82i1ep35ztnie10/Evolve+Gaming+Price+Table+ver6.4.xlsm 可定制的价格表]
*[http://www.mediafire.com/download/7ako58lj8ka9k51/Economy+Tool.rar 备选的价目表]

==完整的插件信息==
*阅览本插件的完整信息,请访问[http://forums.bukkit.org/threads/4150/ Bukkit论坛上本插件的板块].

==本插件报错或您对本插件有建议?==

*请点击[http://dev.bukkit.org/server-mods/chestshop/tickets/?status=+ 此处]提交Bug！

==你是否认为ChestShop能帮助你的服务器?==
*如果你认为插件不错，请力所能及的[https://www.paypal.com/cgi-bin/webscr?return=http%3A%2F%2Fdev.bukkit.org%2Fserver-mods%2Fchestshop%2F&cn=Add+special+instructions+to+the+addon+author%28s%29&business=andrzejp%40dysleksja.pl&bn=PP-DonationsBF%3Abtn_donateCC_LG.gif%3ANonHosted&cancel_return=http%3A%2F%2Fdev.bukkit.org%2Fserver-mods%2Fchestshop%2F&lc=US&item_name=ChestShop+%28iConomyChestShop%29+%28from+Bukkit.org%29&cmd=_donations&rm=1&no_shipping=1&currency_code=USD 捐助作者]:)

ChestShop

2015-08-11T08:29:39Z

Minedx：修改表格修改格式

http://dev.bukkit.org/bukkit-plugins/chestshop/
==使用商店==

十分简单！右键来购买物品，左键来卖出物品（当然你也可以在配置文件中自定义按键用途！）

==如何创建一个商店==

===普通玩家商店===

*放置一个箱子在地上.
*放置一个在箱子周围一方格的牌子（例如，在箱子上）.
*在牌子上, 书写文字：
*第一行会被插件自动填充
*价格行是用来描述卖出和买进的价格的，你需要一个价格注释在价格的附近比如“B”来描述这是被玩家买的S来描述玩家卖出的，用冒号隔开，可用的序列有： "B 5:5 S", "B 5", "S free"，free指免费
*你可以通过使用/iteminfo命令来得到你手上物品的名字
*
*A person can buy 64 diamonds
*for 10 dollars and sell them back
*for 5 dollars from
*AcrobotPL
*
===管理员商店===
*有无限物品的商店
*确保你安装了插件后有 ChestShop.admin权限，在牌子上第一行加上Admin shop就可以了在config中可以配置。

===翻译===

右边是玩家自制的翻译列表: [http://dev.bukkit.org/bukkit-plugins/chestshop/pages/translations/ 翻译列表]

===权限节点===
ChestShop.shop.* 创造和使用商店
ChestShop.shop.create.* 创造所有商店
ChestShop.shop.buy 卖任何物品到商店
ChestShop.shop.sell 从商店买任何物品
ChestShop.mod 打开和破坏商店箱子
ChestShop.admin 开启任何商店，破坏，创造管理员商店

===对玩家们有用的提示===

*[http://dev.bukkit.org/bukkit-plugins/chestshop/tickets/629-a-new-technique-for-not-going-bankrupt/ 如何不破产]
*[http://www.mediafire.com/download/82i1ep35ztnie10/Evolve+Gaming+Price+Table+ver6.4.xlsm 可定制的价格表]
*[http://www.mediafire.com/download/7ako58lj8ka9k51/Economy+Tool.rar 备选的价目表]

===完整的插件信息===
阅览本插件的完整信息,请访问[http://forums.bukkit.org/threads/4150/ Bukkit论坛上本插件的板块].

===本插件报错或您对本插件有建议?===

请点击[http://dev.bukkit.org/server-mods/chestshop/tickets/?status=+ 此处]提交Bug！

===你是否认为ChestShop能帮助你的服务器?===
如果你认为插件不错，请力所能及的[https://www.paypal.com/cgi-bin/webscr?return=http%3A%2F%2Fdev.bukkit.org%2Fserver-mods%2Fchestshop%2F&cn=Add+special+instructions+to+the+addon+author%28s%29&business=andrzejp%40dysleksja.pl&bn=PP-DonationsBF%3Abtn_donateCC_LG.gif%3ANonHosted&cancel_return=http%3A%2F%2Fdev.bukkit.org%2Fserver-mods%2Fchestshop%2F&lc=US&item_name=ChestShop+%28iConomyChestShop%29+%28from+Bukkit.org%29&cmd=_donations&rm=1&no_shipping=1&currency_code=USD 捐助作者]:)

ChestShop

2015-08-11T08:26:03Z

Minedx：本身内容即无图为范例,牌子范例内容无需翻译已编辑完成

http://dev.bukkit.org/bukkit-plugins/chestshop/
==使用商店==

十分简单！右键来购买物品，左键来卖出物品（当然你也可以在配置文件中自定义按键用途！）

==如何创建一个商店==

===普通玩家商店===

放置一个箱子在地上.
放置一个在箱子周围一方格的牌子（例如，在箱子上）.
在牌子上, 书写文字：
第一行会被插件自动填充
价格行是用来描述卖出和买进的价格的，你需要一个价格注释在价格的附近比如“B”来描述这是被玩家买的S来描述玩家卖出的，用冒号隔开，可用的序列有： "B 5:5 S", "B 5", "S free"，free指免费
你可以通过使用/iteminfo命令来得到你手上物品的名字
{| style="color:green;background-color:#ffffcc;" cellpadding="20" cellspacing="0" border="1"
|A person can buy 64 diamonds
|-
|for 10 dollars and sell them back
|-
|for 5 dollars from
|-
|AcrobotPL
|}
===管理员商店===
- 有无限物品的商店
确保你安装了插件后有 ChestShop.admin权限，在牌子上第一行加上Admin shop就可以了在config中可以配置。

===翻译===

右边是玩家自制的翻译列表: [http://dev.bukkit.org/bukkit-plugins/chestshop/pages/translations/ 翻译列表]

===权限节点===
ChestShop.shop.* 创造和使用商店
ChestShop.shop.create.* 创造所有商店
ChestShop.shop.buy 卖任何物品到商店
ChestShop.shop.sell 从商店买任何物品
ChestShop.mod 打开和破坏商店箱子
ChestShop.admin 开启任何商店，破坏，创造管理员商店

===对玩家们有用的提示===

[http://dev.bukkit.org/bukkit-plugins/chestshop/tickets/629-a-new-technique-for-not-going-bankrupt/ 如何不破产]
[http://www.mediafire.com/download/82i1ep35ztnie10/Evolve+Gaming+Price+Table+ver6.4.xlsm 可定制的价格表]
[http://www.mediafire.com/download/7ako58lj8ka9k51/Economy+Tool.rar 备选的价目表]

===完整的插件信息===
阅览本插件的完整信息,请访问[http://forums.bukkit.org/threads/4150/ Bukkit论坛上本插件的板块].

===本插件报错或您对本插件有建议?===

请点击[http://dev.bukkit.org/server-mods/chestshop/tickets/?status=+ 此处]提交Bug！

===你是否认为ChestShop能帮助你的服务器?===
如果你认为插件不错，请力所能及的[https://www.paypal.com/cgi-bin/webscr?return=http%3A%2F%2Fdev.bukkit.org%2Fserver-mods%2Fchestshop%2F&cn=Add+special+instructions+to+the+addon+author%28s%29&business=andrzejp%40dysleksja.pl&bn=PP-DonationsBF%3Abtn_donateCC_LG.gif%3ANonHosted&cancel_return=http%3A%2F%2Fdev.bukkit.org%2Fserver-mods%2Fchestshop%2F&lc=US&item_name=ChestShop+%28iConomyChestShop%29+%28from+Bukkit.org%29&cmd=_donations&rm=1&no_shipping=1&currency_code=USD 捐助作者]:)

MCMMO

2015-08-11T08:08:59Z

Minedx：重定向页面至McMMO

#REDIRECT [[McMMO]]

Mcmmo

2015-08-11T08:08:29Z

Minedx：重定向页面至McMMO

#REDIRECT [[McMMO]]

McMMO

2015-08-11T07:59:20Z

Minedx：

{{待翻译}}
http://dev.bukkit.org/bukkit-plugins/mcmmo/
http://mcmmo.wikia.com/wiki/McMMO_Wiki
https://github.com/mcMMO-Dev/mcMMO

== 来自 bukkit 发布帖的内容==
===McMMO 指令===

说明:

显示简介和完整的指令列表.

输入方法:

/mcmmo [commands]

别名:

无

权限节点:

无

详细内容:

显示简介和完整的指令列表.

====•McStats 指令====

说明:

显示你的 mcMMO 等级和经验.

输入方法:

/mcstats

别名:

/stats

权限节点:

无

详细内容:

显示你的 mcMMO 等级和经验.

===组队指令相关===

====ptp 指令====

说明:

传送到一个组队成员附近.

输入方法:

/ptp [name]

例如:

/ptp nossr50

别名:

无

权限节点:

mcmmo.commands.ptp

详细内容:

你可以输入ptp指令,传送到一个组队成员附近.

====party 指令====

说明:

管理你的组队相关内容

输入方法:

/party 查看队伍详细信息.
/party create <队伍名> <密码> 创建一个队伍.
/party join <队伍名> <密码> 加入一个玩家队伍.
/party invite <玩家名> 邀请一个玩家加入你的队伍.
/party accept <玩家名> 允许一个玩家加入你的队伍.
/party password <密码> 设置你现在拥有队伍的密码.
/party kick <玩家名> 将一个玩家移除队伍.
/party owner <玩家名> 将队伍转让给一个玩家.
/party expshare [无/equal] 设置队伍经验共享.
/party lock 锁定队伍.
/party unlock 解锁队伍.
/party q 离开你目前所在的队伍.
/party ? 关于组队的更多信息.

例如:

/party create CoolGrindersParty pass1234

别名:

无

权限节点:

mcmmo.commands.party

详细内容:

通过party指令，你可以创建一个队伍或加入一个队伍。

====partychat 指令====

说明:

设置组队聊天打开/关闭或发送一条队伍聊天信息.

输入方法:

/partychat [message]

例如:

/pc hello! (译者注:发送一条队伍聊天信息)
/partychat (译者注:设置队伍聊天开关)

别名:

p pc

权限节点:

mcmmo.chat.partychat

详细内容:

通过这个指令,你可以和你的组队成员在你们的私人领域聊天,只有你们自己的组员才能看到这些消息。

===adminchat 指令===

说明:

设置管理员聊天打开/关闭或发送一条队伍聊天信息.

输入方法:

/adminchat /a [message]

别名:

/a
/ac

权限节点:

mcmmo.chat.adminchat

详细内容:

设置管理员聊天打开/关闭或发送一条队伍聊天信息，只有拥有指定权限节点(译者注:权限节点即为mcmmo.chat.adminchat)

===mcrefresh 指令===

说明:

重置某个玩家McMMO的所有冷却时间

输入方法:

/mcrefresh [player]

别名:

无

权限节点:

mcmmo.commands.mcrefresh
mcmmo.commands.mcrefresh.others

详细内容:

With this command, you can refresh your own ability cool downs, or those of the targeted player.

===mcgod 指令===

说明:

McMMO 上帝模式的开关.

输入方法:

/mcgod [player]

别名:

无

权限节点:

mcmmo.commands.mcgod
mcmmo.commands.mcgod.others

详细内容:

你可以用这个指令控制你/其他人McMMO上帝模式的开关,在此模式下你是无敌的.

===xprate 指令===

说明:

设置经验比例或重置经验比例.

输入方法:

/xprate [rate]
/xprate reset

别名:

/mcxprate

权限节点:

mcmmo.commands.xprate.all
mcmmo.commands.xprate
mcmmo.commands.xprate.reset
mcmmo.commands.xprate.set

详细内容:

你可以输入这个指令开启一次McMMO经验加成的活动.例如输入/xprate 2开启一次全体双倍经验的活动！所有人皆享有经验加成！

===mmoedit 指令===

说明:

修改某个玩家的McMMO技能等级.

输入方法:

/mmoedit [player] <skill> <level>

别名:

无

权限节点:

mcmmo.commands.mmoedit
mcmmo.commands.mmoedit.others

详细内容:

这个指令是用来修改玩家某个技能的等级的.输入 /mmoedit nossr50 herbalism 613 会设置玩家 nossr50 的 Herbalism 技能等级为 613.

===addxp 指令===

说明:

向一名玩家增加某技能的经验.

输入方法:

/addxp [player] <skill> <xp>

别名:

无

权限节点:

mcmmo.commands.addxp
mcmmo.commands.addxp.others

详细内容:

这个指令是用来给一名玩家加某个技能的经验的.使用/addxp nossr50 mining 45 会给 nossr50 增加45点 Mining 技能的经验.

===addlevels 指令===

说明:

添加一个玩家的McMMO等级.

输入方法:

/addlevels [player] <技能名> <等级>

别名:

无

权限节点:

mcmmo.commands.addlevels
mcmmo.commands.addlevels.others

详细内容:

这个指令可以用来给某个用户增加技能等级.输入 /addlevels nossr50 acrobatics 12 会在玩家 nossr50 现有的 Acrobatics 等级上加12.

===mcremove 指令===

说明:

将一个用户从数据库移除.

输入方法:

/mcremove [player]

别名:

无

权限节点:

mcmmo.commands.mcremove

详细内容:

这个指令会将玩家从数据库移除.输入 /mcremove nossr50 会将 nossr50 从数据库中移除.

===skillreset 指令===

说明:

重置一个或你全部的mcmmo技能等级.

输入方法:

/skillreset [player] <skill>

别名:

无

权限节点:

mcmmo.commands.skillreset
mcmmo.commands.skillreset.acrobatics mcmmo.commands.skillreset.archery mcmmo.commands.skillreset.axes mcmmo.commands.skillreset.excavation mcmmo.commands.skillreset.fishing mcmmo.commands.skillreset.herbalism mcmmo.commands.skillreset.mining mcmmo.commands.skillreset.others.all mcmmo.commands.skillreset.repair mcmmo.commands.skillreset.smelting mcmmo.commands.skillreset.swords mcmmo.commands.skillreset.taming mcmmo.commands.skillreset.unarmed mcmmo.commands.skillreset.woodcutting

详细内容:

重置一个或你全部的mcmmo技能等级.This command is used to reset a users skill level. Using /skillreset nossr50 herbalism will set nossr50's Herbalism level and experience to 0. Using /skillreset will reset your own stats for every skill.

===mcpurge 指令===

说明:

从服务器数据库中清除0技能等级的用户或者未在几个月内登陆过的用户.

输入方法:

/mcpurge

别名:

无

权限节点:

mcmmo.commands.mcpurge

详细内容:

使用 /mcpurge 会立即在服务器数据库中启动一个清理进程,默认的McMMO设定下会清除一切无作为和6个月内从未连接过服务器的玩家.

===mcconvert 指令===

说明:

从不同的数据库类型和格式类型间转换。

输入方法:

/mcconvert database <flatfile|sql> /mcconvert experience <linear|exponential>

别名:

无

权限节点:

mcmmo.commands.mcconvert

详细内容:

这个指令可以把一个无格式文件转换到MySQL数据库中, 反之亦然. 它也可以把一个不仅合规范的文本变成一个规范的文本.

===mcimport 指令===

说明:

全自动生成插件设置文本.

输入方法:

/mcimport

别名:

无

权限节点:

mcmmo.commands.mcimport

详细内容:

这个指令可以用在从你的Cauldron启动日志中来导入并重生成插件设置,你需要至少1.7.x才能运行这个指令.

创建一个 /mcMMO/mods/ 的文件夹. 将你的Cauldron 1.7+运行日志放到其中并重命名import.log.

注意在系统创建时,最佳状态是每次启动或关闭服务器保存一次日志,或编辑你的日志文件使它只剩下你想导入的内容,这样可以有效加速导入速度.

当服务器在运行时,你使用 /mcimport 时可以在控制台中看到导入进程,当导入完成后它将会全被导出到 /mcMMO/mods/output/.

任何你放在文件夹中但名字不为import.log的设置文件,你需要手动让它们符合标准.

现在你只需要把所有output文件夹中的内容整合起来,然后填入经验收益倍数.

== 来自McMMO Wiki的内容 ==

=== Commands ===
'''Commands''' are simple lines of code used in-game as a way to keep track of various aspects of the plugin that range from general information to in-depth Mcmmo

{| class="toc" id="toc" style=" "
|-
|

{| class="wikitable" style=" height: 235px; width: 630px; "
|-
|Toggle ability notifications on/off.
|-
|/mcremove <playername>

|as
|-
|/mcpurge

|Purges all users from MySQL or FlatFile.
|-
|/a OR /ac

|
Toggles Admin Chat (Not working)
|-
|/xplock <skillname>

|Lock the xp bar to named skill.
|-
|/mcrefresh [player]

|Refreshes all cooldowns for McMMO or optionally named player.(Not Working)
|}
|}
[[Category:Configuration]]
[[Category:Axes]]
[[Category:Commands]]
[[Category:Moderator]]

=== Configuration ===
{{Stub}}

==== MySQL ====
Optional configuration to use a MySQL database instead of the YAML flatfiles. If you intend to use MySQL, make sure you configure all of the parts in this section! MaxConnections and MaxPoolSize can probably be left alone for smaller servers, but a foray into the official MySQL documentation for both would not be discouraged...
MySQL:
Enabled: false # Set to true to enable MySQL
Database:
User_Name: UserName # Username for the mysql server. Usually "root"
User_Password: UserPassword # Password for the mysql server
Name: DataBaseName # The database in which the mcmmo data will be stored
TablePrefix: mcmmo_ # The prefix of each mcmmo table in said database
MaxConnections: # Max number of clients connected to the mysql server.
Misc: 30 # Must be high enough to support multiple sequential logins
Load: 30
Save: 30
MaxPoolSize: # Cached connections that are always held available
Misc: 10
Load: 20
Save: 20
Server:
Port: 3306 # Port of the mysql server
Address: localhost # Address of the mysql server
==== General ====
Miscellaneous settings, used thorough the functionalities.

===== Locale =====
:'''''String''''': This sets the language and locale settings used in the plugin, currently supported values are ''''<nowiki>en_us'</nowiki>''', ''''<nowiki>fi'</nowiki>''', ''''<nowiki>de'</nowiki>''', ''''<nowiki>fr'</nowiki>''', ''''<nowiki>es'</nowiki>''' and ''''<nowiki>pl'</nowiki>'''. Further languages can be implemented, see [[Localization]]. Defaults to ''''<nowiki>en_us'</nowiki>'''.

===== General Features =====

===== Items =====
Items:
Chimaera_Wing:
Enabled: true
Cooldown: 240
Warmup: 5
RecentlyHurt_Cooldown: 60
Prevent_Use_Underground: true
Use_Cost: 1
Recipe_Cost: 5
Item_Name: FEATHER
Sound_Enabled: true

===== Colors =====
Spout:
Menu:

BLUE: 0.75
GREEN: 0.3
RED: 0.3
Taming:
BLUE: 0.75
GREEN: 0.3
RED: 0.3
Acrobatics:
BLUE: 0.75
GREEN: 0.3
RED: 0.3
Border:
BLUE: 0.0
GREEN: 0.0
RED: 0.0
Background:
BLUE: 0.75
GREEN: 0.75
RED: 0.75
Woodcutting:
BLUE: 0.75
GREEN: 0.3
RED: 0.3
Archery:
BLUE: 0.75
GREEN: 0.3
RED: 0.3
Axes:
BLUE: 0.75
GREEN: 0.3
RED: 0.3
Repair:
BLUE: 0.75
GREEN: 0.3
RED: 0.3
Fishing:
BLUE: 0.75
GREEN: 0.3
RED: 0.3
Excavation:
BLUE: 0.75
GREEN: 0.3
RED: 0.3
Herbalism:
BLUE: 0.75
GREEN: 0.3
RED: 0.3
Unarmed:
BLUE: 0.75
GREEN: 0.3
RED: 0.3
Mining:
BLUE: 0.75
GREEN: 0.3
RED: 0.3

===== Experience =====
''Note: Multiplier values are applied inversely. For example to double the amount of xp earned, change the multiplier value from 1.0 to 0.5.''

Experience:
Fishing:
Base: 200
Formula:
Multiplier:
Swords: 0.25
Taming: .5
Acrobatics: .6
Sorcery: .05
Excavation: 0.25
Herbalism: 0.25
Unarmed: .5
Woodcutting: 0.25
Mining: 0.25
Archery: 0.25
Axes: 1.0
Repair: .8
Gains:
Mobspawners:
Enabled: true
Multiplier:
PVP: 1
Global: 0.25
PVP:
Rewards: true
Excavation:
Base: 40
Cake: 3000
Sulphur: 30
Bones: 30
Map: 200
Slimeballs: 100
Bucket: 100
Apple: 100
Mushroom: 80
Eggs: 100
Slowsand: 80
Watch: 200
Web: 150
String: 200
Glowstone: 80
Music: 3000
Diamond: 1000
Cocoa_Beans: 100
Woodcutting:
Birch: 70
Spruce: 80
Pine: 90
Herbalism:
Sugar_Cane: 30
Cactus: 30
Flowers: 100
Pumpkin: 20
Mushrooms: 150
Wheat: 50
Melon: 20
Nether_Wart: 50
Lily_Pads: 100
Vines: 10
Mining:
Sandstone: 30
Glowstone: 30
Lapis: 400
Obsidian: 150
Stone: 30
Netherrack: 30
Gold: 350
Redstone: 150
Coal: 100
Diamond: 750
lapis: 400
Iron: 250

===== Sorcery-What is this? =====
Sorcery:
Spells:
Water: 15
Thunder: 15
Curative: 15
Cure_Self: 15
Mana_Cost: 5
Cure_Other: 15
Mana_Cost:

===== Gathering =====
Excavation:
Drops:
Cocoa_Beans: true
Mushrooms: true
Glowstone: true
Eggs: true
Apples: true
Cake: true
Music: false
Diamond: true
Slowsand: true
Sulphur: true
Netherrack: true
Bones: true
Fishing:
Drops:
Gold_Tools: true
Diamond_Armor: true
Stone_Tools: true
Diamonds: true
Iron_Armor: true
Iron_Tools: true
Diamond_Tools: true
Item_Drops_Enabled: true
Records: true
Blaze_Rod: true
Leather_Armor: true
Drop_Chance:
Tier_1: 15
Tier_2: 20
Tier_3: 25
Tier_4: 30
Tier_5: 30
Gold_Armor: true
Glowstone_Dust: true
Ender_Pearl: true
Wooden_Tools: true

=====Commands=====
Commands:
mctop:
Name: mctop
Enabled: true
addxp:
Name: addxp
Enabled: true
mcability:
Name: mcability
Enabled: true
mcrefresh:
Name: mcrefresh
Enabled: true
mcmmo:
Name: mcmmo
Enabled: true
Donate_Message: true
mcc:
Name: mcc
Enabled: true
mcgod:
Name: mcgod
Enabled: true
stats:
Name: stats
Enabled: true
mmoedit:
Name: mmoedit
Enabled: false
ptp:
Name: ptp
Enabled: true
party:
Name: party
Enabled: tru
myspawn:
Name: myspawn
Enabled: true
whois:
Name: whois
Enabled: true
invite:
Name: invite
Enabled: true
accept:
Name: accept
Enabled: true
clearmyspawn:
Name: clearmyspawn
Enabled: true

=====Abilities=====

=====Skills===
Skills:
Agility:
Level_Cap: 200 #Level cap of 0 for no limit
Range:
Level_Cap: 200
Strength:
Level_Cap: 200
Excavation:
Level_Cap: 200
Requires_Shovel: true
Fishing:
Level_Cap: 100
Herblore:
Level_Cap: 200
Green_Thumb:
Cobble_To_Mossy: true
Mining:
Level_Cap: 200
Requires_Pickaxe: true
Smithing:
Level_Cap: 200
Leather:
ID: 334
String:
Name: Leather
ID: 287
Stone:
Name: Cobblestone
ID: 4
Wood:
Name: Wood Planks
ID: 5
Gold:
Name: Gold Bars
ID: 266
Anvil_Messages: true
Diamond:
Name: Diamond
Level_Required: 50
ID: 264
Iron:
Name: Iron Bars
ID: 265
Attack:
Level_Cap: 200
Summoning:
Level_Cap: 200
Call_Of_The_Wild:
Bones_Required: 10
Defence:
Level_Cap: 200
Woodcutting:
Level_Cap: 200
Requires_Axe: true
[[Category:Configuration]]

=== Localization ===

{{Stub}}
First of all use an archive program like WinRar or 7zip to open up mcMMO.jar and navigate to com\gmail\nossr50\locale\ inside the Jar file. Here you will see a file called locale_en_US.properties this is the localization file for en_US and will be the template for other languages. You can either modify all strings in this file or copy it and start making a new file for localization.

If you want to make a file for another language you would copy locale_en_US.properties and rename the en_US part of it to something else. Then inside mcmmo.properties you will change the localization file setting from en_US to whatever the new files name is. You would have to add your new localization file to the same location in mcMMO.jar that messages_en_US.properties is in. For example, If you were translating mcMMO to Mexican Spanish you would name it es_MX. If you want to know what the correct name for your localization would be you can check the [http://en.wikipedia.org/wiki/ISO_639-1 ISO 639-1 Table]. I'll probably change these files to be located inside your plugins folder in future versions.

Anyways theres a few things you should know about the localization files, they use special words to insert color codes, for example <nowiki>[[GREEN]]</nowiki> will insert the green color code. These are based on the ChatColor bukkit uses found [https://github.com/Bukkit/Bukkit/blob/master/src/main/java/org/bukkit/ChatColor.java in this source file]. So if you want to insert RED used in bukkit, write <nowiki>[[RED]]</nowiki> in the localization file.

If you fully translate mcMMO into another language [[User talk:Nossr50|contact Nossr50]] to get it included into mcMMO.

=== Permissions ===

;Party
: Allows players to enter a party using /party <party name>
: 'mcmmo.commands.party'

;Party Teleport
: Let players use the party teleport command.
: 'mcmmo.commands.ptp'

;Mining Ability
: Allows the use of the [[Mining#Ability|Super Breaker]] ability.
: 'mcmmo.ability.mining'

;Axes Ability
: Allows the use of the [[Axes#Ability|Skull Splitter]] ability.
: 'mcmmo.ability.axes'

;Excavation Ability
: Allows the use of the [[Excavation#Ability|Giga Drill Breaker]] ability.
: 'mcmmo.ability.excavation'

;Swords Ability
: Allows the use of the [[Swords#Ability|Serrated Strike]] ability.
: 'mcmmo.ability.swords'

;Unarmed Ability
: Allows the use of the [[Unarmed#Ability|Beserk]] ability.
: 'mcmmo.ability.unarmed'

====[[:Category:Skills|Skills]]====
;All Skills
: Allows access to all of the skills. Recommended.
: 'mcmmo.skills.*'

;Mining
: Allows the use of the [[Mining]] skill.
: 'mcmmo.skills.mining'

;Woodcutting
: Allows the use of the [[Woodcutting]] skill.
: 'mcmmo.skills.woodcutting'

;Repair
: Allows the use of the [[Repair]] skill.
: 'mcmmo.skills.repair'

;Unarmed
: Allows the use of the [[Unarmed]] skill.
: 'mcmmo.skills.unarmed'

;Archery
: Allows the use of the [[Archery]] skill.
: 'mcmmo.skills.archery'

;Herbalism
: Allows the use of the [[Herbalism]] skills.
: 'mcmmo.skills.herbalism'

;Excavation
: Allows the use of the [[Excavation]] skill.
: 'mcmmo.skills.excavation'

;Swords
: Allows the use of the [[Swords]] skill.
: 'mcmmo.skills.swords'

;Acrobatics
: Allows the use of the [[Acrobatics]] skill.
: 'mcmmo.skills.acrobatics'

;Axes
: Allows the use of the [[Axes]] skill.
: 'mcmmo.skills.axes'.

;Taming
: Allows the use of the [[Taming]] skill.
: 'mcmmo.skills.taming'.

;
;

=== API ===
The mcMMO API is a new utility to mcMMO. It is used with the new events system, to make it easy. 
The basic syntax goes like this: 

<div style="background: #DDD;">
package packagename; import com.gmail.nossr50.events.McMMOPlayerLevelUpEvent; public class MyListener implements Listener { 
@EventHandler public void onPlayerLevelUp(McMMOPlayerLevelUpEvent event) { Player player = event.getPlayer(); SkillType skill = event.getSkill(); }
 }
</div>

That would be your Listener class. Now, you just add this line into your public void onEnable():<div style="background: #DDD;">
Bukkit.getServer().getPluginManager().registerEvents(new MyListener(this), this);
</div>

From there you can extend and add more features. :D
[[Category:API]]

=== Compatible Software ===
[[File:ZombiePigmanFace.png|right|zombie pig man]]
These plugins are plugins that are either add extra functions to McMMO (i.e. Money2Xp allows the purchase of experience through iConomy) or a web page that display stats or features to a web page.
====WS:====
[http://forums.bukkit.org/threads/info-web-ws-v0-2-web-stat-page-for-mcmmo-740.15315/ WS] is a simple WebStat page for McMMo. It is currently updated for [http://bukkit.org bukkit] build #740 and is compatible with McMMO V1.0.05 or later (because it uses mySQL). The respective topic on the [http://forums.bukkit.org bukkit forums] can be found [http://forums.bukkit.org/threads/info-web-ws-v0-2-web-stat-page-for-mcmmo-740.15315/ here] .
====McMMO Web Stats:====
mcMMO Web Stats is a simple PHP page you can link to directly or include in an existing page to display the mcMMO stats of every player on your server. Think of it like a character sheet for your players. It's respective [http://forums.bukkit.org bukkit forum] topic can be found [http://forums.bukkit.org/threads/info-web-mcmmo-web-stats-v1-1-a-web-based-view-of-your-mcmmo-stats-0-556.9815/ here]. It is confirmed to be compatible with McMMO V0.9.2 and later.

====Money2Xp:====
[http://forums.bukkit.org/threads/mech-econ-money2xp-v0-2-3-train-your-mcmmo-skills-using-money-now-with-zones-740.11831/ Money2Xp] is a slightly complicated (but very clever) plugin that allows the purchase of McMMO skill experience, with support for the [http://forums.bukkit.org/threads/econ-iconomy-5-0-eruanna-602-740.40/ iConomy] and [http://forums.bukkit.org/threads/econ-boseconomy-v0-6-2-simple-server-economy-714.4874/ BOSEconomy] plugins. It also requires the [http://forums.bukkit.org/threads/admn-dev-permissions-v2-7-2-phoenix-now-with-real-multiworld-permissions-740.5974/ Permissions] plugin and a McMMO version of 1.0 or later. It is currently updated for [http://bukkit.org bukkit] build #740 and the forum topic can be found [http://forums.bukkit.org/threads/mech-econ-money2xp-v0-2-3-train-your-mcmmo-skills-using-money-now-with-zones-740.11831/ here] .

:) discontinued
:

====VirtualChest:====
[http://forums.bukkit.org/threads/gen-mech-virtualchest-3-6-1-have-a-chest-with-you-everywhere-iconomy-5-0-4-6-permissions-740.11695/ VirtualChest] is not a plugin that adapts or adds an existing feature - it is "A Virtual Chest is a chest that can't be accessed in the "physical world of minecraft" - there is no block, nothing", with added support for McMMO parties (more than one player may access it if they are in an McMMO party). The [http://forums.bukkit.org bukkit forum] topic can be found [http://forums.bukkit.org/threads/gen-mech-virtualchest-3-6-1-have-a-chest-with-you-everywhere-iconomy-5-0-4-6-permissions-740.11695/ here], and the plugin is currently updated for bukkit build #740.

=== Admin Video ===
在Wiki上未编辑

=== Source Code ===
https://github.com/mcMMO-Dev/mcMMO

McMMO

2015-08-11T07:58:12Z

Minedx：搬运 McMMO Wikia

http://dev.bukkit.org/bukkit-plugins/mcmmo/

== 来自 bukkit 发布帖的内容==
===McMMO 指令===

说明:

显示简介和完整的指令列表.

输入方法:

/mcmmo [commands]

别名:

无

权限节点:

无

详细内容:

显示简介和完整的指令列表.

====•McStats 指令====

说明:

显示你的 mcMMO 等级和经验.

输入方法:

/mcstats

别名:

/stats

权限节点:

无

详细内容:

显示你的 mcMMO 等级和经验.

===组队指令相关===

====ptp 指令====

说明:

传送到一个组队成员附近.

输入方法:

/ptp [name]

例如:

/ptp nossr50

别名:

无

权限节点:

mcmmo.commands.ptp

详细内容:

你可以输入ptp指令,传送到一个组队成员附近.

====party 指令====

说明:

管理你的组队相关内容

输入方法:

/party 查看队伍详细信息.
/party create <队伍名> <密码> 创建一个队伍.
/party join <队伍名> <密码> 加入一个玩家队伍.
/party invite <玩家名> 邀请一个玩家加入你的队伍.
/party accept <玩家名> 允许一个玩家加入你的队伍.
/party password <密码> 设置你现在拥有队伍的密码.
/party kick <玩家名> 将一个玩家移除队伍.
/party owner <玩家名> 将队伍转让给一个玩家.
/party expshare [无/equal] 设置队伍经验共享.
/party lock 锁定队伍.
/party unlock 解锁队伍.
/party q 离开你目前所在的队伍.
/party ? 关于组队的更多信息.

例如:

/party create CoolGrindersParty pass1234

别名:

无

权限节点:

mcmmo.commands.party

详细内容:

通过party指令，你可以创建一个队伍或加入一个队伍。

====partychat 指令====

说明:

设置组队聊天打开/关闭或发送一条队伍聊天信息.

输入方法:

/partychat [message]

例如:

/pc hello! (译者注:发送一条队伍聊天信息)
/partychat (译者注:设置队伍聊天开关)

别名:

p pc

权限节点:

mcmmo.chat.partychat

详细内容:

通过这个指令,你可以和你的组队成员在你们的私人领域聊天,只有你们自己的组员才能看到这些消息。

===adminchat 指令===

说明:

设置管理员聊天打开/关闭或发送一条队伍聊天信息.

输入方法:

/adminchat /a [message]

别名:

/a
/ac

权限节点:

mcmmo.chat.adminchat

详细内容:

设置管理员聊天打开/关闭或发送一条队伍聊天信息，只有拥有指定权限节点(译者注:权限节点即为mcmmo.chat.adminchat)

===mcrefresh 指令===

说明:

重置某个玩家McMMO的所有冷却时间

输入方法:

/mcrefresh [player]

别名:

无

权限节点:

mcmmo.commands.mcrefresh
mcmmo.commands.mcrefresh.others

详细内容:

With this command, you can refresh your own ability cool downs, or those of the targeted player.

===mcgod 指令===

说明:

McMMO 上帝模式的开关.

输入方法:

/mcgod [player]

别名:

无

权限节点:

mcmmo.commands.mcgod
mcmmo.commands.mcgod.others

详细内容:

你可以用这个指令控制你/其他人McMMO上帝模式的开关,在此模式下你是无敌的.

===xprate 指令===

说明:

设置经验比例或重置经验比例.

输入方法:

/xprate [rate]
/xprate reset

别名:

/mcxprate

权限节点:

mcmmo.commands.xprate.all
mcmmo.commands.xprate
mcmmo.commands.xprate.reset
mcmmo.commands.xprate.set

详细内容:

你可以输入这个指令开启一次McMMO经验加成的活动.例如输入/xprate 2开启一次全体双倍经验的活动！所有人皆享有经验加成！

===mmoedit 指令===

说明:

修改某个玩家的McMMO技能等级.

输入方法:

/mmoedit [player] <skill> <level>

别名:

无

权限节点:

mcmmo.commands.mmoedit
mcmmo.commands.mmoedit.others

详细内容:

这个指令是用来修改玩家某个技能的等级的.输入 /mmoedit nossr50 herbalism 613 会设置玩家 nossr50 的 Herbalism 技能等级为 613.

===addxp 指令===

说明:

向一名玩家增加某技能的经验.

输入方法:

/addxp [player] <skill> <xp>

别名:

无

权限节点:

mcmmo.commands.addxp
mcmmo.commands.addxp.others

详细内容:

这个指令是用来给一名玩家加某个技能的经验的.使用/addxp nossr50 mining 45 会给 nossr50 增加45点 Mining 技能的经验.

===addlevels 指令===

说明:

添加一个玩家的McMMO等级.

输入方法:

/addlevels [player] <技能名> <等级>

别名:

无

权限节点:

mcmmo.commands.addlevels
mcmmo.commands.addlevels.others

详细内容:

这个指令可以用来给某个用户增加技能等级.输入 /addlevels nossr50 acrobatics 12 会在玩家 nossr50 现有的 Acrobatics 等级上加12.

===mcremove 指令===

说明:

将一个用户从数据库移除.

输入方法:

/mcremove [player]

别名:

无

权限节点:

mcmmo.commands.mcremove

详细内容:

这个指令会将玩家从数据库移除.输入 /mcremove nossr50 会将 nossr50 从数据库中移除.

===skillreset 指令===

说明:

重置一个或你全部的mcmmo技能等级.

输入方法:

/skillreset [player] <skill>

别名:

无

权限节点:

mcmmo.commands.skillreset
mcmmo.commands.skillreset.acrobatics mcmmo.commands.skillreset.archery mcmmo.commands.skillreset.axes mcmmo.commands.skillreset.excavation mcmmo.commands.skillreset.fishing mcmmo.commands.skillreset.herbalism mcmmo.commands.skillreset.mining mcmmo.commands.skillreset.others.all mcmmo.commands.skillreset.repair mcmmo.commands.skillreset.smelting mcmmo.commands.skillreset.swords mcmmo.commands.skillreset.taming mcmmo.commands.skillreset.unarmed mcmmo.commands.skillreset.woodcutting

详细内容:

重置一个或你全部的mcmmo技能等级.This command is used to reset a users skill level. Using /skillreset nossr50 herbalism will set nossr50's Herbalism level and experience to 0. Using /skillreset will reset your own stats for every skill.

===mcpurge 指令===

说明:

从服务器数据库中清除0技能等级的用户或者未在几个月内登陆过的用户.

输入方法:

/mcpurge

别名:

无

权限节点:

mcmmo.commands.mcpurge

详细内容:

使用 /mcpurge 会立即在服务器数据库中启动一个清理进程,默认的McMMO设定下会清除一切无作为和6个月内从未连接过服务器的玩家.

===mcconvert 指令===

说明:

从不同的数据库类型和格式类型间转换。

输入方法:

/mcconvert database <flatfile|sql> /mcconvert experience <linear|exponential>

别名:

无

权限节点:

mcmmo.commands.mcconvert

详细内容:

这个指令可以把一个无格式文件转换到MySQL数据库中, 反之亦然. 它也可以把一个不仅合规范的文本变成一个规范的文本.

===mcimport 指令===

说明:

全自动生成插件设置文本.

输入方法:

/mcimport

别名:

无

权限节点:

mcmmo.commands.mcimport

详细内容:

这个指令可以用在从你的Cauldron启动日志中来导入并重生成插件设置,你需要至少1.7.x才能运行这个指令.

创建一个 /mcMMO/mods/ 的文件夹. 将你的Cauldron 1.7+运行日志放到其中并重命名import.log.

注意在系统创建时,最佳状态是每次启动或关闭服务器保存一次日志,或编辑你的日志文件使它只剩下你想导入的内容,这样可以有效加速导入速度.

当服务器在运行时,你使用 /mcimport 时可以在控制台中看到导入进程,当导入完成后它将会全被导出到 /mcMMO/mods/output/.

任何你放在文件夹中但名字不为import.log的设置文件,你需要手动让它们符合标准.

现在你只需要把所有output文件夹中的内容整合起来,然后填入经验收益倍数.

== 来自McMMO Wiki的内容 ==

=== Commands ===
'''Commands''' are simple lines of code used in-game as a way to keep track of various aspects of the plugin that range from general information to in-depth Mcmmo

{| class="toc" id="toc" style=" "
|-
|

{| class="wikitable" style=" height: 235px; width: 630px; "
|-
|Toggle ability notifications on/off.
|-
|/mcremove <playername>

|as
|-
|/mcpurge

|Purges all users from MySQL or FlatFile.
|-
|/a OR /ac

|
Toggles Admin Chat (Not working)
|-
|/xplock <skillname>

|Lock the xp bar to named skill.
|-
|/mcrefresh [player]

|Refreshes all cooldowns for McMMO or optionally named player.(Not Working)
|}
|}
[[Category:Configuration]]
[[Category:Axes]]
[[Category:Commands]]
[[Category:Moderator]]

=== Configuration ===
{{Stub}}

==== MySQL ====
Optional configuration to use a MySQL database instead of the YAML flatfiles. If you intend to use MySQL, make sure you configure all of the parts in this section! MaxConnections and MaxPoolSize can probably be left alone for smaller servers, but a foray into the official MySQL documentation for both would not be discouraged...
MySQL:
Enabled: false # Set to true to enable MySQL
Database:
User_Name: UserName # Username for the mysql server. Usually "root"
User_Password: UserPassword # Password for the mysql server
Name: DataBaseName # The database in which the mcmmo data will be stored
TablePrefix: mcmmo_ # The prefix of each mcmmo table in said database
MaxConnections: # Max number of clients connected to the mysql server.
Misc: 30 # Must be high enough to support multiple sequential logins
Load: 30
Save: 30
MaxPoolSize: # Cached connections that are always held available
Misc: 10
Load: 20
Save: 20
Server:
Port: 3306 # Port of the mysql server
Address: localhost # Address of the mysql server
==== General ====
Miscellaneous settings, used thorough the functionalities.

===== Locale =====
:'''''String''''': This sets the language and locale settings used in the plugin, currently supported values are ''''<nowiki>en_us'</nowiki>''', ''''<nowiki>fi'</nowiki>''', ''''<nowiki>de'</nowiki>''', ''''<nowiki>fr'</nowiki>''', ''''<nowiki>es'</nowiki>''' and ''''<nowiki>pl'</nowiki>'''. Further languages can be implemented, see [[Localization]]. Defaults to ''''<nowiki>en_us'</nowiki>'''.

===== General Features =====

===== Items =====
Items:
Chimaera_Wing:
Enabled: true
Cooldown: 240
Warmup: 5
RecentlyHurt_Cooldown: 60
Prevent_Use_Underground: true
Use_Cost: 1
Recipe_Cost: 5
Item_Name: FEATHER
Sound_Enabled: true

===== Colors =====
Spout:
Menu:

BLUE: 0.75
GREEN: 0.3
RED: 0.3
Taming:
BLUE: 0.75
GREEN: 0.3
RED: 0.3
Acrobatics:
BLUE: 0.75
GREEN: 0.3
RED: 0.3
Border:
BLUE: 0.0
GREEN: 0.0
RED: 0.0
Background:
BLUE: 0.75
GREEN: 0.75
RED: 0.75
Woodcutting:
BLUE: 0.75
GREEN: 0.3
RED: 0.3
Archery:
BLUE: 0.75
GREEN: 0.3
RED: 0.3
Axes:
BLUE: 0.75
GREEN: 0.3
RED: 0.3
Repair:
BLUE: 0.75
GREEN: 0.3
RED: 0.3
Fishing:
BLUE: 0.75
GREEN: 0.3
RED: 0.3
Excavation:
BLUE: 0.75
GREEN: 0.3
RED: 0.3
Herbalism:
BLUE: 0.75
GREEN: 0.3
RED: 0.3
Unarmed:
BLUE: 0.75
GREEN: 0.3
RED: 0.3
Mining:
BLUE: 0.75
GREEN: 0.3
RED: 0.3

===== Experience =====
''Note: Multiplier values are applied inversely. For example to double the amount of xp earned, change the multiplier value from 1.0 to 0.5.''

Experience:
Fishing:
Base: 200
Formula:
Multiplier:
Swords: 0.25
Taming: .5
Acrobatics: .6
Sorcery: .05
Excavation: 0.25
Herbalism: 0.25
Unarmed: .5
Woodcutting: 0.25
Mining: 0.25
Archery: 0.25
Axes: 1.0
Repair: .8
Gains:
Mobspawners:
Enabled: true
Multiplier:
PVP: 1
Global: 0.25
PVP:
Rewards: true
Excavation:
Base: 40
Cake: 3000
Sulphur: 30
Bones: 30
Map: 200
Slimeballs: 100
Bucket: 100
Apple: 100
Mushroom: 80
Eggs: 100
Slowsand: 80
Watch: 200
Web: 150
String: 200
Glowstone: 80
Music: 3000
Diamond: 1000
Cocoa_Beans: 100
Woodcutting:
Birch: 70
Spruce: 80
Pine: 90
Herbalism:
Sugar_Cane: 30
Cactus: 30
Flowers: 100
Pumpkin: 20
Mushrooms: 150
Wheat: 50
Melon: 20
Nether_Wart: 50
Lily_Pads: 100
Vines: 10
Mining:
Sandstone: 30
Glowstone: 30
Lapis: 400
Obsidian: 150
Stone: 30
Netherrack: 30
Gold: 350
Redstone: 150
Coal: 100
Diamond: 750
lapis: 400
Iron: 250

===== Sorcery-What is this? =====
Sorcery:
Spells:
Water: 15
Thunder: 15
Curative: 15
Cure_Self: 15
Mana_Cost: 5
Cure_Other: 15
Mana_Cost:

===== Gathering =====
Excavation:
Drops:
Cocoa_Beans: true
Mushrooms: true
Glowstone: true
Eggs: true
Apples: true
Cake: true
Music: false
Diamond: true
Slowsand: true
Sulphur: true
Netherrack: true
Bones: true
Fishing:
Drops:
Gold_Tools: true
Diamond_Armor: true
Stone_Tools: true
Diamonds: true
Iron_Armor: true
Iron_Tools: true
Diamond_Tools: true
Item_Drops_Enabled: true
Records: true
Blaze_Rod: true
Leather_Armor: true
Drop_Chance:
Tier_1: 15
Tier_2: 20
Tier_3: 25
Tier_4: 30
Tier_5: 30
Gold_Armor: true
Glowstone_Dust: true
Ender_Pearl: true
Wooden_Tools: true

=====Commands=====
Commands:
mctop:
Name: mctop
Enabled: true
addxp:
Name: addxp
Enabled: true
mcability:
Name: mcability
Enabled: true
mcrefresh:
Name: mcrefresh
Enabled: true
mcmmo:
Name: mcmmo
Enabled: true
Donate_Message: true
mcc:
Name: mcc
Enabled: true
mcgod:
Name: mcgod
Enabled: true
stats:
Name: stats
Enabled: true
mmoedit:
Name: mmoedit
Enabled: false
ptp:
Name: ptp
Enabled: true
party:
Name: party
Enabled: tru
myspawn:
Name: myspawn
Enabled: true
whois:
Name: whois
Enabled: true
invite:
Name: invite
Enabled: true
accept:
Name: accept
Enabled: true
clearmyspawn:
Name: clearmyspawn
Enabled: true

=====Abilities=====

=====Skills===
Skills:
Agility:
Level_Cap: 200 #Level cap of 0 for no limit
Range:
Level_Cap: 200
Strength:
Level_Cap: 200
Excavation:
Level_Cap: 200
Requires_Shovel: true
Fishing:
Level_Cap: 100
Herblore:
Level_Cap: 200
Green_Thumb:
Cobble_To_Mossy: true
Mining:
Level_Cap: 200
Requires_Pickaxe: true
Smithing:
Level_Cap: 200
Leather:
ID: 334
String:
Name: Leather
ID: 287
Stone:
Name: Cobblestone
ID: 4
Wood:
Name: Wood Planks
ID: 5
Gold:
Name: Gold Bars
ID: 266
Anvil_Messages: true
Diamond:
Name: Diamond
Level_Required: 50
ID: 264
Iron:
Name: Iron Bars
ID: 265
Attack:
Level_Cap: 200
Summoning:
Level_Cap: 200
Call_Of_The_Wild:
Bones_Required: 10
Defence:
Level_Cap: 200
Woodcutting:
Level_Cap: 200
Requires_Axe: true
[[Category:Configuration]]

=== Localization ===

{{Stub}}
First of all use an archive program like WinRar or 7zip to open up mcMMO.jar and navigate to com\gmail\nossr50\locale\ inside the Jar file. Here you will see a file called locale_en_US.properties this is the localization file for en_US and will be the template for other languages. You can either modify all strings in this file or copy it and start making a new file for localization.

If you want to make a file for another language you would copy locale_en_US.properties and rename the en_US part of it to something else. Then inside mcmmo.properties you will change the localization file setting from en_US to whatever the new files name is. You would have to add your new localization file to the same location in mcMMO.jar that messages_en_US.properties is in. For example, If you were translating mcMMO to Mexican Spanish you would name it es_MX. If you want to know what the correct name for your localization would be you can check the [http://en.wikipedia.org/wiki/ISO_639-1 ISO 639-1 Table]. I'll probably change these files to be located inside your plugins folder in future versions.

Anyways theres a few things you should know about the localization files, they use special words to insert color codes, for example <nowiki>[[GREEN]]</nowiki> will insert the green color code. These are based on the ChatColor bukkit uses found [https://github.com/Bukkit/Bukkit/blob/master/src/main/java/org/bukkit/ChatColor.java in this source file]. So if you want to insert RED used in bukkit, write <nowiki>[[RED]]</nowiki> in the localization file.

If you fully translate mcMMO into another language [[User talk:Nossr50|contact Nossr50]] to get it included into mcMMO.

=== Permissions ===

;Party
: Allows players to enter a party using /party <party name>
: 'mcmmo.commands.party'

;Party Teleport
: Let players use the party teleport command.
: 'mcmmo.commands.ptp'

;Mining Ability
: Allows the use of the [[Mining#Ability|Super Breaker]] ability.
: 'mcmmo.ability.mining'

;Axes Ability
: Allows the use of the [[Axes#Ability|Skull Splitter]] ability.
: 'mcmmo.ability.axes'

;Excavation Ability
: Allows the use of the [[Excavation#Ability|Giga Drill Breaker]] ability.
: 'mcmmo.ability.excavation'

;Swords Ability
: Allows the use of the [[Swords#Ability|Serrated Strike]] ability.
: 'mcmmo.ability.swords'

;Unarmed Ability
: Allows the use of the [[Unarmed#Ability|Beserk]] ability.
: 'mcmmo.ability.unarmed'

====[[:Category:Skills|Skills]]====
;All Skills
: Allows access to all of the skills. Recommended.
: 'mcmmo.skills.*'

;Mining
: Allows the use of the [[Mining]] skill.
: 'mcmmo.skills.mining'

;Woodcutting
: Allows the use of the [[Woodcutting]] skill.
: 'mcmmo.skills.woodcutting'

;Repair
: Allows the use of the [[Repair]] skill.
: 'mcmmo.skills.repair'

;Unarmed
: Allows the use of the [[Unarmed]] skill.
: 'mcmmo.skills.unarmed'

;Archery
: Allows the use of the [[Archery]] skill.
: 'mcmmo.skills.archery'

;Herbalism
: Allows the use of the [[Herbalism]] skills.
: 'mcmmo.skills.herbalism'

;Excavation
: Allows the use of the [[Excavation]] skill.
: 'mcmmo.skills.excavation'

;Swords
: Allows the use of the [[Swords]] skill.
: 'mcmmo.skills.swords'

;Acrobatics
: Allows the use of the [[Acrobatics]] skill.
: 'mcmmo.skills.acrobatics'

;Axes
: Allows the use of the [[Axes]] skill.
: 'mcmmo.skills.axes'.

;Taming
: Allows the use of the [[Taming]] skill.
: 'mcmmo.skills.taming'.

;
;

=== API ===
The mcMMO API is a new utility to mcMMO. It is used with the new events system, to make it easy. 
The basic syntax goes like this: 

<div style="background: #DDD;">
package packagename; import com.gmail.nossr50.events.McMMOPlayerLevelUpEvent; public class MyListener implements Listener { 
@EventHandler public void onPlayerLevelUp(McMMOPlayerLevelUpEvent event) { Player player = event.getPlayer(); SkillType skill = event.getSkill(); }
 }
</div>

That would be your Listener class. Now, you just add this line into your public void onEnable():<div style="background: #DDD;">
Bukkit.getServer().getPluginManager().registerEvents(new MyListener(this), this);
</div>

From there you can extend and add more features. :D
[[Category:API]]

=== Compatible Software ===
[[File:ZombiePigmanFace.png|right|zombie pig man]]
These plugins are plugins that are either add extra functions to McMMO (i.e. Money2Xp allows the purchase of experience through iConomy) or a web page that display stats or features to a web page.
====WS:====
[http://forums.bukkit.org/threads/info-web-ws-v0-2-web-stat-page-for-mcmmo-740.15315/ WS] is a simple WebStat page for McMMo. It is currently updated for [http://bukkit.org bukkit] build #740 and is compatible with McMMO V1.0.05 or later (because it uses mySQL). The respective topic on the [http://forums.bukkit.org bukkit forums] can be found [http://forums.bukkit.org/threads/info-web-ws-v0-2-web-stat-page-for-mcmmo-740.15315/ here] .
====McMMO Web Stats:====
mcMMO Web Stats is a simple PHP page you can link to directly or include in an existing page to display the mcMMO stats of every player on your server. Think of it like a character sheet for your players. It's respective [http://forums.bukkit.org bukkit forum] topic can be found [http://forums.bukkit.org/threads/info-web-mcmmo-web-stats-v1-1-a-web-based-view-of-your-mcmmo-stats-0-556.9815/ here]. It is confirmed to be compatible with McMMO V0.9.2 and later.

====Money2Xp:====
[http://forums.bukkit.org/threads/mech-econ-money2xp-v0-2-3-train-your-mcmmo-skills-using-money-now-with-zones-740.11831/ Money2Xp] is a slightly complicated (but very clever) plugin that allows the purchase of McMMO skill experience, with support for the [http://forums.bukkit.org/threads/econ-iconomy-5-0-eruanna-602-740.40/ iConomy] and [http://forums.bukkit.org/threads/econ-boseconomy-v0-6-2-simple-server-economy-714.4874/ BOSEconomy] plugins. It also requires the [http://forums.bukkit.org/threads/admn-dev-permissions-v2-7-2-phoenix-now-with-real-multiworld-permissions-740.5974/ Permissions] plugin and a McMMO version of 1.0 or later. It is currently updated for [http://bukkit.org bukkit] build #740 and the forum topic can be found [http://forums.bukkit.org/threads/mech-econ-money2xp-v0-2-3-train-your-mcmmo-skills-using-money-now-with-zones-740.11831/ here] .

:) discontinued
:

====VirtualChest:====
[http://forums.bukkit.org/threads/gen-mech-virtualchest-3-6-1-have-a-chest-with-you-everywhere-iconomy-5-0-4-6-permissions-740.11695/ VirtualChest] is not a plugin that adapts or adds an existing feature - it is "A Virtual Chest is a chest that can't be accessed in the "physical world of minecraft" - there is no block, nothing", with added support for McMMO parties (more than one player may access it if they are in an McMMO party). The [http://forums.bukkit.org bukkit forum] topic can be found [http://forums.bukkit.org/threads/gen-mech-virtualchest-3-6-1-have-a-chest-with-you-everywhere-iconomy-5-0-4-6-permissions-740.11695/ here], and the plugin is currently updated for bukkit build #740.

=== Admin Video ===
在Wiki上未编辑

=== Source Code ===
https://github.com/mcMMO-Dev/mcMMO

McMMO

2015-08-11T03:26:43Z

Minedx：McMMO Bukkit发布帖翻译已完成

http://dev.bukkit.org/bukkit-plugins/mcmmo/

==McMMO 指令==

说明:

显示简介和完整的指令列表.

输入方法:

/mcmmo [commands]

别名:

无

权限节点:

无

详细内容:

显示简介和完整的指令列表.

===•McStats 指令===

说明:

显示你的 mcMMO 等级和经验.

输入方法:

/mcstats

别名:

/stats

权限节点:

无

详细内容:

显示你的 mcMMO 等级和经验.

==组队指令相关==

===ptp 指令===

说明:

传送到一个组队成员附近.

输入方法:

/ptp [name]

例如:

/ptp nossr50

别名:

无

权限节点:

mcmmo.commands.ptp

详细内容:

你可以输入ptp指令,传送到一个组队成员附近.

===party 指令===

说明:

管理你的组队相关内容

输入方法:

/party 查看队伍详细信息.
/party create <队伍名> <密码> 创建一个队伍.
/party join <队伍名> <密码> 加入一个玩家队伍.
/party invite <玩家名> 邀请一个玩家加入你的队伍.
/party accept <玩家名> 允许一个玩家加入你的队伍.
/party password <密码> 设置你现在拥有队伍的密码.
/party kick <玩家名> 将一个玩家移除队伍.
/party owner <玩家名> 将队伍转让给一个玩家.
/party expshare [无/equal] 设置队伍经验共享.
/party lock 锁定队伍.
/party unlock 解锁队伍.
/party q 离开你目前所在的队伍.
/party ? 关于组队的更多信息.

例如:

/party create CoolGrindersParty pass1234

别名:

无

权限节点:

mcmmo.commands.party

详细内容:

通过party指令，你可以创建一个队伍或加入一个队伍。

===partychat 指令===

说明:

设置组队聊天打开/关闭或发送一条队伍聊天信息.

输入方法:

/partychat [message]

例如:

/pc hello! (译者注:发送一条队伍聊天信息)
/partychat (译者注:设置队伍聊天开关)

别名:

p pc

权限节点:

mcmmo.chat.partychat

详细内容:

通过这个指令,你可以和你的组队成员在你们的私人领域聊天,只有你们自己的组员才能看到这些消息。

==adminchat 指令==

说明:

设置管理员聊天打开/关闭或发送一条队伍聊天信息.

输入方法:

/adminchat /a [message]

别名:

/a
/ac

权限节点:

mcmmo.chat.adminchat

详细内容:

设置管理员聊天打开/关闭或发送一条队伍聊天信息，只有拥有指定权限节点(译者注:权限节点即为mcmmo.chat.adminchat)

==mcrefresh 指令==

说明:

重置某个玩家McMMO的所有冷却时间

输入方法:

/mcrefresh [player]

别名:

无

权限节点:

mcmmo.commands.mcrefresh
mcmmo.commands.mcrefresh.others

详细内容:

With this command, you can refresh your own ability cool downs, or those of the targeted player.

==mcgod 指令==

说明:

McMMO 上帝模式的开关.

输入方法:

/mcgod [player]

别名:

无

权限节点:

mcmmo.commands.mcgod
mcmmo.commands.mcgod.others

详细内容:

你可以用这个指令控制你/其他人McMMO上帝模式的开关,在此模式下你是无敌的.

==xprate 指令==

说明:

设置经验比例或重置经验比例.

输入方法:

/xprate [rate]
/xprate reset

别名:

/mcxprate

权限节点:

mcmmo.commands.xprate.all
mcmmo.commands.xprate
mcmmo.commands.xprate.reset
mcmmo.commands.xprate.set

详细内容:

你可以输入这个指令开启一次McMMO经验加成的活动.例如输入/xprate 2开启一次全体双倍经验的活动！所有人皆享有经验加成！

==mmoedit 指令==

说明:

修改某个玩家的McMMO技能等级.

输入方法:

/mmoedit [player] <skill> <level>

别名:

无

权限节点:

mcmmo.commands.mmoedit
mcmmo.commands.mmoedit.others

详细内容:

这个指令是用来修改玩家某个技能的等级的.输入 /mmoedit nossr50 herbalism 613 会设置玩家 nossr50 的 Herbalism 技能等级为 613.

==addxp 指令==

说明:

向一名玩家增加某技能的经验.

输入方法:

/addxp [player] <skill> <xp>

别名:

无

权限节点:

mcmmo.commands.addxp
mcmmo.commands.addxp.others

详细内容:

这个指令是用来给一名玩家加某个技能的经验的.使用/addxp nossr50 mining 45 会给 nossr50 增加45点 Mining 技能的经验.

==addlevels 指令==

说明:

添加一个玩家的McMMO等级.

输入方法:

/addlevels [player] <技能名> <等级>

别名:

无

权限节点:

mcmmo.commands.addlevels
mcmmo.commands.addlevels.others

详细内容:

这个指令可以用来给某个用户增加技能等级.输入 /addlevels nossr50 acrobatics 12 会在玩家 nossr50 现有的 Acrobatics 等级上加12.

==mcremove 指令==

说明:

将一个用户从数据库移除.

输入方法:

/mcremove [player]

别名:

无

权限节点:

mcmmo.commands.mcremove

详细内容:

这个指令会将玩家从数据库移除.输入 /mcremove nossr50 会将 nossr50 从数据库中移除.

==skillreset 指令==

说明:

重置一个或你全部的mcmmo技能等级.

输入方法:

/skillreset [player] <skill>

别名:

无

权限节点:

mcmmo.commands.skillreset
mcmmo.commands.skillreset.acrobatics mcmmo.commands.skillreset.archery mcmmo.commands.skillreset.axes mcmmo.commands.skillreset.excavation mcmmo.commands.skillreset.fishing mcmmo.commands.skillreset.herbalism mcmmo.commands.skillreset.mining mcmmo.commands.skillreset.others.all mcmmo.commands.skillreset.repair mcmmo.commands.skillreset.smelting mcmmo.commands.skillreset.swords mcmmo.commands.skillreset.taming mcmmo.commands.skillreset.unarmed mcmmo.commands.skillreset.woodcutting

详细内容:

重置一个或你全部的mcmmo技能等级.This command is used to reset a users skill level. Using /skillreset nossr50 herbalism will set nossr50's Herbalism level and experience to 0. Using /skillreset will reset your own stats for every skill.

==mcpurge 指令==

说明:

从服务器数据库中清除0技能等级的用户或者未在几个月内登陆过的用户.

输入方法:

/mcpurge

别名:

无

权限节点:

mcmmo.commands.mcpurge

详细内容:

使用 /mcpurge 会立即在服务器数据库中启动一个清理进程,默认的McMMO设定下会清除一切无作为和6个月内从未连接过服务器的玩家.

==mcconvert 指令==

说明:

从不同的数据库类型和格式类型间转换。

输入方法:

/mcconvert database <flatfile|sql> /mcconvert experience <linear|exponential>

别名:

无

权限节点:

mcmmo.commands.mcconvert

详细内容:

这个指令可以把一个无格式文件转换到MySQL数据库中, 反之亦然. 它也可以把一个不仅合规范的文本变成一个规范的文本.

==mcimport 指令==

说明:

全自动生成插件设置文本.

输入方法:

/mcimport

别名:

无

权限节点:

mcmmo.commands.mcimport

详细内容:

这个指令可以用在从你的Cauldron启动日志中来导入并重生成插件设置,你需要至少1.7.x才能运行这个指令.

创建一个 /mcMMO/mods/ 的文件夹. 将你的Cauldron 1.7+运行日志放到其中并重命名import.log.

注意在系统创建时,最佳状态是每次启动或关闭服务器保存一次日志,或编辑你的日志文件使它只剩下你想导入的内容,这样可以有效加速导入速度.

当服务器在运行时,你使用 /mcimport 时可以在控制台中看到导入进程,当导入完成后它将会全被导出到 /mcMMO/mods/output/.

任何你放在文件夹中但名字不为import.log的设置文件,你需要手动让它们符合标准.

现在你只需要把所有output文件夹中的内容整合起来,然后填入经验收益倍数.

McMMO

2015-08-10T15:45:34Z

Minedx：skillreset mark

{{待搬运}}
http://dev.bukkit.org/bukkit-plugins/mcmmo/

==McMMO 指令==

说明:

显示简介和完整的指令列表.

输入方法:

/mcmmo [commands]

别名:

无

权限节点:

无

详细内容:

显示简介和完整的指令列表.

===•McStats 指令===

说明:

显示你的 mcMMO 等级和经验.

输入方法:

/mcstats

别名:

/stats

权限节点:

无

详细内容:

显示你的 mcMMO 等级和经验.

==组队指令相关==

===ptp 指令===

说明:

传送到一个组队成员附近.

输入方法:

/ptp [name]

例如:

/ptp nossr50

别名:

无

权限节点:

mcmmo.commands.ptp

详细内容:

你可以输入ptp指令,传送到一个组队成员附近.

===party 指令===

说明:

管理你的组队相关内容

输入方法:

/party 查看队伍详细信息.
/party create <队伍名> <密码> 创建一个队伍.
/party join <队伍名> <密码> 加入一个玩家队伍.
/party invite <玩家名> 邀请一个玩家加入你的队伍.
/party accept <玩家名> 允许一个玩家加入你的队伍.
/party password <密码> 设置你现在拥有队伍的密码.
/party kick <玩家名> 将一个玩家移除队伍.
/party owner <玩家名> 将队伍转让给一个玩家.
/party expshare [无/equal] 设置队伍经验共享.
/party lock 锁定队伍.
/party unlock 解锁队伍.
/party q 离开你目前所在的队伍.
/party ? 关于组队的更多信息.

例如:

/party create CoolGrindersParty pass1234

别名:

无

权限节点:

mcmmo.commands.party

详细内容:

通过party指令，你可以创建一个队伍或加入一个队伍。

===partychat 指令===

说明:

设置组队聊天打开/关闭或发送一条队伍聊天信息.

输入方法:

/partychat [message]

例如:

/pc hello! (译者注:发送一条队伍聊天信息)
/partychat (译者注:设置队伍聊天开关)

别名:

p pc

权限节点:

mcmmo.chat.partychat

详细内容:

通过这个指令,你可以和你的组队成员在你们的私人领域聊天,只有你们自己的组员才能看到这些消息。

==adminchat 指令==

说明:

设置管理员聊天打开/关闭或发送一条队伍聊天信息.

输入方法:

/adminchat /a [message]

别名:

/a
/ac

权限节点:

mcmmo.chat.adminchat

详细内容:

设置管理员聊天打开/关闭或发送一条队伍聊天信息，只有拥有指定权限节点(译者注:权限节点即为mcmmo.chat.adminchat)

==mcrefresh 指令==

说明:

重置某个玩家McMMO的所有冷却时间

输入方法:

/mcrefresh [player]

别名:

无

权限节点:

mcmmo.commands.mcrefresh
mcmmo.commands.mcrefresh.others

详细内容:

With this command, you can refresh your own ability cool downs, or those of the targeted player.

==mcgod 指令==

说明:

McMMO 上帝模式的开关.

输入方法:

/mcgod [player]

别名:

无

权限节点:

mcmmo.commands.mcgod
mcmmo.commands.mcgod.others

详细内容:

你可以用这个指令控制你/其他人McMMO上帝模式的开关,在此模式下你是无敌的.

==xprate 指令==

说明:

设置经验比例或重置经验比例.

输入方法:

/xprate [rate]
/xprate reset

别名:

/mcxprate

权限节点:

mcmmo.commands.xprate.all
mcmmo.commands.xprate
mcmmo.commands.xprate.reset
mcmmo.commands.xprate.set

详细内容:

你可以输入这个指令开启一次McMMO经验加成的活动.例如输入/xprate 2开启一次全体双倍经验的活动！所有人皆享有经验加成！

==mmoedit 指令==

说明:

修改某个玩家的McMMO技能等级.

输入方法:

/mmoedit [player] <skill> <level>

别名:

无

权限节点:

mcmmo.commands.mmoedit
mcmmo.commands.mmoedit.others

详细内容:

这个指令是用来修改玩家某个技能的等级的.输入 /mmoedit nossr50 herbalism 613 会设置玩家 nossr50 的 Herbalism 技能等级为 613.

==addxp 指令==

说明:

向一名玩家增加某技能的经验.

输入方法:

/addxp [player] <skill> <xp>

别名:

无

权限节点:

mcmmo.commands.addxp
mcmmo.commands.addxp.others

详细内容:

这个指令是用来给一名玩家加某个技能的经验的.使用/addxp nossr50 mining 45 会给 nossr50 增加45点 Mining 技能的经验.

==addlevels 指令==

说明:

添加一个玩家的McMMO等级.

输入方法:

/addlevels [player] <技能名> <等级>

别名:

无

权限节点:

mcmmo.commands.addlevels
mcmmo.commands.addlevels.others

详细内容:

这个指令可以用来给某个用户增加技能等级.输入 /addlevels nossr50 acrobatics 12 会在玩家 nossr50 现有的 Acrobatics 等级上加12.

==mcremove 指令==

说明:

将一个用户从数据库移除.

输入方法:

/mcremove [player]

别名:

无

权限节点:

mcmmo.commands.mcremove

详细内容:

这个指令会将玩家从数据库移除.输入 /mcremove nossr50 会将 nossr50 从数据库中移除.

•skillreset Command

说明:

Reset the level of one or all of your skills.

输入方法:

/skillreset [player] <skill>

别名:

无

权限节点:

mcmmo.commands.skillreset
mcmmo.commands.skillreset.acrobatics mcmmo.commands.skillreset.archery mcmmo.commands.skillreset.axes mcmmo.commands.skillreset.excavation mcmmo.commands.skillreset.fishing mcmmo.commands.skillreset.herbalism mcmmo.commands.skillreset.mining mcmmo.commands.skillreset.others.all mcmmo.commands.skillreset.repair mcmmo.commands.skillreset.smelting mcmmo.commands.skillreset.swords mcmmo.commands.skillreset.taming mcmmo.commands.skillreset.unarmed mcmmo.commands.skillreset.woodcutting

详细内容:

This command is used to reset a users skill level. Using /skillreset nossr50 herbalism will set nossr50's Herbalism level and experience to 0. Using /skillreset will reset your own stats for every skill.

==•mcpurge Command==

说明:

Purge users with 0 powerlevel and/or who haven't connected in several months from the server DB.

输入方法:

/mcpurge

别名:

无

权限节点:

mcmmo.commands.mcpurge

详细内容:

Using /mcpurge will immediately start a purge run using the settings in the config file. By default mcMMO will purge all powerless users and users who haven't connected in the last 6 months.

==•mcconvert Command==

说明:

Convert between different database and formula types.

输入方法:

/mcconvert database <flatfile|sql> /mcconvert experience <linear|exponential>

别名:

无

权限节点:

mcmmo.commands.mcconvert

详细内容:

This command can be used to convert a flatfile database to MySQL, or the other way round. It is also used to convert from a linear XP formula to an exponential shaped formula curve.

==• mcimport Command==

说明:

Automagically generate mod config files, ready to be filled in.

输入方法:

/mcimport

别名:

无

权限节点:

mcmmo.commands.mcimport

详细内容:

This command can be used to import and generate mod config files from your Cauldron server's startup log. You need to use at least 1.7.x for this to work.

Create a folder called import inside /mcMMO/mods/. Place your latest Cauldron 1.7+ startup log in this folder and rename it to import.log.

It is worth noting that it's advisable to create a short log by starting and stopping the server once, or by manually editing the log file to only include material mapping in order to speed up the import process.

When the server is running, use the command /mcimport. You will see the import progress in the console, once it is done the files are created in /mcMMO/mods/output/.

Any item that wasn't recognised gets placed in a .unknown.yml config file, you need to handle these manually.

Now you should have a whole bunch of "empty" mod config files and you just need to fill in the XP gains.

PermissionsEX

2015-07-20T04:59:46Z

Minedx：/* Permissions Inheritance Rules */

{{待翻译}}
{{Bukkit Plugin Infobox
|插件名=PermissonEX(PEX)
|版本=v1.23.1
|前置插件=无
|兼容服务端版本=1.8.1
|網址=http://dev.bukkit.org/bukkit-plugins/permissionsex/
}}
=概述=
==介绍==
PermissionsEx (PEX) 是一个新的权限（组）, 基于权限组和它的所有功能. 但是PEX插件能做到更多！它提供了各式各样有力的后台和游戏内管理方式, 很好的限制了一些玩家对于服务器的修改.

==现有特性==
版本V1.21开始支持UUID
不同的存储方式。目前的存储方式有:文本存储(YAML),数据库存储(MySQL，SQLite)。当然,也支持你自己添加！
YAML存储方式,对于新手,最容易配置的方式,所有玩家的信息都存储在 permission.yml 文件里面,缺点:后期读取可能出现卡顿。
SQL存储方式,对于有一定基础的人,推荐此方式，目前支持MySQL和SQLite，其他的数据库(如Postgre)也是可以的。PEX会自动创建数据库的表单。这就说明了,你只需要设置好PEX如何连接到数据库，剩余的你就只需要看着PEX自己完成了。
简明的构架和API接口，如果你对编程有一定了解，那么你可以改变很多。
全面的指令，你可以在游戏里/控制台，做到你想做的任何事情。指令列表看下文。
多世界 - 你可以设置一个玩家在某个世界的单独权限，比如在世界A不能破坏，在世界B不能拾取等等。(设置个别方块等权限,见下文)
权限组的继承，用户可以继承组的权限,组也可以继承组的权限，并且可以选择继承他们的权限、前缀、后缀。
权限的表达方式，这说明,如果你习惯于GroupManager,你也不用担心更换权限插件之后的不习惯。例子: - essentials.fly 这个权限就是允许玩家使用/fly指令
多世界权限继承，你可以继承不同世界的权限。也可以在不同世界继承不同的权限。
良好的优化，当你拥有大量用户的时候,你会发现没有延迟！
排行榜,你可以设置权限组的排列顺序
计时权限!你可以使用指令给玩家添加一个时限权限！注意:当服务端重启,或者崩溃将会失效。
V1.21.1版本开始 PEX支持自动更新,不过并不是跨阶段的更新,只支持BUG修复等更新,防止出现大更新,没有备份而导致文件丢失(V1.21.1→V1.21.2 而不是 V1.21.1 →V1.22.1),当然你也可以在config.yml文件中关闭更新。
Bukkit权限的兼容
禁用错误报告,在插件文件夹目录下创建一个文件,名为'report-disable'。

=进阶权限管理=
===权限的继承 ===

很多服务器配置了多个权限组, 添加权限要各组分别添加. 权限继承可以服务器管理最大限度的减少每一组重复的节点数量.

这里假定您已经完成了基本教程，如还没有，请看基础权限知识，不然的话不能保证您能明白这里的每一步.

实际上，使用了基本教程中的案例，你会发现Member, VIP 和Moderator组都有共同的节点 , modifyworld.* .这里不需要使用继承.

===权限继承规则===

当继承需要处理,PEX会遵循下列规则:

对玩家的设置(前缀,后缀,权限节点,etc.)拥有比组更高的优先权.
设置给一个组的玩家权限在当玩家个人设置生效前被组中任意玩家继承.
Permission nodes are evaluated in order of the inheritance tree (see The Inheritance Tree for details)
A group set to inherit from another group will inherit everything (this includes other inheritance directives!) from the source group, not just permissions. For example, if you have group B inheriting from group A, and group A is set to inherit from group B, PEX will follow the inheritance chain on group A, which is set to inherit from B, which inherits from A, and so on. Watch for this, it will cause a loop that will crash PEX.

===Converting Existing Groups To Use Inheritance ===

Converting an existing group to use inheritance is easy with the pex group parents set command.

Convert the VIP and Moderator groups

pex group VIP parents set Member
pex group Moderator parents set VIP
Remove the redundant nodes

pex group VIP remove modifyworld.*
pex group Moderator remove modifyworld.*
At this point, the VIP and Moderator groups still have the same access as before as the VIP group inherits the modifyworld.* node from the Member group while adding the -modifyworld.mobtarget.monster.creeper node, and the Moderator group inherits it's nodes from the VIP group (including the nodes it inherited from the Member group) while adding the -modifyworld.mobtarget.* node.

The relevant portion of the permissions file now looks like this:

Member:
prefix: '&0(&8M&7ember&0)&7 '
permissions:
- modifyworld.*
options:
rank: '900'
VIP:
prefix: '&0(&eVIP&0)&7 '
inheritance:
- Member
permissions:
- -modifyworld.mobtarget.monster.creeper
options:
rank: '800'
Moderator:
prefix: '&0(&1Moderator&0)&7 '
inheritance:
- VIP
permissions:
- -modifyworld.mobtarget.*
options:
rank: '100'
It's not a large reduction with this example, but if a server has multiple groups with a dozen or more nodes in common with the groups, the file size savings can be considerable.

This inheritance can also be applied at a world level for servers with multiple worlds. See the Multiworld inheritance section page for more.

===The Inheritance Tree===

(Thanks goes to aviator14 for use of these nodes)

Due to the way PEX deals with file backends, it may help to view inheritance as a tree. For example, we have the following permission nodes:

Guest:
prefix: '&7'
default: true
permissions: []
Player:
prefix: '&f'
default: false
permissions:
- generic.user.permissions
- -multiverse.access.world_creative
- -multiverse.portal.access.end
- multiverse.access.*
- multiverse.core.coord
- multiverse.core.info
- multiverse.core.list.who
- multiverse.portal.access.*
inheritance:
- Guest
Donator:
prefix: '&5'
permissions:
- generic.donor.permissions
- multiverse.access.world_creative
inheritance:
- Player
Supporter:
prefix: '&6'
permissions:
- more.generic.donor.permissons
- multiverse.portal.access.end
inheritance:
- Donator
Moderator:
prefix: '&d'
permissions:
- generic.moderator.permissions
inheritance:
- Player
ModD:
prefix: '&d'
permissions: []
inheritance:
- Moderator
- Donator
ModS:
prefix: '&d'
permissions: []
inheritance:
- Moderator
- Supporter
The original forum post these nodes came from was asking why the ModD group was not getting the multiverse.portal.access.end node it was inheriting from the Donator group. Well, the reason for this is because of the way PEX evaluates nodes in a file backend and the inheritance tree.

An abbreviated version of the tree for the ModD group is this:

ModD permissions (none)
Moderator (generic.moderator.permissions) which inherits from Player
Player (which has -multiverse.access.world_creative among others) and inherits from Guest
Guest (no permissions)
Donator (generic.donor.permissions, multiverse portal access node) which inherits from Player
Player (which has -multiverse.access.world_creative among others) and inherits from Guest
Guest (no permissions)
In this case, the issue was due to the Moderator tree being evaluated first, which finds the negation node for multiverse and stops looking. If the Donator tree was listed first (which was the suggested fix), PEX would follow that inheritance tree first, which has the multiverse permissions, and allow access to that node.

===Regular Expressions (regex)===

Regular Expressions, also known as regex or regexp, is a way to 'match' strings of text, such as particular characters, words, or patterns of characters. PEX supports a subset of regex in it's permission node checks.

PEX supports open and closed parentheses ( ) for grouping, curly braces { } for pattern matching, a pipe | for "or", and a dash - for through (as in numbers 1 through 5).

WARNING: If you have any nodes that use these characters then you MUST either put the line in quotes or escape with a backslash the character. If you do not, PEX may mistake the character as an attempt to use a regex, causing a Java error and rendering your permissions useless!

To use it, place the conditions/keywords and/or id numbers in a group, separated by a pipe or a dash if wanting to cover multiple numbers in a sequence.

If this is confusing, worry not. There is a reason why several technical book publishers sell books dedicated to regular expressions. Fortunately, for the purposes of PEX and permission nodes, it's much simpler to deal with, especially with examples of it in action.

Assume that you have a group that you don't want opening the following:

Dispensers ('dispenser', or 23)
Chests ('chest', or 54)
Furnaces ('furnace', or 61 unlit and 'burning_furnance', or 62 lit)
Jukeboxes ('jukebox', or 84)
Remember to check your use-material-names node setting.

You could have a set of nodes like this:

- -modifyworld.blocks.interact.dispenser
- -modifyworld.blocks.interact.chest
- -modifyworld.blocks.interact.furnace
- -modifyworld.blocks.interact.burning_furnace
- -modifyworld.blocks.interact.jukebox
However, this is unnecessary. Using the regex support in PEX, you can combine the nodes into a single line: - -modifyworld.blocks.interact.(dispenser|chest|burning_furnace|furnace|jukebox) - -modifyworld.blocks.interact.(23|54|61|62|84) (for use-material-names: false)

If you wanted to keep a group from destroying stone (1), grass (2), dirt (3), and cobblestone (4), you can use modifyworld.blocks.destroy.(1-4)

You can also use 'or' on other parts of the node.

Keeping with the previous example, adding the ability to place the blocks looks like modifyworld.blocks.(destroy|place).(1-4) Adding sand (12) to this example, you could use modifyworld.blocks.(destroy|place).(1-4|12)

Adding this to a group, such as the default group, is as simple as using the pex group <group> add <node> command.

pex group default add modifyworld.blocks.(destroy|place).(1-4|12)
Any extra nodes can be removed with the pex group <group> remove <node> command. See Commands for more on the add/remove commands.

For advanced users, users can place a $ character directly in front of the node (after any other flag characters) to prevent PEX from performing regex escaping of . and *, so that they behave as normal regex characters rather than their function as delimiters in permissions nodes (escaped by default for backwards compatibility and user sanity)

As you can see, the ability to use regex in permissions can save a lot of typing.

File Back-end Example

In the interest of completeness, this is the full permissions file after the inheritance and regex commands listed above. This example assume use-material-names: false in your plugins/Modifyworld/config.yml file.

groups:
default:
default: true
options:
rank: '1000'
permissions:
- modifyworld.chat
- modifyworld.blocks.(destroy|place).(1-4|12)
Member:
prefix: '&0(&8M&7ember&0)&7 '
permissions:
- modifyworld.*
options:
rank: '900'
VIP:
prefix: '&0(&eVIP&0)&7 '
inheritance:
- Member
permissions:
- -modifyworld.mobtarget.monster.creeper
options:
rank: '800'
Moderator:
prefix: '&0(&1Moderator&0)&7 '
inheritance:
- VIP
permissions:
- -modifyworld.mobtarget.*
options:
rank: '100'
Admins:
prefix: '&0(&4Admins&0)&7 '
permissions:
- -modifyworld.mobtarget.*
- modifyworld.*
- permissions.*
options:
rank: '1'
users:
AnotherPlayer:
group:
- default
YourPlayerName:
group:
- Admins
===Multiworld===[[Multiworld]]

Having several maps (or worlds) on a server is a common way to offer more than one game play experience. However, not all commands are suitable for all worlds. You wouldn't want a hardcore survival world to have access to the give command, but it may be perfectly fine, if not required, in a world intended for free building. Fortunately, limiting a permission node to a specific world is easy with PEX by specifying the world when adding the permission node.

Assume the following server setup:

A survival world with Nether and End worlds (named survival, survival_nether, and survival_the_end respectively)
A free build world (named freebuild)
A group (pvp) that has the ability to build in the survival world only (modifyworld.*)
A group (build) that has the ability to build in the survival and free build world (modifyworld.*)
See Modifyworld page for details on block placement permission nodes.

The commands to set this up are:

/pex group pvp add modifyworld.* survival (add build permissions to the survival world for the pvp group)
/pex group build add modifyworld.* freebuild (add build permissions to the freebuild world for the build group)
/pex group build parents set pvp (Set the build group to inherit the permission to build in the survival world)
Keep in mind that if you edit/add the multiworld lines into the permissions file by hand, make sure the name you use matches the one used in the bukkit configs and what is on the server, capitalization matters here!

The resulting permissions will look like this in the file back-end:

groups:
pvp:
permissions:
worlds:
survival:
permissions:
- modifyworld.*
build:
inheritance:
- pvp
permissions:
worlds:
freebuild:
permissions:
- modifyworld.*
===Multiworld inheritance===

You may have noticed the flaw in this setup, which is neither group had permission to build in the Nether and End worlds. This can be corrected in two ways:

Add the modifyworld.* node to each world individually
Set up world-level inheritance using /pex world <world> inherit <parentWorlds> /pex world pvp_nether inherit pvp /pex world pvp_the_end inherit pvp
These commands look like the following in the file back-end:

worlds:
pvp_nether:
inheritance:
- pvp
pvp_the_end:
inheritance:
- pvp

=Backends=
原帖是这么说的
PermissionsEx provides several backends to store permissions data. This page (will explain) explains them all.
（PEX插件提供了一些用于保存权限数据的后台，这个页面会解释所有）
但其实这个页面只有这一句话（或许是服务器问题）
所以请等待更新。

=基础的权限设定=
==权限节点的基本添加和否定 ==
PEX插件有一个普遍原则，就是权限运行命令是不允许的，除非这个权限节点是具体列出的. 对于那些可以被默认（default）操作的事件和命令, PEX插件可以拒绝访问那些被否定的节点.

使用一个可以拒绝访问节点就像用 pex group <group> add <node>（最基本的权限给予命令）命令那样简单. 使用同样的命令，只在权限节点前加一个负号（-）即可.

举个例子 /give 和 /plugins 命令是水桶客户端的一部分（基本命令）

/give 命令有一个权限节点 command.give 这个命令一般限制在ops.txt列出的人使用（管理员命令）
/plugins 命令也有个权限节点 command.plugins 它可以被服务器中任何人使用。
我们可以试试对于某个权限组增加和否定这两个节点:

如果允许某个权限组使用/give, 就可以输入命令 pex group 组别名 add bukkit.command.give
不允许某个权限组使用 /plugins, 这时候的命令就为 pex group 组别名 add -bukkit.command.plugins

===重要的关于*的信息 ===
PEX插件允许使用XXX*来给予XXX下的所有的分权限节点，但是呢，在使用这个前，''你必须要明白它怎么工作以及会造成什么效果''。一开始浏览的时候，这看上去很简单，给一个权限组“*”使它可以访问所有的权限节点，但是这也可能会导致你给了你不想要给这个权限组的权限。例如，在插件VanishNoPacket（简称VNP）中，它提供了一个权限vanish.silentjoin，使得所有的用户在登入时都不会显示加入公告，这是大多数服务器主人都不想要的效果。实际上这也可以用否定节点来简单解决（否定节点优先），任何给默认组使用的权限节点都能被否定以“关闭功能”

===重要的后台文件 ===
如果你要在后台修改编辑权限的话，请阅读并遵守以下规则:
权限必须以一个空格或者负号开始
- modifyworld.chat 和 - -modifyworld.mobtarget.*是在后台文件中有效的（格式正确）。
modifyworld.chat 和 -modifyworld.mobtarget.* 在后台文件中无效（格式不正确，无空格或负号）。
所有在YAML文件中的格式规则在PEX插件基本文件中必须被遵守，错误的文件会使得PEX插件无法启动，然后把log文件塞满错误信息。
PEX插件用自上而下的方式来检查用户和组别的权限节点，就像网络防火墙一样，如果它找到了一个与它想找的匹配的节点，它就会停止寻找，这就意味着在现实中，如果一个权限给了主要组别和它所有的子组别，它在看到允许的权限后就会停止寻找而忽略否定节点。
我们举个错误的例子

default:
options:
default: true
permissions:
- modifyworld.*
- -modifyworld.blocks.interact.23
用这样的权限节点文件，如果一个玩家想要打开一个发射器（ID 23），它第一个会匹配到modifyworld.*节点然后停止，以至于允许玩家打开！（实际上第二个权限节点是不允许这样的事情发生的。

不过，如果把这两行互换，-modifyworld.blocks.interact.23在modifyworld.*之前，玩家会被拒绝访问发射器（插件先检测到-modifyworld.blocks.interact.23节点）如果一个玩家想要打开一个熔炉（ID 61）插件就会检测到modifyworld.*节点，然后认为是modifyworld.blocks.interact.61节点，使得玩家可以打开。

==上机操作==

先来试试基本的权限指令和插件基本功能（以下作为教程实例并且推荐各服务器使用。）
创建五个组别个组别：Default，Member，VIP,Mod,Admin。
"Default" 可以聊天但是不可以改动任何东西，没有称号
"Member"信任的玩家组别，可以改动世界，拥有称号 ("&0(&8M&7ember&0)&7 ")
"VIP" 可以改动世界还可以不受到苦力怕的烦恼（这个VIP棒）！并且拥有称号"&0(&eVIP&0)&7 ".
A "Mod" 可以不受到任何怪物的困扰（万岁！）.
An "Admin" (管理员) 是超级用户，可以使用这个插件的所有功能并且拥有炫酷的称号比如 "&0(&4Admin&0)&7 ".
可选: 去除 modifyworld.* 权限从 "Default" 权限组中
可选: 添加 modifyworld.chat 权限到 "Default" 权限组里
是时候测试环境了

===准备===
安装PEX插件（放在插件目录下）

开启服务器.

打开浏览器控制台（租借，后台服务器的话）

在浏览器中打开PEX插件的配置文件

===开始基础及基本权限 ===
这些命令必须在控制台输入

创建一个Admin权限组（pex group admin create命令）

把 permissions.* 权限加入到组别中（pex group Admin add pressions.*命令）
把你自己加入组中（pex user 你的游戏名 group set Admin）, 其中你的游戏名是你在游戏内的ID名.
可选的:给自己所有权限不管自己是不是在拥有permissions.*权限的权限组里

====如果你不想（不能）在控制台输入====
创建一个permissions.yml文件输入以下文字，并上传（放置）到PEX插件的目录，请确保你的格式是正确的！看上面的YAML后台信息的帮助。

groups:
Default:
options:
default: true
permissions:

modifyworld.* Admin: options: prefix: '&0(&4Admin&0)&7 ' permissions:
permissions.* users:你的用户名: group:
Admin permissions:
permissions.*
是时候创建其他组别了

===创建其他组别: Member, VIP, Mod ===

使用这个命令创建Member组 /pex group Member create
使用这个命令创建VIP组 /pex group VIP create
使用这个命令创建Mod组 /pex group Mod create
接下来我们要标注这几个组别的阶级使得符合这样的顺序 Member -> VIP -> Mod -> Admin.看阶级页面以知道更多

===设置阶级 ===
输入以下命令
/pex group default set rank 1000
/pex group Member set rank 900
/pex group VIP set rank 800
/pex group Mod set rank 100
/pex group Admin set rank 1
阶级100是最高提升的阶级数。

升级和降级命令都会在游戏内收到限制 (但在控制台不会). 在游戏中，你不可以:

把一个低于你阶级的升到你的阶级 (Mod到Admin, 用前面的例子)
把一个阶级高于你的降到低于你的阶级(Admin到Mod,用前面的例子)
不能对于你同样阶级的升降级 (Mob不能对Mob操作，Admin不能对Admin操作。)
如果你在游戏内（只是举个例子）是Admin，想要把一个玩家提高到你一样的阶级必须使用/pex user PlayerName group set Admin.

在控制台，你很自由可以不受以上限制。

===炫酷的滑板鞋!(好吧只是称号吗)===
使用以下命令
/pex group Member prefix "&0(&8M&7ember&0)&7 "
/pex group VIP prefix "&0(&eVIP&0)&7 "
/pex group Mod prefix "&0(&1Mod&0)&7 "
/pex group Admin prefix "&0(&4Admin&0)&7 "
确保在每个称号后面都加上了个空格，这可以阻止称号和用户名混在一起在聊天中。实际上，后缀前也是因为同样的理由加一个空格为好。还有一种可以显示前缀后缀的方法就是前缀后缀相同（只需把prefix变成suffix就行）。

===给每个组别添加权限 ===
注意: 如果你还没有允许这些组别修改世界，那么删除modifiyworld.*这一步是不需要的.

可选的: /pex group default remove modifyworld.*
可选的: /pex group default add modifyworld.chat (Only needed if modifyworld.* has been removed)
/pex group Member add modifyworld.*
/pex group VIP add modifyworld.*
/pex group VIP add -modifyworld.mobtarget.monster.creeper
/pex group Mod add modifyworld.*
/pex group Mod add -modifyworld.mobtarget.*
/pex group Admin add permissions.*
/pex group Admin add modifyworld.*
/pex group Admin add -modifyworld.mobtarget.*
来看看成果吧！

===见证奇迹！===

你想要改变你的权限组的话，使用这个命令 /pex user 玩家名 group set 权限组名，接下来就测试啦！

Default

验证你可以聊天
验证你有正确的前缀在聊天时
验证你可以在出生点外破坏方块
注意: 如果你把modifyworld.* 节点之前移除了，就不能破坏（之前是可选项）
如果你可以破坏但是modifyworld.* 节点被移除了！, 找到个爬行者然后拥抱它！ (别担心，它保证对你没兴趣但是你伤得了它)
Member

验证你可以聊天
验证你有正确的前缀在聊天时
验证你可以在出生点外破坏方块
VIP

验证你可以聊天
验证你有正确的前缀在聊天时
验证你可以在出生点外破坏方块
如果你可以破坏但是modifyworld.* 节点被移除了！, 找到个爬行者然后拥抱它！ (别担心，它保证对你没兴趣但是你伤得了它)
Admin

验证你可以聊天
验证你有正确的前缀在聊天时
验证你可以在出生点外破坏方块 (如果你把玩家名字放在了OP文件中，并且在PEX插件配置config文档里把allowOps设置为了true，你将可以在出生点附近破坏).
验证你可以使用PEX插件所有命令(使用/pex reload命令测试，它应该会回复 "Permissions Reloaded（权限重新加载）")
验证所有怪物都对你没兴趣
下一步你可以换一个玩家作为“实验对象”比如加入游戏的好基友(这是为了科学！!)

===测试阶级 ===

首先使用/pex user 另一个玩家 group set default
验证升降级别命令有效使用/pex promote 前面你移动的那个玩家. 你会看见 "User AnotherPlayer promoted to NextGroup（这个玩家到了下个组别）"
一直使用这个命令直到出现 "Promotion error: User is not promotable（升级错误，用户不允许）". 使用 /pex user 这个玩家命令会显示:
playername are member of:
Mod (rank 100 @ default)
playername's permissions:
-modifyworld.mobtarget.* (from Mod)
modifyworld.* (from Mod)
playername's options:
降级和升级一样，只不过把命令中的promote变成demote
如果那个玩家只是个机器人, 如果你想的话，使用这个命令把它删掉 /pex user 玩家名 delete
如果那个玩家是真人，确保每个组别都正常工作（看上机教程最前面。）

===后台文件案例===
如果你成功了上面那个案例，你就会发现后台文件变成了这样。很具有参考性:

groups:
default:
options:
rank: '1000'
default: true
permissions:
- modifyworld.chat
Member:
permissions:
- modifyworld.*
options:
rank: '900'
prefix: '&0(&8M&7ember&0)&7 '
VIP:
permissions:
- -modifyworld.mobtarget.monster.creeper
- modifyworld.*
options:
rank: '800'
prefix: '&0(&eVIP&0)&7 '
Mod:
permissions:
- -modifyworld.mobtarget.*
- modifyworld.*
options:
rank: '100'
prefix: '&0(&1Mod&0)&7 '
Admin:
permissions:
- -modifyworld.mobtarget.*
- modifyworld.*
- permissions.*
options:
rank: '1'
prefix: '&0(&4Admin&0)&7 '
users:
AnotherPlayer:
group:
- default
YourPlayerName:
group:
- Admin
这就是被解析后的文件的样子，但是最好使用YAML编写工具来确保你的文件已经正确，不然插件可能会出所有类别的错误！

{
"users": {
"AnotherPlayer": {
"group": [
"default"
]
},
"YourPlayerName": {
"group": [
"Admin"
]
}
},
"groups": {
"default": {
"options": {
"default": true,
"rank": "1000"
},
"permissions": [
"modifyworld.chat"
]
},
"Member": {
"options": {
"prefix": "&0(&8M&7ember&0)&7 ",
"rank": "900"
},
"permissions": [
"modifyworld.*"
]
},
"VIP": {
"options": {
"prefix": "&0(&eVIP&0)&7 ",
"rank": "800"
},
"permissions": [
"-modifyworld.mobtarget.monster.creeper",
"modifyworld.*"
]
},
"Mod": {
"options": {
"prefix": "&0(&1Mod&0)&7 ",
"rank": "100"
},
"permissions": [
"-modifyworld.mobtarget.*",
"modifyworld.*"
]
},
"Admin": {
"options": {
"prefix": "&0(&4Admin&0)&7 ",
"rank": "1"
},
"permissions": [
"-modifyworld.mobtarget.*",
"modifyworld.*",
"permissions.*"
]
}
}
}

=Chat Manager=
=命令=
===实用指令===
注意，在以下命令里 user=玩家名字，world=世界名字 permission=权限 node=节点 backend=后台文件 group=权限组别
/pex 显示帮助
permissions.manage
/pex toggle debug 调试开关（不要总开着！，要不然会出很多信息文件）
permissions.debug
/pex user <user> toggle debug 给指定的一个人测试调整（上面一样）
permissions.manage.<user>
/pex user <user> check <permission> 检查一个具体的玩家的具体的权限
permissions.manage.<user>
/pex reload 重新载入所有pex文件
permissions.manage.reload
/pex config <node> [value] 看节点的值（写上后面的更改值）
permissions.manage.config
/pex backend 看现在的后台文件（也就是正在用的文件）
permissions.manage.backend
/pex hierarchy 看现在服务器结构（阶级）
permissions.manage.users
/pex dump <backend> <filename> 把你的后台文件倒到另外一个文件里谨慎使用！不会立刻保存，但会在游戏中有效果
permissions.manage.dump
/pex users cleanup <group> [threshold] 清走“死亡”的会员（默认30天不活动）
permissions.manage.users.cleanup

===世界管理===
/pex worlds 看PEX里面的世界
permissions.manage.worlds
/pex world <world> 看这个世界的层次信息
permissions.manage.worlds
/pex world <world> inherit <parentWorlds> 让你选择的世界继承一个世界（继承permission,etc.)
permissions.manage.worlds.inheritance
玩家指令：
/pex users list 看所有在PEX里面的玩家
permissions.manage.users
/pex users 一样一样
/pex user 一样一样 = =
玩家permission管理：
/pex user 一样.....······
permissions.manage.users
/pex user <user> 看玩家的权限
permissions.manage.users.permissions.<user>
/pex user <user> prefix [newprefix] 设置玩家前缀颜色
permissions.manage.users.prefix.<user>
/pex user <user> suffix [newsuffix] 设置玩家后缀颜色
permissions.manage.users.suffix.<user>
/pex user <user> delete 把玩家从权限文件里面移除
permissions.manage.users.<user>
/pex user <user> list [world] 看玩家的权限
permissions.manage.users.permissions.<user>
/pex user <user> add <permission> [world] 给玩家增加权限
permissions.manage.users.permissions.<user>
/pex user <user> remove <permission> [world] 给玩家移除权限
permissions.manage.users.permissions.<user>
/pex user <user> timed add <permission> <lifetime in seconds> [world] 给玩家在时间内（秒）添加权限
permissions.manage.users.permissions.timed.<user>
/pex user <user> timed remove <permission> <lifetime in seconds> [world]给玩家在时间内（秒）移除权限
permissions.manage.users.permissions.timed.<user>
/pex user <user> set <option> <value> [world] 给玩家设选择值（不怎么懂表示，望进一步翻译和解释）
permissions.manage.users.permissions.<user>

===玩家组管理===
/pex user <user> group list 给出玩家所有现在在的组
permissions.manage.membership.<user>
/pex user <user> group add <group> [world] [lifetime]把玩家加入组（时间，秒，不设默认永久）
permissions.manage.membership.<group>
/pex user <user> group set <group> [world] 把玩家放进组，注意这将会把玩家从另一个组移除
permissions.manage.membership.<group>
/pex user <user> group remove <group> [world] 把玩家从组移除
permissions.manage.membership.<group>

===默认组管理===
/pex default group [world] 看默认的管理组情况
permissions.manage.groups.inheritance
/pex set default group <group> [world] 把权限组组设成默认
permissions.manage.groups.inheritance

===组的指令===
/pex group 显示所有创建了的组
permissions.manage.groups.list
/pex groups ↑（同上）
permissions.manage.groups.list
/pex groups list ↑
permissions.manage.groups.list
/pex group <group> prefix [newprefix] 设置组前缀
permissions.manage.groups.prefix.<group>
/pex group <group> suffix [newsuffix] 设置组后缀
permissions.manage.groups.suffix.<group>
/pex group <group> create [parents] 创建组，parents（母权限组）是说他是从哪里升级得来的（继承权限)
permissions.manage.groups.create.<group>
/pex group <group> delete 删除权限组
permissions.manage.groups.remove.<group>
/pex group <group> parents list 看权限组的继承表
permissions.manage.groups.inheritance.<group>
/pex group <group> parents set <parents> 设置权限组组的母权限组
permissions.manage.groups.inheritance.<group>
/pex group <group> 显示所有组的权限
permissions.manage.groups.permissions.<group>
/pex group <group> list [world] 组的所有权限，加上世界名称可以看单个世界的权限
permissions.manage.groups.permissions.<group>
/pex group <group> add <permission> [world] 给小组加权限
permissions.manage.groups.permissions.<group>
/pex group <group> remove <permission> [world] 移除权限
permissions.manage.groups.permissions.<group>
/pex group <group> timed add <permission> [lifetime] [world] 给权限组限时加权限，不填默认永久
permissions.manage.groups.permissions.timed.<group>
/pex group <group> timed remove <permission> [world] 给权限组限时移除权限组，不填默认永久
permissions.manage.groups.permissions.timed.<group>
/pex group <group> set <option> <value> [world] 给组的人设置选则的值
permissions.manage.groups.permissions.<group>

===组的玩家的管理===
/pex group <group> users 所有在组里的玩家
permissions.manage.membership.<group>
/pex group <group> user add <user> 把玩家弄进小组
permissions.manage.membership.<group>
/pex group <group> user remove <user> 把玩家从组里移除
permissions.manage.membership.<group>
/pex promote <user> <ladder> 不知道怎么翻译了Promote <玩家名> on <ladder>. If <ladder> is not specified, the default ladder (named default) will be used.
permissions.user.promote.<ladder>
/pex demote <user> <ladder> 大题同上
permissions.user.demote.<ladder>

=FAQ=
=Features=
=Integrating with PEX=
=Migration=
=Migration and UUIDs=
=Modifyworld=
===Modifyworld Notes===

This section requires that you have a permissions plugin installed, which includes a basic structured group layout that allows the default group to only chat.

By default, users are not restricted. This is by design. Set specific nodes on this list to false to restrict users from performing actions, or set modifyworld.* to false to block a user from doing anything.

By default, modifyworld uses block names instead of block ID's. To use ID's, change or add the use-material-names: false line to the config.
Negate a node (-, set its value to false) to disallow a feature to a user/group. Use the wildcard symbol * to include all subnodes.
When using PermissionsEx, per the Regex section on the Advanced Permissions Setup page, you can specify multiple items within a single line. To do this, put the item codes/names in parentheses, separated by a pipe character (a shift-backslash on most US keyboard layouts). For example, (260|296|297) will match apples, wheat, and bread if use-material-names is false.
===IMPORTANT NOTICES===

Thanks to Bukkit user @Tahg we were notified about one issue with the modifyworld.blocks.place.* node: If you remove modifyworld.* from a group, for the group to place blocks, you will need to specify what blocks the group is allowed to place other blocks on using the modifyworld.blocks.interact.* (alternately you can use a wildcard for the block ID with modifyworld.blocks.interact.*) in addition to the modifyworld.blocks.place.* for the blocks the group is allowed to place. This is because Bukkit checks first for onPlayerInteract() then for onBlockPlace().
For example, when trying to place a sand block on a grass block, the permission node checks are modifyworld.blocks.interact.grass then modifyworld.blocks.place.sand. Consider the block being targeted with this action - the interact permission is required for the block that is targeted with right-click, and thus could be to the side or above the placed block.
Metadata can appear on a lot of blocks and items that you might not expect, please make sure you read the section on Metadata and check the debug output before posting in the forums!
===Configuration===

Modifyworld configuration is stored in plugins/Modifyworld/config.yml

An example ModifyWorld config file:

informPlayers: true
itemRestrictions: true
whitelist: false
messages:
prohibitedItem: You have prohibited item "%s".
whitelist: You are not allowed to join this server. Goodbye!
permissionDenied: Sorry, you don't have enough permissions
use-material-names: true
drop-restricted-item: false
item-use-check: false
===Configuration Properties===

由于搬运，格式有些耽误此处格式为：

权限/实体...名（默认是否开启）简介
informPlayers false Informs players if/when their permissions change
itemRestrictions false Enable/disable item restrictions. If this is enabled, items not configured to be allowed will be removed from the player's inventory if it's found.
messages.prohibitedItem You have prohibited item "%s". Message sent to players who have disallowed item(s)
messages.whitelist You are not allowed to join this server. Goodbye! Message sent to clients not on the whitelist
messages.permissionDenied Sorry, you don't have enough permissions What is sent to players trying to do something they are not allowed to
whitelist false Enable/disable the whitelisting feature
drop-restricted-item false If true, restricted items will be "ejected" from the player as if they dropped the items. If false, the items will just dissappear.
use-material-names true If true, modifyworld will use item names (dirt) instead of item numbers (3) when checking the permission nodes
check-metadata (REMOVED AS OF VERSION 1.19.1) false If true, modifyworld will use the meta-data for blocks and items in the permissions checks. This means that your nodes may need a :* or .* added to the end of them!
item-use-check false If true, modifyworld will enable the modifyworld.item.use.<itemid>.on.block.<blockid> node and check for rights to use <itemid> on <blockid>. Note that this basically replaces the modifyworld.interact.<entityName> checks.
===Metadata Notes===

Starting with release 1.19.1, metadata handling has been changed a bit.

There is no longer a need to specifically turn on metadata handling for modifyworld. However, a lot of blocks and items have metadata that one might not expect, or now has metadata due to changes in minecraft and bukkit.

A few examples are leaf blocks (each type has it's own value), planks (for the different colours), and sandstone (the different designs).

For item ID's that have metadata, using :* will cover all possible values for the metadata. For nodes that cover multiple items/blocks where some have metadata and others do not, the regex value of :?* will cover ID's that have metadata and ID's that do not.

Many blocks that you might not expect can have metadata, such as chests and doors that are freshly placed but have not been opened yet. When in doubt and you can't get a permission node, turning on debug will show what is being looked for. Please do this before posting in the forums, I can't stress this enough. Metadata is a very large stumbling block for many new users to PEX.

===Generic Nodes===

modifyworld.login 是否允许玩家加入游戏，你需要吧白名单开启来启动这个功能
modifyworld.chat 是否允许玩家能发布公告，聊天
modifyworld.sneak Player can crouch (check your Minecraft client config for the key) NOTE: Per https://github.com/PEXPlugins/PermissionsEx/issues/78, 这个节点在bukkit中因为缺少支持难以工作
modifyworld.sprint Player can sprint (double tap your forward key) NOTE: Per http://github.com/t3hk0d3/PermissionsEx/issues/78,也因为同样的原因难以工作。
modifyworld.chat.private 玩家是否能私聊
modifyworld.usebeds 玩家是否能使用床
modifyworld.bucket.empty.<fluid> 玩家是否能使用液体（清空桶）
<fluid>指的是水或岩浆
modifyworld.bucket.fill.<fluid> 玩家是否能用桶装东西
<fluid> 指的是谁，岩浆或牛奶（早期版本里，air就是牛奶）
modifyworld.digestion Allows players' energy bar to deplete. A popular application of this would be to do -modifyworld.digestion to disable energy consumption whilst still enabling modifyworld.*

===Block Nodes===

See Materials for <blockid> values.

modifyworld.blocks.destroy.<blockid> Player can break <blockid>. It's also possible to specify <blockid> by name. Example: modifyworld.blocks.destroy.stone
modifyworld.blocks.place.<blockid> Player can place <blockid>. NOTICE: This permission requires modifyworld.blocks.interact.<blockid> to work properly.
modifyworld.blocks.interact.<blockid> Player can interact with <blockid> (use levers, press buttons, etc.)
===Item Nodes===

See Materials for <itemid> values.

modifyworld.items.craft.<itemid> Player can craft <itemid>.
modifyworld.items.drop.<itemid> Player can drop <itemid>.
modifyworld.items.enchant.<itemid> Player can enchant <itemid>.
modifyworld.items.have.<itemid> Player can have <itemid> in their inventory. itemRestrictions: true need to be set for this to work.
modifyworld.items.hold.<itemid> Player can have <itemid> in their hand. itemRestrictions: true need to be set for this to work.
modifyworld.items.pickup.<itemid> Player can pickup <itemid>. Also it's possible to specify <itemid> by name, example: 、modifyworld.items.pickup.diamondpickaxe
modifyworld.item.use.<itemid>.on.block.<blockid> Player can use <itemid> on block <blockid>. item-use-check: true need to be set for this to work and is check in addition to the modifyworld.interact.<entityName> checks
As of 1.19.3
modifyworld.items.use.<itemid>.on.block.<blockid> Player can use <itemid> on block <blockid>. item-use-check: true need to be set for this to work and is check in addition to the modifyworld.interact.<entityName> checks
modifyworld.items.throw.<itemid> Player may throw eggs, snowballs, splash potions or experience bottles. Potion metadata excludes splash flag: potion:34 will match a Splash Potion of Swiftness II.
As of 1.19.4
modifyworld.items.take.<itemid>.of.<container> Player may take items from containers, such as chests.
modifyworld.items.put.<itemid>.of.<container> Player may take put items in containers, such as chests.
===Entity Nodes===

modifyworld.damage.deal.<entityName> Player can deal damage to <entityName> (e.g. skeleton, spider, creeper, cow, pig, minecart, etc)
modifyworld.damage.take.<entityName> Player can take damage from <entityName>
modifyworld.mobtarget.<entityName> Player can be targeted by <entityName>
modifyworld.interact.<entityName> Player can interact with <entityName>
modifyworld.tame.<entityName> Player can tame <entityName>. This permission won't give you ability to tame animals or mobs that are not normally tameable (no pet creepers). Currently, only animal.wolf and animal.ocelot are applicable.
===Possible <entityName> values===

Players and Wolves
player.<playerName> Player called <playerName>. (Example: player.t3hk0d3)
group.<groupName> Any member of <groupName> group. (Example: group.admins)
animal.wolf Wild wolf
animal.wolf.<playerName> Wolf tamed by <playerName> (Example: wolf.t3hk0d3)
animal.ocelot Wild ocelot (cat)
animal.ocelot.<playerName> Tamed cat (ocelot)
Example: animal.ocelot.t3hk0d3
npc.villager Not related to Bert
snowman Not related Frosty
irongolem Defenders of the Villagers
Animals
animal.chicken cluck-cluck
animal.cow Mooo
animal.mushroomcow Mooshroom
animal.pig Pig
animal.sheep Sheep
animal.squid Squid
Monsters
monster.blaze Pyros, every one...
monster.cavespider Worse than spiders
monster.creeper SssssSSSssss
monster.enderman Don't look at them directly
monster.ghast AWWWWWWW
monster.giant Giant Zombie
monster.pigzombie Pig Zombie, omg
monster.silverfish Beware the horde
monster.skeleton Them bones, them dry bones...
monster.slime Covers regular slimes and magma cubes
monster.spider Yep, this is Spider, he is annoying.
monster.zombie Brainzzzz...
Environment
starvation Num nums, or lack there of
fire Initial fire damage
lava Lava damage. Add firetick too for full protection.
firetick Damage from touching fire (or after stepping into lava) over time.
blockexplosion Damage from TNT explosion.
projectile.arrow Arrows shot at player
drowning Failing to grab a breath of fresh air
fall Jumping without a parachute
suicide Committing Seppuku
poison Poison potions
===Vehicle Nodes===

NOTE: If you want to have permission to enter or exit a vehicle, you will also need modifyworld.interact.*

modifyworld.vehicle.destroy.<vehicleName> Player can damage vehicles (minecarts for example)
modifyworld.vehicle.enter.<vehicleName> Player can enter vehicles
modifyworld.vehicle.collide.<vehicleName> Player can collide with a vehicle
===Possible <vehicleName> values===

Boat
boat Not related to the Love Boat
Minecart
minecart Indiana Jones rides in one of these
===Material Names===

If use-material-names is false use the ID column value. Otherwise use the Name value.

You can find more detail, including metadata information, at Minecraft Wiki.

=Pex basics=
===Permissions and Server Terminology===

Server Console (AKA Console); The window that appears when the server is started. Displays server and plugin startup information, as well as server and plugin errors.
Global Permissions: Permissions that are applied to all worlds on a server.
World Specific Permissions: Permissions that are applied only to specified worlds.
Users: Your players.
Group: A name given to a set of permission nodes, often used to designate various levels of support on a server.
Groups can have global and world specific permissions, as well as other information used by other plugins.
Node: A line of text that represents a command, action or ability. For example, the /give command in bukkit has the node of bukkit.command.give
Negation: Mark a node as not available. Generally used only in certain specific situations.
Inheritance: The ability of a group to have the permissions from another group automatically apply. PEX supports group and world level Inheritance.
Metadata: (Also know as damage value) Metadata is another value added to an item ID number for various things, such as the different colours of wool blocks, the position of a switch, if a door is open or not, and so on. Primary used with Modifyworld.
===Permissions Hierarchy ===

PEX supports both a file based and SQL permissions hierarchy. For the purposes of explanation and ease of visualization, the following example will use a file based permissions hierarchy.

users: <- Users Section
t3hk0d3: <- Player Name
group: <- Player Group(s) Section
- default <- Player Group Name
permissions: <- Player Specific Permissions Section
- permissions.* <- Permissions node
worlds: <- World Specific Permission Section
world: <- World designator
permissions: <- World Specific Permission Group
- test.* <- World Specific Permission
group: <- World Specific Group Section
- testers <- World Specific Group
prefix: '&5[YARR]&f' <- World Specific Prefix
groups: <- Group Section
default: <- Group Name
default: true <- Default Group Setting
permissions: <- Group Permissions Section
- -modifyworld.blocks.interact.23 <- Negated Permission Node
- modifyworld.* <- Permission Node
admins:
inheritance: <- Group Inheritance Section
- default <- Groups) To Inherit From
permissions:
- example.permission
- -punish.noobs
options: <- Group Options Section
test.test: '100500' <- Extra Data
rank: '1' <- Rank Designator
worlds:
nether:
permissions:
- nocheat.fly
prefix: '&7[ADMIN FROM HELL]'
testers:
inheritance:
- admins
options:
test.test: '9000'
worlds: <- World Specific Section
nether: <- World Name
inheritance: <- World Inheritance Section
- world <- World To Inherit From
===PEX File Format (YAML)===

PEX, like many other plugins, uses a format for it's files called YAML (YAML Ain't Markup Language, see http://yaml.org/ if you want to know more). YAML, unlike some other file formats, is very picky about the formatting and characters used. Config files used by PEX, including the permissions file, must be indented correctly! Capitalization matters as well!

The rules for YAML as they apply to PEX are:

Certain characters are reserved for use by YAML. Some of the characters are ' - : # and %. If the data for an entry is going to use one of those characters, it must be in quotes.
%prefix%player%suffix> &e%message is invalid. "%prefix%player%suffix> &e%message" is valid
Any entries that are made of numbers only must be in quotes.
rank: 1000 or 45625: is invalid. rank: '1000' or '45625': is valid.
Tabs are not allowed to be in the file anywhere, unless it is in quotes. Any place where you would use a tab must use exactly two spaces.
Each group must start at the very beginning of the line, and each section contained within that section must be indented.
Due to the regex support in PEX, there are other characters that one has to be aware of. Characters such as } { ) ( ? and * must be quoted or escaped (a backslash works well). This isn't a YAML limitation, but is a similar situation to the reserved characters in YAML.

=PEXML=
=Plugin Configuration=
=Ranks (Promotion and Demotion)=
=Troubleshooting and FAQ=

用户:Minedx

2015-07-19T16:25:27Z

Minedx：

== 个人信息与属性 ==

MCBBS:tony990412

江苏苏州物联网专业！

单片机轻度兼容！

萌,腹黑,强受属性

快速学习快速忘！

'''傲娇！'''

其实就是逗比一枚！

== 特殊技能 ==

c51！

奇怪声线！

两年后台插件经验！

意识落后但是可以通过不同角度解决你的问题！

用户:Minedx

2015-07-19T16:24:02Z

Minedx：/* 特殊技能 */

== 个人信息与属性 ==

MCBBS:tony990412
----
江苏苏州物联网专业！
----
单片机轻度兼容！
----
萌,腹黑,强受属性
----
快速学习快速忘！
----
'''傲娇！'''
----

其实就是逗比一枚！

----

== 特殊技能 ==

c51！
----
奇怪声线！
----
两年后台插件经验！
----
意识落后但是
可以通过不同角度解决你的问题！

用户:Minedx

2015-07-19T16:23:39Z

Minedx：/* 个人信息与属性 */

== 个人信息与属性 ==

MCBBS:tony990412
----
江苏苏州物联网专业！
----
单片机轻度兼容！
----
萌,腹黑,强受属性
----
快速学习快速忘！
----
'''傲娇！'''
----

其实就是逗比一枚！

----

== 特殊技能 ==

c51！
奇怪声线！
两年后台插件经验！
意识落后但是
可以通过不同角度解决你的问题！

用户:Minedx

2015-07-19T16:23:15Z

Minedx：

== 个人信息与属性 ==

MCBBS:tony990412
江苏苏州物联网专业！单片机轻度兼容！
萌,腹黑,强受属性
快速学习快速忘！
'''傲娇！'''

其实就是逗比一枚！

----

== 特殊技能 ==

c51！
奇怪声线！
两年后台插件经验！
意识落后但是
可以通过不同角度解决你的问题！

用户:Minedx

2015-07-19T16:19:56Z

Minedx：以“ == 个人信息与属性 == MCBBS:tony990412 江苏苏州物联网专业！单片机轻度兼容！萌,腹黑,强受属性快速学习快速忘！ '''傲娇！...”为内容创建页面

== 个人信息与属性 ==

MCBBS:tony990412
江苏苏州物联网专业！单片机轻度兼容！
萌,腹黑,强受属性
快速学习快速忘！
'''傲娇！'''

其实就是逗比一枚！

== 特殊技能 ==

c51！
奇怪声线！
两年后台插件经验！
意识落后但是
可以通过不同角度解决你的问题！

CrazyLogin/配置文件

2015-07-19T16:01:38Z

Minedx：

= config.yml =
version: X.Y
此插件的版本可以在这里找到
https://github.com/ST-DDT/CrazyLogin/blob/master/src/main/resources/plugin.yml
提示信息头部 (它不能被任意一种reload所改变（也就是说，只能重启）)
chatHeader: '&C[&ACrazyLogin&C] &F'
database:
保存类型↓ 可以为： 'MYSQL'（MYSQL数据库）,'FLAT'（文件name.db）,'CONFIG'（不明)
saveType: FLAT
是否在关服时写入数据
saveOnShutdown: true
CONFIG 数据记录模式配置
CONFIG:
path inside config.yml
path: accounts
columns:
name: name
password: password
ips: ips
lastAction: lastAction
FLAT 数据记录模式配置
FLAT:
数据库文件在插件config.yml所在目录中，下面可以更改文件名
filePath: accounts.db
MYSQL 数据库记录配置
更多MYSQL配置戳这里 → [http://dev.bukkit.org/bukkit-plugins/crazycore/pages/mys-ql/ 这里]
MYSQL:
connection:
host: localhost 链接数据库地址
port: '3306' 端口
dbname: Crazy 数据库名
user: root 用户名
password: '' 密码
tableName: CrazyLogin_accounts 表的名字
是否在没有玩家在线时让数据加载（这会消耗RAM！）.
设置为false来使插件RAM占用减少
cached: true
如果下面的选项设置为true，那么在玩家登陆时将不会更新数据库,
通常在多个服务器使用同一数据库时派上用场
static: false
columns:
name: name
password: password
ips: ips
lastAction: lastAction
SQLITE 数据库配置
SQLITE:
connection:
path: plugins/CrazyLogin/accounts.sqlite sqlite路径
tableName: CrazyLogin_accounts 表名
是否在没有玩家在线时让数据加载（这会消耗RAM！）.
设置为false来使插件RAM占用减少
cached: true
如果下面的选项设置为true，那么在玩家登陆时将不会更新数据库,
通常在多个服务器使用同一数据库时派上用场
static: false
columns:
name: name
password: password
ips: ips
lastAction: lastAction
设置在登录时是否一定需要密码或令玩家在想登陆时输入密码，玩家没有登录（或注册）时不能聊天、合成、破坏/创建方块、扔掉/拾取物品、移动/传送或瞬移、打开容器
权限节点无效，op或者玩家一定需要输入密码或可选地输入密码
alwaysNeedPassword: true
如果设置为true你得输入两次你的密码.（}注意，这个括号表示不用输）
例: /register {OldPassword} <NewPassword> <NewPassword>
confirmNewPassword: false
如果设置为true你必须在改变新密码时输入旧密码.
例: /register <OldPassword> <NewPassword> {NewPassword}
confirmWithOldPassword: false
如果设置为true的话，在玩家加入时保护将会被禁用，以降低服务器负担,
会减少加入服务器,登陆,退出服务器时服务器的负担.
dynamicProtection: false
隐藏登陆错误 & <nowiki>COMMAND.EXPLOITWARN</nowiki> 消息
详细: 可能在未来会有其他警告消息同时被屏蔽.
'''警告: 您不会收到任何可能攻占您服务器的信息 (直到它成功了).'''
hideWarnings: false
你必须要在不活跃/下线 x 秒后重新登录
当你换了个ip登陆的时候肯定会被搞下线！
autoLogout: 3600
功能开启时，在线却不登陆x秒后会被踢出 (-1=不开启)
autoKick: -1
当开启时您因不登陆被t出时时同时会被ban x 秒 (-1=不开启)
autoTempBan: -1
当你无账号时你会在 x 秒内被请出. (-1=不开启)
autoKickUnregistered: -1
功能开启时，将会在失败登陆x次后被踢出 (-1=不开启)
autoKickLoginFailer: 3
功能开启时，将会因为登陆失败而封禁x秒 (-1=不开启)
autoTempBanLoginFailer: -1
功能开启时，将会因为使用不在白名单内的命令（违禁命令）x次而被踢出 (-1=不开启，下面的false也是不开启)
autoKickCommandUsers: false
功能开启时，你将会因为使用不在白名单内的命令而被封禁x秒 (-1=不开启)
autoTempBanCommandUsers:
功能开启时，不能在未登录状态下使用命令 (同使用违禁命令自动踢出功能一起工作) (true=开启/false=不开启)
blockGuestCommands: true
功能开启时，不能在未登录状态下发信息(true=开启/false=不开启)
blockGuestChat: false
功能开启时，不能在未注册（数据库注册）情况下加入服务器 (同SQL数据库一起工作) (true=开启/false=不开启)
blockGuestJoin: false
玩家数据将会在离开游戏后被重置
这包括所有的crazy系列插件, 玩家信息 (如果启动), +更多 (如果已启用)
在这之后在服务器内搜索玩家名字将不会搜索到文件 (最好情况)
removeGuestData: false
如果设置为true游戏中注册会被禁止(指令和插件相关) (true=开启/false=不开启)
disableRegistrations: false
如果设置为true你将会无法使用AdminLogin的相关内容 (true=开启/false=不开启)
disableAdminLogin: false
如果设置为true你将会无法使用TokenLogin的相关内容 (true=开启/false=不开启)
disableTokenLogin: false
当不停过多使用屏蔽登陆/注册指令时将会使登陆/注册指令只能5秒使用一次 (true=开启/false=不开启)
doNotSpamAuthRequests: false
只向玩家发送一次注册提示信息 (如果 alwaysNeedPassword=false) (true=开启/false=不开启)
doNotSpamRegisterRequests: false
注册信息会延迟 x ticks 防止被其他信息覆盖.
delayAuthRequests: 0
重复注册信息 x ticks 防止被其他信息覆盖.
repeatAuthRequests: 200
以下这些指令游客或未登陆者可以执行 (即使 BlockGuestCommands 被启用了).
commandWhitelist:
- /l(ogin)?(\z| .*)
- /register(\z| .*)
- /language(\z| [a-z]{2,3}_[a-z]{2,3})
- /language select(\z| .*)
- /language list(\z| .*)
- /worldedit cui
关于加密您的密码库的算法请访问以下页面. http://dev.bukkit.org/server-mods/crazylogin/pages/encryption/
encryptor:
name: CrazyCrypt1
密码最短长度:
minPasswordLength: 3
对于保护者（特定权限拥有者）的最短密码长度
protectedAccountMinPasswordLength: 7
防止玩家顶号 (true/false)
forceSingleSession: true
当使用同一ip时越过 <nowiki>ForceSingleSession</nowiki>[强制会话信息]. (true/false)
forceSingleSessionSameIPBypass: true
激活预[[注册]]保护 x ticks(隐藏背包内容/ForceSaveLogin) (false/0, 1 , ...)
目的是为了防止customSpawns和joinRewards.
delayPreRegisterSecurity: 5
激活预[[登陆]]保护 x ticks(隐藏背包内容/ForceSaveLogin) (false/0, 1 , ...)
目的是为了防止customSpawns和joinRewards.
'''警告:部分作弊客户端可能会在这段时间内读取背包内容'''
delayPreLoginSecurity: false
当开启时如果你受到伤害时你会被传送到出生点直到你登陆完成. (true/false)
saveLoginEnabled: true
当开启时你会被传送到出生点直到你登陆完成. (true/false)
这会修复AntiCheatPlugins当你在半空中时将你t出游戏.
forceSaveLogin: false
各个世界的强制出生点:
saveLoginLocations: {}
world:
x: 1500
y: -300
z: 0.1
这是可选参数！
world: world
yaw: 0
pitch: 0
当开启时你的背包将会被隐藏到你登陆为止. (true/false)
hideInventory: false
隐藏未登录的玩家. (true/false)
hidePlayer: false
阻止未登录的玩家获取聊天消息. (true/false)
hideChat: false
不提示登陆消息直到玩家成功登陆/离开游戏. (true/false)
delayJoinQuitMessages: false
使用多国语言. (true/false)
useCustomJoinQuitMessages: true
隐藏服务端的密码 (提示信息为: Player issues command: /login Password) (true/false)
''信息:在极罕见的情况下可以越过某些其他插件的保护结构.''
hidePasswordsFromConsole: false
每个ip存储玩家的最大数:
maxStoredIPs: 5
每个ip允许的最大在线玩家数:
maxOnlinesPerIP: 3
每个ip允许的最大注册量:
maxRegistrationsPerIP: 3
自动删除 x 天未登陆过的号(-1=关闭功能)
'''警告:这会清除此玩家的所有信息(包括其他插件存储的内容;等同于"/crazycore player delete <Player>")'''
autoDelete: -1
唤醒特殊事件(大部分情况请关闭此选项)
当换密码时向其他插件传达未经加密的密码.
pluginCommunicationEnabled: false
在你未登录的情况下你可以移动 x 格.
设置为0你将不能移动或转向.
moveRange: 5.0
启用名称过滤器. (true/false/[a-zA-Z0-9_]/...)
filterNames: true
检查大小写. (true/false)
如果你使用 "PLaYer" 注册就不能使用 "Player" 登陆了！
当玩家用不同大小写登录时一些加密会错误.
INFO: a player cannot bypass login by using an different name case at any time.
blockDifferentNameCases: false
最短用户名限制:
minNameLength: 3
最长用户名限制: (minecraft 游戏中默认是 16)
maxNameLength: 16
附加消息内容可以在以下网站中找到: http://dev.bukkit.org/server-mods/crazycore/pages/logging/
logs:
Join:
path: false
console: false
Quit:
path: false
console: false
Login:
path: false
console: false
Account:
path: false
console: false
Logout:
path: false
console: false
LoginFail:
path: false
console: false
ChatBlocked:
path: false
console: false
CommandBlocked:
path: false
console: false
AccessDenied:
path: false
console: false

CrazyLogin/配置文件

2015-07-19T16:01:13Z

Minedx：blockGuestCommands joinRewards customSpawns ForceSaveLogin 未翻译 ForceSingleSession 非正式翻译

{{待翻译}}
= config.yml =
version: X.Y
此插件的版本可以在这里找到
https://github.com/ST-DDT/CrazyLogin/blob/master/src/main/resources/plugin.yml
提示信息头部 (它不能被任意一种reload所改变（也就是说，只能重启）)
chatHeader: '&C[&ACrazyLogin&C] &F'
database:
保存类型↓ 可以为： 'MYSQL'（MYSQL数据库）,'FLAT'（文件name.db）,'CONFIG'（不明)
saveType: FLAT
是否在关服时写入数据
saveOnShutdown: true
CONFIG 数据记录模式配置
CONFIG:
path inside config.yml
path: accounts
columns:
name: name
password: password
ips: ips
lastAction: lastAction
FLAT 数据记录模式配置
FLAT:
数据库文件在插件config.yml所在目录中，下面可以更改文件名
filePath: accounts.db
MYSQL 数据库记录配置
更多MYSQL配置戳这里 → [http://dev.bukkit.org/bukkit-plugins/crazycore/pages/mys-ql/ 这里]
MYSQL:
connection:
host: localhost 链接数据库地址
port: '3306' 端口
dbname: Crazy 数据库名
user: root 用户名
password: '' 密码
tableName: CrazyLogin_accounts 表的名字
是否在没有玩家在线时让数据加载（这会消耗RAM！）.
设置为false来使插件RAM占用减少
cached: true
如果下面的选项设置为true，那么在玩家登陆时将不会更新数据库,
通常在多个服务器使用同一数据库时派上用场
static: false
columns:
name: name
password: password
ips: ips
lastAction: lastAction
SQLITE 数据库配置
SQLITE:
connection:
path: plugins/CrazyLogin/accounts.sqlite sqlite路径
tableName: CrazyLogin_accounts 表名
是否在没有玩家在线时让数据加载（这会消耗RAM！）.
设置为false来使插件RAM占用减少
cached: true
如果下面的选项设置为true，那么在玩家登陆时将不会更新数据库,
通常在多个服务器使用同一数据库时派上用场
static: false
columns:
name: name
password: password
ips: ips
lastAction: lastAction
设置在登录时是否一定需要密码或令玩家在想登陆时输入密码，玩家没有登录（或注册）时不能聊天、合成、破坏/创建方块、扔掉/拾取物品、移动/传送或瞬移、打开容器
权限节点无效，op或者玩家一定需要输入密码或可选地输入密码
alwaysNeedPassword: true
如果设置为true你得输入两次你的密码.（}注意，这个括号表示不用输）
例: /register {OldPassword} <NewPassword> <NewPassword>
confirmNewPassword: false
如果设置为true你必须在改变新密码时输入旧密码.
例: /register <OldPassword> <NewPassword> {NewPassword}
confirmWithOldPassword: false
如果设置为true的话，在玩家加入时保护将会被禁用，以降低服务器负担,
会减少加入服务器,登陆,退出服务器时服务器的负担.
dynamicProtection: false
隐藏登陆错误 & <nowiki>COMMAND.EXPLOITWARN</nowiki> 消息
详细: 可能在未来会有其他警告消息同时被屏蔽.
'''警告: 您不会收到任何可能攻占您服务器的信息 (直到它成功了).'''
hideWarnings: false
你必须要在不活跃/下线 x 秒后重新登录
当你换了个ip登陆的时候肯定会被搞下线！
autoLogout: 3600
功能开启时，在线却不登陆x秒后会被踢出 (-1=不开启)
autoKick: -1
当开启时您因不登陆被t出时时同时会被ban x 秒 (-1=不开启)
autoTempBan: -1
当你无账号时你会在 x 秒内被请出. (-1=不开启)
autoKickUnregistered: -1
功能开启时，将会在失败登陆x次后被踢出 (-1=不开启)
autoKickLoginFailer: 3
功能开启时，将会因为登陆失败而封禁x秒 (-1=不开启)
autoTempBanLoginFailer: -1
功能开启时，将会因为使用不在白名单内的命令（违禁命令）x次而被踢出 (-1=不开启，下面的false也是不开启)
autoKickCommandUsers: false
功能开启时，你将会因为使用不在白名单内的命令而被封禁x秒 (-1=不开启)
autoTempBanCommandUsers:
功能开启时，不能在未登录状态下使用命令 (同使用违禁命令自动踢出功能一起工作) (true=开启/false=不开启)
blockGuestCommands: true
功能开启时，不能在未登录状态下发信息(true=开启/false=不开启)
blockGuestChat: false
功能开启时，不能在未注册（数据库注册）情况下加入服务器 (同SQL数据库一起工作) (true=开启/false=不开启)
blockGuestJoin: false
玩家数据将会在离开游戏后被重置
这包括所有的crazy系列插件, 玩家信息 (如果启动), +更多 (如果已启用)
在这之后在服务器内搜索玩家名字将不会搜索到文件 (最好情况)
removeGuestData: false
如果设置为true游戏中注册会被禁止(指令和插件相关) (true=开启/false=不开启)
disableRegistrations: false
如果设置为true你将会无法使用AdminLogin的相关内容 (true=开启/false=不开启)
disableAdminLogin: false
如果设置为true你将会无法使用TokenLogin的相关内容 (true=开启/false=不开启)
disableTokenLogin: false
当不停过多使用屏蔽登陆/注册指令时将会使登陆/注册指令只能5秒使用一次 (true=开启/false=不开启)
doNotSpamAuthRequests: false
只向玩家发送一次注册提示信息 (如果 alwaysNeedPassword=false) (true=开启/false=不开启)
doNotSpamRegisterRequests: false
注册信息会延迟 x ticks 防止被其他信息覆盖.
delayAuthRequests: 0
重复注册信息 x ticks 防止被其他信息覆盖.
repeatAuthRequests: 200
以下这些指令游客或未登陆者可以执行 (即使 BlockGuestCommands 被启用了).
commandWhitelist:
- /l(ogin)?(\z| .*)
- /register(\z| .*)
- /language(\z| [a-z]{2,3}_[a-z]{2,3})
- /language select(\z| .*)
- /language list(\z| .*)
- /worldedit cui
关于加密您的密码库的算法请访问以下页面. http://dev.bukkit.org/server-mods/crazylogin/pages/encryption/
encryptor:
name: CrazyCrypt1
密码最短长度:
minPasswordLength: 3
对于保护者（特定权限拥有者）的最短密码长度
protectedAccountMinPasswordLength: 7
防止玩家顶号 (true/false)
forceSingleSession: true
当使用同一ip时越过 <nowiki>ForceSingleSession</nowiki>[强制会话信息]. (true/false)
forceSingleSessionSameIPBypass: true
激活预[[注册]]保护 x ticks(隐藏背包内容/ForceSaveLogin) (false/0, 1 , ...)
目的是为了防止customSpawns和joinRewards.
delayPreRegisterSecurity: 5
激活预[[登陆]]保护 x ticks(隐藏背包内容/ForceSaveLogin) (false/0, 1 , ...)
目的是为了防止customSpawns和joinRewards.
'''警告:部分作弊客户端可能会在这段时间内读取背包内容'''
delayPreLoginSecurity: false
当开启时如果你受到伤害时你会被传送到出生点直到你登陆完成. (true/false)
saveLoginEnabled: true
当开启时你会被传送到出生点直到你登陆完成. (true/false)
这会修复AntiCheatPlugins当你在半空中时将你t出游戏.
forceSaveLogin: false
各个世界的强制出生点:
saveLoginLocations: {}
world:
x: 1500
y: -300
z: 0.1
这是可选参数！
world: world
yaw: 0
pitch: 0
当开启时你的背包将会被隐藏到你登陆为止. (true/false)
hideInventory: false
隐藏未登录的玩家. (true/false)
hidePlayer: false
阻止未登录的玩家获取聊天消息. (true/false)
hideChat: false
不提示登陆消息直到玩家成功登陆/离开游戏. (true/false)
delayJoinQuitMessages: false
使用多国语言. (true/false)
useCustomJoinQuitMessages: true
隐藏服务端的密码 (提示信息为: Player issues command: /login Password) (true/false)
''信息:在极罕见的情况下可以越过某些其他插件的保护结构.''
hidePasswordsFromConsole: false
每个ip存储玩家的最大数:
maxStoredIPs: 5
每个ip允许的最大在线玩家数:
maxOnlinesPerIP: 3
每个ip允许的最大注册量:
maxRegistrationsPerIP: 3
自动删除 x 天未登陆过的号(-1=关闭功能)
'''警告:这会清除此玩家的所有信息(包括其他插件存储的内容;等同于"/crazycore player delete <Player>")'''
autoDelete: -1
唤醒特殊事件(大部分情况请关闭此选项)
当换密码时向其他插件传达未经加密的密码.
pluginCommunicationEnabled: false
在你未登录的情况下你可以移动 x 格.
设置为0你将不能移动或转向.
moveRange: 5.0
启用名称过滤器. (true/false/[a-zA-Z0-9_]/...)
filterNames: true
检查大小写. (true/false)
如果你使用 "PLaYer" 注册就不能使用 "Player" 登陆了！
当玩家用不同大小写登录时一些加密会错误.
INFO: a player cannot bypass login by using an different name case at any time.
blockDifferentNameCases: false
最短用户名限制:
minNameLength: 3
最长用户名限制: (minecraft 游戏中默认是 16)
maxNameLength: 16
附加消息内容可以在以下网站中找到: http://dev.bukkit.org/server-mods/crazycore/pages/logging/
logs:
Join:
path: false
console: false
Quit:
path: false
console: false
Login:
path: false
console: false
Account:
path: false
console: false
Logout:
path: false
console: false
LoginFail:
path: false
console: false
ChatBlocked:
path: false
console: false
CommandBlocked:
path: false
console: false
AccessDenied:
path: false
console: false

CrazyLogin/配置文件

2015-07-19T15:19:04Z

Minedx：半数存档 COMMAND.EXPLOITWARN AdminLogin TokenLogin alwaysNeedPassword未翻译

{{待翻译}}
= config.yml =
version: X.Y
此插件的版本可以在这里找到
https://github.com/ST-DDT/CrazyLogin/blob/master/src/main/resources/plugin.yml
提示信息头部 (它不能被任意一种reload所改变（也就是说，只能重启）)
chatHeader: '&C[&ACrazyLogin&C] &F'
database:
保存类型↓ 可以为： 'MYSQL'（MYSQL数据库）,'FLAT'（文件name.db）,'CONFIG'（不明)
saveType: FLAT
是否在关服时写入数据
saveOnShutdown: true
CONFIG 数据记录模式配置
CONFIG:
path inside config.yml
path: accounts
columns:
name: name
password: password
ips: ips
lastAction: lastAction
FLAT 数据记录模式配置
FLAT:
数据库文件在插件config.yml所在目录中，下面可以更改文件名
filePath: accounts.db
MYSQL 数据库记录配置
更多MYSQL配置戳这里 → [http://dev.bukkit.org/bukkit-plugins/crazycore/pages/mys-ql/ 这里]
MYSQL:
connection:
host: localhost 链接数据库地址
port: '3306' 端口
dbname: Crazy 数据库名
user: root 用户名
password: '' 密码
tableName: CrazyLogin_accounts 表的名字
是否在没有玩家在线时让数据加载（这会消耗RAM！）.
设置为false来使插件RAM占用减少
cached: true
如果下面的选项设置为true，那么在玩家登陆时将不会更新数据库,
通常在多个服务器使用同一数据库时派上用场
static: false
columns:
name: name
password: password
ips: ips
lastAction: lastAction
SQLITE 数据库配置
SQLITE:
connection:
path: plugins/CrazyLogin/accounts.sqlite sqlite路径
tableName: CrazyLogin_accounts 表名
是否在没有玩家在线时让数据加载（这会消耗RAM！）.
设置为false来使插件RAM占用减少
cached: true
如果下面的选项设置为true，那么在玩家登陆时将不会更新数据库,
通常在多个服务器使用同一数据库时派上用场
static: false
columns:
name: name
password: password
ips: ips
lastAction: lastAction
设置在登录时是否一定需要密码或令玩家在想登陆时输入密码，玩家没有登录（或注册）时不能聊天、合成、破坏/创建方块、扔掉/拾取物品、移动/传送或瞬移、打开容器
权限节点无效，op或者玩家一定需要输入密码或可选地输入密码
alwaysNeedPassword: true
如果设置为true你得输入两次你的密码.（}注意，这个括号表示不用输）
例: /register {OldPassword} <NewPassword> <NewPassword>
confirmNewPassword: false
如果设置为true你必须在改变新密码时输入旧密码.
例: /register <OldPassword> <NewPassword> {NewPassword}
confirmWithOldPassword: false
如果设置为true的话，在玩家加入时保护将会被禁用，以降低服务器负担,
会减少加入服务器,登陆,退出服务器时服务器的负担.
dynamicProtection: false
隐藏登陆错误 & <nowiki>COMMAND.EXPLOITWARN</nowiki> 消息
详细: 可能在未来会有其他警告消息同时被屏蔽.
'''警告: 您不会收到任何可能攻占您服务器的信息 (直到它成功了).'''
hideWarnings: false
你必须要在不活跃/下线 x 秒后重新登录
当你换了个ip登陆的时候肯定会被搞下线！
autoLogout: 3600
功能开启时，在线却不登陆x秒后会被踢出 (-1=不开启)
autoKick: -1
当开启时您因不登陆被t出时时同时会被ban x 秒 (-1=不开启)
autoTempBan: -1
当你无账号时你会在 x 秒内被请出. (-1=不开启)
autoKickUnregistered: -1
功能开启时，将会在失败登陆x次后被踢出 (-1=不开启)
autoKickLoginFailer: 3
功能开启时，将会因为登陆失败而封禁x秒 (-1=不开启)
autoTempBanLoginFailer: -1
功能开启时，将会因为使用不在白名单内的命令（违禁命令）x次而被踢出 (-1=不开启，下面的false也是不开启)
autoKickCommandUsers: false
功能开启时，你将会因为使用不在白名单内的命令而被封禁x秒 (-1=不开启)
autoTempBanCommandUsers:
功能开启时，不能在未登录状态下使用命令 (同使用违禁命令自动踢出功能一起工作) (true=开启/false=不开启)
blockGuestCommands: true
功能开启时，不能在未登录状态下发信息(true=开启/false=不开启)
blockGuestChat: false
功能开启时，不能在未注册（数据库注册）情况下加入服务器 (同SQL数据库一起工作) (true=开启/false=不开启)
blockGuestJoin: false
玩家数据将会在离开游戏后被重置
这包括所有的crazy系列插件, 玩家信息 (如果启动), +更多 (如果已启用)
在这之后在服务器内搜索玩家名字将不会搜索到文件 (最好情况)
removeGuestData: false
如果设置为true游戏中注册会被禁止(指令和插件相关) (true=开启/false=不开启)
disableRegistrations: false
如果设置为true你将会无法使用AdminLogin的相关内容 (true=开启/false=不开启)
disableAdminLogin: false
如果设置为true你将会无法使用TokenLogin的相关内容 (true=开启/false=不开启)
disableTokenLogin: false
当不停过多使用屏蔽登陆/注册指令时将会使登陆/注册指令只能5秒使用一次 (true=开启/false=不开启)
doNotSpamAuthRequests: false
只向玩家发送一次注册提示信息 (如果 alwaysNeedPassword=false) (true=开启/false=不开启)
doNotSpamRegisterRequests: false
auth request are delayed for x ticks to prevent it from being displaced by other messages.
delayAuthRequests: 0
repeat requests every x ticks to prevent it from being displaced by other messages.
repeatAuthRequests: 200
these commands can be executed as guest (even if blockGuestCommands is enabled) or when not logged in
commandWhitelist:
- /l(ogin)?(\z| .*)
- /register(\z| .*)
- /language(\z| [a-z]{2,3}_[a-z]{2,3})
- /language select(\z| .*)
- /language list(\z| .*)
- /worldedit cui
the encryption alogrithm used to encrypt your passwords. http://dev.bukkit.org/server-mods/crazylogin/pages/encryption/
encryptor:
name: CrazyCrypt1
密码最短长度
minPasswordLength: 3
对于保护者（特定权限拥有者）的最短密码长度
protectedAccountMinPasswordLength: 7
block player join with an online players name (prevents Logged in from another location messages) (true/false)
forceSingleSession: true
bypass forceSingleSession when using the same ip (true/false)
forceSingleSessionSameIPBypass: true
activates the preLoginSecurity x ticks later (hideInventory / forceSaveLogin) (false/0, 1 , ...)
this is intended to allow customSpawns and joinRewards
delayPreRegisterSecurity: 5
activates the preLoginSecurity x ticks later (hideInventory / forceSaveLogin) (false/0, 1 , ...)
this is intended to allow customSpawns and joinRewards
WARNING: some hacked clients may be able to use that time to read the inventory/location
delayPreLoginSecurity: false
when enabled you are teleported to spawn until login if recieving damage. (true/false)
saveLoginEnabled: true
when enabled you are teleported to spawn until login. (true/false)
this fixes issues with AntiCheatPlugins whilte not logged in and being in mid air.
forceSaveLogin: false
custom saveLogin locations for each world
saveLoginLocations: {}
world:
x: 1500
y: -300
z: 0.1
this parameters are optional
world: world
yaw: 0
pitch: 0
when enabled your inventory is hidden until login. (true/false)
hideInventory: false
hide every player which isn't logged in. (true/false)
hidePlayer: false
hide chat from players who aren't logged in to avoid espionage. (true/false)
hideChat: false
Delay Join messages until login / hide Quit messages if not logged in. (true/false)
delayJoinQuitMessages: false
use the multilingual messages defined in the lang files. (true/false)
useCustomJoinQuitMessages: true
hide Password from Console (Player issues command: /login Password) (true/false)
INFO: This could bypass some command protections/mechanics from other plugins in very rare cases.
hidePasswordsFromConsole: false
maximum count of ips stored per player
maxStoredIPs: 5
maximum players allowed to play on your server at once
maxOnlinesPerIP: 3
maximum players allowed to register an account using the same ip on your server
maxRegistrationsPerIP: 3
automatically delete accounts that haven't been used for x days(-1=disabled)
WARNING: deletes all data belonging to this player (including those saved in other plugins; equals "/crazycore player delete <Player>")
autoDelete: -1
call special events (do not enable it, if you don't need it)
send raw passwords to other plugins when changing passwords
pluginCommunicationEnabled: false
you can move x blocks from the location you joined when not logged in
when set to 0 you cannot move/rotate
moveRange: 5.0
when enabled only default chars are allowed in a players name (true/false/[a-zA-Z0-9_]/...)
filterNames: true
check a players name case for its char case (true/false)
when enabled a player cannot join as "PLaYer" when he registered as "Player"
some encryptions may fail when a player has different char cases.
INFO: a player cannot bypass login by using an different name case at any time.
blockDifferentNameCases: false
最短用户名限制
minNameLength: 3
最长用户名限制 (minecraft 游戏中默认是 16)
maxNameLength: 16
additional information about logging can be found here http://dev.bukkit.org/server-mods/crazycore/pages/logging/
logs:
Join:
path: false
console: false
Quit:
path: false
console: false
Login:
path: false
console: false
Account:
path: false
console: false
Logout:
path: false
console: false
LoginFail:
path: false
console: false
ChatBlocked:
path: false
console: false
CommandBlocked:
path: false
console: false
AccessDenied:
path: false
console: false