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

Bukkit/插件开发教程

2015-08-07T17:46:30Z

9032676：/* Block Manipulation */

{{模板:待翻译}}
本页面英文原文内容来源 [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/apidocs/ 这]找到它 (Beta版的Java文档在[http://jd.bukkit.org/beta/apidocs/ 这]找, 新开发出来的Java文档在

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

（Bukkit的）Java文档就会冒出来。

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

'''http://jd.bukkit.org/apidocs/''' (或者上面的测试版/最新版 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]]''

== 权限 ==

With the new Bukkit API for permissions, they couldn't be easier. 检测玩家是否拥有权限，可以使用以下代码:
<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.'''

=== 配置权限 ===

If you want more control over your permissions, for example default values or children then you should consider adding them to your ''[[plugin.yml]]''. This is completely optional, however it is advised. Below is an example permissions config that would be appended to the end of your existing ''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) {
// Get the player's location.
Location loc = event.getPlayer().getLocation();
// Sets loc to five above where it used to be. Note that this doesn't change the player's position.
loc.setY(loc.getY() + 5);
// Gets the block at the new location.
Block b = loc.getBlock();
// Sets the block to type id 1 (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(); // The player who joined
PlayerInventory inventory = player.getInventory(); // The player's inventory
ItemStack itemstack = new ItemStack(Material.DIAMOND, 64); // A stack of diamonds

if (inventory.contains(itemstack)) {
inventory.addItem(itemstack); // Adds a stack of diamonds to the player's inventory
player.sendMessage("Welcome! You seem to be reeeally rich, so we gave you some more diamonds!");
}
}</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"; //use the displayname you want here

ItemStack myItem = new ItemStack(Material.DIAMOND_SWORD); //your item
ItemMeta im = myItem.getItemMeta(); //get the itemmeta of the item
im.setDisplayName(myDisplayName); //set the displayname
myItem.setItemMeta(im); //give the item the new itemmeta
</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! ==

Besides the Map/HashMap classes, Java offers many other data structures. They offer these different classes because there are times when a Map is not the most appropriate. Here's a separate page for discussing [[Java data structure classes]] in more detail.

=== HashMaps and How to Use Them ===
<big>
'''Keep in mind to never use a player in a hashmap!'''
You need to use Strings instead. So use "p.getName()" to add, remove or check if a list contains a player.
Saving a player as an object causes huge memory leaks.
</big>

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.

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

// Example Declaration
public Map<String, Boolean> pluginEnabled = new HashMap<>();
public Map<String, Boolean> isGodMode = new HashMap<>();
</source> </blockquote>
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.
<blockquote><source lang="java">Player player = (Player) sender;
togglePluginState(player);</source> </blockquote>
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.
<blockquote><source lang="java">public void togglePluginState(Player player) {
// 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");
}
}</source> </blockquote>
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.

==== More Ideas for HashMaps ====

A HashMap (or really any kind of Map in Java) is an association. It allows quick and efficient lookup of some sort of '''value''', given a unique '''key'''. 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.

===== Data Value Lookups =====

<blockquote><source lang="java">
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) {}
}
</source> </blockquote>

==== Saving/Loading a HashMap ====

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

*you don't want an administrator to edit the data manually

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

*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<String, Integer> with any type of HashMap you want. Let's take an example HashMap with code to save it:
<blockquote><source lang="java">
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");</source></blockquote>
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.
<blockquote><source lang="java">public HashMap<String, Integer> load(String path) {
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);
}</source></blockquote>
You can use this "API" for saving/loading HashMaps, ArrayLists, and all Objects which implement Serializable or Externalizable interface.
<blockquote><source lang="java">/** SLAPI = Saving/Loading API
* 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;
}
}</source> </blockquote>
Example implementation of this API: '''I'm skipping some part of code in this source'''
<blockquote><source lang="java">public class Example extends JavaPlugin {
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();
}
}
}</source> </blockquote>
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.

===== Tips & Examples =====

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.

== 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:大篇幅条目]]

MobArena

2015-07-03T17:01:44Z

9032676：/* 权限 */

{{待搬运}}
{{Bukkit Plugin Infobox
|版本=v0.96.9
|兼容服务端版本=1.8.1
|网址=http://dev.bukkit.org/bukkit-plugins/mobarena/}}
[[Category:娱乐]][[Category:机械]]
=安装=
安装MobArena其实很简单，只需以下四步:
*关闭服务器<del>咳咳，当然是关你自己的服务器啦</del>.
*从论坛主题或是Bukkit Dev站点的项目页下载jar文件.
*将jar文件拖入服务端的plugins文件夹中.
*重启服务端.
之后，配置文件 (config.yml) 以及一个宣告文本(announcements.yml) 会自动创建在plugins/MobArena/路径下.
文件结构如下:

plugins/
MobArena.jar
MobArena/
config.yml
announcements.yml
此时此刻, 或许你想直接开始设置竞技场, 但是你需要先看看配置文件，并把它配置成你喜欢的样子<del>就是说，还是根据情况配置一下吧</del>. 你可以在配置文件自定义MobArena的设置，职业，奖励，波数（怪物类型）

=建立竞技场=
==建造一个竞技场==
完整的竞技场应该包含一个可以选择职业的准备区域，一个竞技场地以及观察点(离开点)
下面是各个选项的讲解

大厅：
玩家加入游戏之前将会在大厅选择职业.一个建造好的游戏大厅会有每一个职业的选择牌子，玩家通过点击牌子可以获取一个职业, 还有一个铁块, 玩家可以通过点击铁块来表示他们已经准备好开始游戏.牌子必须在第一行写上职业的名字（区分大小写）,但是无论你在另外三行上写什么，都不会被怪物竞技场识别，你是不能写上 ,所以你不会得到确认的信息（如果有，那是另一个插件）

竞技场地：
这里是玩家和怪物搏斗的地方.竞技场地会有墙，可能会有一个屋顶 , 这样玩家和怪物就不能跑出去了. 这使得玩家们不会只是在竞技场外闲逛。.

观察点:
当玩家想要观看一场战斗时,他们可以使用/ma spec 命令来传送到竞技场的观察点. 这同样也是竞技场中玩家死去后会传送到的地方,前提是在配置文件中，把 spectate-after-death设置为ture. 这块区域要保证观看者不能走出去闲逛（进入竞技场地或者离远竞技场）因为在观看过程中，玩家是无敌的.

离开点:
在使用 /ma leave命令后,玩家和观察者会被传送到原来所在的地方,除非竞技场有一个离开点(只是可选). 使用离开点,可以准确控制玩家在游戏后去何处.

关于区域，传送点等，

当竞技场建好后，就是设置怪物竞技场的区域和传送点的时候了。在设置它们前，我们先来看看他们有什么作用.

区域:
一个竞技场需要一个竞技区域,然后还可以有一个准备区域，怪物竞技场会使用这些区域来确保玩家不会作弊（通过破坏竞技场来走出区域）,然后确保怪物竞技场所产生的怪物会在里面产生. 怪物竞技场非常排外（不要局外人）, 所以也最好把不想要的生物排除在外. 区域是通过区域工具来设置的.

传送点:
当玩家加入一个怪物竞技场的游戏时，他们会被传送到准备区域中的准备点来选择职业和准备开始游戏（通过点击铁块）.当每个人都准备好的时候，玩家会被传送到竞技场内的竞技场出生点。观察者会被传送到竞技场的观察点来进入观察区域,当游戏结束的时候，玩家和观察者会被传送到他们传送来之前的地方，或者去可选的离开点,传送点会用传送点工具来设置。.

出生点:
这里的出生点指的是怪物出生的地点.怪物竞技场只会在附近有玩家的出生点产出怪物（十五个方格的半径）.需要注意的是，怪物的数量不随着按照出生点的数量改变，只会因为在配置文件中波数的倍率改变和玩家的数量所改变.出生点可以通过出生点工具来设置。.

容器:
容器就是竞技场里的箱子，回收站等。这些容器将会在一场游戏后重置其内部空间为初始值。只有被声明了的容器才会更新其存储空间，所以仅仅在竞技场里放一个箱子可不够 - 它还需要被用工具声明。

==设置模式==
我们能用配置模式来设置竞技场。当我们进入配置模式时，物品栏将会被保存并给我们一套金工具（工具栏），每一个都有其独特作用。同时我们也可以飞行，使得我们在竞技场附近移动时更加快捷方便一些，最后，但不是绝对，我们不能够聊天或者使用普通命令如果在在配置模式下的话，因为配置模式和你建立起了独立会话（即你所发表的信息都是针对插件的。）

进入设置模式的方法：输入/ma setup 竞技场名，值得提醒的是，如果服务器中只有一个竞技场，你不用输入竞技场的名字，如果竞技场没有设置完毕或者没有被创造，首先使用/ma addarena 竞技场名来创造它

离开设置模式的方法：聊天框内输入done，注意不是命令，是聊天信息，没有斜杠

另外，如果你刚安装怪物竞技场插件，会有一个预置的，名称为default竞技场存在于配置文件中，如果你想要一个不同的名字，你需要先创造一个新竞技场然后把原来的竞技场使用/ma delarena default来删除

下面我们会提到在设置模式中有什么命令可以使用。

==设置模式的命令==

设置模式是一个独立，特殊的会话，这意味着插件会监控我们说的每一句话，使得插件的命令可以缩短，以致于设置过程没有特别麻烦。比如exp命令替代了/ma expandregion，并且还可以防止我们错误地使用了其他插件的命令

下面是我们可以在设置模式中使用的命令，很多都十分浅显易懂（如果您懂英文的话。）使得您设置竞技场十分快速
done
离开设置模式
别名: end stop done quit

help
显示帮助信息
别名: ? h

missing
显示我们还没有设置好的区域（准备区诸如此类）
这个命令在你不知道你已经设置了那些区域的时候十分有用
别名: miss

expand <region> <amount> <direction>
Expand a region by some amount in some direction.
Valid regions: ar for the arena region, or lr for the lobby region
Valid amounts: positive integers (whole numbers)
Valid directions: up, down, or out
Example: expand ar 5 up
别名: exp

show [<region>|<warp>|<point>]
Show a region, warp, or point(s) as red wool blocks.
Valid regions: ar for the arena region, or lr for the lobby region
Valid warps: arena, lobby, spec, exit
Valid points: spawns (or just sp) for spawnpoints, chests (or just c) for chests
Example: show sp

==设置时的工具==

The Toolbox is a set of golden tools, where each tool has a specific function. We will use these tools to set up the regions, warps, and points of our arena. The tools are used by left- or right-clicking a block while holding them, and the actions vary depending on the specific tool.

Note that the functions of a tool are described in the item tooltip, which we can see by opening up our inventory and hovering our mouse over the tools.

===区域工具===

The arena and lobby regions can be set up using the Region tools (axe). There are two golden axes in the Toolbox, and they both behave the same, except that one is for the arena region, and the other is for the lobby region. The tools are named accordingly, and they will display either "Arena Region" or "Lobby Region" above the quickbar when we select them.

Note that the behavior of the Region tools is similar to that of the WorldEdit wand (wooden axe), so if you are familiar with defining regions in WorldEdit, the Region tools should feel familiar.

Left-click: Set the first point to be the location of the target block
Right-click: Set the second point to be the location of the target block

Upon setting both points, the region will be defined. Type show ar (or show lr) to check that the region spans the desired area. If the region is a little bit too small, use the expand command (see above) to make it a little bigger.

Note: The region MUST look like a box (3D) and not a rectangle (2D). If the region is just a rectangle, your arena will not work correctly. The same applies if the arena floor is not fully contained in the box, so make sure to expand the region down a block or two to be sure.

===玩家传送点工具===

The arena, lobby, spectator, and exit warps can be set up using the Warps tool (hoe). The tool knows about all the warps, and we have to cycle through them to select the warp we want to place. The default selected warp is the arena warp.

Left-click: Set the currently selected warp on top of the target block
Right-click: Cycle between available warps

When left-clicking, the selected warp will be set to the top of the clicked block. The pitch (up and down) will be set to 0, which means when players are teleported, they will be looking "straight ahead". The yaw (rotation, left/right) will be set to whatever direction we are facing, when we set the warp. This means that we need to rotate ourselves to be looking in the direction we want the players to look in when they are teleported to the point.

Note: The arena, lobby, and spectator warps are all required. The exit warp is optional.

===怪物产生点工具===

The spawnpoints can be set up using the Spawnpoints tool (sword). The tool knows about all the spawnpoints of the arena, and allows us to remove existing ones or add new ones as we please.

Left-click: Add a spawnpoint on top of the target block
Right-click: Remove the spawnpoint on top of the target block (if the spawnpoint exists)

When left-clicking, a spawnpoint will be added on top of the clicked block, if one doesn't already exist. Right-clicking a block will remove a spawnpoint on that block, if one exists.

Note: Due to limitations and "bugs" in Minecraft, it is not possible (read: viable) to spawn mobs further than 15 blocks away from a player, and still make it target and attack the player naturally. Therefore, it is recommended to place many spawnpoints, so that every single location in the arena is within a 15-block radius of a spawnpoint. If a player is not within 15 blocks of any spawnpoint, MobArena will print a warning to the console with the coordinates. If no players are within 15 blocks of any spawnpoint, MobArena will default to using all spawnpoints, which may result in mobs spawning far away from players, so they will have to run around searching for them.

===容器工具===

The chests and containers can be set up using the Chests tool (spade). It works very much like the Spawnpoints tool, but requires that the clicked block is a valid container.

Left-click: Register the clicked container (if it wasn't registered)
Right-click: Unregister the clicked container (if it was registered)

When left-clicking a container, MobArena will register the container (if it wasn't registered already), such that when an arena session ends, the container will be restored to contain whatever was in it when the arena began. Right-clicking a container will unregister it.

=命令=
==玩家命令==

这些指令能够给所有玩家使用. 它们包括了加入, 离开, 旁观和列出所有竞技场(可用或不可用)

/ma join (<竞技场>) or /ma j (<竞技场>) - 加入指定名称的竞技场.
/ma leave or /ma l - 离开竞技场或是离开旁观者模式.
/ma notready - 获取所有未准备的玩家.
/ma spec (<竞技场>) or /ma s (<竞技场>) - 以旁观者模式加入指定名称竞技场.
/ma arenas - 获取所有竞技场的名字, 若是绿色则已启用, 灰色则未启用.
/ma players - 获取当前所有竞技场的所有玩家.
/ma players <竞技场> - 获取指定竞技场的所有玩家.
/ma class <职业> - 如果你在大厅里, 是应直接用指令而不是透过牌子互动选择职业.

==管理员指令==

只有后台或者服务器op能使用下面这些指令. 这里包括了开始或是停止竞技场, 启用或是卸载竞技场甚至包含了MobArena的所有管理.

/ma enable - 启用MobArena插件.
/ma disable - 卸载MobArena插件.
/ma enable <竞技场> - 启用指定名字的竞技场.
/ma disable <竞技场> - 关闭指定名字的竞技场.
/ma force end - 停止所有竞技场的运作.
/ma force end <竞技场> - 停止指定名称竞技场的运作及使该竞技场的所有玩家离开.
/ma force start <竞技场> - 开始运作一个指定名称的竞技场以及请出该竞技场内未准备的玩家.
/ma notready <竞技场> - 获取该竞技场内所有未准备的玩家.
/ma restore <玩家> - 在可能的情况下恢复指定玩家背包.
/ma config reload - 重载config配置文件夹.
==建设指令==

只有op (以及某些合理的指令能在后台) 使用这些指令. 它们包括了设置竞技场传送点, 竞技场出生点以及竞技场范围.

/ma setup <竞技场> - 进入建设指定名称的竞技场模式.
/ma addarena <竞技场> - 建立一个新的竞技场节点于当前所在世界.
/ma delarena <竞技场> - 删除指定名称的竞技场.
/ma editarena <竞技场> - 开启或关闭指定竞技场修改模式.
/ma editarena <竞技场> [true|false] - 开启 (true) 或关闭 (false) 指定竞技场的修改模式.
/ma setting <竞技场> - 列出所有指定竞技场的设置项.
/ma setting <竞技场> <设置项> - 查询当前指定设置项的值于指定的竞技场.
/ma setting <竞技场> <设置项> <值> - 设置指定竞技场中指定设置项的指定值.
/ma checkspawns - 显示竞技场出生点 (在你当前的竞技场下) 是使用红色羊毛覆盖的范围在当前你当前的位置上. 这个指令同时也能查询在这个范围内不同的点是否被出生点覆盖着.
/ma classchest <职业> - 当正在查询箱子, 使指定的职业与这个箱子建立连接. 连接一个职业箱子意味着当MobArena连接建立后, 将同时复制于职业箱子内的物品, 而不是于竞技场大厅内的任何职业箱子. 当你建立一个职业箱子网络时它能带给你便利.
/ma auto-generate <竞技场> - 自动生成一个指定名称的竞技场. 这个竞技场只会生成于玩家所站的位置下方.
/ma auto-degenerate <竞技场> - 自动停止生成竞技场, 能基于自动生成器下有效地恢复, 当这是一个 "bulldozed" 补丁.

=权限=
几乎全部的权限插件是'''不需要'''MobArena插件作为前置而能够单独运行的, 但若果你想要更多额外的控制功能, 这里提供了很多不同类型的权限节点哦喵~
== 节点 ==
你能够在安装MobArena插件后使用这些权限节点

提示: MobArena这个插件提供了很多人性化的默认设定, 所有玩家能够使用所有竞技场及职业, 还有的是OP默认能够使用所有管理员以及建设指令. 除非你想要禁止一些组别进入特定的竞技场或是职业
NOTE: MobArena uses sane defaults. This means that by default, all players can use all arenas and all classes, and ops can use all admin and setup commands. Unless you want to prevent some groups from accessing certain arenas or classes, or you want to give non-ops admin and setup permissions, there is no need to mess with any permissions at all, so go away from this page and remove all occurrences of mobarena in your permissions-file!

==竞技场权限==

Did you read the note at the top? If not, read it before you continue.

So, you want to remove permissions for certain arenas from certain users? Alright, that means you will have to negate or revoke the permissions in your permissions plugin. In bPermissions, the negation modifier is a caret, ^, in GroupManager and PermissionsEx it is a minus, -, and in zPermissions it is by setting the permission to false. The examples below revoke the permission for the default arena.

bPermissions: ^mobarena.arenas.default
GroupManager: -mobarena.arenas.default
zPermissions: mobarena.arenas.default: false

I recommend letting everyone enjoy all your arenas, but this could be used in combination with "leveling" plugins to allow players to use "harder" arenas at higher levels. It could also be used for sponsors-only arenas.

Still confused? Check the sample setup at the bottom of the page!

==职业权限==

Did you read the note at the top? If not, read it before you continue.

Alright, if you're reading this, you want to remove permissions for certain classes from certain users. As with the arena permissions, you need to negate or revoke the permissions in your permissions plugin. In bPermissions, the negation modifier is a caret, ^, in GroupManager and PermissionsEx it is a minus, -, and in zPermissions it is by setting the permission to false. The examples below revoke the permission for the Knight class.

bPermissions: ^mobarena.classes.knight
GroupManager: -mobarena.classes.knight
zPermissions: mobarena.classes.knight: false

Note how the class name is lowercase. This is important. Even if the Knight class is called KnIGhT in your config-file, it MUST be all lowercase in your permissions-file.

As with arenas, I recommend letting everyone enjoy all the classes, unless you have a special reason not to.

Still confused? Check the sample setup at the bottom of the page!

==命令权限==

Did you read the note at the top? If not, read it before you continue.

If you're reading this, you want to either give certain users access to some of the admin and/or setup commands, or you want to remove some of the user commands from some groups. If this is not the case, stop reading and leave this page!

The first group of commands are the user commands. They are accessible by all players by default, so don't put mobarena.use.* or something stupid like that in your permissions-file! If you want a group to not have access to the user commands, negate the permission mobarena.use, which is the parent permission node for all the user commands. See the classes and arenas sections for information on how to negate permissions. If that doesn't work, negate the mobarena.use.join and mobarena.use.spec permissions. That should be enough.

mobarena.use.join
mobarena.use.leave
mobarena.use.spec
mobarena.use.arenalist
mobarena.use.playerlist
mobarena.use.notready
mobarena.use.class
The admin commands are simple. They allow disabling/enabling MobArena and individual arenas, kicking players from the arenas, restoring player inventories if they got lost somehow, forcing arenas to start or end, and teleporting in and out of arenas regardless of what the arena state is. If you want to grant all of these permissions, use the parent permission node mobarena.admin. Don't mess around with * or something stupid like that.

mobarena.admin.enable
mobarena.admin.kick
mobarena.admin.restore
mobarena.admin.force
mobarena.admin.teleport
Setup commands are only for ops, just like admin commands. Do not give these permissions to random people, because they can remove your arenas and destroy your config-files, if they do something stupid. The setup commands allow you to manage arenas, regions, spawnpoints, chests, leaderboards, etc. They also allow you to set up new classes in-game. If you want to grant all of these permissions, use the parent permission node mobarena.setup. Don't mess around with * or something stupid like that.

mobarena.setup.config
mobarena.setup.setup
mobarena.setup.setting
mobarena.setup.addarena
mobarena.setup.removearena
mobarena.setup.editarena
mobarena.setup.spawnpoints
mobarena.setup.containers
mobarena.setup.checkdata
mobarena.setup.checkspawns
mobarena.setup.classchest
mobarena.setup.classes
mobarena.setup.leaderboards
mobarena.setup.autogenerate
mobarena.setup.autodegenerate
Sample setup

Assume you have a class called DiamondKnight that you only want your donors to be able to use (very common use case). How do you set up your permissions plugin when you have to revoke the class permission from the default group, but the donor group inherits from the default group? It's very simple: You're doing it wrong...

What you have to do instead is make an auxiliary default-group that contains all your default permissions, and have your default group inherit from that group, and furthermore revoke the DiamondKnight class permission in MobArena. Your donor group then also inherits from the auxiliary group, and everything is wonderful. Confusing? Here's a pseudo-code example:

default-aux: <-- This is the auxiliary group that is to
permissions: be inherited by the default group and
- essentials.balance the donor group. It is not used for
- essentials.pay anything else.
- essentials.sell

default: <-- This is the default group. It inherits
inherits: default-aux from default-aux, but also revokes the
permissions: permission for the special class.
- -mobarena.classes.diamondknight

donor: <-- This is the donor group, which also
inherits: default-aux inherits from default-aux, but it
permissions: does not revoke any class permissions,
- essentials.balance.others which means it has access to all of
- essentials.kit them by default.
This sample setup is pseudo code and cannot be simply copy/pasted into your own permissions file. It's your job to figure out how your permissions plugin works, and what its syntax is.

=物品语法（Item Syntax待搬运）=
=职业箱子（Class Chests待搬运｝=
=怪物波设置（Formulas待搬运）=
=怪物种类（Monster types待搬运）=
以上内容搬运自英文wiki[https://github.com/garbagemule/MobArena/wiki]

MobArena

2015-07-01T16:34:34Z

9032676：/* 命令 */

{{待搬运}}
{{Bukkit Plugin Infobox
|版本=v0.96.9
|兼容服务端版本=1.8.1
|网址=http://dev.bukkit.org/bukkit-plugins/mobarena/}}
[[Category:娱乐]][[Category:机械]]
=安装=
安装MobArena其实很简单，只需以下四步:
*关闭服务器<del>咳咳，当然是关你自己的服务器啦</del>.
*从论坛主题或是Bukkit Dev站点的项目页下载jar文件.
*将jar文件拖入服务端的plugins文件夹中.
*重启服务端.
之后，配置文件 (config.yml) 以及一个宣告文本(announcements.yml) 会自动创建在plugins/MobArena/路径下.
文件结构如下:

plugins/
MobArena.jar
MobArena/
config.yml
announcements.yml
此时此刻, 或许你想直接开始设置竞技场, 但是你需要先看看配置文件，并把它配置成你喜欢的样子<del>就是说，还是根据情况配置一下吧</del>. 你可以在配置文件自定义MobArena的设置，职业，奖励，波数（怪物类型）

=建立竞技场=
==建造一个竞技场==
完整的竞技场应该包含一个可以选择职业的准备区域，一个竞技场地以及观察点(离开点)
下面是各个选项的讲解

大厅：
玩家加入游戏之前将会在大厅选择职业.一个建造好的游戏大厅会有每一个职业的选择牌子，玩家通过点击牌子可以获取一个职业, 还有一个铁块, 玩家可以通过点击铁块来表示他们已经准备好开始游戏.牌子必须在第一行写上职业的名字（区分大小写）,但是无论你在另外三行上写什么，都不会被怪物竞技场识别，你是不能写上 ,所以你不会得到确认的信息（如果有，那是另一个插件）

竞技场地：
这里是玩家和怪物搏斗的地方.竞技场地会有墙，可能会有一个屋顶 , 这样玩家和怪物就不能跑出去了. 这使得玩家们不会只是在竞技场外闲逛。.

观察点:
当玩家想要观看一场战斗时,他们可以使用/ma spec 命令来传送到竞技场的观察点. 这同样也是竞技场中玩家死去后会传送到的地方,前提是在配置文件中，把 spectate-after-death设置为ture. 这块区域要保证观看者不能走出去闲逛（进入竞技场地或者离远竞技场）因为在观看过程中，玩家是无敌的.

离开点:
在使用 /ma leave命令后,玩家和观察者会被传送到原来所在的地方,除非竞技场有一个离开点(只是可选). 使用离开点,可以准确控制玩家在游戏后去何处.

关于区域，传送点等，

当竞技场建好后，就是设置怪物竞技场的区域和传送点的时候了。在设置它们前，我们先来看看他们有什么作用.

区域:
一个竞技场需要一个竞技区域,然后还可以有一个准备区域，怪物竞技场会使用这些区域来确保玩家不会作弊（通过破坏竞技场来走出区域）,然后确保怪物竞技场所产生的怪物会在里面产生. 怪物竞技场非常排外（不要局外人）, 所以也最好把不想要的生物排除在外. 区域是通过区域工具来设置的.

传送点:
当玩家加入一个怪物竞技场的游戏时，他们会被传送到准备区域中的准备点来选择职业和准备开始游戏（通过点击铁块）.当每个人都准备好的时候，玩家会被传送到竞技场内的竞技场出生点。观察者会被传送到竞技场的观察点来进入观察区域,当游戏结束的时候，玩家和观察者会被传送到他们传送来之前的地方，或者去可选的离开点,传送点会用传送点工具来设置。.

出生点:
这里的出生点指的是怪物出生的地点.怪物竞技场只会在附近有玩家的出生点产出怪物（十五个方格的半径）.需要注意的是，怪物的数量不随着按照出生点的数量改变，只会因为在配置文件中波数的倍率改变和玩家的数量所改变.出生点可以通过出生点工具来设置。.

容器:
容器就是竞技场里的箱子，回收站等。这些容器将会在一场游戏后重置其内部空间为初始值。只有被声明了的容器才会更新其存储空间，所以仅仅在竞技场里放一个箱子可不够 - 它还需要被用工具声明。

==设置模式==
我们能用配置模式来设置竞技场。当我们进入配置模式时，物品栏将会被保存并给我们一套金工具（工具栏），每一个都有其独特作用。. We will also be able to fly, making moving around the arena a lot easier. Last, but not least, we will not be able to chat or type normal commands while in Setup Mode, because Setup Mode starts an isolated conversation with us.

To enter Setup Mode: Type /ma setup <arena>, where <arena> is the name of an arena. Note that if you only have one arena, you don't have to type the arena name. If the arena you want to set up has not yet been created, first type /ma addarena <arena> to create it.

To leave Setup Mode: Type done.

Note that if you have just installed MobArena, there will be a premade arena-node called default in the config-file already. If you want a different name, create a new arena first, and then remove the default arena by typing /ma delarena default.

In the next section, we will take a look at the different commands available in Setup Mode...

==设置模式的命令==

Setup Mode is an isolated conversation, which means Setup Mode will intercept everything we type. The reason for this is that it makes the commands in Setup Mode shorter (e.g. exp instead of /ma expandregion), and it also prevents us from accidentally typing commands from other plugins.

Below is a list of all the commands we can use in Setup Mode. Many of the commands have short-hand aliases which might make them even faster to type out. As an example, the expand command has the alias exp. Sometimes it's easier to remember the longer names, but the short-hand aliases are provided for faster setup.

done
Leave Setup Mode.
Aliases: end stop done quit

help
Display help screen.
Aliases: ? h

missing
Display a list of missing (mandatory) regions, warps, and points.
This command is useful if you have forgotten how far you are in the setup process, and what you still need to set up.
Aliases: miss

expand <region> <amount> <direction>
Expand a region by some amount in some direction.
Valid regions: ar for the arena region, or lr for the lobby region
Valid amounts: positive integers (whole numbers)
Valid directions: up, down, or out
Example: expand ar 5 up
Aliases: exp

show [<region>|<warp>|<point>]
Show a region, warp, or point(s) as red wool blocks.
Valid regions: ar for the arena region, or lr for the lobby region
Valid warps: arena, lobby, spec, exit
Valid points: spawns (or just sp) for spawnpoints, chests (or just c) for chests
Example: show sp

==设置时的工具==

The Toolbox is a set of golden tools, where each tool has a specific function. We will use these tools to set up the regions, warps, and points of our arena. The tools are used by left- or right-clicking a block while holding them, and the actions vary depending on the specific tool.

Note that the functions of a tool are described in the item tooltip, which we can see by opening up our inventory and hovering our mouse over the tools.

===区域工具===

The arena and lobby regions can be set up using the Region tools (axe). There are two golden axes in the Toolbox, and they both behave the same, except that one is for the arena region, and the other is for the lobby region. The tools are named accordingly, and they will display either "Arena Region" or "Lobby Region" above the quickbar when we select them.

Note that the behavior of the Region tools is similar to that of the WorldEdit wand (wooden axe), so if you are familiar with defining regions in WorldEdit, the Region tools should feel familiar.

Left-click: Set the first point to be the location of the target block
Right-click: Set the second point to be the location of the target block

Upon setting both points, the region will be defined. Type show ar (or show lr) to check that the region spans the desired area. If the region is a little bit too small, use the expand command (see above) to make it a little bigger.

Note: The region MUST look like a box (3D) and not a rectangle (2D). If the region is just a rectangle, your arena will not work correctly. The same applies if the arena floor is not fully contained in the box, so make sure to expand the region down a block or two to be sure.

===玩家传送点工具===

The arena, lobby, spectator, and exit warps can be set up using the Warps tool (hoe). The tool knows about all the warps, and we have to cycle through them to select the warp we want to place. The default selected warp is the arena warp.

Left-click: Set the currently selected warp on top of the target block
Right-click: Cycle between available warps

When left-clicking, the selected warp will be set to the top of the clicked block. The pitch (up and down) will be set to 0, which means when players are teleported, they will be looking "straight ahead". The yaw (rotation, left/right) will be set to whatever direction we are facing, when we set the warp. This means that we need to rotate ourselves to be looking in the direction we want the players to look in when they are teleported to the point.

Note: The arena, lobby, and spectator warps are all required. The exit warp is optional.

===怪物产生点工具===

The spawnpoints can be set up using the Spawnpoints tool (sword). The tool knows about all the spawnpoints of the arena, and allows us to remove existing ones or add new ones as we please.

Left-click: Add a spawnpoint on top of the target block
Right-click: Remove the spawnpoint on top of the target block (if the spawnpoint exists)

When left-clicking, a spawnpoint will be added on top of the clicked block, if one doesn't already exist. Right-clicking a block will remove a spawnpoint on that block, if one exists.

Note: Due to limitations and "bugs" in Minecraft, it is not possible (read: viable) to spawn mobs further than 15 blocks away from a player, and still make it target and attack the player naturally. Therefore, it is recommended to place many spawnpoints, so that every single location in the arena is within a 15-block radius of a spawnpoint. If a player is not within 15 blocks of any spawnpoint, MobArena will print a warning to the console with the coordinates. If no players are within 15 blocks of any spawnpoint, MobArena will default to using all spawnpoints, which may result in mobs spawning far away from players, so they will have to run around searching for them.

===容器工具===

The chests and containers can be set up using the Chests tool (spade). It works very much like the Spawnpoints tool, but requires that the clicked block is a valid container.

Left-click: Register the clicked container (if it wasn't registered)
Right-click: Unregister the clicked container (if it was registered)

When left-clicking a container, MobArena will register the container (if it wasn't registered already), such that when an arena session ends, the container will be restored to contain whatever was in it when the arena began. Right-clicking a container will unregister it.

=命令=
==玩家命令==

这些指令能够给所有玩家使用. 它们包括了加入, 离开, 旁观和列出所有竞技场(可用或不可用)

/ma join (<竞技场>) or /ma j (<竞技场>) - 加入指定名称的竞技场.
/ma leave or /ma l - 离开竞技场或是离开旁观者模式.
/ma notready - 获取所有未准备的玩家.
/ma spec (<竞技场>) or /ma s (<竞技场>) - 以旁观者模式加入指定名称竞技场.
/ma arenas - 获取所有竞技场的名字, 若是绿色则已启用, 灰色则未启用.
/ma players - 获取当前所有竞技场的所有玩家.
/ma players <竞技场> - 获取指定竞技场的所有玩家.
/ma class <职业> - 如果你在大厅里, 是应直接用指令而不是透过牌子互动选择职业.

==管理员指令==

只有后台或者服务器op能使用下面这些指令. 这里包括了开始或是停止竞技场, 启用或是卸载竞技场甚至包含了MobArena的所有管理.

/ma enable - 启用MobArena插件.
/ma disable - 卸载MobArena插件.
/ma enable <竞技场> - 启用指定名字的竞技场.
/ma disable <竞技场> - 关闭指定名字的竞技场.
/ma force end - 停止所有竞技场的运作.
/ma force end <竞技场> - 停止指定名称竞技场的运作及使该竞技场的所有玩家离开.
/ma force start <竞技场> - 开始运作一个指定名称的竞技场以及请出该竞技场内未准备的玩家.
/ma notready <竞技场> - 获取该竞技场内所有未准备的玩家.
/ma restore <玩家> - 在可能的情况下恢复指定玩家背包.
/ma config reload - 重载config配置文件夹.
==建设指令==

只有op (以及某些合理的指令能在后台) 使用这些指令. 它们包括了设置竞技场传送点, 竞技场出生点以及竞技场范围.

/ma setup <竞技场> - 进入建设指定名称的竞技场模式.
/ma addarena <竞技场> - 建立一个新的竞技场节点于当前所在世界.
/ma delarena <竞技场> - 删除指定名称的竞技场.
/ma editarena <竞技场> - 开启或关闭指定竞技场修改模式.
/ma editarena <竞技场> [true|false] - 开启 (true) 或关闭 (false) 指定竞技场的修改模式.
/ma setting <竞技场> - 列出所有指定竞技场的设置项.
/ma setting <竞技场> <设置项> - 查询当前指定设置项的值于指定的竞技场.
/ma setting <竞技场> <设置项> <值> - 设置指定竞技场中指定设置项的指定值.
/ma checkspawns - 显示竞技场出生点 (在你当前的竞技场下) 是使用红色羊毛覆盖的范围在当前你当前的位置上. 这个指令同时也能查询在这个范围内不同的点是否被出生点覆盖着.
/ma classchest <职业> - 当正在查询箱子, 使指定的职业与这个箱子建立连接. 连接一个职业箱子意味着当MobArena连接建立后, 将同时复制于职业箱子内的物品, 而不是于竞技场大厅内的任何职业箱子. 当你建立一个职业箱子网络时它能带给你便利.
/ma auto-generate <竞技场> - 自动生成一个指定名称的竞技场. 这个竞技场只会生成于玩家所站的位置下方.
/ma auto-degenerate <竞技场> - 自动停止生成竞技场, 能基于自动生成器下有效地恢复, 当这是一个 "bulldozed" 补丁.

=权限=
A permissions plugin is NOT required for MobArena to work, but if you want that extra bit of control, here's a rundown of the different types of permission nodes you can use with MobArena.

NOTE: MobArena uses sane defaults. This means that by default, all players can use all arenas and all classes, and ops can use all admin and setup commands. Unless you want to prevent some groups from accessing certain arenas or classes, or you want to give non-ops admin and setup permissions, there is no need to mess with any permissions at all, so go away from this page and remove all occurrences of mobarena in your permissions-file!

==竞技场权限==

Did you read the note at the top? If not, read it before you continue.

So, you want to remove permissions for certain arenas from certain users? Alright, that means you will have to negate or revoke the permissions in your permissions plugin. In bPermissions, the negation modifier is a caret, ^, in GroupManager and PermissionsEx it is a minus, -, and in zPermissions it is by setting the permission to false. The examples below revoke the permission for the default arena.

bPermissions: ^mobarena.arenas.default
GroupManager: -mobarena.arenas.default
zPermissions: mobarena.arenas.default: false

I recommend letting everyone enjoy all your arenas, but this could be used in combination with "leveling" plugins to allow players to use "harder" arenas at higher levels. It could also be used for sponsors-only arenas.

Still confused? Check the sample setup at the bottom of the page!

==职业权限==

Did you read the note at the top? If not, read it before you continue.

Alright, if you're reading this, you want to remove permissions for certain classes from certain users. As with the arena permissions, you need to negate or revoke the permissions in your permissions plugin. In bPermissions, the negation modifier is a caret, ^, in GroupManager and PermissionsEx it is a minus, -, and in zPermissions it is by setting the permission to false. The examples below revoke the permission for the Knight class.

bPermissions: ^mobarena.classes.knight
GroupManager: -mobarena.classes.knight
zPermissions: mobarena.classes.knight: false

Note how the class name is lowercase. This is important. Even if the Knight class is called KnIGhT in your config-file, it MUST be all lowercase in your permissions-file.

As with arenas, I recommend letting everyone enjoy all the classes, unless you have a special reason not to.

Still confused? Check the sample setup at the bottom of the page!

==命令权限==

Did you read the note at the top? If not, read it before you continue.

If you're reading this, you want to either give certain users access to some of the admin and/or setup commands, or you want to remove some of the user commands from some groups. If this is not the case, stop reading and leave this page!

The first group of commands are the user commands. They are accessible by all players by default, so don't put mobarena.use.* or something stupid like that in your permissions-file! If you want a group to not have access to the user commands, negate the permission mobarena.use, which is the parent permission node for all the user commands. See the classes and arenas sections for information on how to negate permissions. If that doesn't work, negate the mobarena.use.join and mobarena.use.spec permissions. That should be enough.

mobarena.use.join
mobarena.use.leave
mobarena.use.spec
mobarena.use.arenalist
mobarena.use.playerlist
mobarena.use.notready
mobarena.use.class
The admin commands are simple. They allow disabling/enabling MobArena and individual arenas, kicking players from the arenas, restoring player inventories if they got lost somehow, forcing arenas to start or end, and teleporting in and out of arenas regardless of what the arena state is. If you want to grant all of these permissions, use the parent permission node mobarena.admin. Don't mess around with * or something stupid like that.

mobarena.admin.enable
mobarena.admin.kick
mobarena.admin.restore
mobarena.admin.force
mobarena.admin.teleport
Setup commands are only for ops, just like admin commands. Do not give these permissions to random people, because they can remove your arenas and destroy your config-files, if they do something stupid. The setup commands allow you to manage arenas, regions, spawnpoints, chests, leaderboards, etc. They also allow you to set up new classes in-game. If you want to grant all of these permissions, use the parent permission node mobarena.setup. Don't mess around with * or something stupid like that.

mobarena.setup.config
mobarena.setup.setup
mobarena.setup.setting
mobarena.setup.addarena
mobarena.setup.removearena
mobarena.setup.editarena
mobarena.setup.spawnpoints
mobarena.setup.containers
mobarena.setup.checkdata
mobarena.setup.checkspawns
mobarena.setup.classchest
mobarena.setup.classes
mobarena.setup.leaderboards
mobarena.setup.autogenerate
mobarena.setup.autodegenerate
Sample setup

Assume you have a class called DiamondKnight that you only want your donors to be able to use (very common use case). How do you set up your permissions plugin when you have to revoke the class permission from the default group, but the donor group inherits from the default group? It's very simple: You're doing it wrong...

What you have to do instead is make an auxiliary default-group that contains all your default permissions, and have your default group inherit from that group, and furthermore revoke the DiamondKnight class permission in MobArena. Your donor group then also inherits from the auxiliary group, and everything is wonderful. Confusing? Here's a pseudo-code example:

default-aux: <-- This is the auxiliary group that is to
permissions: be inherited by the default group and
- essentials.balance the donor group. It is not used for
- essentials.pay anything else.
- essentials.sell

default: <-- This is the default group. It inherits
inherits: default-aux from default-aux, but also revokes the
permissions: permission for the special class.
- -mobarena.classes.diamondknight

donor: <-- This is the donor group, which also
inherits: default-aux inherits from default-aux, but it
permissions: does not revoke any class permissions,
- essentials.balance.others which means it has access to all of
- essentials.kit them by default.
This sample setup is pseudo code and cannot be simply copy/pasted into your own permissions file. It's your job to figure out how your permissions plugin works, and what its syntax is.
=物品语法（Item Syntax待搬运）=
=职业箱子（Class Chests待搬运｝=
=怪物波设置（Formulas待搬运）=
=怪物种类（Monster types待搬运）=
以上内容搬运自英文wiki[https://github.com/garbagemule/MobArena/wiki]

MobArena

2015-07-01T15:10:34Z

9032676：/* 玩家命令 */

{{待搬运}}
{{Bukkit Plugin Infobox
|版本=v0.96.9
|兼容服务端版本=1.8.1
|网址=http://dev.bukkit.org/bukkit-plugins/mobarena/}}
[[Category:娱乐]][[Category:机械]]
=安装=
安装MobArena其实很简单，只需以下四步:
*关闭服务器<del>咳咳，当然是关你自己的服务器啦</del>.
*从论坛主题或是Bukkit Dev站点的项目页下载jar文件.
*将jar文件拖入服务端的plugins文件夹中.
*重启服务端.
之后，配置文件 (config.yml) 以及一个宣告文本(announcements.yml) 会自动创建在plugins/MobArena/路径下.
文件结构如下:

plugins/
MobArena.jar
MobArena/
config.yml
announcements.yml
此时此刻, 或许你想直接开始设置竞技场, 但是你需要先看看配置文件，并把它配置成你喜欢的样子<del>就是说，还是根据情况配置一下吧</del>. 你可以在配置文件自定义MobArena的设置，职业，奖励，波数（怪物类型）

=建立竞技场=
==建造一个竞技场==
完整的竞技场应该包含一个可以选择职业的准备区域，一个竞技场地以及观察点(离开点)
下面是各个选项的讲解

大厅：
玩家加入游戏之前将会在大厅选择职业.一个建造好的游戏大厅会有每一个职业的选择牌子，玩家通过点击牌子可以获取一个职业, 还有一个铁块, 玩家可以通过点击铁块来表示他们已经准备好开始游戏.牌子必须在第一行写上职业的名字（区分大小写）,但是无论你在另外三行上写什么，都不会被怪物竞技场识别，你是不能写上 ,所以你不会得到确认的信息（如果有，那是另一个插件）

竞技场地：
这里是玩家和怪物搏斗的地方.竞技场地会有墙，可能会有一个屋顶 , 这样玩家和怪物就不能跑出去了. 这使得玩家们不会只是在竞技场外闲逛。.

观察点:
当玩家想要观看一场战斗时,他们可以使用/ma spec 命令来传送到竞技场的观察点. 这同样也是竞技场中玩家死去后会传送到的地方,前提是在配置文件中，把 spectate-after-death设置为ture. 这块区域要保证观看者不能走出去闲逛（进入竞技场地或者离远竞技场）因为在观看过程中，玩家是无敌的.

离开点:
在使用 /ma leave命令后,玩家和观察者会被传送到原来所在的地方,除非竞技场有一个离开点(只是可选). 使用离开点,可以准确控制玩家在游戏后去何处.

关于区域，传送点等，

当竞技场建好后，就是设置怪物竞技场的区域和传送点的时候了。在设置它们前，我们先来看看他们有什么作用.

区域:
一个竞技场需要一个竞技区域,然后还可以有一个准备区域，怪物竞技场会使用这些区域来确保玩家不会作弊（通过破坏竞技场来走出区域）,然后确保怪物竞技场所产生的怪物会在里面产生. 怪物竞技场非常排外（不要局外人）, 所以也最好把不想要的生物排除在外. 区域是通过区域工具来设置的.

传送点:
当玩家加入一个怪物竞技场的游戏时，他们会被传送到准备区域中的准备点来选择职业和准备开始游戏（通过点击铁块）.当每个人都准备好的时候，玩家会被传送到竞技场内的竞技场出生点。观察者会被传送到竞技场的观察点来进入观察区域,当游戏结束的时候，玩家和观察者会被传送到他们传送来之前的地方，或者去可选的离开点,传送点会用传送点工具来设置。.

出生点:
这里的出生点指的是怪物出生的地点.怪物竞技场只会在附近有玩家的出生点产出怪物（十五个方格的半径）.需要注意的是，怪物的数量不随着按照出生点的数量改变，只会因为在配置文件中波数的倍率改变和玩家的数量所改变.出生点可以通过出生点工具来设置。.

容器:
容器就是竞技场里的箱子，回收站等。这些容器将会在一场游戏后重置其内部空间为初始值。只有被声明了的容器才会更新其存储空间，所以仅仅在竞技场里放一个箱子可不够 - 它还需要被用工具声明。

==设置模式==
我们能用配置模式来设置竞技场。当我们进入配置模式时，物品栏将会被保存并给我们一套金工具（工具栏），每一个都有其独特作用。. We will also be able to fly, making moving around the arena a lot easier. Last, but not least, we will not be able to chat or type normal commands while in Setup Mode, because Setup Mode starts an isolated conversation with us.

To enter Setup Mode: Type /ma setup <arena>, where <arena> is the name of an arena. Note that if you only have one arena, you don't have to type the arena name. If the arena you want to set up has not yet been created, first type /ma addarena <arena> to create it.

To leave Setup Mode: Type done.

Note that if you have just installed MobArena, there will be a premade arena-node called default in the config-file already. If you want a different name, create a new arena first, and then remove the default arena by typing /ma delarena default.

In the next section, we will take a look at the different commands available in Setup Mode...

==设置模式的命令==

Setup Mode is an isolated conversation, which means Setup Mode will intercept everything we type. The reason for this is that it makes the commands in Setup Mode shorter (e.g. exp instead of /ma expandregion), and it also prevents us from accidentally typing commands from other plugins.

Below is a list of all the commands we can use in Setup Mode. Many of the commands have short-hand aliases which might make them even faster to type out. As an example, the expand command has the alias exp. Sometimes it's easier to remember the longer names, but the short-hand aliases are provided for faster setup.

done
Leave Setup Mode.
Aliases: end stop done quit

help
Display help screen.
Aliases: ? h

missing
Display a list of missing (mandatory) regions, warps, and points.
This command is useful if you have forgotten how far you are in the setup process, and what you still need to set up.
Aliases: miss

expand <region> <amount> <direction>
Expand a region by some amount in some direction.
Valid regions: ar for the arena region, or lr for the lobby region
Valid amounts: positive integers (whole numbers)
Valid directions: up, down, or out
Example: expand ar 5 up
Aliases: exp

show [<region>|<warp>|<point>]
Show a region, warp, or point(s) as red wool blocks.
Valid regions: ar for the arena region, or lr for the lobby region
Valid warps: arena, lobby, spec, exit
Valid points: spawns (or just sp) for spawnpoints, chests (or just c) for chests
Example: show sp

==设置时的工具==

The Toolbox is a set of golden tools, where each tool has a specific function. We will use these tools to set up the regions, warps, and points of our arena. The tools are used by left- or right-clicking a block while holding them, and the actions vary depending on the specific tool.

Note that the functions of a tool are described in the item tooltip, which we can see by opening up our inventory and hovering our mouse over the tools.

===区域工具===

The arena and lobby regions can be set up using the Region tools (axe). There are two golden axes in the Toolbox, and they both behave the same, except that one is for the arena region, and the other is for the lobby region. The tools are named accordingly, and they will display either "Arena Region" or "Lobby Region" above the quickbar when we select them.

Note that the behavior of the Region tools is similar to that of the WorldEdit wand (wooden axe), so if you are familiar with defining regions in WorldEdit, the Region tools should feel familiar.

Left-click: Set the first point to be the location of the target block
Right-click: Set the second point to be the location of the target block

Upon setting both points, the region will be defined. Type show ar (or show lr) to check that the region spans the desired area. If the region is a little bit too small, use the expand command (see above) to make it a little bigger.

Note: The region MUST look like a box (3D) and not a rectangle (2D). If the region is just a rectangle, your arena will not work correctly. The same applies if the arena floor is not fully contained in the box, so make sure to expand the region down a block or two to be sure.

===玩家传送点工具===

The arena, lobby, spectator, and exit warps can be set up using the Warps tool (hoe). The tool knows about all the warps, and we have to cycle through them to select the warp we want to place. The default selected warp is the arena warp.

Left-click: Set the currently selected warp on top of the target block
Right-click: Cycle between available warps

When left-clicking, the selected warp will be set to the top of the clicked block. The pitch (up and down) will be set to 0, which means when players are teleported, they will be looking "straight ahead". The yaw (rotation, left/right) will be set to whatever direction we are facing, when we set the warp. This means that we need to rotate ourselves to be looking in the direction we want the players to look in when they are teleported to the point.

Note: The arena, lobby, and spectator warps are all required. The exit warp is optional.

===怪物产生点工具===

The spawnpoints can be set up using the Spawnpoints tool (sword). The tool knows about all the spawnpoints of the arena, and allows us to remove existing ones or add new ones as we please.

Left-click: Add a spawnpoint on top of the target block
Right-click: Remove the spawnpoint on top of the target block (if the spawnpoint exists)

When left-clicking, a spawnpoint will be added on top of the clicked block, if one doesn't already exist. Right-clicking a block will remove a spawnpoint on that block, if one exists.

Note: Due to limitations and "bugs" in Minecraft, it is not possible (read: viable) to spawn mobs further than 15 blocks away from a player, and still make it target and attack the player naturally. Therefore, it is recommended to place many spawnpoints, so that every single location in the arena is within a 15-block radius of a spawnpoint. If a player is not within 15 blocks of any spawnpoint, MobArena will print a warning to the console with the coordinates. If no players are within 15 blocks of any spawnpoint, MobArena will default to using all spawnpoints, which may result in mobs spawning far away from players, so they will have to run around searching for them.

===容器工具===

The chests and containers can be set up using the Chests tool (spade). It works very much like the Spawnpoints tool, but requires that the clicked block is a valid container.

Left-click: Register the clicked container (if it wasn't registered)
Right-click: Unregister the clicked container (if it was registered)

When left-clicking a container, MobArena will register the container (if it wasn't registered already), such that when an arena session ends, the container will be restored to contain whatever was in it when the arena began. Right-clicking a container will unregister it.

=命令=
==玩家命令==

这些指令能够给所有玩家使用. 它们包括了加入, 离开, 旁观和列出所有竞技场(可用或不可用)

/ma join (<竞技场>) or /ma j (<竞技场>) - 加入指定名称的竞技场.
/ma leave or /ma l - 离开竞技场或是离开旁观者模式.
/ma notready - 获取所有未准备的玩家.
/ma spec (<竞技场>) or /ma s (<竞技场>) - 以旁观者模式加入指定名称竞技场.
/ma arenas - 获取所有竞技场的名字, 若是绿色则已启用, 灰色则未启用.
/ma players - 获取当前所有竞技场的所有玩家.
/ma players <竞技场> - 获取指定竞技场的所有玩家.
/ma class <职业> - 如果你在大厅里, 是应直接用指令而不是透过牌子互动选择职业.

==管理员指令==

Only ops and the console can issue these commands. They include forcefully starting or ending arenas, enabling/disabling individual arenas or MobArena entirely.

/ma enable - Enable MobArena.
/ma disable - Disable MobArena.
/ma enable <arena> - Enable the arena with the specified name.
/ma disable <arena> - Disable the arena with the specified name.
/ma force end - Forcefully end all arenas.
/ma force end <arena> - Forcefully end the arena with the specified name; forces all players to leave.
/ma force start <arena> - Forcefully start the arena with the specified name; forces all players who aren't ready to leave.
/ma notready <arena> - Get a list of all players in the given arena who aren't ready.
/ma restore <player> - Restore the inventory of the player with the given name, if possible.
/ma config reload - Reload the config-file into memory. This is useful if changes are made in the config-file while the server is running.
==建设指令==

Only ops (and the console, if it makes sense) can issue these commands. They include setting warp points, spawnpoints and region points.

/ma setup <arena> - Enter Setup Mode for the given arena.
/ma addarena <arena> - Create a new arena-node in the current world.
/ma delarena <arena> - Delete the arena with the given name.
/ma editarena <arena> - Toggle Edit Mode for the given arena.
/ma editarena <arena> [true|false] - Turn on or off Edit Mode for the given arena.
/ma setting <arena> - List all per-arena settings for the given arena.
/ma setting <arena> <setting> - Check the current value of the given setting for the given arena.
/ma setting <arena> <setting> <value> - Set the value of the given setting for the given arena to the given value.
/ma checkspawns - Shows the spawnpoints (of the arena you are currently standing in) which cover your current location as red wool blocks. This command can be used to check if specific
points in your arena are actually covered by spawnpoints or not.
/ma classchest <class> - While looking at a chest, link the chest to the given class as a linked class chest. Linking a class chest means MobArena will always copy the items from the linked
chest, regardless of any local class chests in arena lobbies. This is useful if you want a global class chest for a class.
/ma auto-generate <arena> - Auto-generate a new arena with the given name. The arena will be generated just below the player in the world they are standing in.
/ma auto-degenerate <arena> - Degenerate the arena with the given name, effectively restoring the patch that was "bulldozed" with the auto-generator.

=权限=
A permissions plugin is NOT required for MobArena to work, but if you want that extra bit of control, here's a rundown of the different types of permission nodes you can use with MobArena.

NOTE: MobArena uses sane defaults. This means that by default, all players can use all arenas and all classes, and ops can use all admin and setup commands. Unless you want to prevent some groups from accessing certain arenas or classes, or you want to give non-ops admin and setup permissions, there is no need to mess with any permissions at all, so go away from this page and remove all occurrences of mobarena in your permissions-file!

==竞技场权限==

Did you read the note at the top? If not, read it before you continue.

So, you want to remove permissions for certain arenas from certain users? Alright, that means you will have to negate or revoke the permissions in your permissions plugin. In bPermissions, the negation modifier is a caret, ^, in GroupManager and PermissionsEx it is a minus, -, and in zPermissions it is by setting the permission to false. The examples below revoke the permission for the default arena.

bPermissions: ^mobarena.arenas.default
GroupManager: -mobarena.arenas.default
zPermissions: mobarena.arenas.default: false

I recommend letting everyone enjoy all your arenas, but this could be used in combination with "leveling" plugins to allow players to use "harder" arenas at higher levels. It could also be used for sponsors-only arenas.

Still confused? Check the sample setup at the bottom of the page!

==职业权限==

Did you read the note at the top? If not, read it before you continue.

Alright, if you're reading this, you want to remove permissions for certain classes from certain users. As with the arena permissions, you need to negate or revoke the permissions in your permissions plugin. In bPermissions, the negation modifier is a caret, ^, in GroupManager and PermissionsEx it is a minus, -, and in zPermissions it is by setting the permission to false. The examples below revoke the permission for the Knight class.

bPermissions: ^mobarena.classes.knight
GroupManager: -mobarena.classes.knight
zPermissions: mobarena.classes.knight: false

Note how the class name is lowercase. This is important. Even if the Knight class is called KnIGhT in your config-file, it MUST be all lowercase in your permissions-file.

As with arenas, I recommend letting everyone enjoy all the classes, unless you have a special reason not to.

Still confused? Check the sample setup at the bottom of the page!

==命令权限==

Did you read the note at the top? If not, read it before you continue.

If you're reading this, you want to either give certain users access to some of the admin and/or setup commands, or you want to remove some of the user commands from some groups. If this is not the case, stop reading and leave this page!

The first group of commands are the user commands. They are accessible by all players by default, so don't put mobarena.use.* or something stupid like that in your permissions-file! If you want a group to not have access to the user commands, negate the permission mobarena.use, which is the parent permission node for all the user commands. See the classes and arenas sections for information on how to negate permissions. If that doesn't work, negate the mobarena.use.join and mobarena.use.spec permissions. That should be enough.

mobarena.use.join
mobarena.use.leave
mobarena.use.spec
mobarena.use.arenalist
mobarena.use.playerlist
mobarena.use.notready
mobarena.use.class
The admin commands are simple. They allow disabling/enabling MobArena and individual arenas, kicking players from the arenas, restoring player inventories if they got lost somehow, forcing arenas to start or end, and teleporting in and out of arenas regardless of what the arena state is. If you want to grant all of these permissions, use the parent permission node mobarena.admin. Don't mess around with * or something stupid like that.

mobarena.admin.enable
mobarena.admin.kick
mobarena.admin.restore
mobarena.admin.force
mobarena.admin.teleport
Setup commands are only for ops, just like admin commands. Do not give these permissions to random people, because they can remove your arenas and destroy your config-files, if they do something stupid. The setup commands allow you to manage arenas, regions, spawnpoints, chests, leaderboards, etc. They also allow you to set up new classes in-game. If you want to grant all of these permissions, use the parent permission node mobarena.setup. Don't mess around with * or something stupid like that.

mobarena.setup.config
mobarena.setup.setup
mobarena.setup.setting
mobarena.setup.addarena
mobarena.setup.removearena
mobarena.setup.editarena
mobarena.setup.spawnpoints
mobarena.setup.containers
mobarena.setup.checkdata
mobarena.setup.checkspawns
mobarena.setup.classchest
mobarena.setup.classes
mobarena.setup.leaderboards
mobarena.setup.autogenerate
mobarena.setup.autodegenerate
Sample setup

Assume you have a class called DiamondKnight that you only want your donors to be able to use (very common use case). How do you set up your permissions plugin when you have to revoke the class permission from the default group, but the donor group inherits from the default group? It's very simple: You're doing it wrong...

What you have to do instead is make an auxiliary default-group that contains all your default permissions, and have your default group inherit from that group, and furthermore revoke the DiamondKnight class permission in MobArena. Your donor group then also inherits from the auxiliary group, and everything is wonderful. Confusing? Here's a pseudo-code example:

default-aux: <-- This is the auxiliary group that is to
permissions: be inherited by the default group and
- essentials.balance the donor group. It is not used for
- essentials.pay anything else.
- essentials.sell

default: <-- This is the default group. It inherits
inherits: default-aux from default-aux, but also revokes the
permissions: permission for the special class.
- -mobarena.classes.diamondknight

donor: <-- This is the donor group, which also
inherits: default-aux inherits from default-aux, but it
permissions: does not revoke any class permissions,
- essentials.balance.others which means it has access to all of
- essentials.kit them by default.
This sample setup is pseudo code and cannot be simply copy/pasted into your own permissions file. It's your job to figure out how your permissions plugin works, and what its syntax is.
=物品语法（Item Syntax待搬运）=
=职业箱子（Class Chests待搬运｝=
=怪物波设置（Formulas待搬运）=
=怪物种类（Monster types待搬运）=
以上内容搬运自英文wiki[https://github.com/garbagemule/MobArena/wiki]

Multiworld

2015-02-07T13:36:37Z

9032676：/* Optional features */

{{待翻译}}
{{Bukkit Plugin Infobox
|插件名=Multiworld
|版本=v5.2.5
|前置插件=无
|兼容服务端版本=1.7.9 r0.2
|網址=http://dev.bukkit.org/bukkit-plugins/multiworld-v-2-0/
}}

=概述=
使用Multiworld插件，可以很容易地自定义每个世界对应的末地与下界，你可以随意配置。(受限于插件可实现的功能范围)
==历史==
我制作这个插件是因为该插件的原作者"Baummann"，现在不再活跃。之前，这个插件非常简易，只有两个命令: /goto and /newworld. 于是我接过这个项目并且开发出更好的版本。现在Multiworld已经更新到v5.2.5。
==特性==
自定义世界类型，例如沙子世界
支持修改玩家进入世界时的游戏模式
支持使用/mw move以及/mw goto指令于指定地点之间传送，就像在minecraft服务器使用/teleport指令一样
支持独立世界聊天频道

=命令与权限=
请求:本条目需要创建表格，成员请帮助编辑排版。

世界命令
命令描述权限
====世界====
/mw create <世界名称> [世界类型] [世界种子] 在数据库中创建一个新的世界.
注意: 你也可以使用这个命令来添加已存在的世界.
警告: 不要给你不信任的人这个权限，如果拥有这个权限，他将可以无限地创建世界! multiworld.command.create
/mw load <世界名称> 加载数据库中的世界 multiworld.command.load
/mw unload <世界名称> 卸载数据库中的世界(并非删除)，其他插件将无法查看到该世界 multiworld.command.unload
/mw delete <世界名称> 删除数据库中的世界.
警告: 这个功能是移除multiworld设置里面已经定义的一个世界! multiworld.command.delete
/mw list 列出服务器中已经生成地形的世界. multiworld.command.list
/mw info 显示当前世界的信息 multiworld.command.info
/mw listgens 列出可用的世界地形类型，辅助使用/mw create. multiworld.command.listgens
====规则====
/mw listflagsList 列出所有可能使用于标记值的选项在/mw setflag 指令内. commands.multiworld.command.flags
/mw setflag <世界名称> <标记值> <变量> 于指定世界内设置一个标记值或选项. multiworld.command.setflag
/mw getflag <世界名称> <标记值> 获取标记值在指定世界, 世界名称填写 * 则可以获取全部世界 flags.multiworld.command.getflag
====传送门====
/mw link <源世界> <目标世界> 连接 <源世界> 世界的地狱门到 <目标世界> 世界的地狱门.
提示，使用这个功能需要开启地狱门连接权限! multiworld.command.link.nether
/mw link-end <源世界> <目标世界> 连接全部未界传送门由 <源世界> 至 <目标世界>.
提示，使用这个功能需要开启未地传送门连接权限! multiworld.command.link.end
====传送====
/mw goto <世界名称> 将你自己传送到此世界, 这个指令也能够使用简写/goto <世界名称> multiworld.command.goto
/mw move <玩家名称> <世界名称> 移动指定玩家至一个世界 multiworld.command.move
====出生点====
/mw spawn传送到所在世界的出生点, 移动其他人需要用 /mw move.multiworld.command.spawn
/mw setspawn设置所在世界的出生点, 你可以使用这个命令来修正出生点。 pointmultiworld.command.setspawn
====插件基础命令====
/mw save保存插件数据multiworld.command.save
/mw reload重新加载插件数据multiworld.command.reload
/mw debug显示调试信息，这些将会在你碰到插件错误（报告）时非常有用multiworld.command.debug
/mw help显示帮助，这样你就不用每次来看这个网页了multiworld.command.help
/mw eastereggNot a real command, but there is a easter egg hidden in multiworld-（这个命令比较有趣和无用，故不作翻译。你可以尝试下提示：复活节彩蛋）

====其他====
-如果想要使他人在进入一个世界后转为创造模式. 建议给所有人这个权限.multiworld.creativemode
-Gives access to the basic Multiworld moderator controll, this permission won't allow users to modefy settings of existing world, it only allows them to view the settings / teleport to worldsmultiworld.basic
-你可以使用这个权限来给予一个人关于这个插件的所有权限.Multiworld.admin

=可选的特性=
特性 NameDescriptionConfiguration 的位置
给予 worldoptions.useEndPortalHandler 权限，未地传送门管理器则允许你自定义一个未地传送门
下界传送门管理器，这个管理器可能使下界传送门重新定义到一个自定义的地狱世界，这个配置在 worldoptions.usePortalHandler
WorldChatSeperatorThis allows you to use the RecieveChat and the SendChat flags on a worldoptions.useWorldChatSeperator
GamemodeChangerThis allows you to use the flag CreativeWorld to turn on creative mode for a world, to use this you need to give you users the following permissions on all worlds: multiworld.creativemode
This module also comes with a other configuration settings, when you turn off usecreativemodeinv, it ONLY handles the gamemode part, it won't change the inventory contents, this can be used if you have a custom plugin for per world inventories.options.usecreativemode
EnderBlockPrevents the use of ender chests in creative mode, this can be used to prevent people from cheating stuff by storing it inside a ender chest in a creative world, and then removing it in a survival world.options.blockEnderChestInCrea
WorldSpawnHandlerThis allows you to have custom respawn worlds per world group, this can be setup by turning this part on to generate the configuration needed for this.options.useWorldSpawnHandler
CraftbukkitHooksAllows multiworld to hook into craftbukkit to display information that the bukit api won't provide. This feature will try to turn itself off when there are any errors.options.craftbukkitHooks

=Multiworld and Data=
Multiworld is using a statistcs tracking code so useage statistics wil be logged, for more information what is logged see:
Usage statistics at v3.5.0
=Other recommended plugins for your server=
[[LocationTeleport]] - This plugin teleports users when they enter a arena, when you shape the area like a portal, you can have your own portals
[[hothgenerator]] - Generates a awesome snow world
/mw create WorldName plugin:HothGenerator
(Case sensitive)
[[multiinv]] - Allows more control between the inventories of worlds than multiworld can provide on its own.

Multiworld

2015-01-27T14:29:09Z

9032676：/* 命令与权限 */

{{待翻译}}
{{Bukkit Plugin Infobox
|插件名=Multiworld
|版本=v5.2.5
|前置插件=无
|兼容服务端版本=1.7.9 r0.2
|網址=http://dev.bukkit.org/bukkit-plugins/multiworld-v-2-0/
}}

=概述=
使用Multiworld插件，可以很容易地自定义每个世界对应的末地与下界，你可以随意配置。(受限于插件可实现的功能范围)
==历史==
我制作这个插件是因为该插件的原作者"Baummann"，现在不再活跃。之前，这个插件非常简易，只有两个命令: /goto and /newworld. 于是我接过这个项目并且开发出更好的版本。现在Multiworld已经更新到v5.2.5。
==特性==
自定义世界类型，例如沙子世界
支持修改玩家进入世界时的游戏模式
支持使用/mw move以及/mw goto指令于指定地点之间传送，就像在minecraft服务器使用/teleport指令一样
支持独立世界聊天频道

=命令与权限=
请求:本条目需要创建表格，成员请帮助编辑排版。

世界命令
命令描述权限
====世界====
/mw create <世界名称> [世界类型] [世界种子] 在数据库中创建一个新的世界.
注意: 你也可以使用这个命令来添加已存在的世界.
警告: 不要给你不信任的人这个权限，如果拥有这个权限，他将可以无限地创建世界! multiworld.command.create
/mw load <世界名称> 加载数据库中的世界 multiworld.command.load
/mw unload <世界名称> 卸载数据库中的世界(并非删除)，其他插件将无法查看到该世界 multiworld.command.unload
/mw delete <世界名称> 删除数据库中的世界.
警告: 这个功能是移除multiworld设置里面已经定义的一个世界! multiworld.command.delete
/mw list 列出服务器中已经生成地形的世界. multiworld.command.list
/mw info 显示当前世界的信息 multiworld.command.info
/mw listgens 列出可用的世界地形类型，辅助使用/mw create. multiworld.command.listgens
====规则====
/mw listflagsList 列出所有可能使用于标记值的选项在/mw setflag 指令内. commands.multiworld.command.flags
/mw setflag <世界名称> <标记值> <变量> 于指定世界内设置一个标记值或选项. multiworld.command.setflag
/mw getflag <世界名称> <标记值> 获取标记值在指定世界, 世界名称填写 * 则可以获取全部世界 flags.multiworld.command.getflag
====传送门====
/mw link <源世界> <目标世界> 连接 <源世界> 世界的地狱门到 <目标世界> 世界的地狱门.
提示，使用这个功能需要开启地狱门连接权限! multiworld.command.link.nether
/mw link-end <源世界> <目标世界> 连接全部未界传送门由 <源世界> 至 <目标世界>.
提示，使用这个功能需要开启未地传送门连接权限! multiworld.command.link.end
====传送====
/mw goto <世界名称> 将你自己传送到此世界, 这个指令也能够使用简写/goto <世界名称> multiworld.command.goto
/mw move <玩家名称> <世界名称> 移动指定玩家至一个世界 multiworld.command.move
====出生点====
/mw spawnTeleports yourself to spawn, to move other people use /mw move.multiworld.command.spawn
/mw setspawnSets the spawn of a world, you can use this to correct the starting spawn pointmultiworld.command.setspawn
Core and Utility
/mw saveSaves the plugin datamultiworld.command.save
/mw reloadReload the plugin datamultiworld.command.reload
/mw debugShows some debugging information, this information is very handy when you create a bug reportmultiworld.command.debug
/mw helpShows help about the commands used in Multiworld, useful so you don't need to go to this pagemultiworld.command.help
/mw eastereggNot a real command, but there is a easter egg hidden in multiworld-
====其他====
-Permission used to allow multiworld to change the gamemode of the affected player when entering a creative world. Its recommend to give everyone this permission.multiworld.creativemode
-Gives access to the basic Multiworld moderator controll, this permission won't allow users to modefy settings of existing world, it only allows them to view the settings / teleport to worldsmultiworld.basic
-All the permissions from multiworld, you can also use the star permission to give them all permissions.Multiworld.admin

=Optional features=
Feature NameDescriptionConfiguration location
End portal handlerThe end portal handlers allows you to define custom end portals per worldoptions.useEndPortalHandler
Nether portal handlerThis addon makes it posiable to redirect netherportals to custom nether worlds, this setting is per-worldoptions.usePortalHandler
WorldChatSeperatorThis allows you to use the RecieveChat and the SendChat flags on a worldoptions.useWorldChatSeperator
GamemodeChangerThis allows you to use the flag CreativeWorld to turn on creative mode for a world, to use this you need to give you users the following permissions on all worlds: multiworld.creativemode
This module also comes with a other configuration settings, when you turn off usecreativemodeinv, it ONLY handles the gamemode part, it won't change the inventory contents, this can be used if you have a custom plugin for per world inventories.options.usecreativemode
EnderBlockPrevents the use of ender chests in creative mode, this can be used to prevent people from cheating stuff by storing it inside a ender chest in a creative world, and then removing it in a survival world.options.blockEnderChestInCrea
WorldSpawnHandlerThis allows you to have custom respawn worlds per world group, this can be setup by turning this part on to generate the configuration needed for this.options.useWorldSpawnHandler
CraftbukkitHooksAllows multiworld to hook into craftbukkit to display information that the bukit api won't provide. This feature will try to turn itself off when there are any errors.options.craftbukkitHooks
=Multiworld and Data=
Multiworld is using a statistcs tracking code so useage statistics wil be logged, for more information what is logged see:
Usage statistics at v3.5.0
=Other recommended plugins for your server=
[[LocationTeleport]] - This plugin teleports users when they enter a arena, when you shape the area like a portal, you can have your own portals
[[hothgenerator]] - Generates a awesome snow world
/mw create WorldName plugin:HothGenerator
(Case sensitive)
[[multiinv]] - Allows more control between the inventories of worlds than multiworld can provide on its own.

Multiworld

2015-01-27T14:27:52Z

9032676：/* 命令与权限 */

{{待翻译}}
{{Bukkit Plugin Infobox
|插件名=Multiworld
|版本=v5.2.5
|前置插件=无
|兼容服务端版本=1.7.9 r0.2
|網址=http://dev.bukkit.org/bukkit-plugins/multiworld-v-2-0/
}}

=概述=
使用Multiworld插件，可以很容易地自定义每个世界对应的末地与下界，你可以随意配置。(受限于插件可实现的功能范围)
==历史==
我制作这个插件是因为该插件的原作者"Baummann"，现在不再活跃。之前，这个插件非常简易，只有两个命令: /goto and /newworld. 于是我接过这个项目并且开发出更好的版本。现在Multiworld已经更新到v5.2.5。
==特性==
自定义世界类型，例如沙子世界
支持修改玩家进入世界时的游戏模式
支持使用/mw move以及/mw goto指令于指定地点之间传送，就像在minecraft服务器使用/teleport指令一样
支持独立世界聊天频道

=命令与权限=
请求:本条目需要创建表格，成员请帮助编辑排版。

世界命令
命令描述权限
====世界====
/mw create <世界名称> [世界类型] [世界种子] 在数据库中创建一个新的世界.
注意: 你也可以使用这个命令来添加已存在的世界.
警告: 不要给你不信任的人这个权限，如果拥有这个权限，他将可以无限地创建世界! multiworld.command.create
/mw load <世界名称> 加载数据库中的世界 multiworld.command.load
/mw unload <世界名称> 卸载数据库中的世界(并非删除)，其他插件将无法查看到该世界 multiworld.command.unload
/mw delete <世界名称> 删除数据库中的世界.
警告: 这个功能是移除multiworld设置里面已经定义的一个世界! multiworld.command.delete
/mw list 列出服务器中已经生成地形的世界. multiworld.command.list
/mw info 显示当前世界的信息 multiworld.command.info
/mw listgens 列出可用的世界地形类型，辅助使用/mw create. multiworld.command.listgens
==规则==
/mw listflagsList 列出所有可能使用于标记值的选项在/mw setflag 指令内. commands.multiworld.command.flags
/mw setflag <世界名称> <标记值> <变量> 于指定世界内设置一个标记值或选项. multiworld.command.setflag
/mw getflag <世界名称> <标记值> 获取标记值在指定世界, 世界名称填写 * 则可以获取全部世界 flags.multiworld.command.getflag
==传送门==
/mw link <源世界> <目标世界> 连接 <源世界> 世界的地狱门到 <目标世界> 世界的地狱门.
提示，使用这个功能需要开启地狱门连接权限! multiworld.command.link.nether
/mw link-end <源世界> <目标世界> 连接全部未界传送门由 <源世界> 至 <目标世界>.
提示，使用这个功能需要开启未地传送门连接权限! multiworld.command.link.end
==传送==
/mw goto <世界名称> 将你自己传送到此世界, 这个指令也能够使用简写/goto <世界名称> multiworld.command.goto
/mw move <玩家名称> <世界名称> 移动指定玩家至一个世界 multiworld.command.move
Spawning
/mw spawnTeleports yourself to spawn, to move other people use /mw move.multiworld.command.spawn
/mw setspawnSets the spawn of a world, you can use this to correct the starting spawn pointmultiworld.command.setspawn
Core and Utility
/mw saveSaves the plugin datamultiworld.command.save
/mw reloadReload the plugin datamultiworld.command.reload
/mw debugShows some debugging information, this information is very handy when you create a bug reportmultiworld.command.debug
/mw helpShows help about the commands used in Multiworld, useful so you don't need to go to this pagemultiworld.command.help
/mw eastereggNot a real command, but there is a easter egg hidden in multiworld-
其他
-Permission used to allow multiworld to change the gamemode of the affected player when entering a creative world. Its recommend to give everyone this permission.multiworld.creativemode
-Gives access to the basic Multiworld moderator controll, this permission won't allow users to modefy settings of existing world, it only allows them to view the settings / teleport to worldsmultiworld.basic
-All the permissions from multiworld, you can also use the star permission to give them all permissions.Multiworld.admin

=Optional features=
Feature NameDescriptionConfiguration location
End portal handlerThe end portal handlers allows you to define custom end portals per worldoptions.useEndPortalHandler
Nether portal handlerThis addon makes it posiable to redirect netherportals to custom nether worlds, this setting is per-worldoptions.usePortalHandler
WorldChatSeperatorThis allows you to use the RecieveChat and the SendChat flags on a worldoptions.useWorldChatSeperator
GamemodeChangerThis allows you to use the flag CreativeWorld to turn on creative mode for a world, to use this you need to give you users the following permissions on all worlds: multiworld.creativemode
This module also comes with a other configuration settings, when you turn off usecreativemodeinv, it ONLY handles the gamemode part, it won't change the inventory contents, this can be used if you have a custom plugin for per world inventories.options.usecreativemode
EnderBlockPrevents the use of ender chests in creative mode, this can be used to prevent people from cheating stuff by storing it inside a ender chest in a creative world, and then removing it in a survival world.options.blockEnderChestInCrea
WorldSpawnHandlerThis allows you to have custom respawn worlds per world group, this can be setup by turning this part on to generate the configuration needed for this.options.useWorldSpawnHandler
CraftbukkitHooksAllows multiworld to hook into craftbukkit to display information that the bukit api won't provide. This feature will try to turn itself off when there are any errors.options.craftbukkitHooks
=Multiworld and Data=
Multiworld is using a statistcs tracking code so useage statistics wil be logged, for more information what is logged see:
Usage statistics at v3.5.0
=Other recommended plugins for your server=
[[LocationTeleport]] - This plugin teleports users when they enter a arena, when you shape the area like a portal, you can have your own portals
[[hothgenerator]] - Generates a awesome snow world
/mw create WorldName plugin:HothGenerator
(Case sensitive)
[[multiinv]] - Allows more control between the inventories of worlds than multiworld can provide on its own.

Multiworld

2015-01-27T14:27:26Z

9032676：/* 命令与权限 */

{{待翻译}}
{{Bukkit Plugin Infobox
|插件名=Multiworld
|版本=v5.2.5
|前置插件=无
|兼容服务端版本=1.7.9 r0.2
|網址=http://dev.bukkit.org/bukkit-plugins/multiworld-v-2-0/
}}

=概述=
使用Multiworld插件，可以很容易地自定义每个世界对应的末地与下界，你可以随意配置。(受限于插件可实现的功能范围)
==历史==
我制作这个插件是因为该插件的原作者"Baummann"，现在不再活跃。之前，这个插件非常简易，只有两个命令: /goto and /newworld. 于是我接过这个项目并且开发出更好的版本。现在Multiworld已经更新到v5.2.5。
==特性==
自定义世界类型，例如沙子世界
支持修改玩家进入世界时的游戏模式
支持使用/mw move以及/mw goto指令于指定地点之间传送，就像在minecraft服务器使用/teleport指令一样
支持独立世界聊天频道

=命令与权限=
请求:本条目需要创建表格，成员请帮助编辑排版。

世界命令
命令描述权限
====世界====
/mw create <世界名称> [世界类型] [世界种子] 在数据库中创建一个新的世界.
注意: 你也可以使用这个命令来添加已存在的世界.
警告: 不要给你不信任的人这个权限，如果拥有这个权限，他将可以无限地创建世界! multiworld.command.create
/mw load <世界名称> 加载数据库中的世界 multiworld.command.load
/mw unload <世界名称> 卸载数据库中的世界(并非删除)，其他插件将无法查看到该世界 multiworld.command.unload
/mw delete <世界名称> 删除数据库中的世界.
警告: 这个功能是移除multiworld设置里面已经定义的一个世界! multiworld.command.delete
/mw list 列出服务器中已经生成地形的世界. multiworld.command.list
/mw info 显示当前世界的信息 multiworld.command.info
/mw listgens 列出可用的世界地形类型，辅助使用/mw create. multiworld.command.listgens
==规则==
/mw listflagsList 列出所有可能使用于标记值的选项在/mw setflag 指令内. commands.multiworld.command.flags
/mw setflag <世界名称> <标记值> <变量> 于指定世界内设置一个标记值或选项. multiworld.command.setflag
/mw getflag <世界名称> <标记值> 获取标记值在指定世界, 世界名称填写 * 则可以获取全部世界 flags.multiworld.command.getflag
==传送门==
/mw link <源世界> <目标世界> 连接 <源世界> 世界的地狱门到 <目标世界> 世界的地狱门.
提示，使用这个功能需要开启地狱门连接权限! multiworld.command.link.nether
/mw link-end <源世界> <目标世界> 连接全部未界传送门由 <源世界> 至 <目标世界>.
提示，使用这个功能需要开启未地传送门连接权限! multiworld.command.link.end
==传送==
/mw goto <世界名称> 将你自己传送到此世界, 这个指令也能够使用简写/goto <世界名称> multiworld.command.goto
/mw move <玩家名称> <世界名称> 移动指定玩家至一个世界 multiworld.command.move
Spawning
/mw spawnTeleports yourself to spawn, to move other people use /mw move.multiworld.command.spawn
/mw setspawnSets the spawn of a world, you can use this to correct the starting spawn pointmultiworld.command.setspawn
Core and Utility
/mw saveSaves the plugin datamultiworld.command.save
/mw reloadReload the plugin datamultiworld.command.reload
/mw debugShows some debugging information, this information is very handy when you create a bug reportmultiworld.command.debug
/mw helpShows help about the commands used in Multiworld, useful so you don't need to go to this pagemultiworld.command.help
/mw eastereggNot a real command, but there is a easter egg hidden in multiworld-
其他
-Permission used to allow multiworld to change the gamemode of the affected player when entering a creative world. Its recommend to give everyone this permission.multiworld.creativemode
-Gives access to the basic Multiworld moderator controll, this permission won't allow users to modefy settings of existing world, it only allows them to view the settings / teleport to worldsmultiworld.basic
-All the permissions from multiworld, you can also use the star permission to give them all permissions.Multiworld.admin

=Optional features=
Feature NameDescriptionConfiguration location
End portal handlerThe end portal handlers allows you to define custom end portals per worldoptions.useEndPortalHandler
Nether portal handlerThis addon makes it posiable to redirect netherportals to custom nether worlds, this setting is per-worldoptions.usePortalHandler
WorldChatSeperatorThis allows you to use the RecieveChat and the SendChat flags on a worldoptions.useWorldChatSeperator
GamemodeChangerThis allows you to use the flag CreativeWorld to turn on creative mode for a world, to use this you need to give you users the following permissions on all worlds: multiworld.creativemode
This module also comes with a other configuration settings, when you turn off usecreativemodeinv, it ONLY handles the gamemode part, it won't change the inventory contents, this can be used if you have a custom plugin for per world inventories.options.usecreativemode
EnderBlockPrevents the use of ender chests in creative mode, this can be used to prevent people from cheating stuff by storing it inside a ender chest in a creative world, and then removing it in a survival world.options.blockEnderChestInCrea
WorldSpawnHandlerThis allows you to have custom respawn worlds per world group, this can be setup by turning this part on to generate the configuration needed for this.options.useWorldSpawnHandler
CraftbukkitHooksAllows multiworld to hook into craftbukkit to display information that the bukit api won't provide. This feature will try to turn itself off when there are any errors.options.craftbukkitHooks
=Multiworld and Data=
Multiworld is using a statistcs tracking code so useage statistics wil be logged, for more information what is logged see:
Usage statistics at v3.5.0
=Other recommended plugins for your server=
[[LocationTeleport]] - This plugin teleports users when they enter a arena, when you shape the area like a portal, you can have your own portals
[[hothgenerator]] - Generates a awesome snow world
/mw create WorldName plugin:HothGenerator
(Case sensitive)
[[multiinv]] - Allows more control between the inventories of worlds than multiworld can provide on its own.

Multiworld

2015-01-27T14:26:11Z

9032676：

{{待翻译}}
{{Bukkit Plugin Infobox
|插件名=Multiworld
|版本=v5.2.5
|前置插件=无
|兼容服务端版本=1.7.9 r0.2
|網址=http://dev.bukkit.org/bukkit-plugins/multiworld-v-2-0/
}}

=概述=
使用Multiworld插件，可以很容易地自定义每个世界对应的末地与下界，你可以随意配置。(受限于插件可实现的功能范围)
==历史==
我制作这个插件是因为该插件的原作者"Baummann"，现在不再活跃。之前，这个插件非常简易，只有两个命令: /goto and /newworld. 于是我接过这个项目并且开发出更好的版本。现在Multiworld已经更新到v5.2.5。
==特性==
自定义世界类型，例如沙子世界
支持修改玩家进入世界时的游戏模式
支持使用/mw move以及/mw goto指令于指定地点之间传送，就像在minecraft服务器使用/teleport指令一样
支持独立世界聊天频道

=命令与权限=
请求:本条目需要创建表格，成员请帮助编辑排版。

世界命令
命令描述权限
==世界==
/mw create <世界名称> [世界类型] [世界种子] 在数据库中创建一个新的世界.
注意: 你也可以使用这个命令来添加已存在的世界.
警告: 不要给你不信任的人这个权限，如果拥有这个权限，他将可以无限地创建世界! multiworld.command.create
/mw load <世界名称> 加载数据库中的世界 multiworld.command.load
/mw unload <世界名称> 卸载数据库中的世界(并非删除)，其他插件将无法查看到该世界 multiworld.command.unload
/mw delete <世界名称> 删除数据库中的世界.
警告: 这个功能是移除multiworld设置里面已经定义的一个世界! multiworld.command.delete
/mw list 列出服务器中已经生成地形的世界. multiworld.command.list
/mw info 显示当前世界的信息 multiworld.command.info
/mw listgens 列出可用的世界地形类型，辅助使用/mw create. multiworld.command.listgens
==规则==
/mw listflagsList 列出所有可能使用于标记值的选项在/mw setflag 指令内. commands.multiworld.command.flags
/mw setflag <世界名称> <标记值> <变量> 于指定世界内设置一个标记值或选项. multiworld.command.setflag
/mw getflag <世界名称> <标记值> 获取标记值在指定世界, 世界名称填写 * 则可以获取全部世界 flags.multiworld.command.getflag
==传送门==
/mw link <源世界> <目标世界> 连接 <源世界> 世界的地狱门到 <目标世界> 世界的地狱门.
提示，使用这个功能需要开启地狱门连接权限! multiworld.command.link.nether
/mw link-end <源世界> <目标世界> 连接全部未界传送门由 <源世界> 至 <目标世界>.
提示，使用这个功能需要开启未地传送门连接权限! multiworld.command.link.end
==传送==
/mw goto <世界名称> 将你自己传送到此世界, 这个指令也能够使用简写/goto <世界名称> multiworld.command.goto
/mw move <玩家名称> <世界名称> 移动指定玩家至一个世界 multiworld.command.move
Spawning
/mw spawnTeleports yourself to spawn, to move other people use /mw move.multiworld.command.spawn
/mw setspawnSets the spawn of a world, you can use this to correct the starting spawn pointmultiworld.command.setspawn
Core and Utility
/mw saveSaves the plugin datamultiworld.command.save
/mw reloadReload the plugin datamultiworld.command.reload
/mw debugShows some debugging information, this information is very handy when you create a bug reportmultiworld.command.debug
/mw helpShows help about the commands used in Multiworld, useful so you don't need to go to this pagemultiworld.command.help
/mw eastereggNot a real command, but there is a easter egg hidden in multiworld-
其他
-Permission used to allow multiworld to change the gamemode of the affected player when entering a creative world. Its recommend to give everyone this permission.multiworld.creativemode
-Gives access to the basic Multiworld moderator controll, this permission won't allow users to modefy settings of existing world, it only allows them to view the settings / teleport to worldsmultiworld.basic
-All the permissions from multiworld, you can also use the star permission to give them all permissions.Multiworld.admin

=Optional features=
Feature NameDescriptionConfiguration location
End portal handlerThe end portal handlers allows you to define custom end portals per worldoptions.useEndPortalHandler
Nether portal handlerThis addon makes it posiable to redirect netherportals to custom nether worlds, this setting is per-worldoptions.usePortalHandler
WorldChatSeperatorThis allows you to use the RecieveChat and the SendChat flags on a worldoptions.useWorldChatSeperator
GamemodeChangerThis allows you to use the flag CreativeWorld to turn on creative mode for a world, to use this you need to give you users the following permissions on all worlds: multiworld.creativemode
This module also comes with a other configuration settings, when you turn off usecreativemodeinv, it ONLY handles the gamemode part, it won't change the inventory contents, this can be used if you have a custom plugin for per world inventories.options.usecreativemode
EnderBlockPrevents the use of ender chests in creative mode, this can be used to prevent people from cheating stuff by storing it inside a ender chest in a creative world, and then removing it in a survival world.options.blockEnderChestInCrea
WorldSpawnHandlerThis allows you to have custom respawn worlds per world group, this can be setup by turning this part on to generate the configuration needed for this.options.useWorldSpawnHandler
CraftbukkitHooksAllows multiworld to hook into craftbukkit to display information that the bukit api won't provide. This feature will try to turn itself off when there are any errors.options.craftbukkitHooks
=Multiworld and Data=
Multiworld is using a statistcs tracking code so useage statistics wil be logged, for more information what is logged see:
Usage statistics at v3.5.0
=Other recommended plugins for your server=
[[LocationTeleport]] - This plugin teleports users when they enter a arena, when you shape the area like a portal, you can have your own portals
[[hothgenerator]] - Generates a awesome snow world
/mw create WorldName plugin:HothGenerator
(Case sensitive)
[[multiinv]] - Allows more control between the inventories of worlds than multiworld can provide on its own.

Multiworld

2015-01-27T14:24:47Z

9032676：

{{待翻译}}
{{Bukkit Plugin Infobox
|插件名=Multiworld
|版本=v5.2.5
|前置插件=无
|兼容服务端版本=1.7.9 r0.2
|網址=http://dev.bukkit.org/bukkit-plugins/multiworld-v-2-0/
}}

=概述=
使用Multiworld插件，可以很容易地自定义每个世界对应的末地与下界，你可以随意配置。(受限于插件可实现的功能范围)
==历史==
我制作这个插件是因为该插件的原作者"Baummann"，现在不再活跃。之前，这个插件非常简易，只有两个命令: /goto and /newworld. 于是我接过这个项目并且开发出更好的版本。现在Multiworld已经更新到v5.2.5。
==特性==
自定义世界类型，例如沙子世界
支持修改玩家进入世界时的游戏模式
支持使用/mw move以及/mw goto指令于指定地点之间传送，就像在minecraft服务器使用/teleport指令一样
支持独立世界聊天频道

=命令与权限=
请求:本条目需要创建表格，成员请帮助编辑排版。

世界命令
命令描述权限
=世界=
/mw create <世界名称> [世界类型] [世界种子] 在数据库中创建一个新的世界.
注意: 你也可以使用这个命令来添加已存在的世界.
警告: 不要给你不信任的人这个权限，如果拥有这个权限，他将可以无限地创建世界! multiworld.command.create
/mw load <世界名称> 加载数据库中的世界 multiworld.command.load
/mw unload <世界名称> 卸载数据库中的世界(并非删除)，其他插件将无法查看到该世界 multiworld.command.unload
/mw delete <世界名称> 删除数据库中的世界.
警告: 这个功能是移除multiworld设置里面已经定义的一个世界! multiworld.command.delete
/mw list 列出服务器中已经生成地形的世界. multiworld.command.list
/mw info 显示当前世界的信息 multiworld.command.info
/mw listgens 列出可用的世界地形类型，辅助使用/mw create. multiworld.command.listgens
=规则=
/mw listflagsList 列出所有可能使用于标记值的选项在/mw setflag 指令内. commands.multiworld.command.flags
/mw setflag <世界名称> <标记值> <变量> 于指定世界内设置一个标记值或选项. multiworld.command.setflag
/mw getflag <世界名称> <标记值> 获取标记值在指定世界, 世界名称填写 * 则可以获取全部世界 flags.multiworld.command.getflag
=传送门=
/mw link <源世界> <目标世界> 连接 <源世界> 世界的地狱门到 <目标世界> 世界的地狱门.
提示，使用这个功能需要开启地狱门连接权限! multiworld.command.link.nether
/mw link-end <源世界> <目标世界> 连接全部未界传送门由 <源世界> 至 <目标世界>.
提示，使用这个功能需要开启未地传送门连接权限! multiworld.command.link.end
=传送=
/mw goto <世界名称> 将你自己传送到此世界, 这个指令也能够使用简写/goto <世界名称> multiworld.command.goto
/mw move <玩家名称> <世界名称> 移动指定玩家至一个世界 multiworld.command.move
Spawning
/mw spawnTeleports yourself to spawn, to move other people use /mw move.multiworld.command.spawn
/mw setspawnSets the spawn of a world, you can use this to correct the starting spawn pointmultiworld.command.setspawn
Core and Utility
/mw saveSaves the plugin datamultiworld.command.save
/mw reloadReload the plugin datamultiworld.command.reload
/mw debugShows some debugging information, this information is very handy when you create a bug reportmultiworld.command.debug
/mw helpShows help about the commands used in Multiworld, useful so you don't need to go to this pagemultiworld.command.help
/mw eastereggNot a real command, but there is a easter egg hidden in multiworld-
其他
-Permission used to allow multiworld to change the gamemode of the affected player when entering a creative world. Its recommend to give everyone this permission.multiworld.creativemode
-Gives access to the basic Multiworld moderator controll, this permission won't allow users to modefy settings of existing world, it only allows them to view the settings / teleport to worldsmultiworld.basic
-All the permissions from multiworld, you can also use the star permission to give them all permissions.Multiworld.admin

=Optional features=
Feature NameDescriptionConfiguration location
End portal handlerThe end portal handlers allows you to define custom end portals per worldoptions.useEndPortalHandler
Nether portal handlerThis addon makes it posiable to redirect netherportals to custom nether worlds, this setting is per-worldoptions.usePortalHandler
WorldChatSeperatorThis allows you to use the RecieveChat and the SendChat flags on a worldoptions.useWorldChatSeperator
GamemodeChangerThis allows you to use the flag CreativeWorld to turn on creative mode for a world, to use this you need to give you users the following permissions on all worlds: multiworld.creativemode
This module also comes with a other configuration settings, when you turn off usecreativemodeinv, it ONLY handles the gamemode part, it won't change the inventory contents, this can be used if you have a custom plugin for per world inventories.options.usecreativemode
EnderBlockPrevents the use of ender chests in creative mode, this can be used to prevent people from cheating stuff by storing it inside a ender chest in a creative world, and then removing it in a survival world.options.blockEnderChestInCrea
WorldSpawnHandlerThis allows you to have custom respawn worlds per world group, this can be setup by turning this part on to generate the configuration needed for this.options.useWorldSpawnHandler
CraftbukkitHooksAllows multiworld to hook into craftbukkit to display information that the bukit api won't provide. This feature will try to turn itself off when there are any errors.options.craftbukkitHooks
=Multiworld and Data=
Multiworld is using a statistcs tracking code so useage statistics wil be logged, for more information what is logged see:
Usage statistics at v3.5.0
=Other recommended plugins for your server=
[[LocationTeleport]] - This plugin teleports users when they enter a arena, when you shape the area like a portal, you can have your own portals
[[hothgenerator]] - Generates a awesome snow world
/mw create WorldName plugin:HothGenerator
(Case sensitive)
[[multiinv]] - Allows more control between the inventories of worlds than multiworld can provide on its own.

Multiworld

2015-01-27T14:20:23Z

9032676：/* 命令与权限 */

{{待翻译}}
{{Bukkit Plugin Infobox
|插件名=Multiworld
|版本=v5.2.5
|前置插件=无
|兼容服务端版本=1.7.9 r0.2
|網址=http://dev.bukkit.org/bukkit-plugins/multiworld-v-2-0/
}}

=概述=
使用Multiworld插件，可以很容易地自定义每个世界对应的末地与下界，你可以随意配置。(受限于插件可实现的功能范围)
==历史==
我制作这个插件是因为该插件的原作者"Baummann"，现在不再活跃。之前，这个插件非常简易，只有两个命令: /goto and /newworld. 于是我接过这个项目并且开发出更好的版本。现在Multiworld已经更新到v5.2.5。
==特性==
自定义世界类型，例如沙子世界
支持修改玩家进入世界时的游戏模式
支持使用/mw move以及/mw goto指令于指定地点之间传送，就像在minecraft服务器使用/teleport指令一样
支持独立世界聊天频道

=命令与权限=
请求:本条目需要创建表格，成员请帮助编辑排版。

世界命令
命令描述权限
【世界】
/mw create <世界名称> [世界类型] [世界种子] 在数据库中创建一个新的世界.
注意: 你也可以使用这个命令来添加已存在的世界.
警告: 不要给你不信任的人这个权限，如果拥有这个权限，他将可以无限地创建世界! multiworld.command.create
/mw load <世界名称> 加载数据库中的世界 multiworld.command.load
/mw unload <世界名称> 卸载数据库中的世界(并非删除)，其他插件将无法查看到该世界 multiworld.command.unload
/mw delete <世界名称> 删除数据库中的世界.
警告: 这个功能是移除multiworld设置里面已经定义的一个世界! multiworld.command.delete
/mw list 列出服务器中已经生成地形的世界. multiworld.command.list
/mw info 显示当前世界的信息 multiworld.command.info
/mw listgens 列出可用的世界地形类型，辅助使用/mw create. multiworld.command.listgens
【规则】
/mw listflagsList 列出所有可能使用于标记值的选项在/mw setflag 指令内. commands.multiworld.command.flags
/mw setflag <世界名称> <标记值> <变量> 于指定世界内设置一个标记值或选项. multiworld.command.setflag
/mw getflag <世界名称> <标记值> 获取标记值在指定世界, 世界名称填写 * 则可以获取全部世界 flags.multiworld.command.getflag
【传送门】
/mw link <源世界> <目标世界> 连接 <源世界> 世界的地狱门到 <目标世界> 世界的地狱门.
提示，使用这个功能需要开启地狱门连接权限! multiworld.command.link.nether
/mw link-end <源世界> <目标世界> 连接全部未界传送门由 <源世界> 至 <目标世界>.
提示，使用这个功能需要开启未地传送门连接权限! multiworld.command.link.end
【传送】
/mw goto <世界名称> 将你自己传送到此世界, 这个指令也能够使用简写/goto <世界名称> multiworld.command.goto
/mw move <玩家名称> <世界名称> 移动指定玩家至一个世界 multiworld.command.move
Spawning
/mw spawnTeleports yourself to spawn, to move other people use /mw move.multiworld.command.spawn
/mw setspawnSets the spawn of a world, you can use this to correct the starting spawn pointmultiworld.command.setspawn
Core and Utility
/mw saveSaves the plugin datamultiworld.command.save
/mw reloadReload the plugin datamultiworld.command.reload
/mw debugShows some debugging information, this information is very handy when you create a bug reportmultiworld.command.debug
/mw helpShows help about the commands used in Multiworld, useful so you don't need to go to this pagemultiworld.command.help
/mw eastereggNot a real command, but there is a easter egg hidden in multiworld-
其他
-Permission used to allow multiworld to change the gamemode of the affected player when entering a creative world. Its recommend to give everyone this permission.multiworld.creativemode
-Gives access to the basic Multiworld moderator controll, this permission won't allow users to modefy settings of existing world, it only allows them to view the settings / teleport to worldsmultiworld.basic
-All the permissions from multiworld, you can also use the star permission to give them all permissions.Multiworld.admin

=Optional features=
Feature NameDescriptionConfiguration location
End portal handlerThe end portal handlers allows you to define custom end portals per worldoptions.useEndPortalHandler
Nether portal handlerThis addon makes it posiable to redirect netherportals to custom nether worlds, this setting is per-worldoptions.usePortalHandler
WorldChatSeperatorThis allows you to use the RecieveChat and the SendChat flags on a worldoptions.useWorldChatSeperator
GamemodeChangerThis allows you to use the flag CreativeWorld to turn on creative mode for a world, to use this you need to give you users the following permissions on all worlds: multiworld.creativemode
This module also comes with a other configuration settings, when you turn off usecreativemodeinv, it ONLY handles the gamemode part, it won't change the inventory contents, this can be used if you have a custom plugin for per world inventories.options.usecreativemode
EnderBlockPrevents the use of ender chests in creative mode, this can be used to prevent people from cheating stuff by storing it inside a ender chest in a creative world, and then removing it in a survival world.options.blockEnderChestInCrea
WorldSpawnHandlerThis allows you to have custom respawn worlds per world group, this can be setup by turning this part on to generate the configuration needed for this.options.useWorldSpawnHandler
CraftbukkitHooksAllows multiworld to hook into craftbukkit to display information that the bukit api won't provide. This feature will try to turn itself off when there are any errors.options.craftbukkitHooks
=Multiworld and Data=
Multiworld is using a statistcs tracking code so useage statistics wil be logged, for more information what is logged see:
Usage statistics at v3.5.0
=Other recommended plugins for your server=
[[LocationTeleport]] - This plugin teleports users when they enter a arena, when you shape the area like a portal, you can have your own portals
[[hothgenerator]] - Generates a awesome snow world
/mw create WorldName plugin:HothGenerator
(Case sensitive)
[[multiinv]] - Allows more control between the inventories of worlds than multiworld can provide on its own.

Multiworld

2015-01-24T16:27:15Z

9032676：/* 特性 */

{{待翻译}}
{{Bukkit Plugin Infobox
|插件名=Multiworld
|版本=v5.2.5
|前置插件=无
|兼容服务端版本=1.7.9 r0.2
|網址=http://dev.bukkit.org/bukkit-plugins/multiworld-v-2-0/
}}

=概述=
使用Multiworld插件，可以很容易地自定义每个世界对应的末地与下界，你可以随意配置。(受限于插件可实现的功能范围)
==历史==
我制作这个插件是因为该插件的原作者"Baummann"，现在不再活跃。之前，这个插件非常简易，只有两个命令: /goto and /newworld. 于是我接过这个项目并且开发出更好的版本。现在Multiworld已经更新到v5.2.5。
==特性==
自定义世界类型，例如沙子世界
支持修改玩家进入世界时的游戏模式
支持使用/mw move以及/mw goto指令于指定地点之间传送，就像在minecraft服务器使用/teleport指令一样
支持独立世界聊天频道

=命令与权限=
world commands
CommandDescriptionPermissions
World
/mw create
<world name>
[generator]
[seed]Adds a new world to the Multiworld Database.
Notice: you can also use this command to add existing worlds.
Warning: Do not give to players you don't thrust because they can create unlimited worlds!multiworld.command.create
/mw load
<world name>Loads a world that has been defined in the Multiworld databasemultiworld.command.load
/mw unload
<world name>Unloads a world that has been defined in the Multiworld database, other plugins cannot see this world anymoremultiworld.command.unload
/mw delete
<wold name>Removes a world from the MultiWorld database.
Warning: This action is destructive to the settings multiworld has defined to the world!multiworld.command.delete
/mw listList the worlds multiworld has generated in your server.multiworld.command.list
/mw infoShows information from a worldmultiworld.command.info
/mw listgensList the supported world generators to use with /mw createmultiworld.command.listgens
Rules
/mw listflagsList the possible flags to use with the following commands.multiworld.command.flags
/mw setflag
<world>
<flagname>
<value>Sets a flag/option on a world.multiworld.command.setflag
/mw getflag
<world>
<flagname>Gets a flag from a world, tip use * to get al the world flags.multiworld.command.getflag
Portalling
/mw link
<src-world>
<dst-world>Links all nether portals from <src-world> to <dst-world>.
Notice, to use this you need to turn on the nether portal handler!multiworld.command.link.nether
/mw link-end
<src-world>
<dst-world>Links al end portals from <src-world> to <dst-world>.
Notice, to use this you need to turn on the end portal handlermultiworld.command.link.end
Teleportation
/mw goto
<world name>Teleports yourself to a world, this command can also be used as alias /goto <world>multiworld.command.goto
/mw move
<player>
<world>
Moves a player to an worldmultiworld.command.move
Spawning
/mw spawnTeleports yourself to spawn, to move other people use /mw move.multiworld.command.spawn
/mw setspawnSets the spawn of a world, you can use this to correct the starting spawn pointmultiworld.command.setspawn
Core and Utility
/mw saveSaves the plugin datamultiworld.command.save
/mw reloadReload the plugin datamultiworld.command.reload
/mw debugShows some debugging information, this information is very handy when you create a bug reportmultiworld.command.debug
/mw helpShows help about the commands used in Multiworld, useful so you don't need to go to this pagemultiworld.command.help
/mw eastereggNot a real command, but there is a easter egg hidden in multiworld-
Other
-Permission used to allow multiworld to change the gamemode of the affected player when entering a creative world. Its recommend to give everyone this permission.multiworld.creativemode
-Gives access to the basic Multiworld moderator controll, this permission won't allow users to modefy settings of existing world, it only allows them to view the settings / teleport to worldsmultiworld.basic
-All the permissions from multiworld, you can also use the star permission to give them all permissions.Multiworld.admin
=Optional features=
Feature NameDescriptionConfiguration location
End portal handlerThe end portal handlers allows you to define custom end portals per worldoptions.useEndPortalHandler
Nether portal handlerThis addon makes it posiable to redirect netherportals to custom nether worlds, this setting is per-worldoptions.usePortalHandler
WorldChatSeperatorThis allows you to use the RecieveChat and the SendChat flags on a worldoptions.useWorldChatSeperator
GamemodeChangerThis allows you to use the flag CreativeWorld to turn on creative mode for a world, to use this you need to give you users the following permissions on all worlds: multiworld.creativemode
This module also comes with a other configuration settings, when you turn off usecreativemodeinv, it ONLY handles the gamemode part, it won't change the inventory contents, this can be used if you have a custom plugin for per world inventories.options.usecreativemode
EnderBlockPrevents the use of ender chests in creative mode, this can be used to prevent people from cheating stuff by storing it inside a ender chest in a creative world, and then removing it in a survival world.options.blockEnderChestInCrea
WorldSpawnHandlerThis allows you to have custom respawn worlds per world group, this can be setup by turning this part on to generate the configuration needed for this.options.useWorldSpawnHandler
CraftbukkitHooksAllows multiworld to hook into craftbukkit to display information that the bukit api won't provide. This feature will try to turn itself off when there are any errors.options.craftbukkitHooks
=Multiworld and Data=
Multiworld is using a statistcs tracking code so useage statistics wil be logged, for more information what is logged see:
Usage statistics at v3.5.0
=Other recommended plugins for your server=
[[LocationTeleport]] - This plugin teleports users when they enter a arena, when you shape the area like a portal, you can have your own portals
[[hothgenerator]] - Generates a awesome snow world
/mw create WorldName plugin:HothGenerator
(Case sensitive)
[[multiinv]] - Allows more control between the inventories of worlds than multiworld can provide on its own.