https://mineplugin.org/api.php?action=feedcontributions&feedformat=atom&user=ZhwMinecraft插件百科 - 用户贡献 [zh-cn]2026-04-14T19:17:50Z用户贡献MediaWiki 1.41.1https://mineplugin.org/index.php?title=%E7%94%A8%E6%88%B7:Zhw&diff=2051用户:Zhw2016-01-20T08:37:53Z<p>Zhw：</p>
<hr />
<div>注意：您来百科的目的不是为了看这个无聊的页面。请转向[[模板:待完善|完善]]页面、[[模板:待翻译|翻译]]内容、[[模板:待修正|修正]]内容以及[[模板:待搬运|搬运]]内容</div>Zhwhttps://mineplugin.org/index.php?title=%E7%94%A8%E6%88%B7:Zhw&diff=2050用户:Zhw2016-01-20T08:10:40Z<p>Zhw：清空页面</p>
<hr />
<div></div>Zhwhttps://mineplugin.org/index.php?title=Event_API_Reference&diff=1332Event API Reference2015-08-29T16:02:08Z<p>Zhw：</p>
<hr />
<div>{{待翻译}}<br />
== 介绍 ==<br />
<br />
'''Events''' are how the CraftBukkit server tells your plugin that something has happened in the world. Bukkit defines many events, in multiple categories; e.g. player actions (player logged in, player clicked a block, player died, player respawned...), block events (block placed, block broken, block's neighbour changed...), entity events (a mob targeted you, a creeper exploded...), world-wide events (a world loaded or unloaded, a chunk loaded or unloaded), and many more. Due to unknown reasons there is no longer any links to official Javadocs as they have all been taken off line.<br />
'''事件'''，就是CraftBukkit服务器告诉插件，这个世界发生了什么的一种方式。Bukkit定义了许多种类的不同事件；例如：玩家行为（玩家登入、玩家点击某个方块、玩家死亡、玩家重生...）、方块事件（方块被放置、方块被扣掉、相邻方块发生变化...）、实体事件（有东西瞄准了你、苦力怕爆炸...）、世界元事件（世界载入或卸载、区块载入或卸载...）、等等其它的分类。Due to unknown reasons there is no longer any links to official Javadocs as they have all been taken off line.<br />
<br />
<br />
== 基础 ==<br />
To keep this section simple, we're going to only work with PlayerLoginEvent. Lets start with setting up the method<br />
为了保持简单易懂，这一节只讨论一种事件——PlayerLoginEnvent。让我们从创建一个监听/处理该事件的方法开始吧。<br />
<br />
=== 创建方法 ===<br />
In order for your plugin to handle an event call, you need to create a method for it:<br />
为了让你的插件能够监听并处理该事件的回调，你需要为它创建一个方法。<br />
<source lang="java">@EventHandler<br />
public void onLogin(PlayerLoginEvent event) {<br />
// 你自己的代码...<br />
}</source><br />
Before this method can be invoked by Bukkit when the "PlayerLoginEvent" is fired, we need to annotate it. We do this with EventHandlers.<br />
你还需要向Bukkit声明一下，这样服务器才会在"PlayerLoginEvent"触发时调用该函数。我们需要用到EventHandlers来做到这一点。<br />
<br />
=== @EventHandler ===<br />
The "@EventHandler" class is an Annotation, which goes just above your method. It looks like this:<br />
“@EventHandler”类是一个Annotation，一般就放在你的方法上面。就像这样：<br />
<source lang="java">@EventHandler // EventPriority（事件优先级）默认为NORMAL</source><br />
This marks your method as an EventHandler with the EventPriority as NORMAL.<br />
这样一来，这一方法就标记为了一个EventPriority（事件优先级）为NORMAL的EventHandler（事件监听/处理器）。<br />
<br />
The EventHandler can take an EventPriority to specify the priority of the method, like so:<br />
EventHandler可以通过EventPriority来自定义事件的优先级，例如：<br />
<source lang="java">@EventHandler(priority = EventPriority.HIGHEST) // 方法优先级设为最高<br />
@EventHandler(priority = EventPriority.LOW) // 方法优先级设为低</source><br />
<br />
Here's what it would look like in your class:<br />
你的回调函数看起来应该和下面这个相类似：<br />
<source lang="java">@EventHandler<br />
public void onLogin(PlayerLoginEvent event) {<br />
// 你自己的代码...<br />
}</source><br />
<br />
=== 添加监听器 ===<br />
In order for Bukkit to be able to register your EventHandler's, the class which contains your event handling methods must implement the ''Listener'' (org.bukkit.event.Listener) interface, e.g.:<br />
<br />
<source lang="java">public final class MyPlayerListener implements Listener {<br />
@EventHandler<br />
public void onLogin(PlayerLoginEvent event) {<br />
// Your code here...<br />
}<br />
} </source><br />
<br />
The name of the method (''onLogin'' in the above example) does not matter; you may call the method anything you like inside your listener.<br />
<br />
You may be wondering.. "How does Bukkit know which event to listen to?" It knows that by the event parameter you specify in the method's signature - in the above example: <code>PlayerLoginEvent</code>.<br />
<br />
{{Note|You ''must'' specify a single specific event or Bukkit will not be able to register it}}<br />
<br />
Your main plugin class (i.e. the class which extends JavaPlugin) can also be an event listener, and this might make sense if your plugin is very small. E.g.:<br />
<source lang="java"><br />
public class MyPlugin extends JavaPlugin implements Listener {<br />
@Override<br />
public void onEnable() {<br />
getServer().getPluginManager().registerEvents(this, this);<br />
}<br />
<br />
@EventHandler<br />
public void onLogin(PlayerLoginEvent event) {<br />
getLogger().log(Level.INFO, "Player " + event.getPlayer().getName() + " is logging in!");<br />
}<br />
}<br />
</source><br />
=== EventHandler Parameters ===<br />
The @EventHandler annotation can take parameters to further define how the event handler behaves. At the moment you can specify:<br />
<br />
{| class="wikitable" cellspacing="0" cellpadding="5" border="1"<br />
|-<br />
! Name<br />
! Type<br />
! Default<br />
! Description<br />
! Values<br />
<br />
|-<br />
| priority<br />
| EventPriority<br />
| EventPriority.NORMAL<br />
| Sets the priority of your method<br />
|<br />
* EventPriority.MONITOR<br />
* EventPriority.HIGHEST<br />
* EventPriority.HIGH<br />
* EventPriority.NORMAL<br />
* EventPriority.LOW<br />
* EventPriority.LOWEST<br />
<br />
|-<br />
| ignoreCancelled<br />
| boolean<br />
| false<br />
| If set to true, your method will not get the event if the event has been cancelled<br />
| <br />
* true<br />
* false<br />
<br />
|}<br />
<br />
<br />
==== Event Priorities ====<br />
There are six priorities in Bukkit that are called in the following order<br />
* EventPriority.LOWEST<br />
* EventPriority.LOW<br />
* EventPriority.NORMAL<br />
* EventPriority.HIGH<br />
* EventPriority.HIGHEST<br />
* EventPriority.MONITOR<br />
<br />
Every plugin gets a say in what happens, and every plugin must get a chance to know the outcome of an event. So, we pass events to plugins even after they've been cancelled. A plugin can actually uncancel an event after another plugin cancelled it. This is where priorities become really important.<br />
<br />
Let's say a BLOCK_PLACE event is being handled. The lowest priority listener is called to get its say in whether it should be cancelled or not. Then the low priority listener is called to see if it wants to override the lowest, etc. Eventually it hits monitor, and at this point nothing should change the outcome of the event. Monitor should be used to see the outcome of an event, without changing any aspect of it.<br />
If we have three plugins enabled; one is a basic area protection plugin, one is a fancy plugin using signs, and another is a logging plugin.<br />
The protection plugin listens on Priority.LOWEST. It says they can't place blocks in this area, and cancels the event.<br />
The fancy sign plugin listens on Priority.NORMAL. It says they can place signs here, and uncancels the event.<br />
The log plugin listens on Priority.MONITOR. It sees that the event was actually allowed, and logs it.<br />
<br />
If you want to change the outcome of an event, choose very carefully from LOWEST to HIGHEST. Suggested generalized protection plugins on lowest, more specific plugins on normal, and override plugins on high.<br />
If you want to act when an event happens, but not change the outcome, use MONITOR. '''It's really really important that you use MONITOR, or an event might get cancelled after you've acted on it, and it's even more important that you don't change the outcome of the event on MONITOR or it'll break other plugins.'''<br />
<br />
== Registering Events ==<br />
To register your methods, the class containing the EventHandler(s) must implement the Listener class.<br />
<blockquote><source lang="java">import org.bukkit.event.Listener;<br />
<br />
public final class LoginListener implements Listener {<br />
}</source></blockquote><br />
<br />
You only need to provide a plugin and a listener to register them in the PluginManager.<br />
<blockquote><source lang="java">getServer().getPluginManager().registerEvents(Listener, Plugin);</source></blockquote><br />
<br />
=== Example Listener ===<br />
This listener contains two EventHandlers. One listening on HIGH, and one on NORMAL.<br />
<blockquote><source lang="java">import org.bukkit.event.Listener;<br />
import org.bukkit.event.EventHandler;<br />
import org.bukkit.event.EventPriority;<br />
import org.bukkit.event.player.PlayerLoginEvent;<br />
<br />
public final class LoginListener implements Listener {<br />
@EventHandler<br />
public void normalLogin(PlayerLoginEvent event) {<br />
// Some code here<br />
}<br />
<br />
@EventHandler(priority = EventPriority.HIGH)<br />
public void highLogin(PlayerLoginEvent event) {<br />
// Some code here<br />
}<br />
}</source></blockquote><br />
<br />
=== Registering Events in Plugin ===<br />
The registerEvents method requires a listener and a plugin. Luckily, we already have our LoginListener. Now for the LoginPlugin!<br />
<blockquote><source lang="java">import org.bukkit.plugin.java.JavaPlugin;<br />
<br />
public final class LoginPlugin extends JavaPlugin {<br />
public void onEnable() {<br />
getServer().getPluginManager().registerEvents(new LoginListener(), this);<br />
}<br />
}</source></blockquote><br />
<br />
<br />
==== Registering Events with Plugin as Listener ====<br />
You could even have the events in the main class, for example:<br />
<blockquote><source lang="java">import org.bukkit.plugin.java.JavaPlugin;<br />
import org.bukkit.event.Listener;<br />
import org.bukkit.event.EventHandler;<br />
import org.bukkit.event.player.PlayerLoginEvent;<br />
<br />
public final class LoginPlugin extends JavaPlugin implements Listener {<br />
public void onEnable() {<br />
getServer().getPluginManager().registerEvents(this, this);<br />
}<br />
<br />
@EventHandler<br />
public void normalLogin(PlayerLoginEvent event) {<br />
// Some code here<br />
}<br />
}</source></blockquote><br />
<br />
=== Registering Events in your Listener ===<br />
There are many ways to register your events. Here's an example where you register them in your listener class.<br />
<blockquote><source lang="java">import org.bukkit.event.Listener;<br />
import org.bukkit.event.EventHandler;<br />
import org.bukkit.event.EventPriority;<br />
import org.bukkit.event.player.PlayerLoginEvent;<br />
<br />
public final class LoginListener implements Listener {<br />
public LoginListener(LoginPlugin plugin) {<br />
plugin.getServer().getPluginManager().registerEvents(this, plugin);<br />
}<br />
<br />
@EventHandler<br />
public void normalLogin(PlayerLoginEvent event) {<br />
// Some code here<br />
}<br />
<br />
@EventHandler(priority = EventPriority.HIGH)<br />
public void highLogin(PlayerLoginEvent event) {<br />
// Some code here<br />
}<br />
}</source></blockquote><br />
<br />
The LoginPlugin would look like this:<br />
<blockquote><source lang="java">import org.bukkit.plugin.java.JavaPlugin;<br />
<br />
public final class LoginPlugin extends JavaPlugin {<br />
public void onEnable() {<br />
new LoginListener(this);<br />
}<br />
}</source></blockquote><br />
<br />
== Un-registering events or listeners ==<br />
You can un-register individual events, entire listener classes or all events registered by your plugin or even by other plugins!<br />
<br />
==== Un-register specific event ====<br />
Each event class has the getHandlerList() static method, call that and then you can use .unregister() method.<br />
Example:<br />
<blockquote><source lang="java"><br />
PlayerInteractEvent.getHandlerList().unregister(plugin);<br />
// this will unregister all PlayerInteractEvent instances from the plugin<br />
// you can also specify a listener class instead of plugin.<br />
</source></blockquote><br />
Now you know why you'll need the getHandlerList() in your custom events.<br />
<br />
==== Un-register all events ====<br />
Using the HandlerList class and its unregisterAll() static method you can easily unregister events from listener classes or plugins.<br />
Example:<br />
<blockquote><source lang="java"><br />
HandlerList.unregisterAll(plugin);<br />
// this will unregister all events from the specified plugin<br />
// you can also specify a listener class instead of plugin.<br />
</source></blockquote><br />
<br />
== Creating Custom Events ==<br />
Creating custom events is very simple, you can use the same system that Bukkit uses without ruining performance.<br />
<br />
There are two (2) things to keep in mind when you create a Custom Event. They are "extend Event" and "static handlers." With static handlers, you must input the following code into your custom event:<br />
<br />
<blockquote><source lang="java">private static final HandlerList handlers = new HandlerList();<br />
<br />
public HandlerList getHandlers() {<br />
return handlers;<br />
}<br />
<br />
public static HandlerList getHandlerList() {<br />
return handlers;<br />
}</source></blockquote><br />
This block of code makes the EventHandlers contained inside your own event, keeping any unrelated events completely separated.<br />
<br />
=== Custom Event Example ===<br />
The following example shows how easy it is to create your own "CustomEvent."<br />
<blockquote><source lang="java">import org.bukkit.event.Event;<br />
import org.bukkit.event.HandlerList;<br />
<br />
public final class CustomEvent extends Event {<br />
private static final HandlerList handlers = new HandlerList();<br />
private String message;<br />
<br />
public CustomEvent(String example) {<br />
message = example;<br />
}<br />
<br />
public String getMessage() {<br />
return message;<br />
}<br />
<br />
public HandlerList getHandlers() {<br />
return handlers;<br />
}<br />
<br />
public static HandlerList getHandlerList() {<br />
return handlers;<br />
}<br />
}</source></blockquote><br />
<br />
==== Calling your Custom Event ====<br />
You are in control of creating and calling your events, where you call it is completely up to you. Here's an example<br />
<blockquote><source lang="java">// Create the event here<br />
CustomEvent event = new CustomEvent("Sample Message");<br />
// Call the event<br />
Bukkit.getServer().getPluginManager().callEvent(event);<br />
// Now you do the event<br />
Bukkit.getServer().broadcastMessage(event.getMessage());</source></blockquote><br />
<br />
Remember: You are in control of your events. If you don't call it, and act upon it, it doesn't happen!<br />
<br />
==== Listening to a Custom Event ====<br />
How do you listen to a custom event you say? Simple, the same way as listening to a normal event!<br />
<blockquote><source lang="java">import org.bukkit.event.Listener;<br />
import org.bukkit.event.EventHandler;<br />
<br />
public final class CustomListener implements Listener {<br />
@EventHandler<br />
public void normalLogin(CustomEvent event) {<br />
// Some code here<br />
}<br />
}</source></blockquote><br />
<br />
==== Making your CustomEvent Cancellable ====<br />
If you ever want to make your event cancellable, remember one thing: "implements Cancellable." Just like you would import Listener. It's really that simple, let me show you an example!<br />
<blockquote><source lang="java">import org.bukkit.event.Event;<br />
import org.bukkit.event.HandlerList;<br />
import org.bukkit.event.Cancellable;<br />
<br />
public final class CustomEvent extends Event implements Cancellable {<br />
private static final HandlerList handlers = new HandlerList();<br />
private String message;<br />
private boolean cancelled;<br />
<br />
public CustomEvent(String example) {<br />
message = example;<br />
}<br />
<br />
public String getMessage() {<br />
return message;<br />
}<br />
<br />
public boolean isCancelled() {<br />
return cancelled;<br />
}<br />
<br />
public void setCancelled(boolean cancel) {<br />
cancelled = cancel;<br />
}<br />
<br />
public HandlerList getHandlers() {<br />
return handlers;<br />
}<br />
<br />
public static HandlerList getHandlerList() {<br />
return handlers;<br />
}<br />
}</source></blockquote><br />
<br />
Afterwards, you would check if a plugin had cancelled the event in your code, before processing normally<br />
<blockquote><source lang="java">// Create the event here<br />
CustomEvent event = new CustomEvent("Sample Message");<br />
// Call the event<br />
Bukkit.getServer().getPluginManager().callEvent(event);<br />
// Check if the event is not cancelled<br />
if (!event.isCancelled()) {<br />
// Now you do the event<br />
Bukkit.getServer().broadcastMessage(event.getMessage());<br />
}</source></blockquote><br />
<br />
== Video Tutorial ==<br />
If you would prefer to watch a video tutorial version of this, please click [http://www.youtube.com/watch?v=PWQNsqwD-AY here].<br />
<br />
[[Category: Tutorials]]</div>Zhwhttps://mineplugin.org/index.php?title=Dynmap&diff=1331Dynmap2015-08-29T15:54:59Z<p>Zhw：</p>
<hr />
<div>{{待搬运}}<br />
https://github.com/webbukkit/dynmap/wiki</div>Zhwhttps://mineplugin.org/index.php?title=Citizens&diff=1330Citizens2015-08-29T15:54:03Z<p>Zhw：</p>
<hr />
<div>{{待搬运}}<br />
http://wiki.citizensnpcs.co/Citizens_Wiki</div>Zhwhttps://mineplugin.org/index.php?title=Bukkit/FAQ&diff=1201Bukkit/FAQ2015-08-05T14:36:07Z<p>Zhw：/* 我在哪里可以获取服务端? */</p>
<hr />
<div>{{待翻译}}<br />
以下英语原文来自BukkitWiki.<br />
==== 什么是BukkitWiki? ====<br />
<br />
BukkitWiki是存放Bukkit文档和其他相关帮助信息的官方网站.站点性质(Wiki)允许社区中的任何人自由地对其贡献. 在你贡献时，意味着你已经直接授权你的文字给bukkit官方，可以给其他人在任何地方自由修改和参考 While we value contributions made by the community, plastering credit all over content you've added creates clutter and makes the wiki look messy.<br />
<br />
==== Bukkit和CraftBukkit的区别是? ====<br />
<br />
Bukkit一种供开发者使用的API(应用程序接口),而CraftBukkit是一种Minecraft官方服务器的拓展模组(服务端)，其使用的接口为Bukkit API. <br />
<br />
从根本上来说, Bukkit即是插件开发者用来开发那些给你们带来酷炫，新颖的特性从而使你的服务器更加高端的东西. <br />
<br />
CraftBukkit则是我们制作的能够使用插件的一种服务端.<br />
<br />
==== 我在哪里可以获取服务端? ====<br />
<br />
最新的CraftBukkit服务端版本将发布在[http://dl.bukkit.org dl.bukkit.org]. 参见 [[教程/服务器相关]] 来开始架设服务器 <br />
<br />
[http://dl.bukkit.org dl.bukkit.org] 在这里你同时也可以获取you can also access beta and development builds by clicking the Alternate Versions link or at [http://dl.bukkit.org/downloads/craftbukkit/ www.dl.bukkit.org/downloads/craftbukkit/]<br />
<br />
==== Recommended（正式版）, Beta（测试版）, 和 Development builds（开发版）不同之处在哪儿？ ====<br />
正式版已经通过了最严格的测试和达到了对应需求，我们认为它是没有漏洞的（啧。）。测试版是已经被严格考量但是没有达到正式版的要求。而开发版本则会体现每个版本之间的修改，但稳定性没有保障。 See [http://forums.bukkit.org/threads/reminder-bukkit-is-following-a-new-release-system.65358/ this post] by EvilSeph for more information on the difference between beta and recommended builds.<br />
==== 哪里可以提交我的插件? ====<br />
<br />
在[http://dev.bukkit.org/ BukkitDev 社区插件资源站]为你的插件创建一个项目页面.这个系统由BukkitDev职员进行管理. [[BukkitDev:Project_Submission_Guidelines|Project Submission Guidelines 在这里查看在提交插件过程中所需要的信息]]<br />
<br />
==== 我怎样才能获得Bukkit源码? ====<br />
<br />
源码可以在 [https://github.com/Bukkit/ here] 找到. 你可能需要在 [http://maven.apache.org/ Maven3] 开发Bukkit.<br />
==== 如何重命名指令? ====<br />
<br />
你可以通过编辑bukkit.yml或是commands.yml创建别名来重命名指令<br />
<br />
在 [[Commands.yml]] 中有说明怎样做到这一点<br />
<br />
==== 怎么才能自定义服务器帮助页面? ====<br />
<br />
你可以通过编辑[[Help.yml]]文件来自定义帮助信息.</div>Zhwhttps://mineplugin.org/index.php?title=Bukkit/FAQ&diff=1200Bukkit/FAQ2015-08-05T14:33:55Z<p>Zhw：</p>
<hr />
<div>{{待翻译}}<br />
以下英语原文来自BukkitWiki.<br />
==== 什么是BukkitWiki? ====<br />
<br />
BukkitWiki是存放Bukkit文档和其他相关帮助信息的官方网站.站点性质(Wiki)允许社区中的任何人自由地对其贡献. 在你贡献时，意味着你已经直接授权你的文字给bukkit官方，可以给其他人在任何地方自由修改和参考 While we value contributions made by the community, plastering credit all over content you've added creates clutter and makes the wiki look messy.<br />
<br />
==== Bukkit和CraftBukkit的区别是? ====<br />
<br />
Bukkit一种供开发者使用的API(应用程序接口),而CraftBukkit是一种Minecraft官方服务器的拓展模组(服务端)，其使用的接口为Bukkit API. <br />
<br />
从根本上来说, Bukkit即是插件开发者用来开发那些给你们带来酷炫，新颖的特性从而使你的服务器更加高端的东西. <br />
<br />
CraftBukkit则是我们制作的能够使用插件的一种服务端.<br />
<br />
==== 我在哪里可以获取服务端? ====<br />
<br />
最新的CraftBukkit服务端版本将发布在[http://dl.bukkit.org dl.bukkit.org]. 参见 [[Setting up a server]] 来开始架设服务器 <br />
<br />
[http://dl.bukkit.org dl.bukkit.org] 在这里你同时也可以获取you can also access beta and development builds by clicking the Alternate Versions link or at [http://dl.bukkit.org/downloads/craftbukkit/ www.dl.bukkit.org/downloads/craftbukkit/]<br />
<br />
==== Recommended（正式版）, Beta（测试版）, 和 Development builds（开发版）不同之处在哪儿？ ====<br />
正式版已经通过了最严格的测试和达到了对应需求，我们认为它是没有漏洞的（啧。）。测试版是已经被严格考量但是没有达到正式版的要求。而开发版本则会体现每个版本之间的修改，但稳定性没有保障。 See [http://forums.bukkit.org/threads/reminder-bukkit-is-following-a-new-release-system.65358/ this post] by EvilSeph for more information on the difference between beta and recommended builds.<br />
==== 哪里可以提交我的插件? ====<br />
<br />
在[http://dev.bukkit.org/ BukkitDev 社区插件资源站]为你的插件创建一个项目页面.这个系统由BukkitDev职员进行管理. [[BukkitDev:Project_Submission_Guidelines|Project Submission Guidelines 在这里查看在提交插件过程中所需要的信息]]<br />
<br />
==== 我怎样才能获得Bukkit源码? ====<br />
<br />
源码可以在 [https://github.com/Bukkit/ here] 找到. 你可能需要在 [http://maven.apache.org/ Maven3] 开发Bukkit.<br />
==== 如何重命名指令? ====<br />
<br />
你可以通过编辑bukkit.yml或是commands.yml创建别名来重命名指令<br />
<br />
在 [[Commands.yml]] 中有说明怎样做到这一点<br />
<br />
==== 怎么才能自定义服务器帮助页面? ====<br />
<br />
你可以通过编辑[[Help.yml]]文件来自定义帮助信息.</div>Zhwhttps://mineplugin.org/index.php?title=MobArena&diff=1172MobArena2015-07-28T10:46:24Z<p>Zhw：</p>
<hr />
<div>{{待翻译}}<br />
{{Bukkit Plugin Infobox<br />
|版本=v0.96.9<br />
|兼容服务端版本=1.8.1<br />
|网址=http://dev.bukkit.org/bukkit-plugins/mobarena/}}<br />
[[Category:娱乐]][[Category:机械]]<br />
=安装=<br />
安装MobArena其实很简单，只需以下四步:<br />
*关闭服务器<del>咳咳，当然是关你自己的服务器啦</del>.<br />
*从论坛主题或是Bukkit Dev站点的项目页下载jar文件.<br />
*将jar文件拖入服务端的plugins文件夹中.<br />
*重启服务端. <br />
之后，配置文件 (config.yml) 以及一个宣告文本(announcements.yml) 会自动创建在plugins/MobArena/路径下.<br />
文件结构如下:<br />
<br />
plugins/<br />
MobArena.jar<br />
MobArena/<br />
config.yml<br />
announcements.yml<br />
此时此刻, 或许你想直接开始设置竞技场, 但是你需要先看看配置文件，并把它配置成你喜欢的样子<del>就是说，还是根据情况配置一下吧</del>. 你可以在配置文件自定义MobArena的设置，职业，奖励，波数（怪物类型）<br />
<br />
=建立竞技场=<br />
==建造一个竞技场==<br />
完整的竞技场应该包含一个可以选择职业的准备区域，一个竞技场地以及观察点(离开点) <br />
下面是各个选项的讲解<br />
<br />
大厅：<br />
玩家加入游戏之前将会在大厅选择职业.一个建造好的游戏大厅会有每一个职业的选择牌子，玩家通过点击牌子可以获取一个职业, 还有一个铁块, 玩家可以通过点击铁块来表示他们已经准备好开始游戏.牌子必须在第一行写上职业的名字（区分大小写）,但是无论你在另外三行上写什么，都不会被怪物竞技场识别，你是不能写上 ,所以你不会得到确认的信息（如果有，那是另一个插件）<br />
<br />
竞技场地：<br />
这里是玩家和怪物搏斗的地方.竞技场地会有墙，可能会有一个屋顶 , 这样玩家和怪物就不能跑出去了. 这使得玩家们不会只是在竞技场外闲逛。.<br />
<br />
观察点: <br />
当玩家想要观看一场战斗时,他们可以使用/ma spec 命令来传送到竞技场的观察点. 这同样也是竞技场中玩家死去后会传送到的地方,前提是在配置文件中，把 spectate-after-death设置为ture. 这块区域要保证观看者不能走出去闲逛（进入竞技场地或者离远竞技场）因为在观看过程中，玩家是无敌的.<br />
<br />
离开点: <br />
在使用 /ma leave命令后,玩家和观察者会被传送到原来所在的地方,除非竞技场有一个离开点(只是可选). 使用离开点,可以准确控制玩家在游戏后去何处.<br />
<br />
关于区域，传送点等，<br />
<br />
当竞技场建好后，就是设置怪物竞技场的区域和传送点的时候了。在设置它们前，我们先来看看他们有什么作用.<br />
<br />
区域: <br />
一个竞技场需要一个竞技区域,然后还可以有一个准备区域，怪物竞技场会使用这些区域来确保玩家不会作弊（通过破坏竞技场来走出区域）,然后确保怪物竞技场所产生的怪物会在里面产生. 怪物竞技场非常排外（不要局外人）, 所以也最好把不想要的生物排除在外. 区域是通过区域工具来设置的.<br />
<br />
传送点: <br />
当玩家加入一个怪物竞技场的游戏时，他们会被传送到准备区域中的准备点来选择职业和准备开始游戏（通过点击铁块）.当每个人都准备好的时候，玩家会被传送到竞技场内的竞技场出生点。观察者会被传送到竞技场的观察点来进入观察区域,当游戏结束的时候，玩家和观察者会被传送到他们传送来之前的地方，或者去可选的离开点,传送点会用传送点工具来设置。.<br />
<br />
出生点: <br />
这里的出生点指的是怪物出生的地点.怪物竞技场只会在附近有玩家的出生点产出怪物（十五个方格的半径）.需要注意的是，怪物的数量不随着按照出生点的数量改变，只会因为在配置文件中波数的倍率改变和玩家的数量所改变.出生点可以通过出生点工具来设置。.<br />
<br />
容器: <br />
容器就是竞技场里的箱子，回收站等。 这些容器将会在一场游戏后重置其内部空间为初始值。只有被声明了的容器才会更新其存储空间，所以仅仅在竞技场里放一个箱子可不够 - 它还需要被用工具声明。<br />
<br />
==设置模式==<br />
我们能用配置模式来设置竞技场。 当我们进入配置模式时，物品栏将会被保存 并给我们一套金工具 （工具栏）， 每一个都有其独特作用。同时我们也可以飞行，使得我们在竞技场附近移动时更加快捷方便一些，最后，但不是绝对，我们不能够聊天或者使用普通命令如果在在配置模式下的话，因为配置模式和你建立起了独立会话（即你所发表的信息都是针对插件的。）<br />
<br />
进入设置模式的方法：输入/ma setup 竞技场名，值得提醒的是，如果服务器中只有一个竞技场，你不用输入竞技场的名字，如果竞技场没有设置完毕或者没有被创造，首先使用/ma addarena 竞技场名来创造它<br />
<br />
离开设置模式的方法：聊天框内输入done，注意不是命令，是聊天信息，没有斜杠<br />
<br />
另外，如果你刚安装怪物竞技场插件，会有一个预置的，名称为default竞技场存在于配置文件中，如果你想要一个不同的名字，你需要先创造一个新竞技场然后把原来的竞技场使用/ma delarena default来删除<br />
<br />
下面我们会提到在设置模式中有什么命令可以使用。<br />
<br />
==设置模式的命令==<br />
<br />
设置模式是一个独立，特殊的会话，这意味着插件会监控我们说的每一句话，使得插件的命令可以缩短，以致于设置过程没有特别麻烦。比如exp命令替代了/ma expandregion，并且还可以防止我们错误地使用了其他插件的命令<br />
<br />
下面是我们可以在设置模式中使用的命令，很多都十分浅显易懂（如果您懂英文的话。）使得您设置竞技场十分快速<br />
done<br />
离开设置模式<br />
别名: end stop done quit<br />
<br />
help<br />
显示帮助信息<br />
别名: ? h<br />
<br />
missing<br />
显示我们还没有设置好的区域（准备区诸如此类）<br />
这个命令在你不知道你已经设置了那些区域的时候十分有用<br />
别名: miss<br />
<br />
expand <region> <amount> <direction><br />
Expand a region by some amount in some direction.<br />
Valid regions: ar for the arena region, or lr for the lobby region<br />
Valid amounts: positive integers (whole numbers)<br />
Valid directions: up, down, or out<br />
Example: expand ar 5 up<br />
别名: exp<br />
<br />
show [<region>|<warp>|<point>]<br />
Show a region, warp, or point(s) as red wool blocks.<br />
Valid regions: ar for the arena region, or lr for the lobby region<br />
Valid warps: arena, lobby, spec, exit<br />
Valid points: spawns (or just sp) for spawnpoints, chests (or just c) for chests<br />
Example: show sp<br />
<br />
==设置时的工具==<br />
<br />
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.<br />
<br />
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.<br />
<br />
===区域工具===<br />
<br />
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.<br />
<br />
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.<br />
<br />
Left-click: Set the first point to be the location of the target block<br />
Right-click: Set the second point to be the location of the target block<br />
<br />
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.<br />
<br />
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.<br />
<br />
===玩家传送点工具===<br />
<br />
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.<br />
<br />
Left-click: Set the currently selected warp on top of the target block<br />
Right-click: Cycle between available warps<br />
<br />
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.<br />
<br />
Note: The arena, lobby, and spectator warps are all required. The exit warp is optional.<br />
<br />
===怪物产生点工具===<br />
<br />
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.<br />
<br />
Left-click: Add a spawnpoint on top of the target block<br />
Right-click: Remove the spawnpoint on top of the target block (if the spawnpoint exists)<br />
<br />
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.<br />
<br />
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.<br />
<br />
===容器工具===<br />
<br />
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.<br />
<br />
Left-click: Register the clicked container (if it wasn't registered)<br />
Right-click: Unregister the clicked container (if it was registered)<br />
<br />
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.<br />
<br />
=命令=<br />
==玩家命令==<br />
<br />
这些指令能够给所有玩家使用. 它们包括了加入, 离开, 旁观和列出所有竞技场(可用或不可用)<br />
<br />
<br />
/ma join (<竞技场>) or /ma j (<竞技场>) - 加入指定名称的竞技场.<br />
/ma leave or /ma l - 离开竞技场或是离开旁观者模式.<br />
/ma notready - 获取所有未准备的玩家.<br />
/ma spec (<竞技场>) or /ma s (<竞技场>) - 以旁观者模式加入指定名称竞技场.<br />
/ma arenas - 获取所有竞技场的名字, 若是绿色则已启用, 灰色则未启用.<br />
/ma players - 获取当前所有竞技场的所有玩家.<br />
/ma players <竞技场> - 获取指定竞技场的所有玩家.<br />
/ma class <职业> - 如果你在大厅里, 是应直接用指令而不是透过牌子互动选择职业.<br />
<br />
==管理员指令==<br />
<br />
只有后台或者服务器op能使用下面这些指令. 这里包括了开始或是停止竞技场, 启用或是卸载竞技场甚至包含了MobArena的所有管理.<br />
<br />
/ma enable - 启用MobArena插件.<br />
/ma disable - 卸载MobArena插件.<br />
/ma enable <竞技场> - 启用指定名字的竞技场.<br />
/ma disable <竞技场> - 关闭指定名字的竞技场.<br />
/ma force end - 停止所有竞技场的运作.<br />
/ma force end <竞技场> - 停止指定名称竞技场的运作及使该竞技场的所有玩家离开. <br />
/ma force start <竞技场> - 开始运作一个指定名称的竞技场以及请出该竞技场内未准备的玩家.<br />
/ma notready <竞技场> - 获取该竞技场内所有未准备的玩家.<br />
/ma restore <玩家> - 在可能的情况下恢复指定玩家背包.<br />
/ma config reload - 重载config配置文件夹.<br />
==建设指令==<br />
<br />
只有op (以及某些合理的指令能在后台) 使用这些指令. 它们包括了设置竞技场传送点, 竞技场出生点以及竞技场范围.<br />
<br />
/ma setup <竞技场> - 进入建设指定名称的竞技场模式.<br />
/ma addarena <竞技场> - 建立一个新的竞技场节点于当前所在世界.<br />
/ma delarena <竞技场> - 删除指定名称的竞技场.<br />
/ma editarena <竞技场> - 开启或关闭指定竞技场修改模式.<br />
/ma editarena <竞技场> [true|false] - 开启 (true) 或关闭 (false) 指定竞技场的修改模式.<br />
/ma setting <竞技场> - 列出所有指定竞技场的设置项.<br />
/ma setting <竞技场> <设置项> - 查询当前指定设置项的值于指定的竞技场.<br />
/ma setting <竞技场> <设置项> <值> - 设置指定竞技场中指定设置项的指定值.<br />
/ma checkspawns - 显示竞技场出生点 (在你当前的竞技场下) 是使用红色羊毛覆盖的范围在当前你当前的位置上. 这个指令同时也能查询在这个范围内不同的点是否被出生点覆盖着.<br />
/ma classchest <职业> - 当正在查询箱子, 使指定的职业与这个箱子建立连接. 连接一个职业箱子意味着当MobArena连接建立后, 将同时复制于职业箱子内的物品, 而不是于竞技场大厅内的任何职业箱子. 当你建立一个职业箱子网络时它能带给你便利.<br />
/ma auto-generate <竞技场> - 自动生成一个指定名称的竞技场. 这个竞技场只会生成于玩家所站的位置下方.<br />
/ma auto-degenerate <竞技场> - 自动停止生成竞技场, 能基于自动生成器下有效地恢复, 当这是一个 "bulldozed" 补丁.<br />
<br />
=权限=<br />
几乎全部的权限插件是'''不需要'''MobArena插件作为前置而能够单独运行的, 但若果你想要更多额外的控制功能, 这里提供了很多不同类型的权限节点哦喵~<br />
== 节点 ==<br />
你能够在安装MobArena插件后使用这些权限节点<br />
<br />
提示: MobArena这个插件提供了很多人性化的默认设定, 所有玩家能够使用所有竞技场及职业, 还有的是OP默认能够使用所有管理员以及建设指令. 除非你想要禁止一些组别进入特定的竞技场或是职业<br />
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!<br />
<br />
==竞技场权限==<br />
<br />
Did you read the note at the top? If not, read it before you continue.<br />
<br />
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.<br />
<br />
bPermissions: ^mobarena.arenas.default<br />
GroupManager: -mobarena.arenas.default<br />
zPermissions: mobarena.arenas.default: false<br />
<br />
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.<br />
<br />
Still confused? Check the sample setup at the bottom of the page!<br />
<br />
==职业权限==<br />
<br />
Did you read the note at the top? If not, read it before you continue.<br />
<br />
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.<br />
<br />
bPermissions: ^mobarena.classes.knight<br />
GroupManager: -mobarena.classes.knight<br />
zPermissions: mobarena.classes.knight: false<br />
<br />
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.<br />
<br />
As with arenas, I recommend letting everyone enjoy all the classes, unless you have a special reason not to.<br />
<br />
Still confused? Check the sample setup at the bottom of the page!<br />
<br />
==命令权限==<br />
<br />
Did you read the note at the top? If not, read it before you continue.<br />
<br />
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!<br />
<br />
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.<br />
<br />
mobarena.use.join<br />
mobarena.use.leave<br />
mobarena.use.spec<br />
mobarena.use.arenalist<br />
mobarena.use.playerlist<br />
mobarena.use.notready<br />
mobarena.use.class<br />
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.<br />
<br />
mobarena.admin.enable<br />
mobarena.admin.kick<br />
mobarena.admin.restore<br />
mobarena.admin.force<br />
mobarena.admin.teleport<br />
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.<br />
<br />
mobarena.setup.config<br />
mobarena.setup.setup<br />
mobarena.setup.setting<br />
mobarena.setup.addarena<br />
mobarena.setup.removearena<br />
mobarena.setup.editarena<br />
mobarena.setup.spawnpoints<br />
mobarena.setup.containers<br />
mobarena.setup.checkdata<br />
mobarena.setup.checkspawns<br />
mobarena.setup.classchest<br />
mobarena.setup.classes<br />
mobarena.setup.leaderboards<br />
mobarena.setup.autogenerate<br />
mobarena.setup.autodegenerate<br />
Sample setup<br />
<br />
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...<br />
<br />
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:<br />
<br />
default-aux: <-- This is the auxiliary group that is to<br />
permissions: be inherited by the default group and<br />
- essentials.balance the donor group. It is not used for<br />
- essentials.pay anything else.<br />
- essentials.sell<br />
<br />
default: <-- This is the default group. It inherits<br />
inherits: default-aux from default-aux, but also revokes the<br />
permissions: permission for the special class.<br />
- -mobarena.classes.diamondknight<br />
<br />
donor: <-- This is the donor group, which also<br />
inherits: default-aux inherits from default-aux, but it<br />
permissions: does not revoke any class permissions,<br />
- essentials.balance.others which means it has access to all of<br />
- essentials.kit them by default.<br />
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.<br />
<br />
=物品语法=<br />
An Overview<br />
<br />
Items in MobArena follow a very specific syntax that you must obey, or you will experience missing items or errors. Be attentive to the details, because if you aren't, there will be consequences.<br />
<br />
MobArena allows these three different ways of defining items:<br />
<br />
Single: [<id>|<name>]<br />
Multiple: [<id>|<name>]:<amount><br />
Sub-types: [<id>|<name>]:<data>:<amount><br />
Confusing? Let's break them down one by one.<br />
<br />
===1. Single Items===<br />
<br />
[<id>|<name>]<br />
This means you can use either the item ID (<id>) or the item name (<name>), both as defined in the Material enum of the Bukkit API (the IDs are the numbers in parentheses). The item names are case-insensitive.<br />
<br />
Make sure to read the important note on item IDs!<br />
<br />
Examples: diamond_sword, stone, 42 (iron block), 322 (snowball)<br />
<br />
===2. Multiple Items===<br />
<br />
[<id>|<name>]:<amount><br />
This way, you append an <amount> to the item, specifying how many of the given item you want. This is useful for giving out stuff like arrows or potions that you generally want to give more than one of.<br />
<br />
Note that if you use this syntax, it is indeed the amount you specify, not the item sub-type. We go over sub-types in the next section.<br />
<br />
Make sure to read the important note on item IDs!<br />
<br />
Examples: arrow:64, grilled_pork:4, 46:10 (10x TNT), 142:5 (5x potato)<br />
<br />
===3. Item Sub-Types (potions, wool, dyes etc.)===<br />
<br />
[<id>|<name>]:<data>:<amount><br />
This way, you append BOTH a <data> value (the sub-type) and an <amount>, regardless of how many of the given item you want. This syntax is mostly used with potions, which have special sub-type values in the 8000's and 16000's. Check out this page for the potion sub-types.<br />
<br />
For wool and dyes (ink sacks), you don't have to use the numeric data value. Instead, you can use the color names as defined in the DyeColor enum of the Bukkit API.<br />
<br />
Make sure to read the important note on item IDs!<br />
<br />
Examples: wool:blue:1 (one blue wool), ink_sack:brown:10 (ten cocoa beans), potion:8201:1 (one strength potion), 373:8197:2 (two health potions)<br />
<br />
An important note on using item IDs<br />
<br />
If you choose to use item IDs, there is a catch. If an item is alone in its node, it MUST be enclosed in apostrophes, or YAML will crap itself. For example, if you decide to have a Barbarian class that only has a pair of lederhosen as armor, and nothing put a couple of health potions, you need to do it like this:<br />
<br />
classes:<br />
Barbarian:<br />
items: '373:8197:2'<br />
armor: '300'<br />
In other words, you have to put '300' in the armor-node, not just 300, and you have to put '373:8197:2' in the items-node, not just 373:8197:2. This requirement is removed if you use the item names instead, or if you add enchantments to the given item.<br />
<br />
Enchantments<br />
<br />
Enchantments can be added to items by appending a space, followed by a semi-colon separated list of pairs <eid>:<level>, where <eid> is an enchantment ID as defined by the Enchantment Wrappers in the Bukkit API (the numbers in the parentheses at the end of each line), i.e.:<br />
<br />
<item> <eid>:<level>;<eid>:<level>;...<br />
The <item> is any item following the normal item syntax as described above. Here is an example:<br />
<br />
diamond_sword 16:2;19:5<br />
This line gives a diamond sword with sharpness (ID 16) level 2, and knockback (ID 19) level 5.<br />
<br />
Economy Money<br />
<br />
$<amount><br />
MobArena supports entry fees and rewards in the form of money from economy plugins. This feature requires Vault. The format quite simply means that you type in a dollar sign followed by a valid monetary value.<br />
<br />
Examples: $1, $5, $3.14 (v0.96+), $0.99 (v0.96+)<br />
<br />
=职业箱子=<br />
==About Class Chests==<br />
<br />
If some of your favorite items aren't supported by MobArena's internal item parser, or if you just want to be able to configure your class items from in-game, the class chests may be what you're looking for!<br />
<br />
Note: The Class Chests will only work for arenas with use-class-chests: true, and the classes MUST exist in the config-file for MobArena to recognize them, however the items and armor lists can be empty.<br />
<br />
The idea behind the class chests is to simply place some chests below the corresponding class signs in the lobby, and fill them with whatever items you want the given class to have. When the players activate the class signs, the contents of the chests are copied to the player inventory. This suggests a type of "control room" setup, where an admin-only access room below the lobby contains the chests, allowing admins to warp down there and change the contents of the chests.<br />
<br />
Lobby and Control Room（[https://github.com/garbagemule/MobArena/wiki/img/1.png]请翻译者添加）<br />
<br />
For easier access and modification of the class chests, omitting the control room from the arena or lobby region may prove useful. Otherwise, arenas may have to be temporarily disabled or put into edit mode to allow warping to and changing the contents of the chests.<br />
<br />
The class chests can be located up to 6 blocks below the sign itself or below the block right behind the sign (for wall signs, this would be the block the sign is attached to). The chest may also be in the block directly behind the sign itself - this is safe, because MobArena prevents players in the lobby from opening inventories, so if your lobby is in a tight spot, this might be the better option.<br />
<br />
Multiple sign rows: It is possible to have two rows of class signs in the lobby and still use this feature. Simply place the class chest for the sign of the bottom row exactly at the 6-block limit, and the class chest for the sign of the top row one block up and behind the other chest (in a stair-like fashion). The blocks are searched in a vertical/pillar-like fashion, which is the reason this works.<br />
<br />
Chests Below<br />
<br />
To get auto-equipped armor from the class chests, place the armor pieces in the last four slots of the third row in the chest. MobArena will check these four slots, and if any of them are armor pieces, they will be equipped. Note that the item placed in the very last slot (bottom right), will always be equipped as a helmet (this allows wool blocks, pumpkins, etc. to be used as helmets). The order of the other three slots doesn't matter.<br />
<br />
Armor Slots https://github.com/garbagemule/MobArena/wiki/img/3.png<br />
<br />
The class chests are the best way to add items that are not currently supported by the MobArena item parser. This is because the class chests simply copy the contents of the chests to the player inventories, thus making any items supported by Bukkit supported by MobArena.<br />
<br />
Dyed Armor https://github.com/garbagemule/MobArena/wiki/img/4.png<br />
<br />
==Linked Class Chests==<br />
<br />
If per-arena class chest setups is too troublesome (e.g. if you have many arenas), if you don't need per-arena setups, or if you simply want a single, global class chest for each class, linked class chests are what you're looking for.<br />
<br />
When you link a chest to a class, MobArena will always copy the contents of that chest to the player's inventory, when they pick the given class, regardless of any local class chests (note that the arena must still have use-class-chests: true).<br />
<br />
To link a chest to a class, simply look at the chest and type /ma classchest <class>, and you're done! The linked class chests may exist in any world, but remember that there can only be one class chest per class, and that local class chests will be ignored!<br />
<br />
To unlink a class chest, you will have to open the config-file and remove the classchest node from the given class.<br />
<br />
=怪物波设置=<br />
This page holds an overview of all the formulas used in the MobArena waves system. Customizing the different properties of the waves should be somewhat easier if they can be calculated, so here they all are!<br />
<br />
About notation: Each variable used in the formulas will have its own name. A variable that starts with a # denotes "number (of)", so #players means "number of players", and #wave means "wave number". The function min(a,b) returns the lowest of the values a and b, and max(a,b) returns the highest.<br />
<br />
===Wave growth===<br />
<br />
The wave growth node growth, used in default waves, denotes how fast monster amounts grow over time. The base is calculated by half of the number of players, but at most 13 (i.e. there is no difference between 25 and 50 players). The amounts can be altered further using the amount-multiplier (see the wave setup page).<br />
<br />
#monsters = base * #wave^exp<br />
base = min(#players/2 + 1 , 13)<br />
The exp variable is defined by the growth node, and has the following values:<br />
<br />
slow = 0.5<br />
medium = 0.65<br />
fast = 0.8<br />
psycho = 1.2<br />
Note that with the node value old (which is the default), the monster count is #wave + #players.<br />
<br />
===Swarm Amount===<br />
<br />
The swarm amount node amount, used in swarm waves, denotes how many monsters should spawn in the swarm waves. There will always be at least 10 monsters due to the max function and the lowest multiplier value being 10, however this can be further customized with the amount-multiplier (see the wave setup page).<br />
<br />
#monsters = max(1, #players/2) * multiplier<br />
The multiplier variable is defined by the amount node, and has the following values:<br />
<br />
low = 10<br />
medium = 20<br />
high = 30<br />
psycho = 60<br />
===Boss Health===<br />
<br />
The boss health node health, used in boss waves, denotes how much health the boss has. Note that the health-multiplier node (see the wave setup page) does NOT affect boss waves at all, so these are the only values that can be used. The minimum health a boss can have is 320 health points (~160 hearts), which is with low health and only 1 player fighting. With 10 players and high health, the boss will have 5500 health points (~2750 hearts).<br />
<br />
health = (#players + 1) * 20 * multiplier<br />
The multiplier variable is defined by the health node, and has the following values:<br />
<br />
verylow = 4<br />
low = 8<br />
medium = 15<br />
high = 25<br />
veryhigh = 40<br />
psycho = 60<br />
<br />
=怪物种类（Monster types待搬运）=<br />
Here's a list of all the different monster types MobArena supports. Most of the types exist in both a singular and plural form (i.e. zombie and zombies are exactly the same type), and this is purely a convenience thing. Use these monster types when configuring the waves in MobArena.<br />
<br />
zombie, zombies<br />
skeleton, skeletons<br />
spider, spiders<br />
creeper, creepers<br />
wolf, wolves (these don't attack unless provoked, bukkit bug)<br />
zombie_pigman, zombie_pigmen<br />
powered_creeper, powered_creepers<br />
angry_wolf, angry_wolves (these don't attack unless provoked, bukkit bug)<br />
giant, giants<br />
ghast, ghasts<br />
enderman, endermen<br />
silverfish<br />
cave_spider, cave_spiders<br />
blaze, blazes<br />
enderdragon, enderdragons<br />
snowman, snowmen, snow_golem, snow_golems<br />
iron_golem, iron_golems<br />
witch, witches<br />
wither, withers<br />
wither_skeleton, wither_skeletons<br />
baby_zombie, baby_zombies<br />
baby_pigman, baby_pigmen<br />
zombie_villager, zombie_villagers<br />
baby_zombie_villager, baby_zombie_villagers<br />
<br />
chicken, chickens<br />
cow, cows<br />
mushroom_cow, mushroom_cows<br />
pig, pigs<br />
sheep<br />
squid, squids<br />
villager, villagers<br />
ocelot, ocelots<br />
bat, bats<br />
<br />
horse, horses<br />
donkey, donkeys<br />
mule, mules<br />
skeleton_horse, skeleton_horses<br />
undead_horse, undead_horses<br />
<br />
exploding_sheep<br />
<br />
slime, slimes<br />
slime_tiny, slimes_tiny<br />
slime_small, slimes_small<br />
slime_big, slimes_big<br />
slime_huge, slimes_huge<br />
<br />
magmacube, magmacubes<br />
magmacube_tiny, magmacubes_tiny<br />
magmacube_small, magmacubes_small<br />
magmacube_big, magmacubes_big<br />
magmacube_huge, magmacubes_huge<br />
以上内容搬运自英文wiki[https://github.com/garbagemule/MobArena/wiki]</div>Zhwhttps://mineplugin.org/index.php?title=MobArena&diff=1171MobArena2015-07-28T10:45:31Z<p>Zhw：/* 怪物种类（Monster types待搬运） */</p>
<hr />
<div>{{待搬运}}<br />
{{Bukkit Plugin Infobox<br />
|版本=v0.96.9<br />
|兼容服务端版本=1.8.1<br />
|网址=http://dev.bukkit.org/bukkit-plugins/mobarena/}}<br />
[[Category:娱乐]][[Category:机械]]<br />
=安装=<br />
安装MobArena其实很简单，只需以下四步:<br />
*关闭服务器<del>咳咳，当然是关你自己的服务器啦</del>.<br />
*从论坛主题或是Bukkit Dev站点的项目页下载jar文件.<br />
*将jar文件拖入服务端的plugins文件夹中.<br />
*重启服务端. <br />
之后，配置文件 (config.yml) 以及一个宣告文本(announcements.yml) 会自动创建在plugins/MobArena/路径下.<br />
文件结构如下:<br />
<br />
plugins/<br />
MobArena.jar<br />
MobArena/<br />
config.yml<br />
announcements.yml<br />
此时此刻, 或许你想直接开始设置竞技场, 但是你需要先看看配置文件，并把它配置成你喜欢的样子<del>就是说，还是根据情况配置一下吧</del>. 你可以在配置文件自定义MobArena的设置，职业，奖励，波数（怪物类型）<br />
<br />
=建立竞技场=<br />
==建造一个竞技场==<br />
完整的竞技场应该包含一个可以选择职业的准备区域，一个竞技场地以及观察点(离开点) <br />
下面是各个选项的讲解<br />
<br />
大厅：<br />
玩家加入游戏之前将会在大厅选择职业.一个建造好的游戏大厅会有每一个职业的选择牌子，玩家通过点击牌子可以获取一个职业, 还有一个铁块, 玩家可以通过点击铁块来表示他们已经准备好开始游戏.牌子必须在第一行写上职业的名字（区分大小写）,但是无论你在另外三行上写什么，都不会被怪物竞技场识别，你是不能写上 ,所以你不会得到确认的信息（如果有，那是另一个插件）<br />
<br />
竞技场地：<br />
这里是玩家和怪物搏斗的地方.竞技场地会有墙，可能会有一个屋顶 , 这样玩家和怪物就不能跑出去了. 这使得玩家们不会只是在竞技场外闲逛。.<br />
<br />
观察点: <br />
当玩家想要观看一场战斗时,他们可以使用/ma spec 命令来传送到竞技场的观察点. 这同样也是竞技场中玩家死去后会传送到的地方,前提是在配置文件中，把 spectate-after-death设置为ture. 这块区域要保证观看者不能走出去闲逛（进入竞技场地或者离远竞技场）因为在观看过程中，玩家是无敌的.<br />
<br />
离开点: <br />
在使用 /ma leave命令后,玩家和观察者会被传送到原来所在的地方,除非竞技场有一个离开点(只是可选). 使用离开点,可以准确控制玩家在游戏后去何处.<br />
<br />
关于区域，传送点等，<br />
<br />
当竞技场建好后，就是设置怪物竞技场的区域和传送点的时候了。在设置它们前，我们先来看看他们有什么作用.<br />
<br />
区域: <br />
一个竞技场需要一个竞技区域,然后还可以有一个准备区域，怪物竞技场会使用这些区域来确保玩家不会作弊（通过破坏竞技场来走出区域）,然后确保怪物竞技场所产生的怪物会在里面产生. 怪物竞技场非常排外（不要局外人）, 所以也最好把不想要的生物排除在外. 区域是通过区域工具来设置的.<br />
<br />
传送点: <br />
当玩家加入一个怪物竞技场的游戏时，他们会被传送到准备区域中的准备点来选择职业和准备开始游戏（通过点击铁块）.当每个人都准备好的时候，玩家会被传送到竞技场内的竞技场出生点。观察者会被传送到竞技场的观察点来进入观察区域,当游戏结束的时候，玩家和观察者会被传送到他们传送来之前的地方，或者去可选的离开点,传送点会用传送点工具来设置。.<br />
<br />
出生点: <br />
这里的出生点指的是怪物出生的地点.怪物竞技场只会在附近有玩家的出生点产出怪物（十五个方格的半径）.需要注意的是，怪物的数量不随着按照出生点的数量改变，只会因为在配置文件中波数的倍率改变和玩家的数量所改变.出生点可以通过出生点工具来设置。.<br />
<br />
容器: <br />
容器就是竞技场里的箱子，回收站等。 这些容器将会在一场游戏后重置其内部空间为初始值。只有被声明了的容器才会更新其存储空间，所以仅仅在竞技场里放一个箱子可不够 - 它还需要被用工具声明。<br />
<br />
==设置模式==<br />
我们能用配置模式来设置竞技场。 当我们进入配置模式时，物品栏将会被保存 并给我们一套金工具 （工具栏）， 每一个都有其独特作用。同时我们也可以飞行，使得我们在竞技场附近移动时更加快捷方便一些，最后，但不是绝对，我们不能够聊天或者使用普通命令如果在在配置模式下的话，因为配置模式和你建立起了独立会话（即你所发表的信息都是针对插件的。）<br />
<br />
进入设置模式的方法：输入/ma setup 竞技场名，值得提醒的是，如果服务器中只有一个竞技场，你不用输入竞技场的名字，如果竞技场没有设置完毕或者没有被创造，首先使用/ma addarena 竞技场名来创造它<br />
<br />
离开设置模式的方法：聊天框内输入done，注意不是命令，是聊天信息，没有斜杠<br />
<br />
另外，如果你刚安装怪物竞技场插件，会有一个预置的，名称为default竞技场存在于配置文件中，如果你想要一个不同的名字，你需要先创造一个新竞技场然后把原来的竞技场使用/ma delarena default来删除<br />
<br />
下面我们会提到在设置模式中有什么命令可以使用。<br />
<br />
==设置模式的命令==<br />
<br />
设置模式是一个独立，特殊的会话，这意味着插件会监控我们说的每一句话，使得插件的命令可以缩短，以致于设置过程没有特别麻烦。比如exp命令替代了/ma expandregion，并且还可以防止我们错误地使用了其他插件的命令<br />
<br />
下面是我们可以在设置模式中使用的命令，很多都十分浅显易懂（如果您懂英文的话。）使得您设置竞技场十分快速<br />
done<br />
离开设置模式<br />
别名: end stop done quit<br />
<br />
help<br />
显示帮助信息<br />
别名: ? h<br />
<br />
missing<br />
显示我们还没有设置好的区域（准备区诸如此类）<br />
这个命令在你不知道你已经设置了那些区域的时候十分有用<br />
别名: miss<br />
<br />
expand <region> <amount> <direction><br />
Expand a region by some amount in some direction.<br />
Valid regions: ar for the arena region, or lr for the lobby region<br />
Valid amounts: positive integers (whole numbers)<br />
Valid directions: up, down, or out<br />
Example: expand ar 5 up<br />
别名: exp<br />
<br />
show [<region>|<warp>|<point>]<br />
Show a region, warp, or point(s) as red wool blocks.<br />
Valid regions: ar for the arena region, or lr for the lobby region<br />
Valid warps: arena, lobby, spec, exit<br />
Valid points: spawns (or just sp) for spawnpoints, chests (or just c) for chests<br />
Example: show sp<br />
<br />
==设置时的工具==<br />
<br />
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.<br />
<br />
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.<br />
<br />
===区域工具===<br />
<br />
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.<br />
<br />
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.<br />
<br />
Left-click: Set the first point to be the location of the target block<br />
Right-click: Set the second point to be the location of the target block<br />
<br />
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.<br />
<br />
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.<br />
<br />
===玩家传送点工具===<br />
<br />
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.<br />
<br />
Left-click: Set the currently selected warp on top of the target block<br />
Right-click: Cycle between available warps<br />
<br />
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.<br />
<br />
Note: The arena, lobby, and spectator warps are all required. The exit warp is optional.<br />
<br />
===怪物产生点工具===<br />
<br />
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.<br />
<br />
Left-click: Add a spawnpoint on top of the target block<br />
Right-click: Remove the spawnpoint on top of the target block (if the spawnpoint exists)<br />
<br />
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.<br />
<br />
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.<br />
<br />
===容器工具===<br />
<br />
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.<br />
<br />
Left-click: Register the clicked container (if it wasn't registered)<br />
Right-click: Unregister the clicked container (if it was registered)<br />
<br />
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.<br />
<br />
=命令=<br />
==玩家命令==<br />
<br />
这些指令能够给所有玩家使用. 它们包括了加入, 离开, 旁观和列出所有竞技场(可用或不可用)<br />
<br />
<br />
/ma join (<竞技场>) or /ma j (<竞技场>) - 加入指定名称的竞技场.<br />
/ma leave or /ma l - 离开竞技场或是离开旁观者模式.<br />
/ma notready - 获取所有未准备的玩家.<br />
/ma spec (<竞技场>) or /ma s (<竞技场>) - 以旁观者模式加入指定名称竞技场.<br />
/ma arenas - 获取所有竞技场的名字, 若是绿色则已启用, 灰色则未启用.<br />
/ma players - 获取当前所有竞技场的所有玩家.<br />
/ma players <竞技场> - 获取指定竞技场的所有玩家.<br />
/ma class <职业> - 如果你在大厅里, 是应直接用指令而不是透过牌子互动选择职业.<br />
<br />
==管理员指令==<br />
<br />
只有后台或者服务器op能使用下面这些指令. 这里包括了开始或是停止竞技场, 启用或是卸载竞技场甚至包含了MobArena的所有管理.<br />
<br />
/ma enable - 启用MobArena插件.<br />
/ma disable - 卸载MobArena插件.<br />
/ma enable <竞技场> - 启用指定名字的竞技场.<br />
/ma disable <竞技场> - 关闭指定名字的竞技场.<br />
/ma force end - 停止所有竞技场的运作.<br />
/ma force end <竞技场> - 停止指定名称竞技场的运作及使该竞技场的所有玩家离开. <br />
/ma force start <竞技场> - 开始运作一个指定名称的竞技场以及请出该竞技场内未准备的玩家.<br />
/ma notready <竞技场> - 获取该竞技场内所有未准备的玩家.<br />
/ma restore <玩家> - 在可能的情况下恢复指定玩家背包.<br />
/ma config reload - 重载config配置文件夹.<br />
==建设指令==<br />
<br />
只有op (以及某些合理的指令能在后台) 使用这些指令. 它们包括了设置竞技场传送点, 竞技场出生点以及竞技场范围.<br />
<br />
/ma setup <竞技场> - 进入建设指定名称的竞技场模式.<br />
/ma addarena <竞技场> - 建立一个新的竞技场节点于当前所在世界.<br />
/ma delarena <竞技场> - 删除指定名称的竞技场.<br />
/ma editarena <竞技场> - 开启或关闭指定竞技场修改模式.<br />
/ma editarena <竞技场> [true|false] - 开启 (true) 或关闭 (false) 指定竞技场的修改模式.<br />
/ma setting <竞技场> - 列出所有指定竞技场的设置项.<br />
/ma setting <竞技场> <设置项> - 查询当前指定设置项的值于指定的竞技场.<br />
/ma setting <竞技场> <设置项> <值> - 设置指定竞技场中指定设置项的指定值.<br />
/ma checkspawns - 显示竞技场出生点 (在你当前的竞技场下) 是使用红色羊毛覆盖的范围在当前你当前的位置上. 这个指令同时也能查询在这个范围内不同的点是否被出生点覆盖着.<br />
/ma classchest <职业> - 当正在查询箱子, 使指定的职业与这个箱子建立连接. 连接一个职业箱子意味着当MobArena连接建立后, 将同时复制于职业箱子内的物品, 而不是于竞技场大厅内的任何职业箱子. 当你建立一个职业箱子网络时它能带给你便利.<br />
/ma auto-generate <竞技场> - 自动生成一个指定名称的竞技场. 这个竞技场只会生成于玩家所站的位置下方.<br />
/ma auto-degenerate <竞技场> - 自动停止生成竞技场, 能基于自动生成器下有效地恢复, 当这是一个 "bulldozed" 补丁.<br />
<br />
=权限=<br />
几乎全部的权限插件是'''不需要'''MobArena插件作为前置而能够单独运行的, 但若果你想要更多额外的控制功能, 这里提供了很多不同类型的权限节点哦喵~<br />
== 节点 ==<br />
你能够在安装MobArena插件后使用这些权限节点<br />
<br />
提示: MobArena这个插件提供了很多人性化的默认设定, 所有玩家能够使用所有竞技场及职业, 还有的是OP默认能够使用所有管理员以及建设指令. 除非你想要禁止一些组别进入特定的竞技场或是职业<br />
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!<br />
<br />
==竞技场权限==<br />
<br />
Did you read the note at the top? If not, read it before you continue.<br />
<br />
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.<br />
<br />
bPermissions: ^mobarena.arenas.default<br />
GroupManager: -mobarena.arenas.default<br />
zPermissions: mobarena.arenas.default: false<br />
<br />
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.<br />
<br />
Still confused? Check the sample setup at the bottom of the page!<br />
<br />
==职业权限==<br />
<br />
Did you read the note at the top? If not, read it before you continue.<br />
<br />
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.<br />
<br />
bPermissions: ^mobarena.classes.knight<br />
GroupManager: -mobarena.classes.knight<br />
zPermissions: mobarena.classes.knight: false<br />
<br />
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.<br />
<br />
As with arenas, I recommend letting everyone enjoy all the classes, unless you have a special reason not to.<br />
<br />
Still confused? Check the sample setup at the bottom of the page!<br />
<br />
==命令权限==<br />
<br />
Did you read the note at the top? If not, read it before you continue.<br />
<br />
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!<br />
<br />
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.<br />
<br />
mobarena.use.join<br />
mobarena.use.leave<br />
mobarena.use.spec<br />
mobarena.use.arenalist<br />
mobarena.use.playerlist<br />
mobarena.use.notready<br />
mobarena.use.class<br />
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.<br />
<br />
mobarena.admin.enable<br />
mobarena.admin.kick<br />
mobarena.admin.restore<br />
mobarena.admin.force<br />
mobarena.admin.teleport<br />
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.<br />
<br />
mobarena.setup.config<br />
mobarena.setup.setup<br />
mobarena.setup.setting<br />
mobarena.setup.addarena<br />
mobarena.setup.removearena<br />
mobarena.setup.editarena<br />
mobarena.setup.spawnpoints<br />
mobarena.setup.containers<br />
mobarena.setup.checkdata<br />
mobarena.setup.checkspawns<br />
mobarena.setup.classchest<br />
mobarena.setup.classes<br />
mobarena.setup.leaderboards<br />
mobarena.setup.autogenerate<br />
mobarena.setup.autodegenerate<br />
Sample setup<br />
<br />
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...<br />
<br />
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:<br />
<br />
default-aux: <-- This is the auxiliary group that is to<br />
permissions: be inherited by the default group and<br />
- essentials.balance the donor group. It is not used for<br />
- essentials.pay anything else.<br />
- essentials.sell<br />
<br />
default: <-- This is the default group. It inherits<br />
inherits: default-aux from default-aux, but also revokes the<br />
permissions: permission for the special class.<br />
- -mobarena.classes.diamondknight<br />
<br />
donor: <-- This is the donor group, which also<br />
inherits: default-aux inherits from default-aux, but it<br />
permissions: does not revoke any class permissions,<br />
- essentials.balance.others which means it has access to all of<br />
- essentials.kit them by default.<br />
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.<br />
<br />
=物品语法=<br />
An Overview<br />
<br />
Items in MobArena follow a very specific syntax that you must obey, or you will experience missing items or errors. Be attentive to the details, because if you aren't, there will be consequences.<br />
<br />
MobArena allows these three different ways of defining items:<br />
<br />
Single: [<id>|<name>]<br />
Multiple: [<id>|<name>]:<amount><br />
Sub-types: [<id>|<name>]:<data>:<amount><br />
Confusing? Let's break them down one by one.<br />
<br />
===1. Single Items===<br />
<br />
[<id>|<name>]<br />
This means you can use either the item ID (<id>) or the item name (<name>), both as defined in the Material enum of the Bukkit API (the IDs are the numbers in parentheses). The item names are case-insensitive.<br />
<br />
Make sure to read the important note on item IDs!<br />
<br />
Examples: diamond_sword, stone, 42 (iron block), 322 (snowball)<br />
<br />
===2. Multiple Items===<br />
<br />
[<id>|<name>]:<amount><br />
This way, you append an <amount> to the item, specifying how many of the given item you want. This is useful for giving out stuff like arrows or potions that you generally want to give more than one of.<br />
<br />
Note that if you use this syntax, it is indeed the amount you specify, not the item sub-type. We go over sub-types in the next section.<br />
<br />
Make sure to read the important note on item IDs!<br />
<br />
Examples: arrow:64, grilled_pork:4, 46:10 (10x TNT), 142:5 (5x potato)<br />
<br />
===3. Item Sub-Types (potions, wool, dyes etc.)===<br />
<br />
[<id>|<name>]:<data>:<amount><br />
This way, you append BOTH a <data> value (the sub-type) and an <amount>, regardless of how many of the given item you want. This syntax is mostly used with potions, which have special sub-type values in the 8000's and 16000's. Check out this page for the potion sub-types.<br />
<br />
For wool and dyes (ink sacks), you don't have to use the numeric data value. Instead, you can use the color names as defined in the DyeColor enum of the Bukkit API.<br />
<br />
Make sure to read the important note on item IDs!<br />
<br />
Examples: wool:blue:1 (one blue wool), ink_sack:brown:10 (ten cocoa beans), potion:8201:1 (one strength potion), 373:8197:2 (two health potions)<br />
<br />
An important note on using item IDs<br />
<br />
If you choose to use item IDs, there is a catch. If an item is alone in its node, it MUST be enclosed in apostrophes, or YAML will crap itself. For example, if you decide to have a Barbarian class that only has a pair of lederhosen as armor, and nothing put a couple of health potions, you need to do it like this:<br />
<br />
classes:<br />
Barbarian:<br />
items: '373:8197:2'<br />
armor: '300'<br />
In other words, you have to put '300' in the armor-node, not just 300, and you have to put '373:8197:2' in the items-node, not just 373:8197:2. This requirement is removed if you use the item names instead, or if you add enchantments to the given item.<br />
<br />
Enchantments<br />
<br />
Enchantments can be added to items by appending a space, followed by a semi-colon separated list of pairs <eid>:<level>, where <eid> is an enchantment ID as defined by the Enchantment Wrappers in the Bukkit API (the numbers in the parentheses at the end of each line), i.e.:<br />
<br />
<item> <eid>:<level>;<eid>:<level>;...<br />
The <item> is any item following the normal item syntax as described above. Here is an example:<br />
<br />
diamond_sword 16:2;19:5<br />
This line gives a diamond sword with sharpness (ID 16) level 2, and knockback (ID 19) level 5.<br />
<br />
Economy Money<br />
<br />
$<amount><br />
MobArena supports entry fees and rewards in the form of money from economy plugins. This feature requires Vault. The format quite simply means that you type in a dollar sign followed by a valid monetary value.<br />
<br />
Examples: $1, $5, $3.14 (v0.96+), $0.99 (v0.96+)<br />
<br />
=职业箱子=<br />
==About Class Chests==<br />
<br />
If some of your favorite items aren't supported by MobArena's internal item parser, or if you just want to be able to configure your class items from in-game, the class chests may be what you're looking for!<br />
<br />
Note: The Class Chests will only work for arenas with use-class-chests: true, and the classes MUST exist in the config-file for MobArena to recognize them, however the items and armor lists can be empty.<br />
<br />
The idea behind the class chests is to simply place some chests below the corresponding class signs in the lobby, and fill them with whatever items you want the given class to have. When the players activate the class signs, the contents of the chests are copied to the player inventory. This suggests a type of "control room" setup, where an admin-only access room below the lobby contains the chests, allowing admins to warp down there and change the contents of the chests.<br />
<br />
Lobby and Control Room（[https://github.com/garbagemule/MobArena/wiki/img/1.png]请翻译者添加）<br />
<br />
For easier access and modification of the class chests, omitting the control room from the arena or lobby region may prove useful. Otherwise, arenas may have to be temporarily disabled or put into edit mode to allow warping to and changing the contents of the chests.<br />
<br />
The class chests can be located up to 6 blocks below the sign itself or below the block right behind the sign (for wall signs, this would be the block the sign is attached to). The chest may also be in the block directly behind the sign itself - this is safe, because MobArena prevents players in the lobby from opening inventories, so if your lobby is in a tight spot, this might be the better option.<br />
<br />
Multiple sign rows: It is possible to have two rows of class signs in the lobby and still use this feature. Simply place the class chest for the sign of the bottom row exactly at the 6-block limit, and the class chest for the sign of the top row one block up and behind the other chest (in a stair-like fashion). The blocks are searched in a vertical/pillar-like fashion, which is the reason this works.<br />
<br />
Chests Below<br />
<br />
To get auto-equipped armor from the class chests, place the armor pieces in the last four slots of the third row in the chest. MobArena will check these four slots, and if any of them are armor pieces, they will be equipped. Note that the item placed in the very last slot (bottom right), will always be equipped as a helmet (this allows wool blocks, pumpkins, etc. to be used as helmets). The order of the other three slots doesn't matter.<br />
<br />
Armor Slots https://github.com/garbagemule/MobArena/wiki/img/3.png<br />
<br />
The class chests are the best way to add items that are not currently supported by the MobArena item parser. This is because the class chests simply copy the contents of the chests to the player inventories, thus making any items supported by Bukkit supported by MobArena.<br />
<br />
Dyed Armor https://github.com/garbagemule/MobArena/wiki/img/4.png<br />
<br />
==Linked Class Chests==<br />
<br />
If per-arena class chest setups is too troublesome (e.g. if you have many arenas), if you don't need per-arena setups, or if you simply want a single, global class chest for each class, linked class chests are what you're looking for.<br />
<br />
When you link a chest to a class, MobArena will always copy the contents of that chest to the player's inventory, when they pick the given class, regardless of any local class chests (note that the arena must still have use-class-chests: true).<br />
<br />
To link a chest to a class, simply look at the chest and type /ma classchest <class>, and you're done! The linked class chests may exist in any world, but remember that there can only be one class chest per class, and that local class chests will be ignored!<br />
<br />
To unlink a class chest, you will have to open the config-file and remove the classchest node from the given class.<br />
<br />
=怪物波设置=<br />
This page holds an overview of all the formulas used in the MobArena waves system. Customizing the different properties of the waves should be somewhat easier if they can be calculated, so here they all are!<br />
<br />
About notation: Each variable used in the formulas will have its own name. A variable that starts with a # denotes "number (of)", so #players means "number of players", and #wave means "wave number". The function min(a,b) returns the lowest of the values a and b, and max(a,b) returns the highest.<br />
<br />
===Wave growth===<br />
<br />
The wave growth node growth, used in default waves, denotes how fast monster amounts grow over time. The base is calculated by half of the number of players, but at most 13 (i.e. there is no difference between 25 and 50 players). The amounts can be altered further using the amount-multiplier (see the wave setup page).<br />
<br />
#monsters = base * #wave^exp<br />
base = min(#players/2 + 1 , 13)<br />
The exp variable is defined by the growth node, and has the following values:<br />
<br />
slow = 0.5<br />
medium = 0.65<br />
fast = 0.8<br />
psycho = 1.2<br />
Note that with the node value old (which is the default), the monster count is #wave + #players.<br />
<br />
===Swarm Amount===<br />
<br />
The swarm amount node amount, used in swarm waves, denotes how many monsters should spawn in the swarm waves. There will always be at least 10 monsters due to the max function and the lowest multiplier value being 10, however this can be further customized with the amount-multiplier (see the wave setup page).<br />
<br />
#monsters = max(1, #players/2) * multiplier<br />
The multiplier variable is defined by the amount node, and has the following values:<br />
<br />
low = 10<br />
medium = 20<br />
high = 30<br />
psycho = 60<br />
===Boss Health===<br />
<br />
The boss health node health, used in boss waves, denotes how much health the boss has. Note that the health-multiplier node (see the wave setup page) does NOT affect boss waves at all, so these are the only values that can be used. The minimum health a boss can have is 320 health points (~160 hearts), which is with low health and only 1 player fighting. With 10 players and high health, the boss will have 5500 health points (~2750 hearts).<br />
<br />
health = (#players + 1) * 20 * multiplier<br />
The multiplier variable is defined by the health node, and has the following values:<br />
<br />
verylow = 4<br />
low = 8<br />
medium = 15<br />
high = 25<br />
veryhigh = 40<br />
psycho = 60<br />
<br />
=怪物种类（Monster types待搬运）=<br />
Here's a list of all the different monster types MobArena supports. Most of the types exist in both a singular and plural form (i.e. zombie and zombies are exactly the same type), and this is purely a convenience thing. Use these monster types when configuring the waves in MobArena.<br />
<br />
zombie, zombies<br />
skeleton, skeletons<br />
spider, spiders<br />
creeper, creepers<br />
wolf, wolves (these don't attack unless provoked, bukkit bug)<br />
zombie_pigman, zombie_pigmen<br />
powered_creeper, powered_creepers<br />
angry_wolf, angry_wolves (these don't attack unless provoked, bukkit bug)<br />
giant, giants<br />
ghast, ghasts<br />
enderman, endermen<br />
silverfish<br />
cave_spider, cave_spiders<br />
blaze, blazes<br />
enderdragon, enderdragons<br />
snowman, snowmen, snow_golem, snow_golems<br />
iron_golem, iron_golems<br />
witch, witches<br />
wither, withers<br />
wither_skeleton, wither_skeletons<br />
baby_zombie, baby_zombies<br />
baby_pigman, baby_pigmen<br />
zombie_villager, zombie_villagers<br />
baby_zombie_villager, baby_zombie_villagers<br />
<br />
chicken, chickens<br />
cow, cows<br />
mushroom_cow, mushroom_cows<br />
pig, pigs<br />
sheep<br />
squid, squids<br />
villager, villagers<br />
ocelot, ocelots<br />
bat, bats<br />
<br />
horse, horses<br />
donkey, donkeys<br />
mule, mules<br />
skeleton_horse, skeleton_horses<br />
undead_horse, undead_horses<br />
<br />
exploding_sheep<br />
<br />
slime, slimes<br />
slime_tiny, slimes_tiny<br />
slime_small, slimes_small<br />
slime_big, slimes_big<br />
slime_huge, slimes_huge<br />
<br />
magmacube, magmacubes<br />
magmacube_tiny, magmacubes_tiny<br />
magmacube_small, magmacubes_small<br />
magmacube_big, magmacubes_big<br />
magmacube_huge, magmacubes_huge<br />
以上内容搬运自英文wiki[https://github.com/garbagemule/MobArena/wiki]</div>Zhwhttps://mineplugin.org/index.php?title=MobArena&diff=1170MobArena2015-07-28T10:44:01Z<p>Zhw：/* 怪物波设置（Formulas待搬运） */</p>
<hr />
<div>{{待搬运}}<br />
{{Bukkit Plugin Infobox<br />
|版本=v0.96.9<br />
|兼容服务端版本=1.8.1<br />
|网址=http://dev.bukkit.org/bukkit-plugins/mobarena/}}<br />
[[Category:娱乐]][[Category:机械]]<br />
=安装=<br />
安装MobArena其实很简单，只需以下四步:<br />
*关闭服务器<del>咳咳，当然是关你自己的服务器啦</del>.<br />
*从论坛主题或是Bukkit Dev站点的项目页下载jar文件.<br />
*将jar文件拖入服务端的plugins文件夹中.<br />
*重启服务端. <br />
之后，配置文件 (config.yml) 以及一个宣告文本(announcements.yml) 会自动创建在plugins/MobArena/路径下.<br />
文件结构如下:<br />
<br />
plugins/<br />
MobArena.jar<br />
MobArena/<br />
config.yml<br />
announcements.yml<br />
此时此刻, 或许你想直接开始设置竞技场, 但是你需要先看看配置文件，并把它配置成你喜欢的样子<del>就是说，还是根据情况配置一下吧</del>. 你可以在配置文件自定义MobArena的设置，职业，奖励，波数（怪物类型）<br />
<br />
=建立竞技场=<br />
==建造一个竞技场==<br />
完整的竞技场应该包含一个可以选择职业的准备区域，一个竞技场地以及观察点(离开点) <br />
下面是各个选项的讲解<br />
<br />
大厅：<br />
玩家加入游戏之前将会在大厅选择职业.一个建造好的游戏大厅会有每一个职业的选择牌子，玩家通过点击牌子可以获取一个职业, 还有一个铁块, 玩家可以通过点击铁块来表示他们已经准备好开始游戏.牌子必须在第一行写上职业的名字（区分大小写）,但是无论你在另外三行上写什么，都不会被怪物竞技场识别，你是不能写上 ,所以你不会得到确认的信息（如果有，那是另一个插件）<br />
<br />
竞技场地：<br />
这里是玩家和怪物搏斗的地方.竞技场地会有墙，可能会有一个屋顶 , 这样玩家和怪物就不能跑出去了. 这使得玩家们不会只是在竞技场外闲逛。.<br />
<br />
观察点: <br />
当玩家想要观看一场战斗时,他们可以使用/ma spec 命令来传送到竞技场的观察点. 这同样也是竞技场中玩家死去后会传送到的地方,前提是在配置文件中，把 spectate-after-death设置为ture. 这块区域要保证观看者不能走出去闲逛（进入竞技场地或者离远竞技场）因为在观看过程中，玩家是无敌的.<br />
<br />
离开点: <br />
在使用 /ma leave命令后,玩家和观察者会被传送到原来所在的地方,除非竞技场有一个离开点(只是可选). 使用离开点,可以准确控制玩家在游戏后去何处.<br />
<br />
关于区域，传送点等，<br />
<br />
当竞技场建好后，就是设置怪物竞技场的区域和传送点的时候了。在设置它们前，我们先来看看他们有什么作用.<br />
<br />
区域: <br />
一个竞技场需要一个竞技区域,然后还可以有一个准备区域，怪物竞技场会使用这些区域来确保玩家不会作弊（通过破坏竞技场来走出区域）,然后确保怪物竞技场所产生的怪物会在里面产生. 怪物竞技场非常排外（不要局外人）, 所以也最好把不想要的生物排除在外. 区域是通过区域工具来设置的.<br />
<br />
传送点: <br />
当玩家加入一个怪物竞技场的游戏时，他们会被传送到准备区域中的准备点来选择职业和准备开始游戏（通过点击铁块）.当每个人都准备好的时候，玩家会被传送到竞技场内的竞技场出生点。观察者会被传送到竞技场的观察点来进入观察区域,当游戏结束的时候，玩家和观察者会被传送到他们传送来之前的地方，或者去可选的离开点,传送点会用传送点工具来设置。.<br />
<br />
出生点: <br />
这里的出生点指的是怪物出生的地点.怪物竞技场只会在附近有玩家的出生点产出怪物（十五个方格的半径）.需要注意的是，怪物的数量不随着按照出生点的数量改变，只会因为在配置文件中波数的倍率改变和玩家的数量所改变.出生点可以通过出生点工具来设置。.<br />
<br />
容器: <br />
容器就是竞技场里的箱子，回收站等。 这些容器将会在一场游戏后重置其内部空间为初始值。只有被声明了的容器才会更新其存储空间，所以仅仅在竞技场里放一个箱子可不够 - 它还需要被用工具声明。<br />
<br />
==设置模式==<br />
我们能用配置模式来设置竞技场。 当我们进入配置模式时，物品栏将会被保存 并给我们一套金工具 （工具栏）， 每一个都有其独特作用。同时我们也可以飞行，使得我们在竞技场附近移动时更加快捷方便一些，最后，但不是绝对，我们不能够聊天或者使用普通命令如果在在配置模式下的话，因为配置模式和你建立起了独立会话（即你所发表的信息都是针对插件的。）<br />
<br />
进入设置模式的方法：输入/ma setup 竞技场名，值得提醒的是，如果服务器中只有一个竞技场，你不用输入竞技场的名字，如果竞技场没有设置完毕或者没有被创造，首先使用/ma addarena 竞技场名来创造它<br />
<br />
离开设置模式的方法：聊天框内输入done，注意不是命令，是聊天信息，没有斜杠<br />
<br />
另外，如果你刚安装怪物竞技场插件，会有一个预置的，名称为default竞技场存在于配置文件中，如果你想要一个不同的名字，你需要先创造一个新竞技场然后把原来的竞技场使用/ma delarena default来删除<br />
<br />
下面我们会提到在设置模式中有什么命令可以使用。<br />
<br />
==设置模式的命令==<br />
<br />
设置模式是一个独立，特殊的会话，这意味着插件会监控我们说的每一句话，使得插件的命令可以缩短，以致于设置过程没有特别麻烦。比如exp命令替代了/ma expandregion，并且还可以防止我们错误地使用了其他插件的命令<br />
<br />
下面是我们可以在设置模式中使用的命令，很多都十分浅显易懂（如果您懂英文的话。）使得您设置竞技场十分快速<br />
done<br />
离开设置模式<br />
别名: end stop done quit<br />
<br />
help<br />
显示帮助信息<br />
别名: ? h<br />
<br />
missing<br />
显示我们还没有设置好的区域（准备区诸如此类）<br />
这个命令在你不知道你已经设置了那些区域的时候十分有用<br />
别名: miss<br />
<br />
expand <region> <amount> <direction><br />
Expand a region by some amount in some direction.<br />
Valid regions: ar for the arena region, or lr for the lobby region<br />
Valid amounts: positive integers (whole numbers)<br />
Valid directions: up, down, or out<br />
Example: expand ar 5 up<br />
别名: exp<br />
<br />
show [<region>|<warp>|<point>]<br />
Show a region, warp, or point(s) as red wool blocks.<br />
Valid regions: ar for the arena region, or lr for the lobby region<br />
Valid warps: arena, lobby, spec, exit<br />
Valid points: spawns (or just sp) for spawnpoints, chests (or just c) for chests<br />
Example: show sp<br />
<br />
==设置时的工具==<br />
<br />
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.<br />
<br />
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.<br />
<br />
===区域工具===<br />
<br />
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.<br />
<br />
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.<br />
<br />
Left-click: Set the first point to be the location of the target block<br />
Right-click: Set the second point to be the location of the target block<br />
<br />
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.<br />
<br />
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.<br />
<br />
===玩家传送点工具===<br />
<br />
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.<br />
<br />
Left-click: Set the currently selected warp on top of the target block<br />
Right-click: Cycle between available warps<br />
<br />
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.<br />
<br />
Note: The arena, lobby, and spectator warps are all required. The exit warp is optional.<br />
<br />
===怪物产生点工具===<br />
<br />
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.<br />
<br />
Left-click: Add a spawnpoint on top of the target block<br />
Right-click: Remove the spawnpoint on top of the target block (if the spawnpoint exists)<br />
<br />
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.<br />
<br />
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.<br />
<br />
===容器工具===<br />
<br />
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.<br />
<br />
Left-click: Register the clicked container (if it wasn't registered)<br />
Right-click: Unregister the clicked container (if it was registered)<br />
<br />
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.<br />
<br />
=命令=<br />
==玩家命令==<br />
<br />
这些指令能够给所有玩家使用. 它们包括了加入, 离开, 旁观和列出所有竞技场(可用或不可用)<br />
<br />
<br />
/ma join (<竞技场>) or /ma j (<竞技场>) - 加入指定名称的竞技场.<br />
/ma leave or /ma l - 离开竞技场或是离开旁观者模式.<br />
/ma notready - 获取所有未准备的玩家.<br />
/ma spec (<竞技场>) or /ma s (<竞技场>) - 以旁观者模式加入指定名称竞技场.<br />
/ma arenas - 获取所有竞技场的名字, 若是绿色则已启用, 灰色则未启用.<br />
/ma players - 获取当前所有竞技场的所有玩家.<br />
/ma players <竞技场> - 获取指定竞技场的所有玩家.<br />
/ma class <职业> - 如果你在大厅里, 是应直接用指令而不是透过牌子互动选择职业.<br />
<br />
==管理员指令==<br />
<br />
只有后台或者服务器op能使用下面这些指令. 这里包括了开始或是停止竞技场, 启用或是卸载竞技场甚至包含了MobArena的所有管理.<br />
<br />
/ma enable - 启用MobArena插件.<br />
/ma disable - 卸载MobArena插件.<br />
/ma enable <竞技场> - 启用指定名字的竞技场.<br />
/ma disable <竞技场> - 关闭指定名字的竞技场.<br />
/ma force end - 停止所有竞技场的运作.<br />
/ma force end <竞技场> - 停止指定名称竞技场的运作及使该竞技场的所有玩家离开. <br />
/ma force start <竞技场> - 开始运作一个指定名称的竞技场以及请出该竞技场内未准备的玩家.<br />
/ma notready <竞技场> - 获取该竞技场内所有未准备的玩家.<br />
/ma restore <玩家> - 在可能的情况下恢复指定玩家背包.<br />
/ma config reload - 重载config配置文件夹.<br />
==建设指令==<br />
<br />
只有op (以及某些合理的指令能在后台) 使用这些指令. 它们包括了设置竞技场传送点, 竞技场出生点以及竞技场范围.<br />
<br />
/ma setup <竞技场> - 进入建设指定名称的竞技场模式.<br />
/ma addarena <竞技场> - 建立一个新的竞技场节点于当前所在世界.<br />
/ma delarena <竞技场> - 删除指定名称的竞技场.<br />
/ma editarena <竞技场> - 开启或关闭指定竞技场修改模式.<br />
/ma editarena <竞技场> [true|false] - 开启 (true) 或关闭 (false) 指定竞技场的修改模式.<br />
/ma setting <竞技场> - 列出所有指定竞技场的设置项.<br />
/ma setting <竞技场> <设置项> - 查询当前指定设置项的值于指定的竞技场.<br />
/ma setting <竞技场> <设置项> <值> - 设置指定竞技场中指定设置项的指定值.<br />
/ma checkspawns - 显示竞技场出生点 (在你当前的竞技场下) 是使用红色羊毛覆盖的范围在当前你当前的位置上. 这个指令同时也能查询在这个范围内不同的点是否被出生点覆盖着.<br />
/ma classchest <职业> - 当正在查询箱子, 使指定的职业与这个箱子建立连接. 连接一个职业箱子意味着当MobArena连接建立后, 将同时复制于职业箱子内的物品, 而不是于竞技场大厅内的任何职业箱子. 当你建立一个职业箱子网络时它能带给你便利.<br />
/ma auto-generate <竞技场> - 自动生成一个指定名称的竞技场. 这个竞技场只会生成于玩家所站的位置下方.<br />
/ma auto-degenerate <竞技场> - 自动停止生成竞技场, 能基于自动生成器下有效地恢复, 当这是一个 "bulldozed" 补丁.<br />
<br />
=权限=<br />
几乎全部的权限插件是'''不需要'''MobArena插件作为前置而能够单独运行的, 但若果你想要更多额外的控制功能, 这里提供了很多不同类型的权限节点哦喵~<br />
== 节点 ==<br />
你能够在安装MobArena插件后使用这些权限节点<br />
<br />
提示: MobArena这个插件提供了很多人性化的默认设定, 所有玩家能够使用所有竞技场及职业, 还有的是OP默认能够使用所有管理员以及建设指令. 除非你想要禁止一些组别进入特定的竞技场或是职业<br />
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!<br />
<br />
==竞技场权限==<br />
<br />
Did you read the note at the top? If not, read it before you continue.<br />
<br />
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.<br />
<br />
bPermissions: ^mobarena.arenas.default<br />
GroupManager: -mobarena.arenas.default<br />
zPermissions: mobarena.arenas.default: false<br />
<br />
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.<br />
<br />
Still confused? Check the sample setup at the bottom of the page!<br />
<br />
==职业权限==<br />
<br />
Did you read the note at the top? If not, read it before you continue.<br />
<br />
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.<br />
<br />
bPermissions: ^mobarena.classes.knight<br />
GroupManager: -mobarena.classes.knight<br />
zPermissions: mobarena.classes.knight: false<br />
<br />
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.<br />
<br />
As with arenas, I recommend letting everyone enjoy all the classes, unless you have a special reason not to.<br />
<br />
Still confused? Check the sample setup at the bottom of the page!<br />
<br />
==命令权限==<br />
<br />
Did you read the note at the top? If not, read it before you continue.<br />
<br />
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!<br />
<br />
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.<br />
<br />
mobarena.use.join<br />
mobarena.use.leave<br />
mobarena.use.spec<br />
mobarena.use.arenalist<br />
mobarena.use.playerlist<br />
mobarena.use.notready<br />
mobarena.use.class<br />
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.<br />
<br />
mobarena.admin.enable<br />
mobarena.admin.kick<br />
mobarena.admin.restore<br />
mobarena.admin.force<br />
mobarena.admin.teleport<br />
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.<br />
<br />
mobarena.setup.config<br />
mobarena.setup.setup<br />
mobarena.setup.setting<br />
mobarena.setup.addarena<br />
mobarena.setup.removearena<br />
mobarena.setup.editarena<br />
mobarena.setup.spawnpoints<br />
mobarena.setup.containers<br />
mobarena.setup.checkdata<br />
mobarena.setup.checkspawns<br />
mobarena.setup.classchest<br />
mobarena.setup.classes<br />
mobarena.setup.leaderboards<br />
mobarena.setup.autogenerate<br />
mobarena.setup.autodegenerate<br />
Sample setup<br />
<br />
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...<br />
<br />
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:<br />
<br />
default-aux: <-- This is the auxiliary group that is to<br />
permissions: be inherited by the default group and<br />
- essentials.balance the donor group. It is not used for<br />
- essentials.pay anything else.<br />
- essentials.sell<br />
<br />
default: <-- This is the default group. It inherits<br />
inherits: default-aux from default-aux, but also revokes the<br />
permissions: permission for the special class.<br />
- -mobarena.classes.diamondknight<br />
<br />
donor: <-- This is the donor group, which also<br />
inherits: default-aux inherits from default-aux, but it<br />
permissions: does not revoke any class permissions,<br />
- essentials.balance.others which means it has access to all of<br />
- essentials.kit them by default.<br />
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.<br />
<br />
=物品语法=<br />
An Overview<br />
<br />
Items in MobArena follow a very specific syntax that you must obey, or you will experience missing items or errors. Be attentive to the details, because if you aren't, there will be consequences.<br />
<br />
MobArena allows these three different ways of defining items:<br />
<br />
Single: [<id>|<name>]<br />
Multiple: [<id>|<name>]:<amount><br />
Sub-types: [<id>|<name>]:<data>:<amount><br />
Confusing? Let's break them down one by one.<br />
<br />
===1. Single Items===<br />
<br />
[<id>|<name>]<br />
This means you can use either the item ID (<id>) or the item name (<name>), both as defined in the Material enum of the Bukkit API (the IDs are the numbers in parentheses). The item names are case-insensitive.<br />
<br />
Make sure to read the important note on item IDs!<br />
<br />
Examples: diamond_sword, stone, 42 (iron block), 322 (snowball)<br />
<br />
===2. Multiple Items===<br />
<br />
[<id>|<name>]:<amount><br />
This way, you append an <amount> to the item, specifying how many of the given item you want. This is useful for giving out stuff like arrows or potions that you generally want to give more than one of.<br />
<br />
Note that if you use this syntax, it is indeed the amount you specify, not the item sub-type. We go over sub-types in the next section.<br />
<br />
Make sure to read the important note on item IDs!<br />
<br />
Examples: arrow:64, grilled_pork:4, 46:10 (10x TNT), 142:5 (5x potato)<br />
<br />
===3. Item Sub-Types (potions, wool, dyes etc.)===<br />
<br />
[<id>|<name>]:<data>:<amount><br />
This way, you append BOTH a <data> value (the sub-type) and an <amount>, regardless of how many of the given item you want. This syntax is mostly used with potions, which have special sub-type values in the 8000's and 16000's. Check out this page for the potion sub-types.<br />
<br />
For wool and dyes (ink sacks), you don't have to use the numeric data value. Instead, you can use the color names as defined in the DyeColor enum of the Bukkit API.<br />
<br />
Make sure to read the important note on item IDs!<br />
<br />
Examples: wool:blue:1 (one blue wool), ink_sack:brown:10 (ten cocoa beans), potion:8201:1 (one strength potion), 373:8197:2 (two health potions)<br />
<br />
An important note on using item IDs<br />
<br />
If you choose to use item IDs, there is a catch. If an item is alone in its node, it MUST be enclosed in apostrophes, or YAML will crap itself. For example, if you decide to have a Barbarian class that only has a pair of lederhosen as armor, and nothing put a couple of health potions, you need to do it like this:<br />
<br />
classes:<br />
Barbarian:<br />
items: '373:8197:2'<br />
armor: '300'<br />
In other words, you have to put '300' in the armor-node, not just 300, and you have to put '373:8197:2' in the items-node, not just 373:8197:2. This requirement is removed if you use the item names instead, or if you add enchantments to the given item.<br />
<br />
Enchantments<br />
<br />
Enchantments can be added to items by appending a space, followed by a semi-colon separated list of pairs <eid>:<level>, where <eid> is an enchantment ID as defined by the Enchantment Wrappers in the Bukkit API (the numbers in the parentheses at the end of each line), i.e.:<br />
<br />
<item> <eid>:<level>;<eid>:<level>;...<br />
The <item> is any item following the normal item syntax as described above. Here is an example:<br />
<br />
diamond_sword 16:2;19:5<br />
This line gives a diamond sword with sharpness (ID 16) level 2, and knockback (ID 19) level 5.<br />
<br />
Economy Money<br />
<br />
$<amount><br />
MobArena supports entry fees and rewards in the form of money from economy plugins. This feature requires Vault. The format quite simply means that you type in a dollar sign followed by a valid monetary value.<br />
<br />
Examples: $1, $5, $3.14 (v0.96+), $0.99 (v0.96+)<br />
<br />
=职业箱子=<br />
==About Class Chests==<br />
<br />
If some of your favorite items aren't supported by MobArena's internal item parser, or if you just want to be able to configure your class items from in-game, the class chests may be what you're looking for!<br />
<br />
Note: The Class Chests will only work for arenas with use-class-chests: true, and the classes MUST exist in the config-file for MobArena to recognize them, however the items and armor lists can be empty.<br />
<br />
The idea behind the class chests is to simply place some chests below the corresponding class signs in the lobby, and fill them with whatever items you want the given class to have. When the players activate the class signs, the contents of the chests are copied to the player inventory. This suggests a type of "control room" setup, where an admin-only access room below the lobby contains the chests, allowing admins to warp down there and change the contents of the chests.<br />
<br />
Lobby and Control Room（[https://github.com/garbagemule/MobArena/wiki/img/1.png]请翻译者添加）<br />
<br />
For easier access and modification of the class chests, omitting the control room from the arena or lobby region may prove useful. Otherwise, arenas may have to be temporarily disabled or put into edit mode to allow warping to and changing the contents of the chests.<br />
<br />
The class chests can be located up to 6 blocks below the sign itself or below the block right behind the sign (for wall signs, this would be the block the sign is attached to). The chest may also be in the block directly behind the sign itself - this is safe, because MobArena prevents players in the lobby from opening inventories, so if your lobby is in a tight spot, this might be the better option.<br />
<br />
Multiple sign rows: It is possible to have two rows of class signs in the lobby and still use this feature. Simply place the class chest for the sign of the bottom row exactly at the 6-block limit, and the class chest for the sign of the top row one block up and behind the other chest (in a stair-like fashion). The blocks are searched in a vertical/pillar-like fashion, which is the reason this works.<br />
<br />
Chests Below<br />
<br />
To get auto-equipped armor from the class chests, place the armor pieces in the last four slots of the third row in the chest. MobArena will check these four slots, and if any of them are armor pieces, they will be equipped. Note that the item placed in the very last slot (bottom right), will always be equipped as a helmet (this allows wool blocks, pumpkins, etc. to be used as helmets). The order of the other three slots doesn't matter.<br />
<br />
Armor Slots https://github.com/garbagemule/MobArena/wiki/img/3.png<br />
<br />
The class chests are the best way to add items that are not currently supported by the MobArena item parser. This is because the class chests simply copy the contents of the chests to the player inventories, thus making any items supported by Bukkit supported by MobArena.<br />
<br />
Dyed Armor https://github.com/garbagemule/MobArena/wiki/img/4.png<br />
<br />
==Linked Class Chests==<br />
<br />
If per-arena class chest setups is too troublesome (e.g. if you have many arenas), if you don't need per-arena setups, or if you simply want a single, global class chest for each class, linked class chests are what you're looking for.<br />
<br />
When you link a chest to a class, MobArena will always copy the contents of that chest to the player's inventory, when they pick the given class, regardless of any local class chests (note that the arena must still have use-class-chests: true).<br />
<br />
To link a chest to a class, simply look at the chest and type /ma classchest <class>, and you're done! The linked class chests may exist in any world, but remember that there can only be one class chest per class, and that local class chests will be ignored!<br />
<br />
To unlink a class chest, you will have to open the config-file and remove the classchest node from the given class.<br />
<br />
=怪物波设置=<br />
This page holds an overview of all the formulas used in the MobArena waves system. Customizing the different properties of the waves should be somewhat easier if they can be calculated, so here they all are!<br />
<br />
About notation: Each variable used in the formulas will have its own name. A variable that starts with a # denotes "number (of)", so #players means "number of players", and #wave means "wave number". The function min(a,b) returns the lowest of the values a and b, and max(a,b) returns the highest.<br />
<br />
===Wave growth===<br />
<br />
The wave growth node growth, used in default waves, denotes how fast monster amounts grow over time. The base is calculated by half of the number of players, but at most 13 (i.e. there is no difference between 25 and 50 players). The amounts can be altered further using the amount-multiplier (see the wave setup page).<br />
<br />
#monsters = base * #wave^exp<br />
base = min(#players/2 + 1 , 13)<br />
The exp variable is defined by the growth node, and has the following values:<br />
<br />
slow = 0.5<br />
medium = 0.65<br />
fast = 0.8<br />
psycho = 1.2<br />
Note that with the node value old (which is the default), the monster count is #wave + #players.<br />
<br />
===Swarm Amount===<br />
<br />
The swarm amount node amount, used in swarm waves, denotes how many monsters should spawn in the swarm waves. There will always be at least 10 monsters due to the max function and the lowest multiplier value being 10, however this can be further customized with the amount-multiplier (see the wave setup page).<br />
<br />
#monsters = max(1, #players/2) * multiplier<br />
The multiplier variable is defined by the amount node, and has the following values:<br />
<br />
low = 10<br />
medium = 20<br />
high = 30<br />
psycho = 60<br />
===Boss Health===<br />
<br />
The boss health node health, used in boss waves, denotes how much health the boss has. Note that the health-multiplier node (see the wave setup page) does NOT affect boss waves at all, so these are the only values that can be used. The minimum health a boss can have is 320 health points (~160 hearts), which is with low health and only 1 player fighting. With 10 players and high health, the boss will have 5500 health points (~2750 hearts).<br />
<br />
health = (#players + 1) * 20 * multiplier<br />
The multiplier variable is defined by the health node, and has the following values:<br />
<br />
verylow = 4<br />
low = 8<br />
medium = 15<br />
high = 25<br />
veryhigh = 40<br />
psycho = 60<br />
<br />
=怪物种类（Monster types待搬运）=<br />
以上内容搬运自英文wiki[https://github.com/garbagemule/MobArena/wiki]</div>Zhwhttps://mineplugin.org/index.php?title=MobArena&diff=1169MobArena2015-07-28T10:41:21Z<p>Zhw：/* 物品语法（Item Syntax待搬运） */</p>
<hr />
<div>{{待搬运}}<br />
{{Bukkit Plugin Infobox<br />
|版本=v0.96.9<br />
|兼容服务端版本=1.8.1<br />
|网址=http://dev.bukkit.org/bukkit-plugins/mobarena/}}<br />
[[Category:娱乐]][[Category:机械]]<br />
=安装=<br />
安装MobArena其实很简单，只需以下四步:<br />
*关闭服务器<del>咳咳，当然是关你自己的服务器啦</del>.<br />
*从论坛主题或是Bukkit Dev站点的项目页下载jar文件.<br />
*将jar文件拖入服务端的plugins文件夹中.<br />
*重启服务端. <br />
之后，配置文件 (config.yml) 以及一个宣告文本(announcements.yml) 会自动创建在plugins/MobArena/路径下.<br />
文件结构如下:<br />
<br />
plugins/<br />
MobArena.jar<br />
MobArena/<br />
config.yml<br />
announcements.yml<br />
此时此刻, 或许你想直接开始设置竞技场, 但是你需要先看看配置文件，并把它配置成你喜欢的样子<del>就是说，还是根据情况配置一下吧</del>. 你可以在配置文件自定义MobArena的设置，职业，奖励，波数（怪物类型）<br />
<br />
=建立竞技场=<br />
==建造一个竞技场==<br />
完整的竞技场应该包含一个可以选择职业的准备区域，一个竞技场地以及观察点(离开点) <br />
下面是各个选项的讲解<br />
<br />
大厅：<br />
玩家加入游戏之前将会在大厅选择职业.一个建造好的游戏大厅会有每一个职业的选择牌子，玩家通过点击牌子可以获取一个职业, 还有一个铁块, 玩家可以通过点击铁块来表示他们已经准备好开始游戏.牌子必须在第一行写上职业的名字（区分大小写）,但是无论你在另外三行上写什么，都不会被怪物竞技场识别，你是不能写上 ,所以你不会得到确认的信息（如果有，那是另一个插件）<br />
<br />
竞技场地：<br />
这里是玩家和怪物搏斗的地方.竞技场地会有墙，可能会有一个屋顶 , 这样玩家和怪物就不能跑出去了. 这使得玩家们不会只是在竞技场外闲逛。.<br />
<br />
观察点: <br />
当玩家想要观看一场战斗时,他们可以使用/ma spec 命令来传送到竞技场的观察点. 这同样也是竞技场中玩家死去后会传送到的地方,前提是在配置文件中，把 spectate-after-death设置为ture. 这块区域要保证观看者不能走出去闲逛（进入竞技场地或者离远竞技场）因为在观看过程中，玩家是无敌的.<br />
<br />
离开点: <br />
在使用 /ma leave命令后,玩家和观察者会被传送到原来所在的地方,除非竞技场有一个离开点(只是可选). 使用离开点,可以准确控制玩家在游戏后去何处.<br />
<br />
关于区域，传送点等，<br />
<br />
当竞技场建好后，就是设置怪物竞技场的区域和传送点的时候了。在设置它们前，我们先来看看他们有什么作用.<br />
<br />
区域: <br />
一个竞技场需要一个竞技区域,然后还可以有一个准备区域，怪物竞技场会使用这些区域来确保玩家不会作弊（通过破坏竞技场来走出区域）,然后确保怪物竞技场所产生的怪物会在里面产生. 怪物竞技场非常排外（不要局外人）, 所以也最好把不想要的生物排除在外. 区域是通过区域工具来设置的.<br />
<br />
传送点: <br />
当玩家加入一个怪物竞技场的游戏时，他们会被传送到准备区域中的准备点来选择职业和准备开始游戏（通过点击铁块）.当每个人都准备好的时候，玩家会被传送到竞技场内的竞技场出生点。观察者会被传送到竞技场的观察点来进入观察区域,当游戏结束的时候，玩家和观察者会被传送到他们传送来之前的地方，或者去可选的离开点,传送点会用传送点工具来设置。.<br />
<br />
出生点: <br />
这里的出生点指的是怪物出生的地点.怪物竞技场只会在附近有玩家的出生点产出怪物（十五个方格的半径）.需要注意的是，怪物的数量不随着按照出生点的数量改变，只会因为在配置文件中波数的倍率改变和玩家的数量所改变.出生点可以通过出生点工具来设置。.<br />
<br />
容器: <br />
容器就是竞技场里的箱子，回收站等。 这些容器将会在一场游戏后重置其内部空间为初始值。只有被声明了的容器才会更新其存储空间，所以仅仅在竞技场里放一个箱子可不够 - 它还需要被用工具声明。<br />
<br />
==设置模式==<br />
我们能用配置模式来设置竞技场。 当我们进入配置模式时，物品栏将会被保存 并给我们一套金工具 （工具栏）， 每一个都有其独特作用。同时我们也可以飞行，使得我们在竞技场附近移动时更加快捷方便一些，最后，但不是绝对，我们不能够聊天或者使用普通命令如果在在配置模式下的话，因为配置模式和你建立起了独立会话（即你所发表的信息都是针对插件的。）<br />
<br />
进入设置模式的方法：输入/ma setup 竞技场名，值得提醒的是，如果服务器中只有一个竞技场，你不用输入竞技场的名字，如果竞技场没有设置完毕或者没有被创造，首先使用/ma addarena 竞技场名来创造它<br />
<br />
离开设置模式的方法：聊天框内输入done，注意不是命令，是聊天信息，没有斜杠<br />
<br />
另外，如果你刚安装怪物竞技场插件，会有一个预置的，名称为default竞技场存在于配置文件中，如果你想要一个不同的名字，你需要先创造一个新竞技场然后把原来的竞技场使用/ma delarena default来删除<br />
<br />
下面我们会提到在设置模式中有什么命令可以使用。<br />
<br />
==设置模式的命令==<br />
<br />
设置模式是一个独立，特殊的会话，这意味着插件会监控我们说的每一句话，使得插件的命令可以缩短，以致于设置过程没有特别麻烦。比如exp命令替代了/ma expandregion，并且还可以防止我们错误地使用了其他插件的命令<br />
<br />
下面是我们可以在设置模式中使用的命令，很多都十分浅显易懂（如果您懂英文的话。）使得您设置竞技场十分快速<br />
done<br />
离开设置模式<br />
别名: end stop done quit<br />
<br />
help<br />
显示帮助信息<br />
别名: ? h<br />
<br />
missing<br />
显示我们还没有设置好的区域（准备区诸如此类）<br />
这个命令在你不知道你已经设置了那些区域的时候十分有用<br />
别名: miss<br />
<br />
expand <region> <amount> <direction><br />
Expand a region by some amount in some direction.<br />
Valid regions: ar for the arena region, or lr for the lobby region<br />
Valid amounts: positive integers (whole numbers)<br />
Valid directions: up, down, or out<br />
Example: expand ar 5 up<br />
别名: exp<br />
<br />
show [<region>|<warp>|<point>]<br />
Show a region, warp, or point(s) as red wool blocks.<br />
Valid regions: ar for the arena region, or lr for the lobby region<br />
Valid warps: arena, lobby, spec, exit<br />
Valid points: spawns (or just sp) for spawnpoints, chests (or just c) for chests<br />
Example: show sp<br />
<br />
==设置时的工具==<br />
<br />
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.<br />
<br />
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.<br />
<br />
===区域工具===<br />
<br />
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.<br />
<br />
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.<br />
<br />
Left-click: Set the first point to be the location of the target block<br />
Right-click: Set the second point to be the location of the target block<br />
<br />
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.<br />
<br />
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.<br />
<br />
===玩家传送点工具===<br />
<br />
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.<br />
<br />
Left-click: Set the currently selected warp on top of the target block<br />
Right-click: Cycle between available warps<br />
<br />
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.<br />
<br />
Note: The arena, lobby, and spectator warps are all required. The exit warp is optional.<br />
<br />
===怪物产生点工具===<br />
<br />
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.<br />
<br />
Left-click: Add a spawnpoint on top of the target block<br />
Right-click: Remove the spawnpoint on top of the target block (if the spawnpoint exists)<br />
<br />
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.<br />
<br />
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.<br />
<br />
===容器工具===<br />
<br />
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.<br />
<br />
Left-click: Register the clicked container (if it wasn't registered)<br />
Right-click: Unregister the clicked container (if it was registered)<br />
<br />
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.<br />
<br />
=命令=<br />
==玩家命令==<br />
<br />
这些指令能够给所有玩家使用. 它们包括了加入, 离开, 旁观和列出所有竞技场(可用或不可用)<br />
<br />
<br />
/ma join (<竞技场>) or /ma j (<竞技场>) - 加入指定名称的竞技场.<br />
/ma leave or /ma l - 离开竞技场或是离开旁观者模式.<br />
/ma notready - 获取所有未准备的玩家.<br />
/ma spec (<竞技场>) or /ma s (<竞技场>) - 以旁观者模式加入指定名称竞技场.<br />
/ma arenas - 获取所有竞技场的名字, 若是绿色则已启用, 灰色则未启用.<br />
/ma players - 获取当前所有竞技场的所有玩家.<br />
/ma players <竞技场> - 获取指定竞技场的所有玩家.<br />
/ma class <职业> - 如果你在大厅里, 是应直接用指令而不是透过牌子互动选择职业.<br />
<br />
==管理员指令==<br />
<br />
只有后台或者服务器op能使用下面这些指令. 这里包括了开始或是停止竞技场, 启用或是卸载竞技场甚至包含了MobArena的所有管理.<br />
<br />
/ma enable - 启用MobArena插件.<br />
/ma disable - 卸载MobArena插件.<br />
/ma enable <竞技场> - 启用指定名字的竞技场.<br />
/ma disable <竞技场> - 关闭指定名字的竞技场.<br />
/ma force end - 停止所有竞技场的运作.<br />
/ma force end <竞技场> - 停止指定名称竞技场的运作及使该竞技场的所有玩家离开. <br />
/ma force start <竞技场> - 开始运作一个指定名称的竞技场以及请出该竞技场内未准备的玩家.<br />
/ma notready <竞技场> - 获取该竞技场内所有未准备的玩家.<br />
/ma restore <玩家> - 在可能的情况下恢复指定玩家背包.<br />
/ma config reload - 重载config配置文件夹.<br />
==建设指令==<br />
<br />
只有op (以及某些合理的指令能在后台) 使用这些指令. 它们包括了设置竞技场传送点, 竞技场出生点以及竞技场范围.<br />
<br />
/ma setup <竞技场> - 进入建设指定名称的竞技场模式.<br />
/ma addarena <竞技场> - 建立一个新的竞技场节点于当前所在世界.<br />
/ma delarena <竞技场> - 删除指定名称的竞技场.<br />
/ma editarena <竞技场> - 开启或关闭指定竞技场修改模式.<br />
/ma editarena <竞技场> [true|false] - 开启 (true) 或关闭 (false) 指定竞技场的修改模式.<br />
/ma setting <竞技场> - 列出所有指定竞技场的设置项.<br />
/ma setting <竞技场> <设置项> - 查询当前指定设置项的值于指定的竞技场.<br />
/ma setting <竞技场> <设置项> <值> - 设置指定竞技场中指定设置项的指定值.<br />
/ma checkspawns - 显示竞技场出生点 (在你当前的竞技场下) 是使用红色羊毛覆盖的范围在当前你当前的位置上. 这个指令同时也能查询在这个范围内不同的点是否被出生点覆盖着.<br />
/ma classchest <职业> - 当正在查询箱子, 使指定的职业与这个箱子建立连接. 连接一个职业箱子意味着当MobArena连接建立后, 将同时复制于职业箱子内的物品, 而不是于竞技场大厅内的任何职业箱子. 当你建立一个职业箱子网络时它能带给你便利.<br />
/ma auto-generate <竞技场> - 自动生成一个指定名称的竞技场. 这个竞技场只会生成于玩家所站的位置下方.<br />
/ma auto-degenerate <竞技场> - 自动停止生成竞技场, 能基于自动生成器下有效地恢复, 当这是一个 "bulldozed" 补丁.<br />
<br />
=权限=<br />
几乎全部的权限插件是'''不需要'''MobArena插件作为前置而能够单独运行的, 但若果你想要更多额外的控制功能, 这里提供了很多不同类型的权限节点哦喵~<br />
== 节点 ==<br />
你能够在安装MobArena插件后使用这些权限节点<br />
<br />
提示: MobArena这个插件提供了很多人性化的默认设定, 所有玩家能够使用所有竞技场及职业, 还有的是OP默认能够使用所有管理员以及建设指令. 除非你想要禁止一些组别进入特定的竞技场或是职业<br />
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!<br />
<br />
==竞技场权限==<br />
<br />
Did you read the note at the top? If not, read it before you continue.<br />
<br />
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.<br />
<br />
bPermissions: ^mobarena.arenas.default<br />
GroupManager: -mobarena.arenas.default<br />
zPermissions: mobarena.arenas.default: false<br />
<br />
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.<br />
<br />
Still confused? Check the sample setup at the bottom of the page!<br />
<br />
==职业权限==<br />
<br />
Did you read the note at the top? If not, read it before you continue.<br />
<br />
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.<br />
<br />
bPermissions: ^mobarena.classes.knight<br />
GroupManager: -mobarena.classes.knight<br />
zPermissions: mobarena.classes.knight: false<br />
<br />
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.<br />
<br />
As with arenas, I recommend letting everyone enjoy all the classes, unless you have a special reason not to.<br />
<br />
Still confused? Check the sample setup at the bottom of the page!<br />
<br />
==命令权限==<br />
<br />
Did you read the note at the top? If not, read it before you continue.<br />
<br />
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!<br />
<br />
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.<br />
<br />
mobarena.use.join<br />
mobarena.use.leave<br />
mobarena.use.spec<br />
mobarena.use.arenalist<br />
mobarena.use.playerlist<br />
mobarena.use.notready<br />
mobarena.use.class<br />
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.<br />
<br />
mobarena.admin.enable<br />
mobarena.admin.kick<br />
mobarena.admin.restore<br />
mobarena.admin.force<br />
mobarena.admin.teleport<br />
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.<br />
<br />
mobarena.setup.config<br />
mobarena.setup.setup<br />
mobarena.setup.setting<br />
mobarena.setup.addarena<br />
mobarena.setup.removearena<br />
mobarena.setup.editarena<br />
mobarena.setup.spawnpoints<br />
mobarena.setup.containers<br />
mobarena.setup.checkdata<br />
mobarena.setup.checkspawns<br />
mobarena.setup.classchest<br />
mobarena.setup.classes<br />
mobarena.setup.leaderboards<br />
mobarena.setup.autogenerate<br />
mobarena.setup.autodegenerate<br />
Sample setup<br />
<br />
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...<br />
<br />
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:<br />
<br />
default-aux: <-- This is the auxiliary group that is to<br />
permissions: be inherited by the default group and<br />
- essentials.balance the donor group. It is not used for<br />
- essentials.pay anything else.<br />
- essentials.sell<br />
<br />
default: <-- This is the default group. It inherits<br />
inherits: default-aux from default-aux, but also revokes the<br />
permissions: permission for the special class.<br />
- -mobarena.classes.diamondknight<br />
<br />
donor: <-- This is the donor group, which also<br />
inherits: default-aux inherits from default-aux, but it<br />
permissions: does not revoke any class permissions,<br />
- essentials.balance.others which means it has access to all of<br />
- essentials.kit them by default.<br />
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.<br />
<br />
=物品语法=<br />
An Overview<br />
<br />
Items in MobArena follow a very specific syntax that you must obey, or you will experience missing items or errors. Be attentive to the details, because if you aren't, there will be consequences.<br />
<br />
MobArena allows these three different ways of defining items:<br />
<br />
Single: [<id>|<name>]<br />
Multiple: [<id>|<name>]:<amount><br />
Sub-types: [<id>|<name>]:<data>:<amount><br />
Confusing? Let's break them down one by one.<br />
<br />
===1. Single Items===<br />
<br />
[<id>|<name>]<br />
This means you can use either the item ID (<id>) or the item name (<name>), both as defined in the Material enum of the Bukkit API (the IDs are the numbers in parentheses). The item names are case-insensitive.<br />
<br />
Make sure to read the important note on item IDs!<br />
<br />
Examples: diamond_sword, stone, 42 (iron block), 322 (snowball)<br />
<br />
===2. Multiple Items===<br />
<br />
[<id>|<name>]:<amount><br />
This way, you append an <amount> to the item, specifying how many of the given item you want. This is useful for giving out stuff like arrows or potions that you generally want to give more than one of.<br />
<br />
Note that if you use this syntax, it is indeed the amount you specify, not the item sub-type. We go over sub-types in the next section.<br />
<br />
Make sure to read the important note on item IDs!<br />
<br />
Examples: arrow:64, grilled_pork:4, 46:10 (10x TNT), 142:5 (5x potato)<br />
<br />
===3. Item Sub-Types (potions, wool, dyes etc.)===<br />
<br />
[<id>|<name>]:<data>:<amount><br />
This way, you append BOTH a <data> value (the sub-type) and an <amount>, regardless of how many of the given item you want. This syntax is mostly used with potions, which have special sub-type values in the 8000's and 16000's. Check out this page for the potion sub-types.<br />
<br />
For wool and dyes (ink sacks), you don't have to use the numeric data value. Instead, you can use the color names as defined in the DyeColor enum of the Bukkit API.<br />
<br />
Make sure to read the important note on item IDs!<br />
<br />
Examples: wool:blue:1 (one blue wool), ink_sack:brown:10 (ten cocoa beans), potion:8201:1 (one strength potion), 373:8197:2 (two health potions)<br />
<br />
An important note on using item IDs<br />
<br />
If you choose to use item IDs, there is a catch. If an item is alone in its node, it MUST be enclosed in apostrophes, or YAML will crap itself. For example, if you decide to have a Barbarian class that only has a pair of lederhosen as armor, and nothing put a couple of health potions, you need to do it like this:<br />
<br />
classes:<br />
Barbarian:<br />
items: '373:8197:2'<br />
armor: '300'<br />
In other words, you have to put '300' in the armor-node, not just 300, and you have to put '373:8197:2' in the items-node, not just 373:8197:2. This requirement is removed if you use the item names instead, or if you add enchantments to the given item.<br />
<br />
Enchantments<br />
<br />
Enchantments can be added to items by appending a space, followed by a semi-colon separated list of pairs <eid>:<level>, where <eid> is an enchantment ID as defined by the Enchantment Wrappers in the Bukkit API (the numbers in the parentheses at the end of each line), i.e.:<br />
<br />
<item> <eid>:<level>;<eid>:<level>;...<br />
The <item> is any item following the normal item syntax as described above. Here is an example:<br />
<br />
diamond_sword 16:2;19:5<br />
This line gives a diamond sword with sharpness (ID 16) level 2, and knockback (ID 19) level 5.<br />
<br />
Economy Money<br />
<br />
$<amount><br />
MobArena supports entry fees and rewards in the form of money from economy plugins. This feature requires Vault. The format quite simply means that you type in a dollar sign followed by a valid monetary value.<br />
<br />
Examples: $1, $5, $3.14 (v0.96+), $0.99 (v0.96+)<br />
<br />
=职业箱子=<br />
==About Class Chests==<br />
<br />
If some of your favorite items aren't supported by MobArena's internal item parser, or if you just want to be able to configure your class items from in-game, the class chests may be what you're looking for!<br />
<br />
Note: The Class Chests will only work for arenas with use-class-chests: true, and the classes MUST exist in the config-file for MobArena to recognize them, however the items and armor lists can be empty.<br />
<br />
The idea behind the class chests is to simply place some chests below the corresponding class signs in the lobby, and fill them with whatever items you want the given class to have. When the players activate the class signs, the contents of the chests are copied to the player inventory. This suggests a type of "control room" setup, where an admin-only access room below the lobby contains the chests, allowing admins to warp down there and change the contents of the chests.<br />
<br />
Lobby and Control Room（[https://github.com/garbagemule/MobArena/wiki/img/1.png]请翻译者添加）<br />
<br />
For easier access and modification of the class chests, omitting the control room from the arena or lobby region may prove useful. Otherwise, arenas may have to be temporarily disabled or put into edit mode to allow warping to and changing the contents of the chests.<br />
<br />
The class chests can be located up to 6 blocks below the sign itself or below the block right behind the sign (for wall signs, this would be the block the sign is attached to). The chest may also be in the block directly behind the sign itself - this is safe, because MobArena prevents players in the lobby from opening inventories, so if your lobby is in a tight spot, this might be the better option.<br />
<br />
Multiple sign rows: It is possible to have two rows of class signs in the lobby and still use this feature. Simply place the class chest for the sign of the bottom row exactly at the 6-block limit, and the class chest for the sign of the top row one block up and behind the other chest (in a stair-like fashion). The blocks are searched in a vertical/pillar-like fashion, which is the reason this works.<br />
<br />
Chests Below<br />
<br />
To get auto-equipped armor from the class chests, place the armor pieces in the last four slots of the third row in the chest. MobArena will check these four slots, and if any of them are armor pieces, they will be equipped. Note that the item placed in the very last slot (bottom right), will always be equipped as a helmet (this allows wool blocks, pumpkins, etc. to be used as helmets). The order of the other three slots doesn't matter.<br />
<br />
Armor Slots https://github.com/garbagemule/MobArena/wiki/img/3.png<br />
<br />
The class chests are the best way to add items that are not currently supported by the MobArena item parser. This is because the class chests simply copy the contents of the chests to the player inventories, thus making any items supported by Bukkit supported by MobArena.<br />
<br />
Dyed Armor https://github.com/garbagemule/MobArena/wiki/img/4.png<br />
<br />
==Linked Class Chests==<br />
<br />
If per-arena class chest setups is too troublesome (e.g. if you have many arenas), if you don't need per-arena setups, or if you simply want a single, global class chest for each class, linked class chests are what you're looking for.<br />
<br />
When you link a chest to a class, MobArena will always copy the contents of that chest to the player's inventory, when they pick the given class, regardless of any local class chests (note that the arena must still have use-class-chests: true).<br />
<br />
To link a chest to a class, simply look at the chest and type /ma classchest <class>, and you're done! The linked class chests may exist in any world, but remember that there can only be one class chest per class, and that local class chests will be ignored!<br />
<br />
To unlink a class chest, you will have to open the config-file and remove the classchest node from the given class.<br />
<br />
=怪物波设置（Formulas待搬运）=<br />
=怪物种类（Monster types待搬运）=<br />
以上内容搬运自英文wiki[https://github.com/garbagemule/MobArena/wiki]</div>Zhwhttps://mineplugin.org/index.php?title=MobArena&diff=1168MobArena2015-07-28T10:40:49Z<p>Zhw：/* 职业箱子（Class Chests待搬运｝ */</p>
<hr />
<div>{{待搬运}}<br />
{{Bukkit Plugin Infobox<br />
|版本=v0.96.9<br />
|兼容服务端版本=1.8.1<br />
|网址=http://dev.bukkit.org/bukkit-plugins/mobarena/}}<br />
[[Category:娱乐]][[Category:机械]]<br />
=安装=<br />
安装MobArena其实很简单，只需以下四步:<br />
*关闭服务器<del>咳咳，当然是关你自己的服务器啦</del>.<br />
*从论坛主题或是Bukkit Dev站点的项目页下载jar文件.<br />
*将jar文件拖入服务端的plugins文件夹中.<br />
*重启服务端. <br />
之后，配置文件 (config.yml) 以及一个宣告文本(announcements.yml) 会自动创建在plugins/MobArena/路径下.<br />
文件结构如下:<br />
<br />
plugins/<br />
MobArena.jar<br />
MobArena/<br />
config.yml<br />
announcements.yml<br />
此时此刻, 或许你想直接开始设置竞技场, 但是你需要先看看配置文件，并把它配置成你喜欢的样子<del>就是说，还是根据情况配置一下吧</del>. 你可以在配置文件自定义MobArena的设置，职业，奖励，波数（怪物类型）<br />
<br />
=建立竞技场=<br />
==建造一个竞技场==<br />
完整的竞技场应该包含一个可以选择职业的准备区域，一个竞技场地以及观察点(离开点) <br />
下面是各个选项的讲解<br />
<br />
大厅：<br />
玩家加入游戏之前将会在大厅选择职业.一个建造好的游戏大厅会有每一个职业的选择牌子，玩家通过点击牌子可以获取一个职业, 还有一个铁块, 玩家可以通过点击铁块来表示他们已经准备好开始游戏.牌子必须在第一行写上职业的名字（区分大小写）,但是无论你在另外三行上写什么，都不会被怪物竞技场识别，你是不能写上 ,所以你不会得到确认的信息（如果有，那是另一个插件）<br />
<br />
竞技场地：<br />
这里是玩家和怪物搏斗的地方.竞技场地会有墙，可能会有一个屋顶 , 这样玩家和怪物就不能跑出去了. 这使得玩家们不会只是在竞技场外闲逛。.<br />
<br />
观察点: <br />
当玩家想要观看一场战斗时,他们可以使用/ma spec 命令来传送到竞技场的观察点. 这同样也是竞技场中玩家死去后会传送到的地方,前提是在配置文件中，把 spectate-after-death设置为ture. 这块区域要保证观看者不能走出去闲逛（进入竞技场地或者离远竞技场）因为在观看过程中，玩家是无敌的.<br />
<br />
离开点: <br />
在使用 /ma leave命令后,玩家和观察者会被传送到原来所在的地方,除非竞技场有一个离开点(只是可选). 使用离开点,可以准确控制玩家在游戏后去何处.<br />
<br />
关于区域，传送点等，<br />
<br />
当竞技场建好后，就是设置怪物竞技场的区域和传送点的时候了。在设置它们前，我们先来看看他们有什么作用.<br />
<br />
区域: <br />
一个竞技场需要一个竞技区域,然后还可以有一个准备区域，怪物竞技场会使用这些区域来确保玩家不会作弊（通过破坏竞技场来走出区域）,然后确保怪物竞技场所产生的怪物会在里面产生. 怪物竞技场非常排外（不要局外人）, 所以也最好把不想要的生物排除在外. 区域是通过区域工具来设置的.<br />
<br />
传送点: <br />
当玩家加入一个怪物竞技场的游戏时，他们会被传送到准备区域中的准备点来选择职业和准备开始游戏（通过点击铁块）.当每个人都准备好的时候，玩家会被传送到竞技场内的竞技场出生点。观察者会被传送到竞技场的观察点来进入观察区域,当游戏结束的时候，玩家和观察者会被传送到他们传送来之前的地方，或者去可选的离开点,传送点会用传送点工具来设置。.<br />
<br />
出生点: <br />
这里的出生点指的是怪物出生的地点.怪物竞技场只会在附近有玩家的出生点产出怪物（十五个方格的半径）.需要注意的是，怪物的数量不随着按照出生点的数量改变，只会因为在配置文件中波数的倍率改变和玩家的数量所改变.出生点可以通过出生点工具来设置。.<br />
<br />
容器: <br />
容器就是竞技场里的箱子，回收站等。 这些容器将会在一场游戏后重置其内部空间为初始值。只有被声明了的容器才会更新其存储空间，所以仅仅在竞技场里放一个箱子可不够 - 它还需要被用工具声明。<br />
<br />
==设置模式==<br />
我们能用配置模式来设置竞技场。 当我们进入配置模式时，物品栏将会被保存 并给我们一套金工具 （工具栏）， 每一个都有其独特作用。同时我们也可以飞行，使得我们在竞技场附近移动时更加快捷方便一些，最后，但不是绝对，我们不能够聊天或者使用普通命令如果在在配置模式下的话，因为配置模式和你建立起了独立会话（即你所发表的信息都是针对插件的。）<br />
<br />
进入设置模式的方法：输入/ma setup 竞技场名，值得提醒的是，如果服务器中只有一个竞技场，你不用输入竞技场的名字，如果竞技场没有设置完毕或者没有被创造，首先使用/ma addarena 竞技场名来创造它<br />
<br />
离开设置模式的方法：聊天框内输入done，注意不是命令，是聊天信息，没有斜杠<br />
<br />
另外，如果你刚安装怪物竞技场插件，会有一个预置的，名称为default竞技场存在于配置文件中，如果你想要一个不同的名字，你需要先创造一个新竞技场然后把原来的竞技场使用/ma delarena default来删除<br />
<br />
下面我们会提到在设置模式中有什么命令可以使用。<br />
<br />
==设置模式的命令==<br />
<br />
设置模式是一个独立，特殊的会话，这意味着插件会监控我们说的每一句话，使得插件的命令可以缩短，以致于设置过程没有特别麻烦。比如exp命令替代了/ma expandregion，并且还可以防止我们错误地使用了其他插件的命令<br />
<br />
下面是我们可以在设置模式中使用的命令，很多都十分浅显易懂（如果您懂英文的话。）使得您设置竞技场十分快速<br />
done<br />
离开设置模式<br />
别名: end stop done quit<br />
<br />
help<br />
显示帮助信息<br />
别名: ? h<br />
<br />
missing<br />
显示我们还没有设置好的区域（准备区诸如此类）<br />
这个命令在你不知道你已经设置了那些区域的时候十分有用<br />
别名: miss<br />
<br />
expand <region> <amount> <direction><br />
Expand a region by some amount in some direction.<br />
Valid regions: ar for the arena region, or lr for the lobby region<br />
Valid amounts: positive integers (whole numbers)<br />
Valid directions: up, down, or out<br />
Example: expand ar 5 up<br />
别名: exp<br />
<br />
show [<region>|<warp>|<point>]<br />
Show a region, warp, or point(s) as red wool blocks.<br />
Valid regions: ar for the arena region, or lr for the lobby region<br />
Valid warps: arena, lobby, spec, exit<br />
Valid points: spawns (or just sp) for spawnpoints, chests (or just c) for chests<br />
Example: show sp<br />
<br />
==设置时的工具==<br />
<br />
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.<br />
<br />
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.<br />
<br />
===区域工具===<br />
<br />
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.<br />
<br />
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.<br />
<br />
Left-click: Set the first point to be the location of the target block<br />
Right-click: Set the second point to be the location of the target block<br />
<br />
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.<br />
<br />
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.<br />
<br />
===玩家传送点工具===<br />
<br />
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.<br />
<br />
Left-click: Set the currently selected warp on top of the target block<br />
Right-click: Cycle between available warps<br />
<br />
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.<br />
<br />
Note: The arena, lobby, and spectator warps are all required. The exit warp is optional.<br />
<br />
===怪物产生点工具===<br />
<br />
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.<br />
<br />
Left-click: Add a spawnpoint on top of the target block<br />
Right-click: Remove the spawnpoint on top of the target block (if the spawnpoint exists)<br />
<br />
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.<br />
<br />
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.<br />
<br />
===容器工具===<br />
<br />
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.<br />
<br />
Left-click: Register the clicked container (if it wasn't registered)<br />
Right-click: Unregister the clicked container (if it was registered)<br />
<br />
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.<br />
<br />
=命令=<br />
==玩家命令==<br />
<br />
这些指令能够给所有玩家使用. 它们包括了加入, 离开, 旁观和列出所有竞技场(可用或不可用)<br />
<br />
<br />
/ma join (<竞技场>) or /ma j (<竞技场>) - 加入指定名称的竞技场.<br />
/ma leave or /ma l - 离开竞技场或是离开旁观者模式.<br />
/ma notready - 获取所有未准备的玩家.<br />
/ma spec (<竞技场>) or /ma s (<竞技场>) - 以旁观者模式加入指定名称竞技场.<br />
/ma arenas - 获取所有竞技场的名字, 若是绿色则已启用, 灰色则未启用.<br />
/ma players - 获取当前所有竞技场的所有玩家.<br />
/ma players <竞技场> - 获取指定竞技场的所有玩家.<br />
/ma class <职业> - 如果你在大厅里, 是应直接用指令而不是透过牌子互动选择职业.<br />
<br />
==管理员指令==<br />
<br />
只有后台或者服务器op能使用下面这些指令. 这里包括了开始或是停止竞技场, 启用或是卸载竞技场甚至包含了MobArena的所有管理.<br />
<br />
/ma enable - 启用MobArena插件.<br />
/ma disable - 卸载MobArena插件.<br />
/ma enable <竞技场> - 启用指定名字的竞技场.<br />
/ma disable <竞技场> - 关闭指定名字的竞技场.<br />
/ma force end - 停止所有竞技场的运作.<br />
/ma force end <竞技场> - 停止指定名称竞技场的运作及使该竞技场的所有玩家离开. <br />
/ma force start <竞技场> - 开始运作一个指定名称的竞技场以及请出该竞技场内未准备的玩家.<br />
/ma notready <竞技场> - 获取该竞技场内所有未准备的玩家.<br />
/ma restore <玩家> - 在可能的情况下恢复指定玩家背包.<br />
/ma config reload - 重载config配置文件夹.<br />
==建设指令==<br />
<br />
只有op (以及某些合理的指令能在后台) 使用这些指令. 它们包括了设置竞技场传送点, 竞技场出生点以及竞技场范围.<br />
<br />
/ma setup <竞技场> - 进入建设指定名称的竞技场模式.<br />
/ma addarena <竞技场> - 建立一个新的竞技场节点于当前所在世界.<br />
/ma delarena <竞技场> - 删除指定名称的竞技场.<br />
/ma editarena <竞技场> - 开启或关闭指定竞技场修改模式.<br />
/ma editarena <竞技场> [true|false] - 开启 (true) 或关闭 (false) 指定竞技场的修改模式.<br />
/ma setting <竞技场> - 列出所有指定竞技场的设置项.<br />
/ma setting <竞技场> <设置项> - 查询当前指定设置项的值于指定的竞技场.<br />
/ma setting <竞技场> <设置项> <值> - 设置指定竞技场中指定设置项的指定值.<br />
/ma checkspawns - 显示竞技场出生点 (在你当前的竞技场下) 是使用红色羊毛覆盖的范围在当前你当前的位置上. 这个指令同时也能查询在这个范围内不同的点是否被出生点覆盖着.<br />
/ma classchest <职业> - 当正在查询箱子, 使指定的职业与这个箱子建立连接. 连接一个职业箱子意味着当MobArena连接建立后, 将同时复制于职业箱子内的物品, 而不是于竞技场大厅内的任何职业箱子. 当你建立一个职业箱子网络时它能带给你便利.<br />
/ma auto-generate <竞技场> - 自动生成一个指定名称的竞技场. 这个竞技场只会生成于玩家所站的位置下方.<br />
/ma auto-degenerate <竞技场> - 自动停止生成竞技场, 能基于自动生成器下有效地恢复, 当这是一个 "bulldozed" 补丁.<br />
<br />
=权限=<br />
几乎全部的权限插件是'''不需要'''MobArena插件作为前置而能够单独运行的, 但若果你想要更多额外的控制功能, 这里提供了很多不同类型的权限节点哦喵~<br />
== 节点 ==<br />
你能够在安装MobArena插件后使用这些权限节点<br />
<br />
提示: MobArena这个插件提供了很多人性化的默认设定, 所有玩家能够使用所有竞技场及职业, 还有的是OP默认能够使用所有管理员以及建设指令. 除非你想要禁止一些组别进入特定的竞技场或是职业<br />
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!<br />
<br />
==竞技场权限==<br />
<br />
Did you read the note at the top? If not, read it before you continue.<br />
<br />
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.<br />
<br />
bPermissions: ^mobarena.arenas.default<br />
GroupManager: -mobarena.arenas.default<br />
zPermissions: mobarena.arenas.default: false<br />
<br />
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.<br />
<br />
Still confused? Check the sample setup at the bottom of the page!<br />
<br />
==职业权限==<br />
<br />
Did you read the note at the top? If not, read it before you continue.<br />
<br />
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.<br />
<br />
bPermissions: ^mobarena.classes.knight<br />
GroupManager: -mobarena.classes.knight<br />
zPermissions: mobarena.classes.knight: false<br />
<br />
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.<br />
<br />
As with arenas, I recommend letting everyone enjoy all the classes, unless you have a special reason not to.<br />
<br />
Still confused? Check the sample setup at the bottom of the page!<br />
<br />
==命令权限==<br />
<br />
Did you read the note at the top? If not, read it before you continue.<br />
<br />
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!<br />
<br />
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.<br />
<br />
mobarena.use.join<br />
mobarena.use.leave<br />
mobarena.use.spec<br />
mobarena.use.arenalist<br />
mobarena.use.playerlist<br />
mobarena.use.notready<br />
mobarena.use.class<br />
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.<br />
<br />
mobarena.admin.enable<br />
mobarena.admin.kick<br />
mobarena.admin.restore<br />
mobarena.admin.force<br />
mobarena.admin.teleport<br />
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.<br />
<br />
mobarena.setup.config<br />
mobarena.setup.setup<br />
mobarena.setup.setting<br />
mobarena.setup.addarena<br />
mobarena.setup.removearena<br />
mobarena.setup.editarena<br />
mobarena.setup.spawnpoints<br />
mobarena.setup.containers<br />
mobarena.setup.checkdata<br />
mobarena.setup.checkspawns<br />
mobarena.setup.classchest<br />
mobarena.setup.classes<br />
mobarena.setup.leaderboards<br />
mobarena.setup.autogenerate<br />
mobarena.setup.autodegenerate<br />
Sample setup<br />
<br />
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...<br />
<br />
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:<br />
<br />
default-aux: <-- This is the auxiliary group that is to<br />
permissions: be inherited by the default group and<br />
- essentials.balance the donor group. It is not used for<br />
- essentials.pay anything else.<br />
- essentials.sell<br />
<br />
default: <-- This is the default group. It inherits<br />
inherits: default-aux from default-aux, but also revokes the<br />
permissions: permission for the special class.<br />
- -mobarena.classes.diamondknight<br />
<br />
donor: <-- This is the donor group, which also<br />
inherits: default-aux inherits from default-aux, but it<br />
permissions: does not revoke any class permissions,<br />
- essentials.balance.others which means it has access to all of<br />
- essentials.kit them by default.<br />
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.<br />
<br />
=物品语法（Item Syntax待搬运）=<br />
An Overview<br />
<br />
Items in MobArena follow a very specific syntax that you must obey, or you will experience missing items or errors. Be attentive to the details, because if you aren't, there will be consequences.<br />
<br />
MobArena allows these three different ways of defining items:<br />
<br />
Single: [<id>|<name>]<br />
Multiple: [<id>|<name>]:<amount><br />
Sub-types: [<id>|<name>]:<data>:<amount><br />
Confusing? Let's break them down one by one.<br />
<br />
===1. Single Items===<br />
<br />
[<id>|<name>]<br />
This means you can use either the item ID (<id>) or the item name (<name>), both as defined in the Material enum of the Bukkit API (the IDs are the numbers in parentheses). The item names are case-insensitive.<br />
<br />
Make sure to read the important note on item IDs!<br />
<br />
Examples: diamond_sword, stone, 42 (iron block), 322 (snowball)<br />
<br />
===2. Multiple Items===<br />
<br />
[<id>|<name>]:<amount><br />
This way, you append an <amount> to the item, specifying how many of the given item you want. This is useful for giving out stuff like arrows or potions that you generally want to give more than one of.<br />
<br />
Note that if you use this syntax, it is indeed the amount you specify, not the item sub-type. We go over sub-types in the next section.<br />
<br />
Make sure to read the important note on item IDs!<br />
<br />
Examples: arrow:64, grilled_pork:4, 46:10 (10x TNT), 142:5 (5x potato)<br />
<br />
===3. Item Sub-Types (potions, wool, dyes etc.)===<br />
<br />
[<id>|<name>]:<data>:<amount><br />
This way, you append BOTH a <data> value (the sub-type) and an <amount>, regardless of how many of the given item you want. This syntax is mostly used with potions, which have special sub-type values in the 8000's and 16000's. Check out this page for the potion sub-types.<br />
<br />
For wool and dyes (ink sacks), you don't have to use the numeric data value. Instead, you can use the color names as defined in the DyeColor enum of the Bukkit API.<br />
<br />
Make sure to read the important note on item IDs!<br />
<br />
Examples: wool:blue:1 (one blue wool), ink_sack:brown:10 (ten cocoa beans), potion:8201:1 (one strength potion), 373:8197:2 (two health potions)<br />
<br />
An important note on using item IDs<br />
<br />
If you choose to use item IDs, there is a catch. If an item is alone in its node, it MUST be enclosed in apostrophes, or YAML will crap itself. For example, if you decide to have a Barbarian class that only has a pair of lederhosen as armor, and nothing put a couple of health potions, you need to do it like this:<br />
<br />
classes:<br />
Barbarian:<br />
items: '373:8197:2'<br />
armor: '300'<br />
In other words, you have to put '300' in the armor-node, not just 300, and you have to put '373:8197:2' in the items-node, not just 373:8197:2. This requirement is removed if you use the item names instead, or if you add enchantments to the given item.<br />
<br />
Enchantments<br />
<br />
Enchantments can be added to items by appending a space, followed by a semi-colon separated list of pairs <eid>:<level>, where <eid> is an enchantment ID as defined by the Enchantment Wrappers in the Bukkit API (the numbers in the parentheses at the end of each line), i.e.:<br />
<br />
<item> <eid>:<level>;<eid>:<level>;...<br />
The <item> is any item following the normal item syntax as described above. Here is an example:<br />
<br />
diamond_sword 16:2;19:5<br />
This line gives a diamond sword with sharpness (ID 16) level 2, and knockback (ID 19) level 5.<br />
<br />
Economy Money<br />
<br />
$<amount><br />
MobArena supports entry fees and rewards in the form of money from economy plugins. This feature requires Vault. The format quite simply means that you type in a dollar sign followed by a valid monetary value.<br />
<br />
Examples: $1, $5, $3.14 (v0.96+), $0.99 (v0.96+)<br />
<br />
=职业箱子=<br />
==About Class Chests==<br />
<br />
If some of your favorite items aren't supported by MobArena's internal item parser, or if you just want to be able to configure your class items from in-game, the class chests may be what you're looking for!<br />
<br />
Note: The Class Chests will only work for arenas with use-class-chests: true, and the classes MUST exist in the config-file for MobArena to recognize them, however the items and armor lists can be empty.<br />
<br />
The idea behind the class chests is to simply place some chests below the corresponding class signs in the lobby, and fill them with whatever items you want the given class to have. When the players activate the class signs, the contents of the chests are copied to the player inventory. This suggests a type of "control room" setup, where an admin-only access room below the lobby contains the chests, allowing admins to warp down there and change the contents of the chests.<br />
<br />
Lobby and Control Room（[https://github.com/garbagemule/MobArena/wiki/img/1.png]请翻译者添加）<br />
<br />
For easier access and modification of the class chests, omitting the control room from the arena or lobby region may prove useful. Otherwise, arenas may have to be temporarily disabled or put into edit mode to allow warping to and changing the contents of the chests.<br />
<br />
The class chests can be located up to 6 blocks below the sign itself or below the block right behind the sign (for wall signs, this would be the block the sign is attached to). The chest may also be in the block directly behind the sign itself - this is safe, because MobArena prevents players in the lobby from opening inventories, so if your lobby is in a tight spot, this might be the better option.<br />
<br />
Multiple sign rows: It is possible to have two rows of class signs in the lobby and still use this feature. Simply place the class chest for the sign of the bottom row exactly at the 6-block limit, and the class chest for the sign of the top row one block up and behind the other chest (in a stair-like fashion). The blocks are searched in a vertical/pillar-like fashion, which is the reason this works.<br />
<br />
Chests Below<br />
<br />
To get auto-equipped armor from the class chests, place the armor pieces in the last four slots of the third row in the chest. MobArena will check these four slots, and if any of them are armor pieces, they will be equipped. Note that the item placed in the very last slot (bottom right), will always be equipped as a helmet (this allows wool blocks, pumpkins, etc. to be used as helmets). The order of the other three slots doesn't matter.<br />
<br />
Armor Slots https://github.com/garbagemule/MobArena/wiki/img/3.png<br />
<br />
The class chests are the best way to add items that are not currently supported by the MobArena item parser. This is because the class chests simply copy the contents of the chests to the player inventories, thus making any items supported by Bukkit supported by MobArena.<br />
<br />
Dyed Armor https://github.com/garbagemule/MobArena/wiki/img/4.png<br />
<br />
==Linked Class Chests==<br />
<br />
If per-arena class chest setups is too troublesome (e.g. if you have many arenas), if you don't need per-arena setups, or if you simply want a single, global class chest for each class, linked class chests are what you're looking for.<br />
<br />
When you link a chest to a class, MobArena will always copy the contents of that chest to the player's inventory, when they pick the given class, regardless of any local class chests (note that the arena must still have use-class-chests: true).<br />
<br />
To link a chest to a class, simply look at the chest and type /ma classchest <class>, and you're done! The linked class chests may exist in any world, but remember that there can only be one class chest per class, and that local class chests will be ignored!<br />
<br />
To unlink a class chest, you will have to open the config-file and remove the classchest node from the given class.<br />
<br />
=怪物波设置（Formulas待搬运）=<br />
=怪物种类（Monster types待搬运）=<br />
以上内容搬运自英文wiki[https://github.com/garbagemule/MobArena/wiki]</div>Zhwhttps://mineplugin.org/index.php?title=MobArena&diff=1167MobArena2015-07-28T10:35:51Z<p>Zhw：/* 物品语法（Item Syntax待搬运） */</p>
<hr />
<div>{{待搬运}}<br />
{{Bukkit Plugin Infobox<br />
|版本=v0.96.9<br />
|兼容服务端版本=1.8.1<br />
|网址=http://dev.bukkit.org/bukkit-plugins/mobarena/}}<br />
[[Category:娱乐]][[Category:机械]]<br />
=安装=<br />
安装MobArena其实很简单，只需以下四步:<br />
*关闭服务器<del>咳咳，当然是关你自己的服务器啦</del>.<br />
*从论坛主题或是Bukkit Dev站点的项目页下载jar文件.<br />
*将jar文件拖入服务端的plugins文件夹中.<br />
*重启服务端. <br />
之后，配置文件 (config.yml) 以及一个宣告文本(announcements.yml) 会自动创建在plugins/MobArena/路径下.<br />
文件结构如下:<br />
<br />
plugins/<br />
MobArena.jar<br />
MobArena/<br />
config.yml<br />
announcements.yml<br />
此时此刻, 或许你想直接开始设置竞技场, 但是你需要先看看配置文件，并把它配置成你喜欢的样子<del>就是说，还是根据情况配置一下吧</del>. 你可以在配置文件自定义MobArena的设置，职业，奖励，波数（怪物类型）<br />
<br />
=建立竞技场=<br />
==建造一个竞技场==<br />
完整的竞技场应该包含一个可以选择职业的准备区域，一个竞技场地以及观察点(离开点) <br />
下面是各个选项的讲解<br />
<br />
大厅：<br />
玩家加入游戏之前将会在大厅选择职业.一个建造好的游戏大厅会有每一个职业的选择牌子，玩家通过点击牌子可以获取一个职业, 还有一个铁块, 玩家可以通过点击铁块来表示他们已经准备好开始游戏.牌子必须在第一行写上职业的名字（区分大小写）,但是无论你在另外三行上写什么，都不会被怪物竞技场识别，你是不能写上 ,所以你不会得到确认的信息（如果有，那是另一个插件）<br />
<br />
竞技场地：<br />
这里是玩家和怪物搏斗的地方.竞技场地会有墙，可能会有一个屋顶 , 这样玩家和怪物就不能跑出去了. 这使得玩家们不会只是在竞技场外闲逛。.<br />
<br />
观察点: <br />
当玩家想要观看一场战斗时,他们可以使用/ma spec 命令来传送到竞技场的观察点. 这同样也是竞技场中玩家死去后会传送到的地方,前提是在配置文件中，把 spectate-after-death设置为ture. 这块区域要保证观看者不能走出去闲逛（进入竞技场地或者离远竞技场）因为在观看过程中，玩家是无敌的.<br />
<br />
离开点: <br />
在使用 /ma leave命令后,玩家和观察者会被传送到原来所在的地方,除非竞技场有一个离开点(只是可选). 使用离开点,可以准确控制玩家在游戏后去何处.<br />
<br />
关于区域，传送点等，<br />
<br />
当竞技场建好后，就是设置怪物竞技场的区域和传送点的时候了。在设置它们前，我们先来看看他们有什么作用.<br />
<br />
区域: <br />
一个竞技场需要一个竞技区域,然后还可以有一个准备区域，怪物竞技场会使用这些区域来确保玩家不会作弊（通过破坏竞技场来走出区域）,然后确保怪物竞技场所产生的怪物会在里面产生. 怪物竞技场非常排外（不要局外人）, 所以也最好把不想要的生物排除在外. 区域是通过区域工具来设置的.<br />
<br />
传送点: <br />
当玩家加入一个怪物竞技场的游戏时，他们会被传送到准备区域中的准备点来选择职业和准备开始游戏（通过点击铁块）.当每个人都准备好的时候，玩家会被传送到竞技场内的竞技场出生点。观察者会被传送到竞技场的观察点来进入观察区域,当游戏结束的时候，玩家和观察者会被传送到他们传送来之前的地方，或者去可选的离开点,传送点会用传送点工具来设置。.<br />
<br />
出生点: <br />
这里的出生点指的是怪物出生的地点.怪物竞技场只会在附近有玩家的出生点产出怪物（十五个方格的半径）.需要注意的是，怪物的数量不随着按照出生点的数量改变，只会因为在配置文件中波数的倍率改变和玩家的数量所改变.出生点可以通过出生点工具来设置。.<br />
<br />
容器: <br />
容器就是竞技场里的箱子，回收站等。 这些容器将会在一场游戏后重置其内部空间为初始值。只有被声明了的容器才会更新其存储空间，所以仅仅在竞技场里放一个箱子可不够 - 它还需要被用工具声明。<br />
<br />
==设置模式==<br />
我们能用配置模式来设置竞技场。 当我们进入配置模式时，物品栏将会被保存 并给我们一套金工具 （工具栏）， 每一个都有其独特作用。同时我们也可以飞行，使得我们在竞技场附近移动时更加快捷方便一些，最后，但不是绝对，我们不能够聊天或者使用普通命令如果在在配置模式下的话，因为配置模式和你建立起了独立会话（即你所发表的信息都是针对插件的。）<br />
<br />
进入设置模式的方法：输入/ma setup 竞技场名，值得提醒的是，如果服务器中只有一个竞技场，你不用输入竞技场的名字，如果竞技场没有设置完毕或者没有被创造，首先使用/ma addarena 竞技场名来创造它<br />
<br />
离开设置模式的方法：聊天框内输入done，注意不是命令，是聊天信息，没有斜杠<br />
<br />
另外，如果你刚安装怪物竞技场插件，会有一个预置的，名称为default竞技场存在于配置文件中，如果你想要一个不同的名字，你需要先创造一个新竞技场然后把原来的竞技场使用/ma delarena default来删除<br />
<br />
下面我们会提到在设置模式中有什么命令可以使用。<br />
<br />
==设置模式的命令==<br />
<br />
设置模式是一个独立，特殊的会话，这意味着插件会监控我们说的每一句话，使得插件的命令可以缩短，以致于设置过程没有特别麻烦。比如exp命令替代了/ma expandregion，并且还可以防止我们错误地使用了其他插件的命令<br />
<br />
下面是我们可以在设置模式中使用的命令，很多都十分浅显易懂（如果您懂英文的话。）使得您设置竞技场十分快速<br />
done<br />
离开设置模式<br />
别名: end stop done quit<br />
<br />
help<br />
显示帮助信息<br />
别名: ? h<br />
<br />
missing<br />
显示我们还没有设置好的区域（准备区诸如此类）<br />
这个命令在你不知道你已经设置了那些区域的时候十分有用<br />
别名: miss<br />
<br />
expand <region> <amount> <direction><br />
Expand a region by some amount in some direction.<br />
Valid regions: ar for the arena region, or lr for the lobby region<br />
Valid amounts: positive integers (whole numbers)<br />
Valid directions: up, down, or out<br />
Example: expand ar 5 up<br />
别名: exp<br />
<br />
show [<region>|<warp>|<point>]<br />
Show a region, warp, or point(s) as red wool blocks.<br />
Valid regions: ar for the arena region, or lr for the lobby region<br />
Valid warps: arena, lobby, spec, exit<br />
Valid points: spawns (or just sp) for spawnpoints, chests (or just c) for chests<br />
Example: show sp<br />
<br />
==设置时的工具==<br />
<br />
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.<br />
<br />
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.<br />
<br />
===区域工具===<br />
<br />
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.<br />
<br />
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.<br />
<br />
Left-click: Set the first point to be the location of the target block<br />
Right-click: Set the second point to be the location of the target block<br />
<br />
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.<br />
<br />
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.<br />
<br />
===玩家传送点工具===<br />
<br />
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.<br />
<br />
Left-click: Set the currently selected warp on top of the target block<br />
Right-click: Cycle between available warps<br />
<br />
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.<br />
<br />
Note: The arena, lobby, and spectator warps are all required. The exit warp is optional.<br />
<br />
===怪物产生点工具===<br />
<br />
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.<br />
<br />
Left-click: Add a spawnpoint on top of the target block<br />
Right-click: Remove the spawnpoint on top of the target block (if the spawnpoint exists)<br />
<br />
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.<br />
<br />
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.<br />
<br />
===容器工具===<br />
<br />
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.<br />
<br />
Left-click: Register the clicked container (if it wasn't registered)<br />
Right-click: Unregister the clicked container (if it was registered)<br />
<br />
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.<br />
<br />
=命令=<br />
==玩家命令==<br />
<br />
这些指令能够给所有玩家使用. 它们包括了加入, 离开, 旁观和列出所有竞技场(可用或不可用)<br />
<br />
<br />
/ma join (<竞技场>) or /ma j (<竞技场>) - 加入指定名称的竞技场.<br />
/ma leave or /ma l - 离开竞技场或是离开旁观者模式.<br />
/ma notready - 获取所有未准备的玩家.<br />
/ma spec (<竞技场>) or /ma s (<竞技场>) - 以旁观者模式加入指定名称竞技场.<br />
/ma arenas - 获取所有竞技场的名字, 若是绿色则已启用, 灰色则未启用.<br />
/ma players - 获取当前所有竞技场的所有玩家.<br />
/ma players <竞技场> - 获取指定竞技场的所有玩家.<br />
/ma class <职业> - 如果你在大厅里, 是应直接用指令而不是透过牌子互动选择职业.<br />
<br />
==管理员指令==<br />
<br />
只有后台或者服务器op能使用下面这些指令. 这里包括了开始或是停止竞技场, 启用或是卸载竞技场甚至包含了MobArena的所有管理.<br />
<br />
/ma enable - 启用MobArena插件.<br />
/ma disable - 卸载MobArena插件.<br />
/ma enable <竞技场> - 启用指定名字的竞技场.<br />
/ma disable <竞技场> - 关闭指定名字的竞技场.<br />
/ma force end - 停止所有竞技场的运作.<br />
/ma force end <竞技场> - 停止指定名称竞技场的运作及使该竞技场的所有玩家离开. <br />
/ma force start <竞技场> - 开始运作一个指定名称的竞技场以及请出该竞技场内未准备的玩家.<br />
/ma notready <竞技场> - 获取该竞技场内所有未准备的玩家.<br />
/ma restore <玩家> - 在可能的情况下恢复指定玩家背包.<br />
/ma config reload - 重载config配置文件夹.<br />
==建设指令==<br />
<br />
只有op (以及某些合理的指令能在后台) 使用这些指令. 它们包括了设置竞技场传送点, 竞技场出生点以及竞技场范围.<br />
<br />
/ma setup <竞技场> - 进入建设指定名称的竞技场模式.<br />
/ma addarena <竞技场> - 建立一个新的竞技场节点于当前所在世界.<br />
/ma delarena <竞技场> - 删除指定名称的竞技场.<br />
/ma editarena <竞技场> - 开启或关闭指定竞技场修改模式.<br />
/ma editarena <竞技场> [true|false] - 开启 (true) 或关闭 (false) 指定竞技场的修改模式.<br />
/ma setting <竞技场> - 列出所有指定竞技场的设置项.<br />
/ma setting <竞技场> <设置项> - 查询当前指定设置项的值于指定的竞技场.<br />
/ma setting <竞技场> <设置项> <值> - 设置指定竞技场中指定设置项的指定值.<br />
/ma checkspawns - 显示竞技场出生点 (在你当前的竞技场下) 是使用红色羊毛覆盖的范围在当前你当前的位置上. 这个指令同时也能查询在这个范围内不同的点是否被出生点覆盖着.<br />
/ma classchest <职业> - 当正在查询箱子, 使指定的职业与这个箱子建立连接. 连接一个职业箱子意味着当MobArena连接建立后, 将同时复制于职业箱子内的物品, 而不是于竞技场大厅内的任何职业箱子. 当你建立一个职业箱子网络时它能带给你便利.<br />
/ma auto-generate <竞技场> - 自动生成一个指定名称的竞技场. 这个竞技场只会生成于玩家所站的位置下方.<br />
/ma auto-degenerate <竞技场> - 自动停止生成竞技场, 能基于自动生成器下有效地恢复, 当这是一个 "bulldozed" 补丁.<br />
<br />
=权限=<br />
几乎全部的权限插件是'''不需要'''MobArena插件作为前置而能够单独运行的, 但若果你想要更多额外的控制功能, 这里提供了很多不同类型的权限节点哦喵~<br />
== 节点 ==<br />
你能够在安装MobArena插件后使用这些权限节点<br />
<br />
提示: MobArena这个插件提供了很多人性化的默认设定, 所有玩家能够使用所有竞技场及职业, 还有的是OP默认能够使用所有管理员以及建设指令. 除非你想要禁止一些组别进入特定的竞技场或是职业<br />
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!<br />
<br />
==竞技场权限==<br />
<br />
Did you read the note at the top? If not, read it before you continue.<br />
<br />
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.<br />
<br />
bPermissions: ^mobarena.arenas.default<br />
GroupManager: -mobarena.arenas.default<br />
zPermissions: mobarena.arenas.default: false<br />
<br />
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.<br />
<br />
Still confused? Check the sample setup at the bottom of the page!<br />
<br />
==职业权限==<br />
<br />
Did you read the note at the top? If not, read it before you continue.<br />
<br />
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.<br />
<br />
bPermissions: ^mobarena.classes.knight<br />
GroupManager: -mobarena.classes.knight<br />
zPermissions: mobarena.classes.knight: false<br />
<br />
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.<br />
<br />
As with arenas, I recommend letting everyone enjoy all the classes, unless you have a special reason not to.<br />
<br />
Still confused? Check the sample setup at the bottom of the page!<br />
<br />
==命令权限==<br />
<br />
Did you read the note at the top? If not, read it before you continue.<br />
<br />
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!<br />
<br />
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.<br />
<br />
mobarena.use.join<br />
mobarena.use.leave<br />
mobarena.use.spec<br />
mobarena.use.arenalist<br />
mobarena.use.playerlist<br />
mobarena.use.notready<br />
mobarena.use.class<br />
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.<br />
<br />
mobarena.admin.enable<br />
mobarena.admin.kick<br />
mobarena.admin.restore<br />
mobarena.admin.force<br />
mobarena.admin.teleport<br />
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.<br />
<br />
mobarena.setup.config<br />
mobarena.setup.setup<br />
mobarena.setup.setting<br />
mobarena.setup.addarena<br />
mobarena.setup.removearena<br />
mobarena.setup.editarena<br />
mobarena.setup.spawnpoints<br />
mobarena.setup.containers<br />
mobarena.setup.checkdata<br />
mobarena.setup.checkspawns<br />
mobarena.setup.classchest<br />
mobarena.setup.classes<br />
mobarena.setup.leaderboards<br />
mobarena.setup.autogenerate<br />
mobarena.setup.autodegenerate<br />
Sample setup<br />
<br />
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...<br />
<br />
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:<br />
<br />
default-aux: <-- This is the auxiliary group that is to<br />
permissions: be inherited by the default group and<br />
- essentials.balance the donor group. It is not used for<br />
- essentials.pay anything else.<br />
- essentials.sell<br />
<br />
default: <-- This is the default group. It inherits<br />
inherits: default-aux from default-aux, but also revokes the<br />
permissions: permission for the special class.<br />
- -mobarena.classes.diamondknight<br />
<br />
donor: <-- This is the donor group, which also<br />
inherits: default-aux inherits from default-aux, but it<br />
permissions: does not revoke any class permissions,<br />
- essentials.balance.others which means it has access to all of<br />
- essentials.kit them by default.<br />
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.<br />
<br />
=物品语法（Item Syntax待搬运）=<br />
An Overview<br />
<br />
Items in MobArena follow a very specific syntax that you must obey, or you will experience missing items or errors. Be attentive to the details, because if you aren't, there will be consequences.<br />
<br />
MobArena allows these three different ways of defining items:<br />
<br />
Single: [<id>|<name>]<br />
Multiple: [<id>|<name>]:<amount><br />
Sub-types: [<id>|<name>]:<data>:<amount><br />
Confusing? Let's break them down one by one.<br />
<br />
===1. Single Items===<br />
<br />
[<id>|<name>]<br />
This means you can use either the item ID (<id>) or the item name (<name>), both as defined in the Material enum of the Bukkit API (the IDs are the numbers in parentheses). The item names are case-insensitive.<br />
<br />
Make sure to read the important note on item IDs!<br />
<br />
Examples: diamond_sword, stone, 42 (iron block), 322 (snowball)<br />
<br />
===2. Multiple Items===<br />
<br />
[<id>|<name>]:<amount><br />
This way, you append an <amount> to the item, specifying how many of the given item you want. This is useful for giving out stuff like arrows or potions that you generally want to give more than one of.<br />
<br />
Note that if you use this syntax, it is indeed the amount you specify, not the item sub-type. We go over sub-types in the next section.<br />
<br />
Make sure to read the important note on item IDs!<br />
<br />
Examples: arrow:64, grilled_pork:4, 46:10 (10x TNT), 142:5 (5x potato)<br />
<br />
===3. Item Sub-Types (potions, wool, dyes etc.)===<br />
<br />
[<id>|<name>]:<data>:<amount><br />
This way, you append BOTH a <data> value (the sub-type) and an <amount>, regardless of how many of the given item you want. This syntax is mostly used with potions, which have special sub-type values in the 8000's and 16000's. Check out this page for the potion sub-types.<br />
<br />
For wool and dyes (ink sacks), you don't have to use the numeric data value. Instead, you can use the color names as defined in the DyeColor enum of the Bukkit API.<br />
<br />
Make sure to read the important note on item IDs!<br />
<br />
Examples: wool:blue:1 (one blue wool), ink_sack:brown:10 (ten cocoa beans), potion:8201:1 (one strength potion), 373:8197:2 (two health potions)<br />
<br />
An important note on using item IDs<br />
<br />
If you choose to use item IDs, there is a catch. If an item is alone in its node, it MUST be enclosed in apostrophes, or YAML will crap itself. For example, if you decide to have a Barbarian class that only has a pair of lederhosen as armor, and nothing put a couple of health potions, you need to do it like this:<br />
<br />
classes:<br />
Barbarian:<br />
items: '373:8197:2'<br />
armor: '300'<br />
In other words, you have to put '300' in the armor-node, not just 300, and you have to put '373:8197:2' in the items-node, not just 373:8197:2. This requirement is removed if you use the item names instead, or if you add enchantments to the given item.<br />
<br />
Enchantments<br />
<br />
Enchantments can be added to items by appending a space, followed by a semi-colon separated list of pairs <eid>:<level>, where <eid> is an enchantment ID as defined by the Enchantment Wrappers in the Bukkit API (the numbers in the parentheses at the end of each line), i.e.:<br />
<br />
<item> <eid>:<level>;<eid>:<level>;...<br />
The <item> is any item following the normal item syntax as described above. Here is an example:<br />
<br />
diamond_sword 16:2;19:5<br />
This line gives a diamond sword with sharpness (ID 16) level 2, and knockback (ID 19) level 5.<br />
<br />
Economy Money<br />
<br />
$<amount><br />
MobArena supports entry fees and rewards in the form of money from economy plugins. This feature requires Vault. The format quite simply means that you type in a dollar sign followed by a valid monetary value.<br />
<br />
Examples: $1, $5, $3.14 (v0.96+), $0.99 (v0.96+)<br />
<br />
=职业箱子（Class Chests待搬运｝=<br />
=怪物波设置（Formulas待搬运）=<br />
=怪物种类（Monster types待搬运）=<br />
以上内容搬运自英文wiki[https://github.com/garbagemule/MobArena/wiki]</div>Zhwhttps://mineplugin.org/index.php?title=PermissionsEX&diff=1114PermissionsEX2015-07-20T13:52:07Z<p>Zhw：/* Modifyworld */</p>
<hr />
<div>{{待翻译}}<br />
{{Bukkit Plugin Infobox<br />
|插件名=PermissonEX(PEX)<br />
|版本=v1.23.1<br />
|前置插件=无<br />
|兼容服务端版本=1.8.1<br />
|網址=http://dev.bukkit.org/bukkit-plugins/permissionsex/<br />
}}<br />
=概述=<br />
==介绍==<br />
PermissionsEx (PEX) 是一个新的权限（组）, 基于权限组和它的所有功能. 但是PEX插件能做到更多！ 它提供了各式各样有力的后台和游戏内管理方式, 很好的限制了一些玩家对于服务器的修改.<br />
<br />
==现有特性==<br />
版本V1.21开始支持UUID<br />
不同的存储方式。目前的存储方式有:文本存储(YAML),数据库存储(MySQL，SQLite)。当然,也支持你自己添加！<br />
YAML存储方式,对于新手,最容易配置的方式,所有玩家的信息都存储在 permission.yml 文件里面,缺点:后期读取可能出现卡顿。<br />
SQL存储方式,对于有一定基础的人,推荐此方式，目前支持MySQL和SQLite，其他的数据库(如Postgre)也是可以的。PEX会自动创建数据库的表单。这就说明了,你只需要设置好PEX如何连接到数据库，剩余的你就只需要看着PEX自己完成了。<br />
简明的构架和API接口，如果你对编程有一定了解，那么你可以改变很多。<br />
全面的指令，你可以在游戏里/控制台，做到你想做的任何事情。指令列表看下文。<br />
多世界 - 你可以设置一个玩家在某个世界的单独权限，比如在世界A不能破坏，在世界B不能拾取等等。(设置个别方块等权限,见下文)<br />
权限组的继承，用户可以继承组的权限,组也可以继承组的权限，并且可以选择继承他们的权限、前缀、后缀。<br />
权限的表达方式，这说明,如果你习惯于GroupManager,你也不用担心更换权限插件之后的不习惯。例子: - essentials.fly 这个权限就是允许玩家使用/fly指令<br />
多世界权限继承，你可以继承不同世界的权限。也可以在不同世界继承不同的权限。<br />
良好的优化，当你拥有大量用户的时候,你会发现没有延迟！<br />
排行榜,你可以设置权限组的排列顺序<br />
计时权限!你可以使用指令给玩家添加一个时限权限！注意:当服务端重启,或者崩溃将会失效。<br />
V1.21.1版本开始 PEX支持自动更新,不过并不是跨阶段的更新,只支持BUG修复等更新,防止出现大更新,没有备份而导致文件丢失(V1.21.1→V1.21.2 而不是 V1.21.1 →V1.22.1),当然你也可以在config.yml文件中关闭更新。<br />
Bukkit权限的兼容<br />
禁用错误报告,在插件文件夹目录下创建一个文件,名为'report-disable'。<br />
<br />
=进阶权限管理=<br />
===权限的继承 ===<br />
<br />
很多服务器配置了多个权限组, 添加权限要各组分别添加. 权限继承可以服务器管理最大限度的减少每一组重复的节点数量.<br />
<br />
这里假定您已经完成了基本教程，如还没有，请看基础权限知识，不然的话不能保证您能明白这里的每一步.<br />
<br />
实际上，使用了基本教程中的案例，你会发现Member, VIP 和Moderator组都有共同的节点 , modifyworld.* .这里不需要使用继承.<br />
<br />
===权限继承规则===<br />
<br />
当继承需要处理,PEX会遵循下列规则:<br />
<br />
对玩家的设置(前缀,后缀,权限节点,etc.)拥有比组更高的优先权.<br />
设置给一个组的玩家权限在当玩家个人设置生效前被组中任意玩家继承.<br />
Permission nodes are evaluated in order of the inheritance tree (see The Inheritance Tree for details)<br />
A group set to inherit from another group will inherit everything (this includes other inheritance directives!) from the source group, not just permissions. For example, if you have group B inheriting from group A, and group A is set to inherit from group B, PEX will follow the inheritance chain on group A, which is set to inherit from B, which inherits from A, and so on. Watch for this, it will cause a loop that will crash PEX.<br />
<br />
===Converting Existing Groups To Use Inheritance ===<br />
<br />
Converting an existing group to use inheritance is easy with the pex group parents set command.<br />
<br />
Convert the VIP and Moderator groups<br />
<br />
pex group VIP parents set Member<br />
pex group Moderator parents set VIP<br />
Remove the redundant nodes<br />
<br />
pex group VIP remove modifyworld.*<br />
pex group Moderator remove modifyworld.*<br />
At this point, the VIP and Moderator groups still have the same access as before as the VIP group inherits the modifyworld.* node from the Member group while adding the -modifyworld.mobtarget.monster.creeper node, and the Moderator group inherits it's nodes from the VIP group (including the nodes it inherited from the Member group) while adding the -modifyworld.mobtarget.* node.<br />
<br />
The relevant portion of the permissions file now looks like this:<br />
<br />
Member:<br />
prefix: '&0(&8M&7ember&0)&7 '<br />
permissions:<br />
- modifyworld.*<br />
options:<br />
rank: '900'<br />
VIP:<br />
prefix: '&0(&eVIP&0)&7 '<br />
inheritance:<br />
- Member<br />
permissions:<br />
- -modifyworld.mobtarget.monster.creeper<br />
options:<br />
rank: '800'<br />
Moderator:<br />
prefix: '&0(&1Moderator&0)&7 '<br />
inheritance:<br />
- VIP<br />
permissions:<br />
- -modifyworld.mobtarget.*<br />
options:<br />
rank: '100'<br />
It's not a large reduction with this example, but if a server has multiple groups with a dozen or more nodes in common with the groups, the file size savings can be considerable.<br />
<br />
This inheritance can also be applied at a world level for servers with multiple worlds. See the Multiworld inheritance section page for more.<br />
<br />
===The Inheritance Tree===<br />
<br />
(Thanks goes to aviator14 for use of these nodes)<br />
<br />
Due to the way PEX deals with file backends, it may help to view inheritance as a tree. For example, we have the following permission nodes:<br />
<br />
Guest:<br />
prefix: '&7'<br />
default: true<br />
permissions: []<br />
Player:<br />
prefix: '&f'<br />
default: false<br />
permissions:<br />
- generic.user.permissions<br />
- -multiverse.access.world_creative<br />
- -multiverse.portal.access.end<br />
- multiverse.access.*<br />
- multiverse.core.coord<br />
- multiverse.core.info<br />
- multiverse.core.list.who<br />
- multiverse.portal.access.*<br />
inheritance:<br />
- Guest<br />
Donator:<br />
prefix: '&5'<br />
permissions:<br />
- generic.donor.permissions<br />
- multiverse.access.world_creative<br />
inheritance:<br />
- Player<br />
Supporter:<br />
prefix: '&6'<br />
permissions:<br />
- more.generic.donor.permissons<br />
- multiverse.portal.access.end<br />
inheritance:<br />
- Donator<br />
Moderator:<br />
prefix: '&d'<br />
permissions:<br />
- generic.moderator.permissions<br />
inheritance:<br />
- Player<br />
ModD:<br />
prefix: '&d'<br />
permissions: []<br />
inheritance:<br />
- Moderator<br />
- Donator<br />
ModS:<br />
prefix: '&d'<br />
permissions: []<br />
inheritance:<br />
- Moderator<br />
- Supporter<br />
The original forum post these nodes came from was asking why the ModD group was not getting the multiverse.portal.access.end node it was inheriting from the Donator group. Well, the reason for this is because of the way PEX evaluates nodes in a file backend and the inheritance tree.<br />
<br />
An abbreviated version of the tree for the ModD group is this:<br />
<br />
ModD permissions (none)<br />
Moderator (generic.moderator.permissions) which inherits from Player<br />
Player (which has -multiverse.access.world_creative among others) and inherits from Guest<br />
Guest (no permissions)<br />
Donator (generic.donor.permissions, multiverse portal access node) which inherits from Player<br />
Player (which has -multiverse.access.world_creative among others) and inherits from Guest<br />
Guest (no permissions)<br />
In this case, the issue was due to the Moderator tree being evaluated first, which finds the negation node for multiverse and stops looking. If the Donator tree was listed first (which was the suggested fix), PEX would follow that inheritance tree first, which has the multiverse permissions, and allow access to that node.<br />
<br />
===Regular Expressions (regex)===<br />
<br />
Regular Expressions, also known as regex or regexp, is a way to 'match' strings of text, such as particular characters, words, or patterns of characters. PEX supports a subset of regex in it's permission node checks.<br />
<br />
PEX supports open and closed parentheses ( ) for grouping, curly braces { } for pattern matching, a pipe | for "or", and a dash - for through (as in numbers 1 through 5).<br />
<br />
WARNING: If you have any nodes that use these characters then you MUST either put the line in quotes or escape with a backslash the character. If you do not, PEX may mistake the character as an attempt to use a regex, causing a Java error and rendering your permissions useless!<br />
<br />
To use it, place the conditions/keywords and/or id numbers in a group, separated by a pipe or a dash if wanting to cover multiple numbers in a sequence.<br />
<br />
If this is confusing, worry not. There is a reason why several technical book publishers sell books dedicated to regular expressions. Fortunately, for the purposes of PEX and permission nodes, it's much simpler to deal with, especially with examples of it in action.<br />
<br />
Assume that you have a group that you don't want opening the following:<br />
<br />
Dispensers ('dispenser', or 23)<br />
Chests ('chest', or 54)<br />
Furnaces ('furnace', or 61 unlit and 'burning_furnance', or 62 lit)<br />
Jukeboxes ('jukebox', or 84)<br />
Remember to check your use-material-names node setting.<br />
<br />
You could have a set of nodes like this:<br />
<br />
- -modifyworld.blocks.interact.dispenser<br />
- -modifyworld.blocks.interact.chest<br />
- -modifyworld.blocks.interact.furnace<br />
- -modifyworld.blocks.interact.burning_furnace<br />
- -modifyworld.blocks.interact.jukebox<br />
However, this is unnecessary. Using the regex support in PEX, you can combine the nodes into a single line: - -modifyworld.blocks.interact.(dispenser|chest|burning_furnace|furnace|jukebox) - -modifyworld.blocks.interact.(23|54|61|62|84) (for use-material-names: false)<br />
<br />
If you wanted to keep a group from destroying stone (1), grass (2), dirt (3), and cobblestone (4), you can use modifyworld.blocks.destroy.(1-4)<br />
<br />
You can also use 'or' on other parts of the node.<br />
<br />
Keeping with the previous example, adding the ability to place the blocks looks like modifyworld.blocks.(destroy|place).(1-4) Adding sand (12) to this example, you could use modifyworld.blocks.(destroy|place).(1-4|12)<br />
<br />
Adding this to a group, such as the default group, is as simple as using the pex group <group> add <node> command.<br />
<br />
pex group default add modifyworld.blocks.(destroy|place).(1-4|12)<br />
Any extra nodes can be removed with the pex group <group> remove <node> command. See Commands for more on the add/remove commands.<br />
<br />
For advanced users, users can place a $ character directly in front of the node (after any other flag characters) to prevent PEX from performing regex escaping of . and *, so that they behave as normal regex characters rather than their function as delimiters in permissions nodes (escaped by default for backwards compatibility and user sanity)<br />
<br />
As you can see, the ability to use regex in permissions can save a lot of typing.<br />
<br />
File Back-end Example<br />
<br />
In the interest of completeness, this is the full permissions file after the inheritance and regex commands listed above. This example assume use-material-names: false in your plugins/Modifyworld/config.yml file.<br />
<br />
groups:<br />
default:<br />
default: true<br />
options:<br />
rank: '1000'<br />
permissions:<br />
- modifyworld.chat<br />
- modifyworld.blocks.(destroy|place).(1-4|12)<br />
Member:<br />
prefix: '&0(&8M&7ember&0)&7 '<br />
permissions:<br />
- modifyworld.*<br />
options:<br />
rank: '900'<br />
VIP:<br />
prefix: '&0(&eVIP&0)&7 '<br />
inheritance:<br />
- Member<br />
permissions:<br />
- -modifyworld.mobtarget.monster.creeper<br />
options:<br />
rank: '800'<br />
Moderator:<br />
prefix: '&0(&1Moderator&0)&7 '<br />
inheritance:<br />
- VIP<br />
permissions:<br />
- -modifyworld.mobtarget.*<br />
options:<br />
rank: '100'<br />
Admins:<br />
prefix: '&0(&4Admins&0)&7 '<br />
permissions:<br />
- -modifyworld.mobtarget.*<br />
- modifyworld.*<br />
- permissions.*<br />
options:<br />
rank: '1'<br />
users:<br />
AnotherPlayer:<br />
group:<br />
- default<br />
YourPlayerName:<br />
group:<br />
- Admins<br />
===Multiworld===[[Multiworld]]<br />
<br />
Having several maps (or worlds) on a server is a common way to offer more than one game play experience. However, not all commands are suitable for all worlds. You wouldn't want a hardcore survival world to have access to the give command, but it may be perfectly fine, if not required, in a world intended for free building. Fortunately, limiting a permission node to a specific world is easy with PEX by specifying the world when adding the permission node.<br />
<br />
Assume the following server setup:<br />
<br />
A survival world with Nether and End worlds (named survival, survival_nether, and survival_the_end respectively)<br />
A free build world (named freebuild)<br />
A group (pvp) that has the ability to build in the survival world only (modifyworld.*)<br />
A group (build) that has the ability to build in the survival and free build world (modifyworld.*)<br />
See Modifyworld page for details on block placement permission nodes.<br />
<br />
The commands to set this up are:<br />
<br />
/pex group pvp add modifyworld.* survival (add build permissions to the survival world for the pvp group)<br />
/pex group build add modifyworld.* freebuild (add build permissions to the freebuild world for the build group)<br />
/pex group build parents set pvp (Set the build group to inherit the permission to build in the survival world)<br />
Keep in mind that if you edit/add the multiworld lines into the permissions file by hand, make sure the name you use matches the one used in the bukkit configs and what is on the server, capitalization matters here!<br />
<br />
The resulting permissions will look like this in the file back-end:<br />
<br />
groups:<br />
pvp:<br />
permissions:<br />
worlds:<br />
survival:<br />
permissions:<br />
- modifyworld.*<br />
build:<br />
inheritance:<br />
- pvp<br />
permissions:<br />
worlds:<br />
freebuild:<br />
permissions:<br />
- modifyworld.*<br />
===Multiworld inheritance===<br />
<br />
You may have noticed the flaw in this setup, which is neither group had permission to build in the Nether and End worlds. This can be corrected in two ways:<br />
<br />
Add the modifyworld.* node to each world individually<br />
Set up world-level inheritance using /pex world <world> inherit <parentWorlds> /pex world pvp_nether inherit pvp /pex world pvp_the_end inherit pvp<br />
These commands look like the following in the file back-end:<br />
<br />
worlds:<br />
pvp_nether:<br />
inheritance:<br />
- pvp<br />
pvp_the_end:<br />
inheritance:<br />
- pvp<br />
<br />
=Backends=<br />
原帖是这么说的<br />
PermissionsEx provides several backends to store permissions data. This page (will explain) explains them all.<br />
（PEX插件提供了一些用于保存权限数据的后台，这个页面会解释所有）<br />
但其实这个页面只有这一句话（或许是服务器问题）<br />
所以请等待更新。<br />
<br />
=基础的权限设定=<br />
==权限节点的基本添加和否定 == <br />
PEX插件有一个普遍原则，就是权限运行命令是不允许的，除非这个权限节点是具体列出的. 对于那些可以被默认（default）操作的事件和命令, PEX插件可以拒绝访问那些被否定的节点.<br />
<br />
使用一个可以拒绝访问节点就像用 pex group <group> add <node>（最基本的权限给予命令） 命令那样简单. 使用同样的命令，只在权限节点前加一个负号（-）即可.<br />
<br />
举个例子 /give 和 /plugins 命令是水桶客户端的一部分（基本命令）<br />
<br />
/give 命令有一个权限节点 command.give 这个命令一般限制在ops.txt列出的人使用（管理员命令）<br />
/plugins 命令也有个权限节点 command.plugins 它可以被服务器中任何人使用。<br />
我们可以试试对于某个权限组增加和否定这两个节点:<br />
<br />
如果允许某个权限组使用/give, 就可以输入命令 pex group 组别名 add bukkit.command.give<br />
不允许某个权限组使用 /plugins, 这时候的命令就为 pex group 组别名 add -bukkit.command.plugins<br />
<br />
===重要的关于*的信息 ===<br />
PEX插件允许使用XXX*来给予XXX下的所有的分权限节点，但是呢，在使用这个前，''你必须要明白它怎么工作以及会造成什么效果''。一开始浏览的时候，这看上去很简单，给一个权限组“*”使它可以访问所有的权限节点，但是这也可能会导致你给了你不想要给这个权限组的权限。例如，在插件VanishNoPacket（简称VNP）中，它提供了一个权限vanish.silentjoin，使得所有的用户在登入时都不会显示加入公告，这是大多数服务器主人都不想要的效果。实际上这也可以用否定节点来简单解决（否定节点优先），任何给默认组使用的权限节点都能被否定以“关闭功能”<br />
<br />
===重要的后台文件 === <br />
如果你要在后台修改编辑权限的话，请阅读并遵守以下规则:<br />
权限必须以一个空格或者负号开始<br />
- modifyworld.chat 和 - -modifyworld.mobtarget.*是在后台文件中有效的（格式正确）。<br />
modifyworld.chat 和 -modifyworld.mobtarget.* 在后台文件中无效（格式不正确，无空格或负号）。<br />
所有在YAML文件中的格式规则在PEX插件基本文件中必须被遵守，错误的文件会使得PEX插件无法启动，然后把log文件塞满错误信息。<br />
PEX插件用自上而下的方式来检查用户和组别的权限节点，就像网络防火墙一样，如果它找到了一个与它想找的匹配的节点，它就会停止寻找，这就意味着在现实中，如果一个权限给了主要组别和它所有的子组别，它在看到允许的权限后就会停止寻找而忽略否定节点。<br />
我们举个错误的例子<br />
<br />
default:<br />
options:<br />
default: true<br />
permissions:<br />
- modifyworld.*<br />
- -modifyworld.blocks.interact.23<br />
用这样的权限节点文件，如果一个玩家想要打开一个发射器（ID 23），它第一个会匹配到modifyworld.*节点然后停止，以至于允许玩家打开！（实际上第二个权限节点是不允许这样的事情发生的。<br />
<br />
不过，如果把这两行互换，-modifyworld.blocks.interact.23在modifyworld.*之前，玩家会被拒绝访问发射器（插件先检测到-modifyworld.blocks.interact.23节点）如果一个玩家想要打开一个熔炉（ID 61）插件就会检测到modifyworld.*节点，然后认为是modifyworld.blocks.interact.61节点，使得玩家可以打开。<br />
<br />
==上机操作==<br />
<br />
先来试试基本的权限指令和插件基本功能（以下作为教程实例并且推荐各服务器使用。）<br />
创建五个组别个组别：Default，Member，VIP,Mod,Admin。<br />
"Default" 可以聊天但是不可以改动任何东西，没有称号<br />
"Member"信任的玩家组别，可以改动世界，拥有称号 ("&0(&8M&7ember&0)&7 ")<br />
"VIP" 可以改动世界还可以不受到苦力怕的烦恼（这个VIP棒）！ 并且拥有称号"&0(&eVIP&0)&7 ".<br />
A "Mod" 可以不受到任何怪物的困扰（万岁！）.<br />
An "Admin" (管理员) 是超级用户，可以使用这个插件的所有功能并且拥有炫酷的称号比如 "&0(&4Admin&0)&7 ".<br />
可选: 去除 modifyworld.* 权限从 "Default" 权限组中<br />
可选: 添加 modifyworld.chat 权限到 "Default" 权限组里<br />
是时候测试环境了<br />
<br />
===准备===<br />
安装PEX插件（放在插件目录下）<br />
<br />
开启服务器.<br />
<br />
打开浏览器控制台（租借，后台服务器的话）<br />
<br />
在浏览器中打开PEX插件的配置文件<br />
<br />
<br />
===开始基础及基本权限 === <br />
这些命令必须在控制台输入<br />
<br />
创建一个Admin权限组（pex group admin create命令）<br />
<br />
把 permissions.* 权限加入到组别中（pex group Admin add pressions.*命令）<br />
把你自己加入组中 （pex user 你的游戏名 group set Admin）, 其中你的游戏名是你在游戏内的ID名.<br />
可选的:给自己所有权限不管自己是不是在拥有permissions.*权限的权限组里<br />
<br />
====如果你不想（不能）在控制台输入====<br />
创建一个permissions.yml文件输入以下文字，并上传（放置）到PEX插件的目录，请确保你的格式是正确的！看上面的YAML后台信息的帮助。<br />
<br />
groups:<br />
Default:<br />
options:<br />
default: true<br />
permissions:<br />
<br />
modifyworld.* Admin: options: prefix: '&0(&4Admin&0)&7 ' permissions:<br />
permissions.* users:你的用户名: group:<br />
Admin permissions:<br />
permissions.*<br />
是时候创建其他组别了<br />
<br />
===创建其他组别: Member, VIP, Mod ===<br />
<br />
使用这个命令创建Member组 /pex group Member create<br />
使用这个命令创建VIP组 /pex group VIP create<br />
使用这个命令创建Mod组 /pex group Mod create<br />
接下来我们要标注这几个组别的阶级使得符合这样的顺序 Member -> VIP -> Mod -> Admin.看阶级页面以知道更多<br />
<br />
===设置阶级 ===<br />
输入以下命令<br />
/pex group default set rank 1000<br />
/pex group Member set rank 900<br />
/pex group VIP set rank 800<br />
/pex group Mod set rank 100<br />
/pex group Admin set rank 1<br />
阶级100是最高提升的阶级数。<br />
<br />
升级和降级命令都会在游戏内收到限制 (但在控制台不会). 在游戏中，你不可以:<br />
<br />
把一个低于你阶级的升到你的阶级 (Mod到Admin, 用前面的例子)<br />
把一个阶级高于你的降到低于你的阶级(Admin到Mod,用前面的例子)<br />
不能对于你同样阶级的升降级 (Mob不能对Mob操作，Admin不能对Admin操作。)<br />
如果你在游戏内（只是举个例子）是Admin，想要把一个玩家提高到你一样的阶级必须使用/pex user PlayerName group set Admin.<br />
<br />
在控制台，你很自由可以不受以上限制。<br />
<br />
===炫酷的滑板鞋!(好吧只是称号吗)===<br />
使用以下命令<br />
/pex group Member prefix "&0(&8M&7ember&0)&7 "<br />
/pex group VIP prefix "&0(&eVIP&0)&7 "<br />
/pex group Mod prefix "&0(&1Mod&0)&7 "<br />
/pex group Admin prefix "&0(&4Admin&0)&7 "<br />
确保在每个称号后面都加上了个空格，这可以阻止称号和用户名混在一起在聊天中。实际上，后缀前也是因为同样的理由加一个空格为好。还有一种可以显示前缀后缀的方法就是前缀后缀相同（只需把prefix变成suffix就行）。<br />
<br />
===给每个组别添加权限 ===<br />
注意: 如果你还没有允许这些组别修改世界，那么删除modifiyworld.*这一步是不需要的.<br />
<br />
可选的: /pex group default remove modifyworld.*<br />
可选的: /pex group default add modifyworld.chat (Only needed if modifyworld.* has been removed)<br />
/pex group Member add modifyworld.*<br />
/pex group VIP add modifyworld.*<br />
/pex group VIP add -modifyworld.mobtarget.monster.creeper<br />
/pex group Mod add modifyworld.*<br />
/pex group Mod add -modifyworld.mobtarget.*<br />
/pex group Admin add permissions.*<br />
/pex group Admin add modifyworld.*<br />
/pex group Admin add -modifyworld.mobtarget.*<br />
来看看成果吧！<br />
<br />
===见证奇迹！===<br />
<br />
你想要改变你的权限组的话，使用这个命令 /pex user 玩家名 group set 权限组名，接下来就测试啦！<br />
<br />
Default<br />
<br />
验证你可以聊天<br />
验证你有正确的前缀在聊天时<br />
验证你可以在出生点外破坏方块<br />
注意: 如果你把modifyworld.* 节点之前移除了，就不能破坏（之前是可选项）<br />
如果你可以破坏但是modifyworld.* 节点被移除了！, 找到个爬行者然后拥抱它！ (别担心，它保证对你没兴趣但是你伤得了它)<br />
Member<br />
<br />
验证你可以聊天<br />
验证你有正确的前缀在聊天时<br />
验证你可以在出生点外破坏方块<br />
VIP<br />
<br />
验证你可以聊天<br />
验证你有正确的前缀在聊天时<br />
验证你可以在出生点外破坏方块<br />
如果你可以破坏但是modifyworld.* 节点被移除了！, 找到个爬行者然后拥抱它！ (别担心，它保证对你没兴趣但是你伤得了它)<br />
Admin<br />
<br />
验证你可以聊天<br />
验证你有正确的前缀在聊天时<br />
验证你可以在出生点外破坏方块 (如果你把玩家名字放在了OP文件中，并且在PEX插件配置config文档里把allowOps设置为了true，你将可以在出生点附近破坏).<br />
验证你可以使用PEX插件所有命令(使用/pex reload命令测试，它应该会回复 "Permissions Reloaded（权限重新加载）")<br />
验证所有怪物都对你没兴趣<br />
下一步你可以换一个玩家作为“实验对象”比如加入游戏的好基友(这是为了科学！!)<br />
<br />
===测试阶级 ===<br />
<br />
首先使用/pex user 另一个玩家 group set default<br />
验证升降级别命令有效 使用/pex promote 前面你移动的那个玩家. 你会看见 "User AnotherPlayer promoted to NextGroup（这个玩家到了下个组别）"<br />
一直使用这个命令直到出现 "Promotion error: User is not promotable（升级错误，用户不允许）". 使用 /pex user 这个玩家 命令会显示:<br />
playername are member of:<br />
Mod (rank 100 @ default)<br />
playername's permissions:<br />
-modifyworld.mobtarget.* (from Mod)<br />
modifyworld.* (from Mod)<br />
playername's options:<br />
降级和升级一样，只不过把命令中的promote变成demote<br />
如果那个玩家只是个机器人, 如果你想的话，使用这个命令把它删掉 /pex user 玩家名 delete<br />
如果那个玩家是真人，确保每个组别都正常工作（看上机教程最前面。）<br />
<br />
===后台文件案例=== <br />
如果你成功了上面那个案例，你就会发现后台文件变成了这样。很具有参考性:<br />
<br />
groups:<br />
default:<br />
options:<br />
rank: '1000'<br />
default: true<br />
permissions:<br />
- modifyworld.chat<br />
Member:<br />
permissions:<br />
- modifyworld.*<br />
options:<br />
rank: '900'<br />
prefix: '&0(&8M&7ember&0)&7 '<br />
VIP:<br />
permissions:<br />
- -modifyworld.mobtarget.monster.creeper<br />
- modifyworld.*<br />
options:<br />
rank: '800'<br />
prefix: '&0(&eVIP&0)&7 '<br />
Mod:<br />
permissions:<br />
- -modifyworld.mobtarget.*<br />
- modifyworld.*<br />
options:<br />
rank: '100'<br />
prefix: '&0(&1Mod&0)&7 '<br />
Admin:<br />
permissions:<br />
- -modifyworld.mobtarget.*<br />
- modifyworld.*<br />
- permissions.*<br />
options:<br />
rank: '1'<br />
prefix: '&0(&4Admin&0)&7 '<br />
users:<br />
AnotherPlayer:<br />
group:<br />
- default<br />
YourPlayerName:<br />
group:<br />
- Admin<br />
这就是被解析后的文件的样子，但是最好使用YAML编写工具来确保你的文件已经正确，不然插件可能会出所有类别的错误！<br />
<br />
{<br />
"users": {<br />
"AnotherPlayer": {<br />
"group": [<br />
"default"<br />
]<br />
}, <br />
"YourPlayerName": {<br />
"group": [<br />
"Admin"<br />
]<br />
}<br />
}, <br />
"groups": {<br />
"default": {<br />
"options": {<br />
"default": true, <br />
"rank": "1000"<br />
}, <br />
"permissions": [<br />
"modifyworld.chat"<br />
]<br />
}, <br />
"Member": {<br />
"options": {<br />
"prefix": "&0(&8M&7ember&0)&7 ", <br />
"rank": "900"<br />
}, <br />
"permissions": [<br />
"modifyworld.*"<br />
]<br />
}, <br />
"VIP": {<br />
"options": {<br />
"prefix": "&0(&eVIP&0)&7 ", <br />
"rank": "800"<br />
}, <br />
"permissions": [<br />
"-modifyworld.mobtarget.monster.creeper", <br />
"modifyworld.*"<br />
]<br />
}, <br />
"Mod": {<br />
"options": {<br />
"prefix": "&0(&1Mod&0)&7 ", <br />
"rank": "100"<br />
}, <br />
"permissions": [<br />
"-modifyworld.mobtarget.*", <br />
"modifyworld.*"<br />
]<br />
}, <br />
"Admin": {<br />
"options": {<br />
"prefix": "&0(&4Admin&0)&7 ", <br />
"rank": "1"<br />
}, <br />
"permissions": [<br />
"-modifyworld.mobtarget.*", <br />
"modifyworld.*", <br />
"permissions.*"<br />
]<br />
}<br />
}<br />
}<br />
<br />
=Chat Manager=<br />
=命令=<br />
===实用指令===<br />
注意，在以下命令里 user=玩家名字，world=世界名字 permission=权限 node=节点 backend=后台文件 group=权限组别<br />
/pex 显示帮助<br />
permissions.manage<br />
/pex toggle debug 调试开关（不要总开着！，要不然会出很多信息文件）<br />
permissions.debug<br />
/pex user <user> toggle debug 给指定的一个人测试调整（上面一样）<br />
permissions.manage.<user><br />
/pex user <user> check <permission> 检查一个具体的玩家的具体的权限<br />
permissions.manage.<user><br />
/pex reload 重新载入所有pex文件<br />
permissions.manage.reload<br />
/pex config <node> [value] 看节点的值（写上后面的更改值）<br />
permissions.manage.config <br />
/pex backend 看现在的后台文件（也就是正在用的文件）<br />
permissions.manage.backend<br />
/pex hierarchy 看现在服务器结构（阶级）<br />
permissions.manage.users<br />
/pex dump <backend> <filename> 把你的后台文件倒到另外一个文件里 谨慎使用！不会立刻保存，但会在游戏中有效果<br />
permissions.manage.dump<br />
/pex users cleanup <group> [threshold] 清走“死亡”的会员（默认30天不活动）<br />
permissions.manage.users.cleanup<br />
<br />
===世界管理===<br />
/pex worlds 看PEX里面的世界<br />
permissions.manage.worlds<br />
/pex world <world> 看这个世界的层次信息<br />
permissions.manage.worlds<br />
/pex world <world> inherit <parentWorlds> 让你选择的世界继承一个世界（继承permission,etc.)<br />
permissions.manage.worlds.inheritance <br />
玩家指令：<br />
/pex users list 看所有在PEX里面的玩家<br />
permissions.manage.users<br />
/pex users 一样一样<br />
/pex user 一样一样 = = <br />
玩家permission管理：<br />
/pex user 一样.....······<br />
permissions.manage.users<br />
/pex user <user> 看玩家的权限<br />
permissions.manage.users.permissions.<user><br />
/pex user <user> prefix [newprefix] 设置玩家前缀颜色<br />
permissions.manage.users.prefix.<user> <br />
/pex user <user> suffix [newsuffix] 设置玩家后缀颜色<br />
permissions.manage.users.suffix.<user><br />
/pex user <user> delete 把玩家从权限文件里面移除<br />
permissions.manage.users.<user><br />
/pex user <user> list [world] 看玩家的权限<br />
permissions.manage.users.permissions.<user><br />
/pex user <user> add <permission> [world] 给玩家增加权限<br />
permissions.manage.users.permissions.<user><br />
/pex user <user> remove <permission> [world] 给玩家移除权限<br />
permissions.manage.users.permissions.<user><br />
/pex user <user> timed add <permission> <lifetime in seconds> [world] 给玩家在时间内（秒）添加权限<br />
permissions.manage.users.permissions.timed.<user><br />
/pex user <user> timed remove <permission> <lifetime in seconds> [world]给玩家在时间内（秒）移除权限<br />
permissions.manage.users.permissions.timed.<user><br />
/pex user <user> set <option> <value> [world] 给玩家设选择值（不怎么懂表示，望进一步翻译和解释）<br />
permissions.manage.users.permissions.<user><br />
<br />
===玩家组管理===<br />
/pex user <user> group list 给出玩家所有现在在的组<br />
permissions.manage.membership.<user><br />
/pex user <user> group add <group> [world] [lifetime]把玩家加入组（时间，秒，不设默认永久）<br />
permissions.manage.membership.<group><br />
/pex user <user> group set <group> [world] 把玩家放进组，注意这将会把玩家从另一个组移除<br />
permissions.manage.membership.<group><br />
/pex user <user> group remove <group> [world] 把玩家从组移除<br />
permissions.manage.membership.<group><br />
<br />
===默认组管理===<br />
/pex default group [world] 看默认的管理组情况<br />
permissions.manage.groups.inheritance<br />
/pex set default group <group> [world] 把权限组组设成默认<br />
permissions.manage.groups.inheritance<br />
<br />
===组的指令===<br />
/pex group 显示所有创建了的组<br />
permissions.manage.groups.list<br />
/pex groups ↑（同上）<br />
permissions.manage.groups.list<br />
/pex groups list ↑<br />
permissions.manage.groups.list<br />
/pex group <group> prefix [newprefix] 设置组前缀<br />
permissions.manage.groups.prefix.<group> <br />
/pex group <group> suffix [newsuffix] 设置组后缀<br />
permissions.manage.groups.suffix.<group><br />
/pex group <group> create [parents] 创建组，parents（母权限组）是说他是从哪里升级得来的（继承权限)<br />
permissions.manage.groups.create.<group><br />
/pex group <group> delete 删除权限组<br />
permissions.manage.groups.remove.<group><br />
/pex group <group> parents list 看权限组的继承表<br />
permissions.manage.groups.inheritance.<group><br />
/pex group <group> parents set <parents> 设置权限组组的母权限组<br />
permissions.manage.groups.inheritance.<group><br />
/pex group <group> 显示所有组的权限<br />
permissions.manage.groups.permissions.<group><br />
/pex group <group> list [world] 组的所有权限，加上世界名称可以看单个世界的权限<br />
permissions.manage.groups.permissions.<group><br />
/pex group <group> add <permission> [world] 给小组加权限 <br />
permissions.manage.groups.permissions.<group><br />
/pex group <group> remove <permission> [world] 移除权限<br />
permissions.manage.groups.permissions.<group><br />
/pex group <group> timed add <permission> [lifetime] [world] 给权限组限时加权限，不填默认永久<br />
permissions.manage.groups.permissions.timed.<group><br />
/pex group <group> timed remove <permission> [world] 给权限组限时移除权限组，不填默认永久<br />
permissions.manage.groups.permissions.timed.<group><br />
/pex group <group> set <option> <value> [world] 给组的人设置选则的值<br />
permissions.manage.groups.permissions.<group><br />
<br />
===组的玩家的管理===<br />
/pex group <group> users 所有在组里的玩家<br />
permissions.manage.membership.<group><br />
/pex group <group> user add <user> 把玩家弄进小组<br />
permissions.manage.membership.<group><br />
/pex group <group> user remove <user> 把玩家从组里移除<br />
permissions.manage.membership.<group><br />
/pex promote <user> <ladder> 不知道怎么翻译了Promote <玩家名> on <ladder>. If <ladder> is not specified, the default ladder (named default) will be used.<br />
permissions.user.promote.<ladder> <br />
/pex demote <user> <ladder> 大题同上<br />
permissions.user.demote.<ladder><br />
<br />
=FAQ=<br />
=Features=<br />
=Integrating with PEX=<br />
=Migration=<br />
=Migration and UUIDs=<br />
=Modifyworld（中译世界修改）=<br />
===需要注意的地方===<br />
<br />
这些需要你已经安装了一个权限插件，其中需要先设置默认组只能聊天。<br />
<br />
默认情况下，玩家不会受限制，但是服务器通常需要通过自定义取消用户的权限节点来限制玩家的行为，你可以把modifyworld.*这个权限否定，这样玩家就什么都干不了了<br />
<br />
除了以上，默认时，这些关于世界修改的权限是使用方块名字来替代物品ID，如果你想使用ID，设置或增加config文件中的use-material-names: false即可<br />
<br />
否定一个节点（在前面加负号"－",或者把它的值设为false）来否定玩家或者组别的一些功能。而通配符*是指父（即*前）权限节点下的所有子权限节点。<br />
<br />
当你在使用PEX插件时，你可以在文件里一行指定多个物品，用|分开，打出这个需要按住shift后按反斜杠\，比如(260|296|297) 就是苹果，小麦和面包，当然先要设置use-material-names: false<br />
===IMPORTANT NOTICES===<br />
<br />
Thanks to Bukkit user @Tahg we were notified about one issue with the modifyworld.blocks.place.* node: If you remove modifyworld.* from a group, for the group to place blocks, you will need to specify what blocks the group is allowed to place other blocks on using the modifyworld.blocks.interact.* (alternately you can use a wildcard for the block ID with modifyworld.blocks.interact.*) in addition to the modifyworld.blocks.place.* for the blocks the group is allowed to place. This is because Bukkit checks first for onPlayerInteract() then for onBlockPlace().<br />
For example, when trying to place a sand block on a grass block, the permission node checks are modifyworld.blocks.interact.grass then modifyworld.blocks.place.sand. Consider the block being targeted with this action - the interact permission is required for the block that is targeted with right-click, and thus could be to the side or above the placed block.<br />
Metadata can appear on a lot of blocks and items that you might not expect, please make sure you read the section on Metadata and check the debug output before posting in the forums!<br />
===Configuration===<br />
<br />
Modifyworld configuration is stored in plugins/Modifyworld/config.yml<br />
<br />
An example ModifyWorld config file:<br />
<br />
informPlayers: true<br />
itemRestrictions: true<br />
whitelist: false<br />
messages:<br />
prohibitedItem: You have prohibited item "%s".<br />
whitelist: You are not allowed to join this server. Goodbye!<br />
permissionDenied: Sorry, you don't have enough permissions<br />
use-material-names: true<br />
drop-restricted-item: false<br />
item-use-check: false<br />
===Configuration Properties===<br />
<br />
由于搬运，格式有些耽误此处格式为：<br />
<br />
权限/实体...名 （默认是否开启，false为不开启，或者该项的值） 简介<br />
informPlayers false 是否通知玩家该玩家的权限变化<br />
itemRestrictions false Enable/disable item restrictions. If this is enabled, items not configured to be allowed will be removed from the player's inventory if it's found.<br />
messages.prohibitedItem 你禁止某项物品后，会发送信息给拥有被禁止的物品者<br />
messages.whitelist You are not allowed to join this server. Goodbye! 给不在白名单内玩家的信息<br />
messages.permissionDenied Sorry, you don't have enough permissions 给尝试做没有权限的事情的玩家的信息<br />
whitelist false 是否开启白名单<br />
drop-restricted-item false 设置为true后玩家丢出物品时是“吐出”然而设置为false后玩家丢物品，物品会直接不见！<br />
use-material-names true true时，检查节点时会使用物品名字来代替ID<br />
check-metadata (版本 1.19.1后无) false If true, modifyworld will use the meta-data for blocks and items in the permissions checks. This means that your nodes may need a :* or .* added to the end of them!<br />
item-use-check false 设置为true后，可以设置modifyworld.item.use.<物品id>.on.block.<方块id> 的节点，即检查物品使用的对象，基本取代了modifyworld.interact.<实体名称><br />
===Metadata Notes===<br />
<br />
Starting with release 1.19.1, metadata handling has been changed a bit.<br />
<br />
There is no longer a need to specifically turn on metadata handling for modifyworld. However, a lot of blocks and items have metadata that one might not expect, or now has metadata due to changes in minecraft and bukkit.<br />
<br />
A few examples are leaf blocks (each type has it's own value), planks (for the different colours), and sandstone (the different designs).<br />
<br />
For item ID's that have metadata, using :* will cover all possible values for the metadata. For nodes that cover multiple items/blocks where some have metadata and others do not, the regex value of :?* will cover ID's that have metadata and ID's that do not.<br />
<br />
Many blocks that you might not expect can have metadata, such as chests and doors that are freshly placed but have not been opened yet. When in doubt and you can't get a permission node, turning on debug will show what is being looked for. Please do this before posting in the forums, I can't stress this enough. Metadata is a very large stumbling block for many new users to PEX.<br />
<br />
===Generic Nodes===<br />
<br />
<br />
modifyworld.login 是否允许玩家加入游戏，你需要吧白名单开启来启动这个功能<br />
modifyworld.chat 是否允许玩家能发布公告，聊天<br />
modifyworld.sneak Player can crouch (check your Minecraft client config for the key) NOTE: Per https://github.com/PEXPlugins/PermissionsEx/issues/78, 这个节点在bukkit中因为缺少支持难以工作<br />
modifyworld.sprint Player can sprint (double tap your forward key) NOTE: Per http://github.com/t3hk0d3/PermissionsEx/issues/78,也因为同样的原因难以工作。<br />
modifyworld.chat.private 玩家是否能私聊<br />
modifyworld.usebeds 玩家是否能使用床<br />
modifyworld.bucket.empty.<fluid> 玩家是否能使用液体（清空桶）<br />
<fluid>指的是水或岩浆<br />
modifyworld.bucket.fill.<fluid> 玩家是否能用桶装东西<br />
<fluid> 指的是谁，岩浆或牛奶（早期版本里，air就是牛奶）<br />
modifyworld.digestion Allows players' energy bar to deplete. A popular application of this would be to do -modifyworld.digestion to disable energy consumption whilst still enabling modifyworld.*<br />
<br />
===Block Nodes===<br />
<br />
See Materials for <blockid> values.<br />
<br />
<br />
modifyworld.blocks.destroy.<blockid> Player can break <blockid>. It's also possible to specify <blockid> by name. Example: modifyworld.blocks.destroy.stone<br />
modifyworld.blocks.place.<blockid> Player can place <blockid>. NOTICE: This permission requires modifyworld.blocks.interact.<blockid> to work properly.<br />
modifyworld.blocks.interact.<blockid> Player can interact with <blockid> (use levers, press buttons, etc.)<br />
===Item Nodes===<br />
<br />
See Materials for <itemid> values.<br />
<br />
<br />
modifyworld.items.craft.<itemid> Player can craft <itemid>.<br />
modifyworld.items.drop.<itemid> Player can drop <itemid>.<br />
modifyworld.items.enchant.<itemid> Player can enchant <itemid>.<br />
modifyworld.items.have.<itemid> Player can have <itemid> in their inventory. itemRestrictions: true need to be set for this to work.<br />
modifyworld.items.hold.<itemid> Player can have <itemid> in their hand. itemRestrictions: true need to be set for this to work.<br />
modifyworld.items.pickup.<itemid> Player can pickup <itemid>. Also it's possible to specify <itemid> by name, example: 、modifyworld.items.pickup.diamondpickaxe<br />
modifyworld.item.use.<itemid>.on.block.<blockid> Player can use <itemid> on block <blockid>. item-use-check: true need to be set for this to work and is check in addition to the modifyworld.interact.<entityName> checks<br />
As of 1.19.3<br />
modifyworld.items.use.<itemid>.on.block.<blockid> Player can use <itemid> on block <blockid>. item-use-check: true need to be set for this to work and is check in addition to the modifyworld.interact.<entityName> checks<br />
modifyworld.items.throw.<itemid> Player may throw eggs, snowballs, splash potions or experience bottles. Potion metadata excludes splash flag: potion:34 will match a Splash Potion of Swiftness II.<br />
As of 1.19.4<br />
modifyworld.items.take.<itemid>.of.<container> Player may take items from containers, such as chests.<br />
modifyworld.items.put.<itemid>.of.<container> Player may take put items in containers, such as chests.<br />
===Entity Nodes===<br />
<br />
<br />
modifyworld.damage.deal.<entityName> Player can deal damage to <entityName> (e.g. skeleton, spider, creeper, cow, pig, minecart, etc)<br />
modifyworld.damage.take.<entityName> Player can take damage from <entityName><br />
modifyworld.mobtarget.<entityName> Player can be targeted by <entityName><br />
modifyworld.interact.<entityName> Player can interact with <entityName><br />
modifyworld.tame.<entityName> Player can tame <entityName>. This permission won't give you ability to tame animals or mobs that are not normally tameable (no pet creepers). Currently, only animal.wolf and animal.ocelot are applicable.<br />
===Possible <entityName> values===<br />
<br />
<br />
Players and Wolves<br />
player.<playerName> Player called <playerName>. (Example: player.t3hk0d3)<br />
group.<groupName> Any member of <groupName> group. (Example: group.admins)<br />
animal.wolf Wild wolf<br />
animal.wolf.<playerName> Wolf tamed by <playerName> (Example: wolf.t3hk0d3)<br />
animal.ocelot Wild ocelot (cat)<br />
animal.ocelot.<playerName> Tamed cat (ocelot)<br />
Example: animal.ocelot.t3hk0d3<br />
npc.villager Not related to Bert<br />
snowman Not related Frosty<br />
irongolem Defenders of the Villagers<br />
Animals<br />
animal.chicken cluck-cluck<br />
animal.cow Mooo<br />
animal.mushroomcow Mooshroom<br />
animal.pig Pig<br />
animal.sheep Sheep<br />
animal.squid Squid<br />
Monsters<br />
monster.blaze Pyros, every one...<br />
monster.cavespider Worse than spiders<br />
monster.creeper SssssSSSssss<br />
monster.enderman Don't look at them directly<br />
monster.ghast AWWWWWWW<br />
monster.giant Giant Zombie<br />
monster.pigzombie Pig Zombie, omg<br />
monster.silverfish Beware the horde<br />
monster.skeleton Them bones, them dry bones...<br />
monster.slime Covers regular slimes and magma cubes<br />
monster.spider Yep, this is Spider, he is annoying.<br />
monster.zombie Brainzzzz...<br />
Environment<br />
starvation Num nums, or lack there of<br />
fire Initial fire damage<br />
lava Lava damage. Add firetick too for full protection.<br />
firetick Damage from touching fire (or after stepping into lava) over time.<br />
blockexplosion Damage from TNT explosion.<br />
projectile.arrow Arrows shot at player<br />
drowning Failing to grab a breath of fresh air<br />
fall Jumping without a parachute<br />
suicide Committing Seppuku<br />
poison Poison potions<br />
===Vehicle Nodes===<br />
<br />
NOTE: If you want to have permission to enter or exit a vehicle, you will also need modifyworld.interact.*<br />
<br />
<br />
modifyworld.vehicle.destroy.<vehicleName> Player can damage vehicles (minecarts for example)<br />
modifyworld.vehicle.enter.<vehicleName> Player can enter vehicles<br />
modifyworld.vehicle.collide.<vehicleName> Player can collide with a vehicle<br />
===Possible <vehicleName> values=== <br />
<br />
Boat<br />
boat Not related to the Love Boat<br />
Minecart<br />
minecart Indiana Jones rides in one of these<br />
===Material Names===<br />
<br />
If use-material-names is false use the ID column value. Otherwise use the Name value.<br />
<br />
You can find more detail, including metadata information, at Minecraft Wiki.<br />
<br />
=Pex basics=<br />
===Permissions and Server Terminology===<br />
<br />
Server Console (AKA Console); The window that appears when the server is started. Displays server and plugin startup information, as well as server and plugin errors.<br />
Global Permissions: Permissions that are applied to all worlds on a server.<br />
World Specific Permissions: Permissions that are applied only to specified worlds.<br />
Users: Your players.<br />
Group: A name given to a set of permission nodes, often used to designate various levels of support on a server.<br />
Groups can have global and world specific permissions, as well as other information used by other plugins.<br />
Node: A line of text that represents a command, action or ability. For example, the /give command in bukkit has the node of bukkit.command.give<br />
Negation: Mark a node as not available. Generally used only in certain specific situations.<br />
Inheritance: The ability of a group to have the permissions from another group automatically apply. PEX supports group and world level Inheritance.<br />
Metadata: (Also know as damage value) Metadata is another value added to an item ID number for various things, such as the different colours of wool blocks, the position of a switch, if a door is open or not, and so on. Primary used with Modifyworld.<br />
===Permissions Hierarchy ===<br />
<br />
PEX supports both a file based and SQL permissions hierarchy. For the purposes of explanation and ease of visualization, the following example will use a file based permissions hierarchy.<br />
<br />
users: <- Users Section<br />
t3hk0d3: <- Player Name<br />
group: <- Player Group(s) Section<br />
- default <- Player Group Name<br />
permissions: <- Player Specific Permissions Section<br />
- permissions.* <- Permissions node<br />
worlds: <- World Specific Permission Section<br />
world: <- World designator<br />
permissions: <- World Specific Permission Group<br />
- test.* <- World Specific Permission<br />
group: <- World Specific Group Section<br />
- testers <- World Specific Group<br />
prefix: '&5[YARR]&f' <- World Specific Prefix<br />
groups: <- Group Section<br />
default: <- Group Name<br />
default: true <- Default Group Setting<br />
permissions: <- Group Permissions Section<br />
- -modifyworld.blocks.interact.23 <- Negated Permission Node<br />
- modifyworld.* <- Permission Node<br />
admins:<br />
inheritance: <- Group Inheritance Section<br />
- default <- Groups) To Inherit From<br />
permissions:<br />
- example.permission<br />
- -punish.noobs<br />
options: <- Group Options Section<br />
test.test: '100500' <- Extra Data<br />
rank: '1' <- Rank Designator<br />
worlds:<br />
nether:<br />
permissions:<br />
- nocheat.fly<br />
prefix: '&7[ADMIN FROM HELL]'<br />
testers:<br />
inheritance:<br />
- admins<br />
options:<br />
test.test: '9000'<br />
worlds: <- World Specific Section<br />
nether: <- World Name<br />
inheritance: <- World Inheritance Section<br />
- world <- World To Inherit From<br />
===PEX File Format (YAML)===<br />
<br />
PEX, like many other plugins, uses a format for it's files called YAML (YAML Ain't Markup Language, see http://yaml.org/ if you want to know more). YAML, unlike some other file formats, is very picky about the formatting and characters used. Config files used by PEX, including the permissions file, must be indented correctly! Capitalization matters as well!<br />
<br />
The rules for YAML as they apply to PEX are:<br />
<br />
Certain characters are reserved for use by YAML. Some of the characters are ' - : # and %. If the data for an entry is going to use one of those characters, it must be in quotes.<br />
%prefix%player%suffix> &e%message is invalid. "%prefix%player%suffix> &e%message" is valid<br />
Any entries that are made of numbers only must be in quotes.<br />
rank: 1000 or 45625: is invalid. rank: '1000' or '45625': is valid.<br />
Tabs are not allowed to be in the file anywhere, unless it is in quotes. Any place where you would use a tab must use exactly two spaces.<br />
Each group must start at the very beginning of the line, and each section contained within that section must be indented.<br />
Due to the regex support in PEX, there are other characters that one has to be aware of. Characters such as } { ) ( ? and * must be quoted or escaped (a backslash works well). This isn't a YAML limitation, but is a similar situation to the reserved characters in YAML.<br />
<br />
=PEXML=<br />
=Plugin Configuration=<br />
=Ranks (Promotion and Demotion)=<br />
=Troubleshooting and FAQ=</div>Zhwhttps://mineplugin.org/index.php?title=ClearLagg&diff=1094ClearLagg2015-07-19T10:27:39Z<p>Zhw：/* 配置文件 */</p>
<hr />
<div>{{Bukkit Plugin Infobox<br />
|版本=v2.7.7<br />
|網址=http://dev.bukkit.org/bukkit-plugins/clearlagg/<br />
|兼容服务端版本=CraftBukkit 1.7.9-R0.2<br />
}}<br />
<br />
=概况=<br />
本插件适用各种类型的服务器, 它的作用即是移除所有实体来避免/减少延迟. 当然，本插件并不能修复所有延迟问题，但它能完成其中大部分修复工作.如果你在运行一个 20+ 玩家的服务器，使用 /lagg clear 命令会显著地减少 RAM 占用, 这取决于你服务器面临的的延迟类型是什么.<br />
<br />
*支持权限管理<br />
*实体限制<br />
*减少延迟<br />
*减少RAM占用<br />
*可以停止TNT的连锁反应<br />
*简单的指令控制<br />
*非常轻量级的插件<br />
*可以通过控制台自动运行<br />
*当服务器已经清理延迟后，插件会调整时间来适应<br />
*configurable removal<br />
<br />
=命令与权限=<br />
命令<br />
<br />
功能<br />
<br />
权限<br />
<br />
/lagg clear<br />
(清理物品)<br />
lagg.clear<br />
<br />
/lagg check<br />
(计算物品数)<br />
lagg.check<br />
<br />
/lagg reload<br />
(重载插件)<br />
lagg.reload<br />
<br />
/lagg killmobs<br />
(杀死生物)<br />
lagg.killmobs<br />
<br />
/lagg area <半径><br />
(清除指定半径的物品)<br />
lagg.area<br />
<br />
/lagg unloadchunks<br />
(卸载不需要的区块)<br />
lagg.unloadchunks<br />
<br />
/lagg chunk<br />
(找到可能的延迟区块)<br />
lagg.chunk<br />
<br />
/lagg tpchunk <x> <z> <世界名><br />
(传送去区块)<br />
lagg.tpchunk<br />
<br />
/lagg<br />
(显示帮助)<br />
lagg.help<br />
<br />
=拓展=<br />
SaveDeathDrops<br />
(Blocks removal of items dropped from death)<br />
下载：http://dev.bukkit.org/bukkit-plugins/clearlag-savedeathdrops/<br />
=配置文件=<br />
{{模板:配置文件}}<br />
<br />
config文件在哪里呢? 路径☞plugins\ClearLag\config.yml<br />
settings:<br />
auto-update: true #是否自动更新插件.<br />
enable-signs: true #是否允许通过木牌使用这个插件<br />
config-version: 1 #配置版本，请勿修改<br />
disable-waterlife: true #鱿鱼是否可以生成<br />
keep-spawn-in-memory: true #出生地区块是否一直加载（极度推荐！不然掉下虚空都有可能。）<br />
enable-api:true #是否允许别的插件使用API<br />
area-filter: #什么样的实体不会被移除<br />
- Itemframe<br />
- Painting<br />
- Wolf <br />
- Villager<br />
- Horse<br />
#是否允许插件重设（此处可能是插件更新配置文件的意思，未实测）配置 (更加稳定的配置文件), 或是尝试在文件中添加新的路径?<br />
config-updater:<br />
force-update: false #设置此项为false将不会重设你的配置，但可能会造成bugs出现.. 本功能仍在测试中!<br />
# 此项用于限制刷怪蛋，因此玩家将无法利用刷怪蛋使服务器过载<br />
# -- 'check-radius' ，插件检测附近实体时，检测的半径范围<br />
# -- 'max-mobs' ，停止生成怪物时，一定加载半径范围内（加载区块中以玩家为中心的加载范围）实体的最大数量<br />
mobegg-limiter:<br />
enabled: false<br />
check-radius:8<br />
max-mobs: 5<br />
#停用形成新区块，或是限制一次加载时区块的最大加载数量<br />
# -- 本功能不适用于 1.6.4!<br />
chunk-limiter:<br />
enabled: false<br />
limit: 6000<br />
create-new-chunks: true <br />
#-Deprecated-<br />
#这里不仅限制了怪物的可视，也规定了怪物的生成<br />
# -- 越低，越流畅<br />
# -- 如果太高，会导致卡顿胡总和错误<br />
mob-range:<br />
enabled: true<br />
zombie: 5<br />
skeleton: 30<br />
creeper: 20<br />
#物品/怪物在地面的保存时间<br />
# -- 单位为秒（s）<br />
live-time:<br />
enabled: false<br />
interval: 10<br />
mobtimer: true<br />
itemtimer: true<br />
arrowtimer: true<br />
arrowkilltime:15<br />
moblivetime:600<br />
itemlivetime:240<br />
#允许clearlag控制所有世界的生成? (支持所有插件!)<br />
# -- This will also respect cancelations, unlike minecraft's native code<br />
custom-mobspawner:<br />
enabled: false<br />
#clearlag寻找安全地点生成怪物时的最大尝试次数<br />
max-tries: 50<br />
#(单位-s) clearlag尝试生成怪物的间隔时间?<br />
interval: 30<br />
#生成怪物时，以玩家为中心的半径大小范围<br />
radius: 30<br />
#距离玩家的半径范围 (单位-方块数!)<br />
radius-from: 7<br />
#怪物生成时该相距多远 (不是简单的方块距离，格式见后!!) (1,010 = 大约 10-20 方块的距离)<br />
mob-radius:1010<br />
#'''带英文的翻译说明不是很准确，请参考后修改。'''Should we keep trying to spawn a mob if a clear location isn't found在找不到清除位置的时候，是否要继续尝试生成怪物<br />
forcespawn:false<br />
#4 = nighttime, what light level should mobs spawn in怎样的光线条件下，怪物生成。<br />
lightlevel: 4<br />
#Chance mobs will have armor/sword, 1 being diamond every time怪物拥有装甲，剑的机会，1代表每次都会有钻石装备<br />
armor-chance:30 mobs: #数字越，几率越高。不输默认为1？('''只在普通/主世界！''')<br />
- zombie 5<br />
- skeleton 3<br />
- creeper<br />
- enderman<br />
animals: #数字越高几率越高('''只在普通/主世界！''')<br />
- pig 4<br />
- sheep 1<br />
- cow 6<br />
- chicken 2<br />
#限制一定半径（radius）内的TNT矿车<br />
tnt-minecart:<br />
enabled: false<br />
max: 2<br />
radius: 6<br />
#减少酿造台的时间<br />
dispenser-reducer:<br />
enabled: false<br />
time: 100<br />
#减少TNT的飞溅，以减少卡顿<br />
tnt:<br />
tnt-reducer:false<br />
#减少火焰传播（时间？）<br />
firespread-reducer:<br />
enabled: false<br />
time: 2000<br />
#允许在一个区块内加载多少实体<br />
chunk-entity-limiter:<br />
enabled: true<br />
limit: 3<br />
spawn-limiter:<br />
enabled: false<br />
interval: 15<br />
monsters: 300<br />
animals: 300<br />
#计算并告知你的延迟。在延迟增加时，使用下面的命令<br />
tps-meter:<br />
enabled: false<br />
interval: 15 tps-trigger:14.0<br />
commands:<br />
- 'lagg<br />
killmobs'<br />
- 'lagg<br />
clear'<br />
#使用/lagg killmobs时，略过的生物列表<br />
kill-mobs:<br />
disable-build-wither:<br />
false mob-filter:<br />
- Villager<br />
- Wolf<br />
- Horse<br />
#这个限制刷怪笼的怪物生成<br />
mobspawner:<br />
enabled: false<br />
max-spawn: 4<br />
#No longer bugged! -- Dont use if you have CB++ or Spigot!<br />
item-merger:<br />
enabled: false<br />
radius: 6<br />
#自动移除选项<br />
# -- 警告信息配置：time是警告被显示的时间，msg是警告讯息<br />
# -- NOTE: The below 'remove' section applies to this remover!<br />
# -- NOTE: Putting the interval to low will cause issues!<br />
auto-removal:<br />
broadcast-message: '&6[ClearLag]<br />
&aRemoved<br />
+RemoveAmount<br />
Entities!'<br />
broadcast-warning: true<br />
enable-scheduler: true<br />
autoremoval-interval: 234<br />
warnings: #You can have thousands of warnings! Put the time they should be executed, and the message (FOLLOW FORMAT!!)<br />
-<br />
time:2 msg:&4[ClearLag] &cWarning Ground items will be removed in &7+remaining &cseconds!<br />
-<br />
time:4 msg:&4[ClearLag] &cWarning Ground items will be removed in &7+remaining &cseconds!<br />
-<br />
time:6 msg:&4[ClearLag] &cWarning Ground items will be removed in &7+remaining &cseconds!<br />
#自动清除时，被清除的。<br />
remove:<br />
world-filter:<br />
#What worlds should NOT be iterated through during clearing~<br />
- this_world<br />
broadcast-removal: true<br />
boat: true<br />
falling-block: true<br />
experienceOrb:true<br />
painting: true<br />
projectile:true<br />
item: true<br />
itemframe:false<br />
minecart:true #What items SHOULD be removed during clearing~<br />
primed-tnt:true<br />
arrow: true<br />
snowball: true<br />
fireball: true<br />
ender-signal:true<br />
item-filter: #What items should NOT be removed during clearing~<br />
- 264<br />
mobs: #实行清除时不去清除的<br />
# - cow<br />
#在使用 /lagg clear时清除的。<br />
command-remove:<br />
world-filter:<br />
- this_world<br />
broadcast-removal: false<br />
boat: true<br />
falling-block: true<br />
experienceOrb:true<br />
painting: true<br />
projectile:true<br />
item: true<br />
itemframe:false<br />
minecart: true<br />
primed-tnt:true<br />
arrow: true<br />
snowball: true<br />
fireball: true<br />
ender-signal:true<br />
item-filter:<br />
# - 264<br />
# - 265<br />
# - 311<br />
# - 312<br />
# - 266<br />
mobs:<br />
# - cow<br />
check:<br />
world-filter:<br />
- this_world<br />
boat: true<br />
falling-block: true<br />
experienceOrb:true<br />
painting: true<br />
projectile:true<br />
item: true<br />
itemframe:false<br />
minecart: true<br />
primed-tnt:true<br />
arrow: true<br />
snowball: true<br />
fireball: true<br />
ender-signal:true<br />
item-filter:<br />
# - 264<br />
# - 265<br />
# - 311<br />
# - 312<br />
# - 266<br />
mobs:<br />
creature:true<br />
animals:true<br />
monster:true<br />
limit:<br />
enable-limit:false<br />
max: 1000<br />
check-interval: 60<br />
broadcast-message: '&6[ClearLag]<br />
&aLimit<br />
reached,<br />
removed<br />
+RemoveAmount<br />
Entities!'<br />
world-filter:<br />
- this_world<br />
broadcast-removal: true<br />
boat: true<br />
falling-block: true<br />
experienceOrb:true<br />
painting: true<br />
projectile:true<br />
item: true<br />
itemframe:false<br />
minecart: true<br />
primed-tnt:true<br />
arrow: true<br />
snowball: true<br />
fireball: true<br />
ender-signal:true<br />
item-filter:<br />
# - 264<br />
# - 265<br />
# - 311<br />
# - 312<br />
# - 266</div>Zhwhttps://mineplugin.org/index.php?title=MobArena&diff=1068MobArena2015-07-02T00:12:09Z<p>Zhw：/* 设置模式的命令 */</p>
<hr />
<div>{{待搬运}}<br />
{{Bukkit Plugin Infobox<br />
|版本=v0.96.9<br />
|兼容服务端版本=1.8.1<br />
|网址=http://dev.bukkit.org/bukkit-plugins/mobarena/}}<br />
[[Category:娱乐]][[Category:机械]]<br />
=安装=<br />
安装MobArena其实很简单，只需以下四步:<br />
*关闭服务器<del>咳咳，当然是关你自己的服务器啦</del>.<br />
*从论坛主题或是Bukkit Dev站点的项目页下载jar文件.<br />
*将jar文件拖入服务端的plugins文件夹中.<br />
*重启服务端. <br />
之后，配置文件 (config.yml) 以及一个宣告文本(announcements.yml) 会自动创建在plugins/MobArena/路径下.<br />
文件结构如下:<br />
<br />
plugins/<br />
MobArena.jar<br />
MobArena/<br />
config.yml<br />
announcements.yml<br />
此时此刻, 或许你想直接开始设置竞技场, 但是你需要先看看配置文件，并把它配置成你喜欢的样子<del>就是说，还是根据情况配置一下吧</del>. 你可以在配置文件自定义MobArena的设置，职业，奖励，波数（怪物类型）<br />
<br />
=建立竞技场=<br />
==建造一个竞技场==<br />
完整的竞技场应该包含一个可以选择职业的准备区域，一个竞技场地以及观察点(离开点) <br />
下面是各个选项的讲解<br />
<br />
大厅：<br />
玩家加入游戏之前将会在大厅选择职业.一个建造好的游戏大厅会有每一个职业的选择牌子，玩家通过点击牌子可以获取一个职业, 还有一个铁块, 玩家可以通过点击铁块来表示他们已经准备好开始游戏.牌子必须在第一行写上职业的名字（区分大小写）,但是无论你在另外三行上写什么，都不会被怪物竞技场识别，你是不能写上 ,所以你不会得到确认的信息（如果有，那是另一个插件）<br />
<br />
竞技场地：<br />
这里是玩家和怪物搏斗的地方.竞技场地会有墙，可能会有一个屋顶 , 这样玩家和怪物就不能跑出去了. 这使得玩家们不会只是在竞技场外闲逛。.<br />
<br />
观察点: <br />
当玩家想要观看一场战斗时,他们可以使用/ma spec 命令来传送到竞技场的观察点. 这同样也是竞技场中玩家死去后会传送到的地方,前提是在配置文件中，把 spectate-after-death设置为ture. 这块区域要保证观看者不能走出去闲逛（进入竞技场地或者离远竞技场）因为在观看过程中，玩家是无敌的.<br />
<br />
离开点: <br />
在使用 /ma leave命令后,玩家和观察者会被传送到原来所在的地方,除非竞技场有一个离开点(只是可选). 使用离开点,可以准确控制玩家在游戏后去何处.<br />
<br />
关于区域，传送点等，<br />
<br />
当竞技场建好后，就是设置怪物竞技场的区域和传送点的时候了。在设置它们前，我们先来看看他们有什么作用.<br />
<br />
区域: <br />
一个竞技场需要一个竞技区域,然后还可以有一个准备区域，怪物竞技场会使用这些区域来确保玩家不会作弊（通过破坏竞技场来走出区域）,然后确保怪物竞技场所产生的怪物会在里面产生. 怪物竞技场非常排外（不要局外人）, 所以也最好把不想要的生物排除在外. 区域是通过区域工具来设置的.<br />
<br />
传送点: <br />
当玩家加入一个怪物竞技场的游戏时，他们会被传送到准备区域中的准备点来选择职业和准备开始游戏（通过点击铁块）.当每个人都准备好的时候，玩家会被传送到竞技场内的竞技场出生点。观察者会被传送到竞技场的观察点来进入观察区域,当游戏结束的时候，玩家和观察者会被传送到他们传送来之前的地方，或者去可选的离开点,传送点会用传送点工具来设置。.<br />
<br />
出生点: <br />
这里的出生点指的是怪物出生的地点.怪物竞技场只会在附近有玩家的出生点产出怪物（十五个方格的半径）.需要注意的是，怪物的数量不随着按照出生点的数量改变，只会因为在配置文件中波数的倍率改变和玩家的数量所改变.出生点可以通过出生点工具来设置。.<br />
<br />
容器: <br />
容器就是竞技场里的箱子，回收站等。 这些容器将会在一场游戏后重置其内部空间为初始值。只有被声明了的容器才会更新其存储空间，所以仅仅在竞技场里放一个箱子可不够 - 它还需要被用工具声明。<br />
<br />
==设置模式==<br />
我们能用配置模式来设置竞技场。 当我们进入配置模式时，物品栏将会被保存 并给我们一套金工具 （工具栏）， 每一个都有其独特作用。同时我们也可以飞行，使得我们在竞技场附近移动时更加快捷方便一些，最后，但不是绝对，我们不能够聊天或者使用普通命令如果在在配置模式下的话，因为配置模式和你建立起了独立会话（即你所发表的信息都是针对插件的。）<br />
<br />
进入设置模式的方法：输入/ma setup 竞技场名，值得提醒的是，如果服务器中只有一个竞技场，你不用输入竞技场的名字，如果竞技场没有设置完毕或者没有被创造，首先使用/ma addarena 竞技场名来创造它<br />
<br />
离开设置模式的方法：聊天框内输入done，注意不是命令，是聊天信息，没有斜杠<br />
<br />
另外，如果你刚安装怪物竞技场插件，会有一个预置的，名称为default竞技场存在于配置文件中，如果你想要一个不同的名字，你需要先创造一个新竞技场然后把原来的竞技场使用/ma delarena default来删除<br />
<br />
下面我们会提到在设置模式中有什么命令可以使用。<br />
<br />
==设置模式的命令==<br />
<br />
设置模式是一个独立，特殊的会话，这意味着插件会监控我们说的每一句话，使得插件的命令可以缩短，以致于设置过程没有特别麻烦。比如exp命令替代了/ma expandregion，并且还可以防止我们错误地使用了其他插件的命令<br />
<br />
下面是我们可以在设置模式中使用的命令，很多都十分浅显易懂（如果您懂英文的话。）使得您设置竞技场十分快速<br />
done<br />
离开设置模式<br />
别名: end stop done quit<br />
<br />
help<br />
显示帮助信息<br />
别名: ? h<br />
<br />
missing<br />
显示我们还没有设置好的区域（准备区诸如此类）<br />
这个命令在你不知道你已经设置了那些区域的时候十分有用<br />
别名: miss<br />
<br />
expand <region> <amount> <direction><br />
Expand a region by some amount in some direction.<br />
Valid regions: ar for the arena region, or lr for the lobby region<br />
Valid amounts: positive integers (whole numbers)<br />
Valid directions: up, down, or out<br />
Example: expand ar 5 up<br />
别名: exp<br />
<br />
show [<region>|<warp>|<point>]<br />
Show a region, warp, or point(s) as red wool blocks.<br />
Valid regions: ar for the arena region, or lr for the lobby region<br />
Valid warps: arena, lobby, spec, exit<br />
Valid points: spawns (or just sp) for spawnpoints, chests (or just c) for chests<br />
Example: show sp<br />
<br />
==设置时的工具==<br />
<br />
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.<br />
<br />
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.<br />
<br />
===区域工具===<br />
<br />
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.<br />
<br />
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.<br />
<br />
Left-click: Set the first point to be the location of the target block<br />
Right-click: Set the second point to be the location of the target block<br />
<br />
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.<br />
<br />
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.<br />
<br />
===玩家传送点工具===<br />
<br />
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.<br />
<br />
Left-click: Set the currently selected warp on top of the target block<br />
Right-click: Cycle between available warps<br />
<br />
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.<br />
<br />
Note: The arena, lobby, and spectator warps are all required. The exit warp is optional.<br />
<br />
===怪物产生点工具===<br />
<br />
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.<br />
<br />
Left-click: Add a spawnpoint on top of the target block<br />
Right-click: Remove the spawnpoint on top of the target block (if the spawnpoint exists)<br />
<br />
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.<br />
<br />
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.<br />
<br />
===容器工具===<br />
<br />
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.<br />
<br />
Left-click: Register the clicked container (if it wasn't registered)<br />
Right-click: Unregister the clicked container (if it was registered)<br />
<br />
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.<br />
<br />
=命令=<br />
==玩家命令==<br />
<br />
这些指令能够给所有玩家使用. 它们包括了加入, 离开, 旁观和列出所有竞技场(可用或不可用)<br />
<br />
<br />
/ma join (<竞技场>) or /ma j (<竞技场>) - 加入指定名称的竞技场.<br />
/ma leave or /ma l - 离开竞技场或是离开旁观者模式.<br />
/ma notready - 获取所有未准备的玩家.<br />
/ma spec (<竞技场>) or /ma s (<竞技场>) - 以旁观者模式加入指定名称竞技场.<br />
/ma arenas - 获取所有竞技场的名字, 若是绿色则已启用, 灰色则未启用.<br />
/ma players - 获取当前所有竞技场的所有玩家.<br />
/ma players <竞技场> - 获取指定竞技场的所有玩家.<br />
/ma class <职业> - 如果你在大厅里, 是应直接用指令而不是透过牌子互动选择职业.<br />
<br />
==管理员指令==<br />
<br />
只有后台或者服务器op能使用下面这些指令. 这里包括了开始或是停止竞技场, 启用或是卸载竞技场甚至包含了MobArena的所有管理.<br />
<br />
/ma enable - 启用MobArena插件.<br />
/ma disable - 卸载MobArena插件.<br />
/ma enable <竞技场> - 启用指定名字的竞技场.<br />
/ma disable <竞技场> - 关闭指定名字的竞技场.<br />
/ma force end - 停止所有竞技场的运作.<br />
/ma force end <竞技场> - 停止指定名称竞技场的运作及使该竞技场的所有玩家离开. <br />
/ma force start <竞技场> - 开始运作一个指定名称的竞技场以及请出该竞技场内未准备的玩家.<br />
/ma notready <竞技场> - 获取该竞技场内所有未准备的玩家.<br />
/ma restore <玩家> - 在可能的情况下恢复指定玩家背包.<br />
/ma config reload - 重载config配置文件夹.<br />
==建设指令==<br />
<br />
只有op (以及某些合理的指令能在后台) 使用这些指令. 它们包括了设置竞技场传送点, 竞技场出生点以及竞技场范围.<br />
<br />
/ma setup <竞技场> - 进入建设指定名称的竞技场模式.<br />
/ma addarena <竞技场> - 建立一个新的竞技场节点于当前所在世界.<br />
/ma delarena <竞技场> - 删除指定名称的竞技场.<br />
/ma editarena <竞技场> - 开启或关闭指定竞技场修改模式.<br />
/ma editarena <竞技场> [true|false] - 开启 (true) 或关闭 (false) 指定竞技场的修改模式.<br />
/ma setting <竞技场> - 列出所有指定竞技场的设置项.<br />
/ma setting <竞技场> <设置项> - 查询当前指定设置项的值于指定的竞技场.<br />
/ma setting <竞技场> <设置项> <值> - 设置指定竞技场中指定设置项的指定值.<br />
/ma checkspawns - 显示竞技场出生点 (在你当前的竞技场下) 是使用红色羊毛覆盖的范围在当前你当前的位置上. 这个指令同时也能查询在这个范围内不同的点是否被出生点覆盖着.<br />
/ma classchest <职业> - 当正在查询箱子, 使指定的职业与这个箱子建立连接. 连接一个职业箱子意味着当MobArena连接建立后, 将同时复制于职业箱子内的物品, 而不是于竞技场大厅内的任何职业箱子. 当你建立一个职业箱子网络时它能带给你便利.<br />
/ma auto-generate <竞技场> - 自动生成一个指定名称的竞技场. 这个竞技场只会生成于玩家所站的位置下方.<br />
/ma auto-degenerate <竞技场> - 自动停止生成竞技场, 能基于自动生成器下有效地恢复, 当这是一个 "bulldozed" 补丁.<br />
<br />
=权限=<br />
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.<br />
<br />
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!<br />
<br />
==竞技场权限==<br />
<br />
Did you read the note at the top? If not, read it before you continue.<br />
<br />
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.<br />
<br />
bPermissions: ^mobarena.arenas.default<br />
GroupManager: -mobarena.arenas.default<br />
zPermissions: mobarena.arenas.default: false<br />
<br />
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.<br />
<br />
Still confused? Check the sample setup at the bottom of the page!<br />
<br />
==职业权限==<br />
<br />
Did you read the note at the top? If not, read it before you continue.<br />
<br />
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.<br />
<br />
bPermissions: ^mobarena.classes.knight<br />
GroupManager: -mobarena.classes.knight<br />
zPermissions: mobarena.classes.knight: false<br />
<br />
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.<br />
<br />
As with arenas, I recommend letting everyone enjoy all the classes, unless you have a special reason not to.<br />
<br />
Still confused? Check the sample setup at the bottom of the page!<br />
<br />
==命令权限==<br />
<br />
Did you read the note at the top? If not, read it before you continue.<br />
<br />
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!<br />
<br />
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.<br />
<br />
mobarena.use.join<br />
mobarena.use.leave<br />
mobarena.use.spec<br />
mobarena.use.arenalist<br />
mobarena.use.playerlist<br />
mobarena.use.notready<br />
mobarena.use.class<br />
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.<br />
<br />
mobarena.admin.enable<br />
mobarena.admin.kick<br />
mobarena.admin.restore<br />
mobarena.admin.force<br />
mobarena.admin.teleport<br />
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.<br />
<br />
mobarena.setup.config<br />
mobarena.setup.setup<br />
mobarena.setup.setting<br />
mobarena.setup.addarena<br />
mobarena.setup.removearena<br />
mobarena.setup.editarena<br />
mobarena.setup.spawnpoints<br />
mobarena.setup.containers<br />
mobarena.setup.checkdata<br />
mobarena.setup.checkspawns<br />
mobarena.setup.classchest<br />
mobarena.setup.classes<br />
mobarena.setup.leaderboards<br />
mobarena.setup.autogenerate<br />
mobarena.setup.autodegenerate<br />
Sample setup<br />
<br />
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...<br />
<br />
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:<br />
<br />
default-aux: <-- This is the auxiliary group that is to<br />
permissions: be inherited by the default group and<br />
- essentials.balance the donor group. It is not used for<br />
- essentials.pay anything else.<br />
- essentials.sell<br />
<br />
default: <-- This is the default group. It inherits<br />
inherits: default-aux from default-aux, but also revokes the<br />
permissions: permission for the special class.<br />
- -mobarena.classes.diamondknight<br />
<br />
donor: <-- This is the donor group, which also<br />
inherits: default-aux inherits from default-aux, but it<br />
permissions: does not revoke any class permissions,<br />
- essentials.balance.others which means it has access to all of<br />
- essentials.kit them by default.<br />
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.<br />
=物品语法（Item Syntax待搬运）=<br />
=职业箱子（Class Chests待搬运｝=<br />
=怪物波设置（Formulas待搬运）=<br />
=怪物种类（Monster types待搬运）=<br />
以上内容搬运自英文wiki[https://github.com/garbagemule/MobArena/wiki]</div>Zhwhttps://mineplugin.org/index.php?title=MobArena&diff=1067MobArena2015-07-02T00:00:49Z<p>Zhw：/* 设置模式 */</p>
<hr />
<div>{{待搬运}}<br />
{{Bukkit Plugin Infobox<br />
|版本=v0.96.9<br />
|兼容服务端版本=1.8.1<br />
|网址=http://dev.bukkit.org/bukkit-plugins/mobarena/}}<br />
[[Category:娱乐]][[Category:机械]]<br />
=安装=<br />
安装MobArena其实很简单，只需以下四步:<br />
*关闭服务器<del>咳咳，当然是关你自己的服务器啦</del>.<br />
*从论坛主题或是Bukkit Dev站点的项目页下载jar文件.<br />
*将jar文件拖入服务端的plugins文件夹中.<br />
*重启服务端. <br />
之后，配置文件 (config.yml) 以及一个宣告文本(announcements.yml) 会自动创建在plugins/MobArena/路径下.<br />
文件结构如下:<br />
<br />
plugins/<br />
MobArena.jar<br />
MobArena/<br />
config.yml<br />
announcements.yml<br />
此时此刻, 或许你想直接开始设置竞技场, 但是你需要先看看配置文件，并把它配置成你喜欢的样子<del>就是说，还是根据情况配置一下吧</del>. 你可以在配置文件自定义MobArena的设置，职业，奖励，波数（怪物类型）<br />
<br />
=建立竞技场=<br />
==建造一个竞技场==<br />
完整的竞技场应该包含一个可以选择职业的准备区域，一个竞技场地以及观察点(离开点) <br />
下面是各个选项的讲解<br />
<br />
大厅：<br />
玩家加入游戏之前将会在大厅选择职业.一个建造好的游戏大厅会有每一个职业的选择牌子，玩家通过点击牌子可以获取一个职业, 还有一个铁块, 玩家可以通过点击铁块来表示他们已经准备好开始游戏.牌子必须在第一行写上职业的名字（区分大小写）,但是无论你在另外三行上写什么，都不会被怪物竞技场识别，你是不能写上 ,所以你不会得到确认的信息（如果有，那是另一个插件）<br />
<br />
竞技场地：<br />
这里是玩家和怪物搏斗的地方.竞技场地会有墙，可能会有一个屋顶 , 这样玩家和怪物就不能跑出去了. 这使得玩家们不会只是在竞技场外闲逛。.<br />
<br />
观察点: <br />
当玩家想要观看一场战斗时,他们可以使用/ma spec 命令来传送到竞技场的观察点. 这同样也是竞技场中玩家死去后会传送到的地方,前提是在配置文件中，把 spectate-after-death设置为ture. 这块区域要保证观看者不能走出去闲逛（进入竞技场地或者离远竞技场）因为在观看过程中，玩家是无敌的.<br />
<br />
离开点: <br />
在使用 /ma leave命令后,玩家和观察者会被传送到原来所在的地方,除非竞技场有一个离开点(只是可选). 使用离开点,可以准确控制玩家在游戏后去何处.<br />
<br />
关于区域，传送点等，<br />
<br />
当竞技场建好后，就是设置怪物竞技场的区域和传送点的时候了。在设置它们前，我们先来看看他们有什么作用.<br />
<br />
区域: <br />
一个竞技场需要一个竞技区域,然后还可以有一个准备区域，怪物竞技场会使用这些区域来确保玩家不会作弊（通过破坏竞技场来走出区域）,然后确保怪物竞技场所产生的怪物会在里面产生. 怪物竞技场非常排外（不要局外人）, 所以也最好把不想要的生物排除在外. 区域是通过区域工具来设置的.<br />
<br />
传送点: <br />
当玩家加入一个怪物竞技场的游戏时，他们会被传送到准备区域中的准备点来选择职业和准备开始游戏（通过点击铁块）.当每个人都准备好的时候，玩家会被传送到竞技场内的竞技场出生点。观察者会被传送到竞技场的观察点来进入观察区域,当游戏结束的时候，玩家和观察者会被传送到他们传送来之前的地方，或者去可选的离开点,传送点会用传送点工具来设置。.<br />
<br />
出生点: <br />
这里的出生点指的是怪物出生的地点.怪物竞技场只会在附近有玩家的出生点产出怪物（十五个方格的半径）.需要注意的是，怪物的数量不随着按照出生点的数量改变，只会因为在配置文件中波数的倍率改变和玩家的数量所改变.出生点可以通过出生点工具来设置。.<br />
<br />
容器: <br />
容器就是竞技场里的箱子，回收站等。 这些容器将会在一场游戏后重置其内部空间为初始值。只有被声明了的容器才会更新其存储空间，所以仅仅在竞技场里放一个箱子可不够 - 它还需要被用工具声明。<br />
<br />
==设置模式==<br />
我们能用配置模式来设置竞技场。 当我们进入配置模式时，物品栏将会被保存 并给我们一套金工具 （工具栏）， 每一个都有其独特作用。同时我们也可以飞行，使得我们在竞技场附近移动时更加快捷方便一些，最后，但不是绝对，我们不能够聊天或者使用普通命令如果在在配置模式下的话，因为配置模式和你建立起了独立会话（即你所发表的信息都是针对插件的。）<br />
<br />
进入设置模式的方法：输入/ma setup 竞技场名，值得提醒的是，如果服务器中只有一个竞技场，你不用输入竞技场的名字，如果竞技场没有设置完毕或者没有被创造，首先使用/ma addarena 竞技场名来创造它<br />
<br />
离开设置模式的方法：聊天框内输入done，注意不是命令，是聊天信息，没有斜杠<br />
<br />
另外，如果你刚安装怪物竞技场插件，会有一个预置的，名称为default竞技场存在于配置文件中，如果你想要一个不同的名字，你需要先创造一个新竞技场然后把原来的竞技场使用/ma delarena default来删除<br />
<br />
下面我们会提到在设置模式中有什么命令可以使用。<br />
<br />
==设置模式的命令==<br />
<br />
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.<br />
<br />
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.<br />
<br />
done<br />
Leave Setup Mode.<br />
Aliases: end stop done quit<br />
<br />
help<br />
Display help screen.<br />
Aliases: ? h<br />
<br />
missing<br />
Display a list of missing (mandatory) regions, warps, and points.<br />
This command is useful if you have forgotten how far you are in the setup process, and what you still need to set up.<br />
Aliases: miss<br />
<br />
expand <region> <amount> <direction><br />
Expand a region by some amount in some direction.<br />
Valid regions: ar for the arena region, or lr for the lobby region<br />
Valid amounts: positive integers (whole numbers)<br />
Valid directions: up, down, or out<br />
Example: expand ar 5 up<br />
Aliases: exp<br />
<br />
show [<region>|<warp>|<point>]<br />
Show a region, warp, or point(s) as red wool blocks.<br />
Valid regions: ar for the arena region, or lr for the lobby region<br />
Valid warps: arena, lobby, spec, exit<br />
Valid points: spawns (or just sp) for spawnpoints, chests (or just c) for chests<br />
Example: show sp<br />
<br />
==设置时的工具==<br />
<br />
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.<br />
<br />
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.<br />
<br />
===区域工具===<br />
<br />
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.<br />
<br />
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.<br />
<br />
Left-click: Set the first point to be the location of the target block<br />
Right-click: Set the second point to be the location of the target block<br />
<br />
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.<br />
<br />
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.<br />
<br />
===玩家传送点工具===<br />
<br />
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.<br />
<br />
Left-click: Set the currently selected warp on top of the target block<br />
Right-click: Cycle between available warps<br />
<br />
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.<br />
<br />
Note: The arena, lobby, and spectator warps are all required. The exit warp is optional.<br />
<br />
===怪物产生点工具===<br />
<br />
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.<br />
<br />
Left-click: Add a spawnpoint on top of the target block<br />
Right-click: Remove the spawnpoint on top of the target block (if the spawnpoint exists)<br />
<br />
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.<br />
<br />
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.<br />
<br />
===容器工具===<br />
<br />
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.<br />
<br />
Left-click: Register the clicked container (if it wasn't registered)<br />
Right-click: Unregister the clicked container (if it was registered)<br />
<br />
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.<br />
<br />
=命令=<br />
==玩家命令==<br />
<br />
这些指令能够给所有玩家使用. 它们包括了加入, 离开, 旁观和列出所有竞技场(可用或不可用)<br />
<br />
<br />
/ma join (<竞技场>) or /ma j (<竞技场>) - 加入指定名称的竞技场.<br />
/ma leave or /ma l - 离开竞技场或是离开旁观者模式.<br />
/ma notready - 获取所有未准备的玩家.<br />
/ma spec (<竞技场>) or /ma s (<竞技场>) - 以旁观者模式加入指定名称竞技场.<br />
/ma arenas - 获取所有竞技场的名字, 若是绿色则已启用, 灰色则未启用.<br />
/ma players - 获取当前所有竞技场的所有玩家.<br />
/ma players <竞技场> - 获取指定竞技场的所有玩家.<br />
/ma class <职业> - 如果你在大厅里, 是应直接用指令而不是透过牌子互动选择职业.<br />
<br />
==管理员指令==<br />
<br />
只有后台或者服务器op能使用下面这些指令. 这里包括了开始或是停止竞技场, 启用或是卸载竞技场甚至包含了MobArena的所有管理.<br />
<br />
/ma enable - 启用MobArena插件.<br />
/ma disable - 卸载MobArena插件.<br />
/ma enable <竞技场> - 启用指定名字的竞技场.<br />
/ma disable <竞技场> - 关闭指定名字的竞技场.<br />
/ma force end - 停止所有竞技场的运作.<br />
/ma force end <竞技场> - 停止指定名称竞技场的运作及使该竞技场的所有玩家离开. <br />
/ma force start <竞技场> - 开始运作一个指定名称的竞技场以及请出该竞技场内未准备的玩家.<br />
/ma notready <竞技场> - 获取该竞技场内所有未准备的玩家.<br />
/ma restore <玩家> - 在可能的情况下恢复指定玩家背包.<br />
/ma config reload - 重载config配置文件夹.<br />
==建设指令==<br />
<br />
只有op (以及某些合理的指令能在后台) 使用这些指令. 它们包括了设置竞技场传送点, 竞技场出生点以及竞技场范围.<br />
<br />
/ma setup <竞技场> - 进入建设指定名称的竞技场模式.<br />
/ma addarena <竞技场> - 建立一个新的竞技场节点于当前所在世界.<br />
/ma delarena <竞技场> - 删除指定名称的竞技场.<br />
/ma editarena <竞技场> - 开启或关闭指定竞技场修改模式.<br />
/ma editarena <竞技场> [true|false] - 开启 (true) 或关闭 (false) 指定竞技场的修改模式.<br />
/ma setting <竞技场> - 列出所有指定竞技场的设置项.<br />
/ma setting <竞技场> <设置项> - 查询当前指定设置项的值于指定的竞技场.<br />
/ma setting <竞技场> <设置项> <值> - 设置指定竞技场中指定设置项的指定值.<br />
/ma checkspawns - 显示竞技场出生点 (在你当前的竞技场下) 是使用红色羊毛覆盖的范围在当前你当前的位置上. 这个指令同时也能查询在这个范围内不同的点是否被出生点覆盖着.<br />
/ma classchest <职业> - 当正在查询箱子, 使指定的职业与这个箱子建立连接. 连接一个职业箱子意味着当MobArena连接建立后, 将同时复制于职业箱子内的物品, 而不是于竞技场大厅内的任何职业箱子. 当你建立一个职业箱子网络时它能带给你便利.<br />
/ma auto-generate <竞技场> - 自动生成一个指定名称的竞技场. 这个竞技场只会生成于玩家所站的位置下方.<br />
/ma auto-degenerate <竞技场> - 自动停止生成竞技场, 能基于自动生成器下有效地恢复, 当这是一个 "bulldozed" 补丁.<br />
<br />
=权限=<br />
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.<br />
<br />
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!<br />
<br />
==竞技场权限==<br />
<br />
Did you read the note at the top? If not, read it before you continue.<br />
<br />
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.<br />
<br />
bPermissions: ^mobarena.arenas.default<br />
GroupManager: -mobarena.arenas.default<br />
zPermissions: mobarena.arenas.default: false<br />
<br />
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.<br />
<br />
Still confused? Check the sample setup at the bottom of the page!<br />
<br />
==职业权限==<br />
<br />
Did you read the note at the top? If not, read it before you continue.<br />
<br />
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.<br />
<br />
bPermissions: ^mobarena.classes.knight<br />
GroupManager: -mobarena.classes.knight<br />
zPermissions: mobarena.classes.knight: false<br />
<br />
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.<br />
<br />
As with arenas, I recommend letting everyone enjoy all the classes, unless you have a special reason not to.<br />
<br />
Still confused? Check the sample setup at the bottom of the page!<br />
<br />
==命令权限==<br />
<br />
Did you read the note at the top? If not, read it before you continue.<br />
<br />
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!<br />
<br />
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.<br />
<br />
mobarena.use.join<br />
mobarena.use.leave<br />
mobarena.use.spec<br />
mobarena.use.arenalist<br />
mobarena.use.playerlist<br />
mobarena.use.notready<br />
mobarena.use.class<br />
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.<br />
<br />
mobarena.admin.enable<br />
mobarena.admin.kick<br />
mobarena.admin.restore<br />
mobarena.admin.force<br />
mobarena.admin.teleport<br />
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.<br />
<br />
mobarena.setup.config<br />
mobarena.setup.setup<br />
mobarena.setup.setting<br />
mobarena.setup.addarena<br />
mobarena.setup.removearena<br />
mobarena.setup.editarena<br />
mobarena.setup.spawnpoints<br />
mobarena.setup.containers<br />
mobarena.setup.checkdata<br />
mobarena.setup.checkspawns<br />
mobarena.setup.classchest<br />
mobarena.setup.classes<br />
mobarena.setup.leaderboards<br />
mobarena.setup.autogenerate<br />
mobarena.setup.autodegenerate<br />
Sample setup<br />
<br />
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...<br />
<br />
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:<br />
<br />
default-aux: <-- This is the auxiliary group that is to<br />
permissions: be inherited by the default group and<br />
- essentials.balance the donor group. It is not used for<br />
- essentials.pay anything else.<br />
- essentials.sell<br />
<br />
default: <-- This is the default group. It inherits<br />
inherits: default-aux from default-aux, but also revokes the<br />
permissions: permission for the special class.<br />
- -mobarena.classes.diamondknight<br />
<br />
donor: <-- This is the donor group, which also<br />
inherits: default-aux inherits from default-aux, but it<br />
permissions: does not revoke any class permissions,<br />
- essentials.balance.others which means it has access to all of<br />
- essentials.kit them by default.<br />
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.<br />
=物品语法（Item Syntax待搬运）=<br />
=职业箱子（Class Chests待搬运｝=<br />
=怪物波设置（Formulas待搬运）=<br />
=怪物种类（Monster types待搬运）=<br />
以上内容搬运自英文wiki[https://github.com/garbagemule/MobArena/wiki]</div>Zhwhttps://mineplugin.org/index.php?title=ChestShop&diff=1056ChestShop2015-07-01T14:51:07Z<p>Zhw：/* 管理员商店 */</p>
<hr />
<div>{{待翻译}}<br />
http://dev.bukkit.org/bukkit-plugins/chestshop/<br />
==使用商店==<br />
<br />
十分简单！右键来购买物品，左键来卖出物品（当然你也可以在配置文件中自定义按键用途！）<br />
<br />
==如何创建一个商店==<br />
<br />
===普通玩家商店===<br />
<br />
放置一个箱子在地上Place a chest on the ground <br />
放置一个在箱子周围一方格的牌子（例如，在箱子上）Place a sign 1 block away from the chest (for example, above it) <br />
在牌子上, 书写文字：<br />
第一行会被插件自动填充First line will be filled by the plugin automatically <br />
价格行是用来描述卖出和买进的价格的，你需要一个价格注释在价格的附近比如“B”来描述这是被玩家买的（Bought by players）S来描述玩家卖出的，用冒号隔开，可用的序列有： "B 5:5 S", "B 5", "S free"，free指免费<br />
你可以通过使用/iteminfo命令来得到你手上物品的名字<br />
我猜测这里有图，但我无法访问，请其他合作编写者补充For example Example sign<br />
一个人可以用10美金来买64个钻石，而用5美金买回去A person can buy 64 diamonds for 10 dollars and sell them back for 5 dollars from AcrobotPL<br />
===管理员商店=== <br />
- 有无限物品的商店<br />
确保你安装了插件后有 ChestShop.admin权限，在牌子上第一行加上Admin shop就可以了 在config中可以配置。<br />
<br />
===Translations===<br />
<br />
Here is a list of player-made translations: Translation list<br />
<br />
===权限节点===<br />
ChestShop.shop.* 创造和使用商店<br />
ChestShop.shop.create.* 创造所有商店<br />
ChestShop.shop.buy 卖任何物品到商店<br />
ChestShop.shop.sell 从商店买任何物品<br />
ChestShop.mod 打开和破坏商店箱子<br />
ChestShop.admin 开启任何商店，破坏，创造管理员商店<br />
<br />
===Useful tips by players===<br />
<br />
How not to get bankrupt A customisable price table<br />
Alternative price table<br />
Full plugin description<br />
<br />
For full plugin description, visit the plugin's thread on Bukkit forums.<br />
<br />
Got an error or suggestion?<br />
<br />
Simply submit a ticket here!<br />
<br />
Has ChestShop helped you or your server?<br />
If you want to thank the team in a more materialistic way, feel free to donate! :)<br />
<br />
Donate</div>Zhwhttps://mineplugin.org/index.php?title=ChestShop&diff=1055ChestShop2015-07-01T14:50:53Z<p>Zhw：/* Permission nodes */</p>
<hr />
<div>{{待翻译}}<br />
http://dev.bukkit.org/bukkit-plugins/chestshop/<br />
==使用商店==<br />
<br />
十分简单！右键来购买物品，左键来卖出物品（当然你也可以在配置文件中自定义按键用途！）<br />
<br />
==如何创建一个商店==<br />
<br />
===普通玩家商店===<br />
<br />
放置一个箱子在地上Place a chest on the ground <br />
放置一个在箱子周围一方格的牌子（例如，在箱子上）Place a sign 1 block away from the chest (for example, above it) <br />
在牌子上, 书写文字：<br />
第一行会被插件自动填充First line will be filled by the plugin automatically <br />
价格行是用来描述卖出和买进的价格的，你需要一个价格注释在价格的附近比如“B”来描述这是被玩家买的（Bought by players）S来描述玩家卖出的，用冒号隔开，可用的序列有： "B 5:5 S", "B 5", "S free"，free指免费<br />
你可以通过使用/iteminfo命令来得到你手上物品的名字<br />
我猜测这里有图，但我无法访问，请其他合作编写者补充For example Example sign<br />
一个人可以用10美金来买64个钻石，而用5美金买回去A person can buy 64 diamonds for 10 dollars and sell them back for 5 dollars from AcrobotPL<br />
===管理员商店=== <br />
- 有无限物品的尚待年<br />
确保你安装了插件后有 ChestShop.admin权限，在牌子上第一行加上Admin shop就可以了 在config中可以配置。<br />
<br />
===Translations===<br />
<br />
Here is a list of player-made translations: Translation list<br />
<br />
===权限节点===<br />
ChestShop.shop.* 创造和使用商店<br />
ChestShop.shop.create.* 创造所有商店<br />
ChestShop.shop.buy 卖任何物品到商店<br />
ChestShop.shop.sell 从商店买任何物品<br />
ChestShop.mod 打开和破坏商店箱子<br />
ChestShop.admin 开启任何商店，破坏，创造管理员商店<br />
<br />
===Useful tips by players===<br />
<br />
How not to get bankrupt A customisable price table<br />
Alternative price table<br />
Full plugin description<br />
<br />
For full plugin description, visit the plugin's thread on Bukkit forums.<br />
<br />
Got an error or suggestion?<br />
<br />
Simply submit a ticket here!<br />
<br />
Has ChestShop helped you or your server?<br />
If you want to thank the team in a more materialistic way, feel free to donate! :)<br />
<br />
Donate</div>Zhwhttps://mineplugin.org/index.php?title=ChestShop&diff=1054ChestShop2015-07-01T14:48:01Z<p>Zhw：/* 普通玩家商店 */</p>
<hr />
<div>{{待翻译}}<br />
http://dev.bukkit.org/bukkit-plugins/chestshop/<br />
==使用商店==<br />
<br />
十分简单！右键来购买物品，左键来卖出物品（当然你也可以在配置文件中自定义按键用途！）<br />
<br />
==如何创建一个商店==<br />
<br />
===普通玩家商店===<br />
<br />
放置一个箱子在地上Place a chest on the ground <br />
放置一个在箱子周围一方格的牌子（例如，在箱子上）Place a sign 1 block away from the chest (for example, above it) <br />
在牌子上, 书写文字：<br />
第一行会被插件自动填充First line will be filled by the plugin automatically <br />
价格行是用来描述卖出和买进的价格的，你需要一个价格注释在价格的附近比如“B”来描述这是被玩家买的（Bought by players）S来描述玩家卖出的，用冒号隔开，可用的序列有： "B 5:5 S", "B 5", "S free"，free指免费<br />
你可以通过使用/iteminfo命令来得到你手上物品的名字<br />
我猜测这里有图，但我无法访问，请其他合作编写者补充For example Example sign<br />
一个人可以用10美金来买64个钻石，而用5美金买回去A person can buy 64 diamonds for 10 dollars and sell them back for 5 dollars from AcrobotPL<br />
===管理员商店=== <br />
- 有无限物品的尚待年<br />
确保你安装了插件后有 ChestShop.admin权限，在牌子上第一行加上Admin shop就可以了 在config中可以配置。<br />
<br />
===Translations===<br />
<br />
Here is a list of player-made translations: Translation list<br />
<br />
===Permission nodes===<br />
<br />
Description<br />
ChestShop.shop.* shop creation and buying/selling - it contains:<br />
ChestShop.shop.create.* create all types of shops<br />
ChestShop.shop.buy buy any item from shop<br />
ChestShop.shop.sell sell any item to shop<br />
ChestShop.mod open any shop chest, destroy stores<br />
ChestShop.admin open any shop chest, destroy stores, create admin shops<br />
A full list of permission nodes<br />
<br />
===Useful tips by players===<br />
<br />
How not to get bankrupt A customisable price table<br />
Alternative price table<br />
Full plugin description<br />
<br />
For full plugin description, visit the plugin's thread on Bukkit forums.<br />
<br />
Got an error or suggestion?<br />
<br />
Simply submit a ticket here!<br />
<br />
Has ChestShop helped you or your server?<br />
If you want to thank the team in a more materialistic way, feel free to donate! :)<br />
<br />
Donate</div>Zhwhttps://mineplugin.org/index.php?title=%E7%94%A8%E6%88%B7:Zhw&diff=1053用户:Zhw2015-07-01T14:29:57Z<p>Zhw：</p>
<hr />
<div>我是zhw。（以下是学生的介绍严重不符合现实请酌量添加汽油与火把）<br />
小周qq983156225<br />
关于我自己，不知道从哪儿开始讲好啊，我有这么几个称号“''坐标系之王''”得名于对于坐标系的亲切度，“''辣条守护者''”给同学们吃辣条的家伙“''导师小周''”专门给MC好友们指路<br />
<br />
六班习惯叫我小周，一班叫我周爷，四班叫我周周（what？），我们班叫我副班<br />
<br />
我是罕见的稀有物种，不但吃吃不胖，晒晒不黑，长得高长得白长得帅（不丑），能认东南西北，能记电话号码，会烧菜会家务（好男人啊），最后在这个自拍泛滥的时代我是罕见的照片比真人难看的人。<br />
<br />
看书，看什么书，长篇小说的看过斗罗大陆第一第二部，看过斗破苍穹，最近在看''冰与火之歌''（特喜欢！）。我阅读过很多著作但是了解颇浅（记得住故事记不住名字之类的）中华上下五千年啊，全球通史啊，看过的历史和科学书很多但是记住的不多，最深刻的数”啊哈灵机一动“那可真是啊哈，还有几本我很喜爱的书写给孩子的哲学书，美德书，乔布斯传这些。<br />
<br />
看视频，动漫看进击，死神，火影，''海贼''，刀剑还有''JOJO''，美剧看''闪电侠''，''绿箭侠''，神盾局，''权力的游戏''（就是冰火歌，也很喜欢！）。国内电视剧连同电视节目基本一个不看（绝对不会追），对漫威和DC出的超级英雄电影必看，绿灯，超人，复联什么的（''还特别喜欢看漫画''）。还看过一个脑洞及其大的动漫飞哥与小佛。<br />
哈哈，平常在同学面前一副脑洞大得不能再大的样子（绝对，绝对，绝对逗到不能想象），成绩过得去（千年老三）<br />
<br />
网上就变成准大神了，给广大MC好友指路，我已经玩我的世界两年余，而且六个月前第一次上服务器玩耍，但现在已经基本广知各项服务器设置和MC知识，有自己的群365053669服务器插件讨论（™就是来问我问题的）群，mcbbsID”''矿工小周''“。还接触了MC插件百科的翻译。http://www.twodam.net/wiki/%E9%A6%96%E9%A1%B5</div>Zhwhttps://mineplugin.org/index.php?title=ChestShop&diff=1052ChestShop2015-07-01T13:46:01Z<p>Zhw：</p>
<hr />
<div>{{待翻译}}<br />
http://dev.bukkit.org/bukkit-plugins/chestshop/<br />
==使用商店==<br />
<br />
十分简单！右键来购买物品，左键来卖出物品（当然你也可以在配置文件中自定义按键用途！）<br />
<br />
==如何创建一个商店==<br />
<br />
===普通玩家商店===<br />
<br />
放置一个箱子在地上Place a chest on the ground <br />
放置一个在箱子周围一方格的牌子（例如，在箱子上）Place a sign 1 block away from the chest (for example, above it) <br />
在牌子上, 书写文字：<br />
第一行会被插件自动填充First line will be filled by the plugin automatically <br />
价格行是用来描述卖出和买进的价格的，你需要一个价格注释在价格的附近比如“B”来描述这是被玩家买的（Bought by players）S来描述玩家卖出的，用冒号隔开，可用的序列有： "B 5:5 S", "B 5", "S free"，free指免费<br />
你可以通过使用/iteminfo命令来得到你手上物品的名字<br />
For example Example sign<br />
A person can buy 64 diamonds for 10 dollars and sell them back for 5 dollars from AcrobotPL<br />
Admin Shop - shop with unlimited items<br />
<br />
Firstly, you've got to be sure that you've the ChestShop.admin permission / you are an OP. To make an Admin Shop, simply put "Admin Shop" (configurable in config.yml) on the first line of the sign.<br />
<br />
Translations<br />
<br />
Here is a list of player-made translations: Translation list<br />
<br />
Permission nodes<br />
<br />
Description<br />
ChestShop.shop.* shop creation and buying/selling - it contains:<br />
ChestShop.shop.create.* create all types of shops<br />
ChestShop.shop.buy buy any item from shop<br />
ChestShop.shop.sell sell any item to shop<br />
ChestShop.mod open any shop chest, destroy stores<br />
ChestShop.admin open any shop chest, destroy stores, create admin shops<br />
A full list of permission nodes<br />
<br />
Useful tips by players<br />
<br />
How not to get bankrupt A customisable price table<br />
Alternative price table<br />
Full plugin description<br />
<br />
For full plugin description, visit the plugin's thread on Bukkit forums.<br />
<br />
Got an error or suggestion?<br />
<br />
Simply submit a ticket here!<br />
<br />
Has ChestShop helped you or your server?<br />
If you want to thank the team in a more materialistic way, feel free to donate! :)<br />
<br />
Donate</div>Zhwhttps://mineplugin.org/index.php?title=McMMO&diff=1051McMMO2015-06-22T02:14:25Z<p>Zhw：</p>
<hr />
<div>{{待搬运}}<br />
http://dev.bukkit.org/bukkit-plugins/mcmmo/<br />
<br />
<br />
==mcMMO Command==<br />
<br />
Description:<br />
<br />
Shows a brief mod description and the available commands.<br />
<br />
Usage:<br />
<br />
/mcmmo [commands]<br />
<br />
Aliases:<br />
<br />
none<br />
<br />
Permission:<br />
<br />
none<br />
<br />
Details:<br />
<br />
Shows a brief mod description and the available commands.<br />
<br />
<br />
<br />
===•mcstats Command===<br />
<br />
Description:<br />
<br />
Shows your mcMMO stats and xp.<br />
<br />
Usage:<br />
<br />
/mcstats<br />
<br />
Aliases:<br />
<br />
/stats<br />
<br />
Permission:<br />
<br />
none<br />
<br />
Details:<br />
<br />
Shows your mcMMO stats and xp<br />
<br />
==Party Commands==<br />
<br />
===•ptp Command===<br />
<br />
Description:<br />
<br />
Teleport to a party member.<br />
<br />
Usage:<br />
<br />
/ptp [name]<br />
<br />
Example:<br />
<br />
/ptp nossr50<br />
<br />
Aliases:<br />
<br />
none<br />
<br />
Permission:<br />
<br />
mcmmo.commands.ptp<br />
<br />
Details:<br />
<br />
With the ptp command, you can teleport to your party members.<br />
<br />
===•party Command===<br />
<br />
Description:<br />
<br />
Manage your party.<br />
<br />
Usage:<br />
<br />
/party Check party information.<br />
/party create <party-name> <password> Create a party<br />
/party join <player> <password> Join a players party<br />
/party invite <player> Invite a player to join your party<br />
/party accept <player> Accept a party invite<br />
/party password <password> Set a password for the party you currently own<br />
/party kick <player-name> Kick a player from the party.<br />
/party owner <player-name> Set a player as the party owner<br />
/party expshare [none/equal] Set the party share mode.<br />
/party lock Lock the party<br />
/party unlock Unlock the party<br />
/party q Quit the party you're currently in.<br />
/party ? More information about parties.<br />
<br />
Example:<br />
<br />
/party create CoolGrindersParty pass1234<br />
<br />
Aliases:<br />
<br />
none<br />
<br />
Permission:<br />
<br />
mcmmo.commands.party<br />
<br />
Details:<br />
<br />
With the party command, you can create parties and join existing ones.<br />
<br />
Back to Top<br />
<br />
===•partychat Command===<br />
<br />
Description:<br />
<br />
Toggle Party chat or send party chat messages.<br />
<br />
Usage:<br />
<br />
/partychat [message]<br />
<br />
Example:<br />
<br />
/pc hello! /partychat<br />
<br />
Aliases:<br />
<br />
p pc<br />
<br />
Permission:<br />
<br />
mcmmo.chat.partychat<br />
<br />
Details:<br />
<br />
With this command, you can chat with your fellow party members in a private channel. Only your party members can view these messages.<br />
<br />
<br />
==•adminchat Command==<br />
<br />
Description:<br />
<br />
Toggle admin chat or send a message in admin chat.<br />
<br />
Usage:<br />
<br />
/adminchat /a [message]<br />
<br />
Aliases:<br />
<br />
/a<br />
/ac<br />
<br />
Permission:<br />
<br />
mcmmo.chat.adminchat<br />
<br />
Details:<br />
<br />
With this command, you can chat with your fellow admins in a private channel. Only players who can also use admin chat (have sufficient permissions) can view these messages.<br />
<br />
<br />
==•mcrefresh Command==<br />
<br />
Description:<br />
<br />
Refresh all cooldowns for mcMMO<br />
<br />
Usage:<br />
<br />
/mcrefresh [player]<br />
<br />
Aliases:<br />
<br />
none<br />
<br />
Permission:<br />
<br />
mcmmo.commands.mcrefresh<br />
mcmmo.commands.mcrefresh.others<br />
<br />
Details:<br />
<br />
With this command, you can refresh your own ability cool downs, or those of the targeted player.<br />
<br />
==•mcgod Command==<br />
<br />
Description:<br />
<br />
Toggle mcMMO god-mode on/off<br />
<br />
Usage:<br />
<br />
/mcgod [player]<br />
<br />
Aliases:<br />
<br />
none<br />
<br />
Permission:<br />
<br />
mcmmo.commands.mcgod<br />
mcmmo.commands.mcgod.others<br />
<br />
Details:<br />
<br />
With this command, you can toggle mcMMO god-mode on/off. While god-mode is enalbed you are invulnerable to all types of damage<br />
<br />
==•xprate Command==<br />
<br />
Description:<br />
<br />
Modify the xp rate or start an event<br />
<br />
Usage:<br />
<br />
/xprate [rate] /xprate reset<br />
<br />
Aliases:<br />
<br />
/mcxprate<br />
<br />
Permission:<br />
<br />
mcmmo.commands.xprate.all<br />
mcmmo.commands.xprate<br />
mcmmo.commands.xprate.reset<br />
mcmmo.commands.xprate.set<br />
<br />
Details:<br />
<br />
With this command, you can start an XP rate event. Type /xprate 2 to multiply all XP gained with two while the XP event is active. More XP for everyone!<br />
<br />
Back to Top<br />
<br />
==•mmoedit Command==<br />
<br />
Description:<br />
<br />
Edit the mcMMO skill values for a user.<br />
<br />
Usage:<br />
<br />
/mmoedit [player] <skill> <level><br />
<br />
Aliases:<br />
<br />
none<br />
<br />
Permission:<br />
<br />
mcmmo.commands.mmoedit<br />
mcmmo.commands.mmoedit.others<br />
<br />
Details:<br />
<br />
This command is used to edit a player's skill level to a specific value. Using /mmoedit nossr50 herbalism 613 will set nossr50's Herbalism level to 613.<br />
<br />
<br />
==•addxp Command==<br />
<br />
Description:<br />
<br />
Add mcMMO XP to a user.<br />
<br />
Usage:<br />
<br />
/addxp [player] <skill> <xp><br />
<br />
Aliases:<br />
<br />
none<br />
<br />
Permission:<br />
<br />
mcmmo.commands.addxp<br />
mcmmo.commands.addxp.others<br />
<br />
Details:<br />
<br />
This command is used to add XP to a user. Using /addxp nossr50 mining 45 will add 45 XP to nossr50's current Mining XP.<br />
<br />
<br />
==addlevels Command==<br />
<br />
Description:<br />
<br />
Add mcMMO levels to a user.<br />
<br />
Usage:<br />
<br />
/addlevels [player] <skill> <levels><br />
<br />
Aliases:<br />
<br />
none<br />
<br />
Permission:<br />
<br />
mcmmo.commands.addlevels<br />
mcmmo.commands.addlevels.others<br />
<br />
Details:<br />
<br />
This command is used to add levels to a user. Using /addlevels nossr50 acrobatics 12 will add 12 levels to nossr50's current Acrobatics level.<br />
<br />
==•mcremove Command==<br />
<br />
Description:<br />
<br />
Remove a user from the database.<br />
<br />
Usage:<br />
<br />
/mcremove [player]<br />
<br />
Aliases:<br />
<br />
none<br />
<br />
Permission:<br />
<br />
mcmmo.commands.mcremove<br />
<br />
Details:<br />
<br />
This command is used to remove a user from the database. Using /mcremove nossr50 will remove nossr50 from the database.<br />
<br />
Back to Top<br />
<br />
•skillreset Command<br />
<br />
Description:<br />
<br />
Reset the level of one or all of your skills.<br />
<br />
Usage:<br />
<br />
/skillreset [player] <skill><br />
<br />
Aliases:<br />
<br />
none<br />
<br />
Permission:<br />
<br />
mcmmo.commands.skillreset<br />
mcmmo.commands.skillreset.acrobatics mcmmo.commands.skillreset.archery mcmmo.commands.skillreset.axes mcmmo.commands.skillreset.excavation mcmmo.commands.skillreset.fishing mcmmo.commands.skillreset.herbalism mcmmo.commands.skillreset.mining mcmmo.commands.skillreset.others.all mcmmo.commands.skillreset.repair mcmmo.commands.skillreset.smelting mcmmo.commands.skillreset.swords mcmmo.commands.skillreset.taming mcmmo.commands.skillreset.unarmed mcmmo.commands.skillreset.woodcutting<br />
<br />
Details:<br />
<br />
This command is used to reset a users skill level. Using /skillreset nossr50 herbalism will set nossr50's Herbalism level and experience to 0. Using /skillreset will reset your own stats for every skill.<br />
<br />
==•mcpurge Command==<br />
<br />
Description:<br />
<br />
Purge users with 0 powerlevel and/or who haven't connected in several months from the server DB.<br />
<br />
Usage:<br />
<br />
/mcpurge<br />
<br />
Aliases:<br />
<br />
none<br />
<br />
Permission:<br />
<br />
mcmmo.commands.mcpurge<br />
<br />
Details:<br />
<br />
Using /mcpurge will immediately start a purge run using the settings in the config file. By default mcMMO will purge all powerless users and users who haven't connected in the last 6 months.<br />
<br />
<br />
==•mcconvert Command==<br />
<br />
Description:<br />
<br />
Convert between different database and formula types.<br />
<br />
Usage:<br />
<br />
/mcconvert database <flatfile|sql> /mcconvert experience <linear|exponential><br />
<br />
Aliases:<br />
<br />
none<br />
<br />
Permission:<br />
<br />
mcmmo.commands.mcconvert<br />
<br />
Details:<br />
<br />
This command can be used to convert a flatfile database to MySQL, or the other way round. It is also used to convert from a linear XP formula to an exponential shaped formula curve.<br />
<br />
==• mcimport Command==<br />
<br />
Description:<br />
<br />
Automagically generate mod config files, ready to be filled in.<br />
<br />
Usage:<br />
<br />
/mcimport<br />
<br />
Aliases:<br />
<br />
none<br />
<br />
Permission:<br />
<br />
mcmmo.commands.mcimport<br />
<br />
Details:<br />
<br />
This command can be used to import and generate mod config files from your Cauldron server's startup log. You need to use at least 1.7.x for this to work.<br />
<br />
Create a folder called import inside /mcMMO/mods/. Place your latest Cauldron 1.7+ startup log in this folder and rename it to import.log.<br />
<br />
It is worth noting that it's advisable to create a short log by starting and stopping the server once, or by manually editing the log file to only include material mapping in order to speed up the import process.<br />
<br />
When the server is running, use the command /mcimport. You will see the import progress in the console, once it is done the files are created in /mcMMO/mods/output/.<br />
<br />
Any item that wasn't recognised gets placed in a .unknown.yml config file, you need to handle these manually.<br />
<br />
Now you should have a whole bunch of "empty" mod config files and you just need to fill in the XP gains.</div>Zhwhttps://mineplugin.org/index.php?title=%E6%A8%A1%E6%9D%BF:%E9%A6%96%E9%A1%B5/%E5%8A%A0%E5%85%A5%E6%88%91%E4%BB%AC&diff=1046模板:首页/加入我们2015-05-30T02:47:22Z<p>Zhw：</p>
<hr />
<div>'''我们的工作是？'''<br />
:我们致力于使更多'''服主'''更加深入地了解'''服务端'''的各种'''插件'''，使服主们更加容易地修改自己的服务器。<br />
<br />
'''为什么加入我们？'''<br />
:在这里，你可以和'''合作编写者'''们一同工作，参与过编写或是在过程中给予较大帮助的贡献者，便可在发布作品时将自己的用户名添加在'''鸣谢列表'''之中。<br />
<br />
'''如何加入我们？'''<br />
:如果你能达到'''(初中)国中毕业'''的英语水平(参考Minecraft Wiki参与编写要求)，或拥有一定的'''编程基础'''，便可加入我们，'''注册'''便可进行编辑。<br />
:为方便交流，可加入插件百科'''QQ讨论群'''，群号为223812289。你可以通过[http://www.twodam.net/wiki/Studio:%E5%AE%A1%E6%A0%B8 此处]测试自己的英语水平<br />
'''快速开始'''<br><br />
<br />
: 你可以先查看[http://www.mediawiki.org/wiki/Help:Contents/zh MediaWiki帮助]；<br />
:: 创建页面？可以从[[特殊:需要的页面|此处]]选择需要创建的页面，或是创建新的页面；<br />
:: 开始编辑？可以从[http://www.twodam.net/wiki/%E5%88%86%E7%B1%BB:%E5%BE%85%E5%AE%8C%E5%96%84 此处]选择需要被完善的页面，抑或是从[http://www.twodam.net/wiki/%E5%88%86%E7%B1%BB:%E5%BE%85%E7%BF%BB%E8%AF%91 此处]帮助翻译页面内容，从[http://www.twodam.net/wiki/%E5%88%86%E7%B1%BB:%E5%BE%85%E6%90%AC%E8%BF%90 此处]帮助搬运页面内容；</div>Zhwhttps://mineplugin.org/index.php?title=%E6%A8%A1%E6%9D%BF:%E9%A6%96%E9%A1%B5/%E5%8A%A0%E5%85%A5%E6%88%91%E4%BB%AC&diff=940模板:首页/加入我们2015-03-29T02:08:38Z<p>Zhw：</p>
<hr />
<div>'''我们的工作是？'''<br />
:我们致力于使更多'''服主'''更加深入地了解'''服务端'''的各种'''插件'''，使服主们更加容易地修改自己的服务器。<br />
<br />
'''为什么加入我们？'''<br />
:在这里，你可以和'''合作编写者'''们一同工作，参与过编写或是在过程中给予较大帮助的贡献者，便可在发布作品时将自己的用户名添加在'''鸣谢列表'''之中。<br />
<br />
'''如何加入我们？'''<br />
:如果你能达到'''(初中)国中毕业'''的英语水平(参考Minecraft Wiki参与编写要求)，或拥有一定的'''编程基础'''，便可加入我们，'''注册'''便可进行编辑。<br />
:为方便交流，可加入插件百科'''QQ讨论群'''，群号为223812289。<br />
:新用户是无法自助注册的，请加群后联系管理员进行添加。<br />
<br />
'''快速开始'''<br><br />
<br />
: 你可以先查看[http://www.mediawiki.org/wiki/Help:Contents/zh MediaWiki帮助]；<br />
:: 创建页面？可以从[[特殊:需要的页面|此处]]选择需要创建的页面，或是创建新的页面；<br />
:: 开始编辑？可以从[http://www.twodam.net/wiki/%E5%88%86%E7%B1%BB:%E5%BE%85%E5%AE%8C%E5%96%84 此处]选择需要被完善的页面，抑或是从[http://www.twodam.net/wiki/%E5%88%86%E7%B1%BB:%E5%BE%85%E7%BF%BB%E8%AF%91 此处]帮助翻译页面内容，从[http://www.twodam.net/wiki/%E5%88%86%E7%B1%BB:%E5%BE%85%E6%90%AC%E8%BF%90 此处]帮助搬运页面内容；</div>Zhwhttps://mineplugin.org/index.php?title=%E6%A8%A1%E6%9D%BF:%E9%A6%96%E9%A1%B5/%E5%8A%A0%E5%85%A5%E6%88%91%E4%BB%AC&diff=939模板:首页/加入我们2015-03-29T02:08:13Z<p>Zhw：</p>
<hr />
<div>'''我们的工作是？'''<br />
:我们致力于使更多'''服主'''更加深入地了解'''服务端'''的各种'''插件'''，使服主们更加容易地修改自己的服务器。<br />
<br />
'''为什么加入我们？'''<br />
:在这里，你可以和'''合作编写者'''们一同工作，参与过编写或是在过程中给予较大帮助的贡献者，便可在发布作品时将自己的用户名添加在'''鸣谢列表'''之中。<br />
<br />
'''如何加入我们？'''<br />
:如果你能达到'''(初中)国中毕业'''的英语水平(参考Minecraft Wiki参与编写要求)，或拥有一定的'''编程基础'''，便可加入我们，'''注册'''便可进行编辑。<br />
:为方便交流，可加入插件百科'''QQ讨论群'''，群号为223812289。<br />
:新用户是无法自助注册的，请加群后联系管理员进行添加。<br />
<br />
'''快速开始'''<br><br />
<br />
: 你可以先查看[http://www.mediawiki.org/wiki/Help:Contents/zh MediaWiki帮助]；<br />
:: 创建页面？可以从[[特殊:需要的页面|此处]]选择需要创建的页面，或是创建新的页面；<br />
:: 开始编辑？可以从[http://www.twodam.net/wiki/%E5%88%86%E7%B1%BB:%E5%BE%85%E5%AE%8C%E5%96%84 此处]选择需要被完善的页面，抑或是从[http://www.twodam.net/wiki/%E5%88%86%E7%B1%BB:%E5%BE%85%E7%BF%BB%E8%AF%91 此处]帮助翻译页面内容<br />
从[http://www.twodam.net/wiki/%E5%88%86%E7%B1%BB:%E5%BE%85%E6%90%AC%E8%BF%90 此处]帮助搬运页面内容；</div>Zhwhttps://mineplugin.org/index.php?title=%E7%94%A8%E6%88%B7:Zhw&diff=886用户:Zhw2015-03-14T03:39:32Z<p>Zhw：</p>
<hr />
<div>我是zhw。（以下是学生的介绍，除了最后一行之外是直接copy的）<br />
小周qq983156225<br />
关于我自己，不知道从哪儿开始讲好啊，我有这么几个称号“''坐标系之王''”得名于对于坐标系的亲切度，“''辣条守护者''”给同学们吃辣条的家伙“''导师小周''”专门给MC好友们指路<br />
<br />
六班习惯叫我小周，一班叫我周爷，四班叫我周周（what？），我们班叫我副班<br />
<br />
我是罕见的稀有物种，不但吃吃不胖，晒晒不黑，长得高长得白长得帅（不丑），能认东南西北，能记电话号码，会烧菜会家务（好男人啊），最后在这个自拍泛滥的时代我是罕见的照片比真人难看的人。<br />
<br />
看书，看什么书，长篇小说的看过斗罗大陆第一第二部，看过斗破苍穹，最近在看''冰与火之歌''（特喜欢！）。我阅读过很多著作但是了解颇浅（记得住故事记不住名字之类的）中华上下五千年啊，全球通史啊，看过的历史和科学书很多但是记住的不多，最深刻的数”啊哈灵机一动“那可真是啊哈，还有几本我很喜爱的书写给孩子的哲学书，美德书，乔布斯传这些。<br />
<br />
看视频，动漫看进击，死神，火影，''海贼''，刀剑还有''JOJO''，美剧看''闪电侠''，''绿箭侠''，神盾局，''权力的游戏''（就是冰火歌，也很喜欢！）。国内电视剧连同电视节目基本一个不看（绝对不会追），对漫威和DC出的超级英雄电影必看，绿灯，超人，复联什么的（''还特别喜欢看漫画''）。还看过一个脑洞及其大的动漫飞哥与小佛。<br />
哈哈，平常在同学面前一副脑洞大得不能再大的样子（绝对，绝对，绝对逗到不能想象），成绩过得去（千年老三）<br />
<br />
网上就变成准大神了，给广大MC好友指路，我已经玩我的世界两年余，而且六个月前第一次上服务器玩耍，但现在已经基本广知各项服务器设置和MC知识，有自己的群365053669服务器插件讨论（™就是来问我问题的）群，mcbbsID”''矿工小周''“。还接触了MC插件百科的翻译。http://www.twodam.net/wiki/%E9%A6%96%E9%A1%B5</div>Zhwhttps://mineplugin.org/index.php?title=ChestShop&diff=880ChestShop2015-02-25T10:24:16Z<p>Zhw：以“{{待搬运}} http://dev.bukkit.org/bukkit-plugins/chestshop/”为内容创建页面</p>
<hr />
<div>{{待搬运}}<br />
http://dev.bukkit.org/bukkit-plugins/chestshop/</div>Zhwhttps://mineplugin.org/index.php?title=Citizens&diff=879Citizens2015-02-25T10:22:54Z<p>Zhw：以“{{待搬运}} http://dev.bukkit.org/bukkit-plugins/citizens/”为内容创建页面</p>
<hr />
<div>{{待搬运}}<br />
http://dev.bukkit.org/bukkit-plugins/citizens/</div>Zhwhttps://mineplugin.org/index.php?title=McMMO&diff=878McMMO2015-02-25T10:22:18Z<p>Zhw：以“{{待搬运}} http://dev.bukkit.org/bukkit-plugins/mcmmo/”为内容创建页面</p>
<hr />
<div>{{待搬运}}<br />
http://dev.bukkit.org/bukkit-plugins/mcmmo/</div>Zhwhttps://mineplugin.org/index.php?title=Dynmap&diff=877Dynmap2015-02-25T10:21:38Z<p>Zhw：以“{{待搬运}} http://dev.bukkit.org/bukkit-plugins/?search=Dynmap”为内容创建页面</p>
<hr />
<div>{{待搬运}}<br />
http://dev.bukkit.org/bukkit-plugins/?search=Dynmap</div>Zhwhttps://mineplugin.org/index.php?title=ProtocolLib&diff=876ProtocolLib2015-02-25T10:17:45Z<p>Zhw：</p>
<hr />
<div>{{待搬运}}<br />
Contents<br />
===定义===<br />
====数据类型====<br />
====定点数====<br />
====其它的定义====<br />
<br />
===数据包===<br />
====协议版本====<br />
===数据包格式===<br />
===Handshaking===<br />
====Serverbound====<br />
=====Handshake=====<br />
===Play===<br />
====Clientbound====<br />
=====存活=====<br />
=====加入游戏=====<br />
=====聊天消息=====<br />
5.1.4 Time Update<br />
5.1.5 Entity Equipment<br />
5.1.6 Spawn Position<br />
5.1.7 Update Health<br />
5.1.8 Respawn<br />
5.1.9 Player Position And Look<br />
5.1.10 Held Item Change<br />
5.1.11 Use Bed<br />
5.1.12 Animation<br />
5.1.13 Spawn Player<br />
5.1.14 Collect Item<br />
5.1.15 Spawn Object<br />
5.1.16 Spawn Mob<br />
5.1.17 Spawn Painting<br />
5.1.18 Spawn Experience Orb<br />
5.1.19 Entity Velocity<br />
5.1.20 Destroy Entities<br />
5.1.21 Entity<br />
5.1.22 Entity Relative Move<br />
5.1.23 Entity Look<br />
5.1.24 Entity Look and Relative Move<br />
5.1.25 Entity Teleport<br />
5.1.26 Entity Head Look<br />
5.1.27 Entity Status<br />
5.1.28 Attach Entity<br />
5.1.29 Entity Metadata<br />
5.1.30 Entity Effect<br />
5.1.31 Remove Entity Effect<br />
5.1.32 Set Experience<br />
5.1.33 Entity Properties<br />
5.1.34 Chunk Data<br />
5.1.35 Multi Block Change<br />
5.1.36 Block Change<br />
5.1.37 Block Action<br />
5.1.38 Block Break Animation<br />
5.1.39 Map Chunk Bulk<br />
5.1.40 Explosion<br />
5.1.41 Effect<br />
5.1.41.1<br />
Effects<br />
5.1.42 Sound Effect<br />
5.1.43 Particle<br />
5.1.44 Change Game State<br />
5.1.45 Spawn Global Entity<br />
5.1.46 Open Window<br />
5.1.47 Close Window<br />
5.1.48 Set Slot<br />
5.1.49 Window Items<br />
5.1.50 Window Property<br />
5.1.51 Confirm Transaction<br />
5.1.52 Update Sign<br />
5.1.53 Maps<br />
5.1.54 Update Block Entity<br />
5.1.55 Sign Editor Open<br />
5.1.56<br />
Statistics<br />
5.1.57 Player List Item<br />
5.1.58 Player Abilities<br />
5.1.59 Tab-Complete<br />
5.1.60<br />
Scoreboard Objective<br />
5.1.61 Update Score<br />
5.1.62 Display Scoreboard<br />
5.1.63 Teams<br />
5.1.64 Plugin Message<br />
5.1.65<br />
Disconnect<br />
5.2 Serverbound<br />
5.2.1 Keep Alive<br />
5.2.2 Chat Message<br />
5.2.3 Use Entity<br />
5.2.4 Player<br />
5.2.5 Player Position<br />
5.2.6 Player Look<br />
5.2.7 Player Position And Look<br />
5.2.8 Player Digging<br />
5.2.9 Player Block Placement<br />
5.2.10 Held Item Change<br />
5.2.11 Animation<br />
5.2.12 Entity Action<br />
5.2.13 Steer Vehicle<br />
5.2.14 Close Window<br />
5.2.15 Click Window<br />
5.2.16 Confirm Transaction<br />
5.2.17 Creative Inventory Action<br />
5.2.18 Enchant Item<br />
5.2.19 Update Sign<br />
5.2.20 Player Abilities<br />
5.2.21 Tab-Complete<br />
5.2.22 Client Settings<br />
5.2.23 Client Status<br />
5.2.24 Plugin Message<br />
6 Status<br />
6.1 Clientbound<br />
6.1.1 Response<br />
6.1.2 Ping<br />
6.2 Serverbound<br />
6.2.1 Request<br />
6.2.2 Ping<br />
7 Login<br />
7.1 Clientbound<br />
7.1.1 Disconnect<br />
7.1.2 Encryption Request<br />
7.1.3 Login Success<br />
7.2 Serverbound<br />
7.2.1 Login Start<br />
7.2.2 Encryption Response<br />
8 See Also</div>Zhwhttps://mineplugin.org/index.php?title=MobArena&diff=875MobArena2015-02-24T16:04:37Z<p>Zhw：/* 建造一个竞技场 */</p>
<hr />
<div>{{待搬运}}<br />
{{Bukkit Plugin Infobox<br />
|版本=v0.96.9<br />
|兼容服务端版本=1.8.1<br />
|网址=http://dev.bukkit.org/bukkit-plugins/mobarena/}}<br />
[[Category:娱乐]][[Category:机械]]<br />
=安装=<br />
安装MobArena其实很简单，只需以下四步:<br />
*关闭服务器<del>咳咳，当然是关你自己的服务器啦</del>.<br />
*从论坛主题或是Bukkit Dev站点的项目页下载jar文件.<br />
*将jar文件拖入服务端的plugins文件夹中.<br />
*重启服务端. <br />
之后，配置文件 (config.yml) 以及一个宣告文本(announcements.yml) 会自动创建在plugins/MobArena/路径下.<br />
文件结构如下:<br />
<br />
plugins/<br />
MobArena.jar<br />
MobArena/<br />
config.yml<br />
announcements.yml<br />
此时此刻, 或许你想直接开始设置竞技场, 但是你需要先看看配置文件，并把它配置成你喜欢的样子<del>就是说，还是根据情况配置一下吧</del>. 你可以在配置文件自定义MobArena的设置，职业，奖励，波数（怪物类型）<br />
<br />
=建立竞技场=<br />
==建造一个竞技场==<br />
完整的竞技场应该包含一个可以选择职业的准备区域，一个竞技场地以及观察点(离开点) <br />
下面是各个选项的讲解<br />
<br />
大厅：<br />
玩家加入游戏之前将会在大厅选择职业.一个建造好的游戏大厅会有每一个职业的选择牌子，玩家通过点击牌子可以获取一个职业, 还有一个铁块, 玩家可以通过点击铁块来表示他们已经准备好开始游戏.牌子必须在第一行写上职业的名字（区分大小写）,但是无论你在另外三行上写什么，都不会被怪物竞技场识别，你是不能写上 ,所以你不会得到确认的信息（如果有，那是另一个插件）<br />
<br />
竞技场地：<br />
这里是玩家和怪物搏斗的地方.竞技场地会有墙，可能会有一个屋顶 , 这样玩家和怪物就不能跑出去了. 这使得玩家们不会只是在竞技场外闲逛。.<br />
<br />
观察点: <br />
当玩家想要观看一场战斗时,他们可以使用/ma spec 命令来传送到竞技场的观察点. 这同样也是竞技场中玩家死去后会传送到的地方,前提是在配置文件中，把 spectate-after-death设置为ture. 这块区域要保证观看者不能走出去闲逛（进入竞技场地或者离远竞技场）因为在观看过程中，玩家是无敌的.<br />
<br />
离开点: <br />
在使用 /ma leave命令后,玩家和观察者会被传送到原来所在的地方,除非竞技场有一个离开点(只是可选). 使用离开点,可以准确控制玩家在游戏后去何处.<br />
<br />
关于区域，传送点等，<br />
<br />
当竞技场建好后，就是设置怪物竞技场的区域和传送点的时候了。在设置它们前，我们先来看看他们有什么作用.<br />
<br />
区域: <br />
一个竞技场需要一个竞技区域,然后还可以有一个准备区域，怪物竞技场会使用这些区域来确保玩家不会作弊（通过破坏竞技场来走出区域）,然后确保怪物竞技场所产生的怪物会在里面产生. 怪物竞技场非常排外（不要局外人）, 所以也最好把不想要的生物排除在外. 区域是通过区域工具来设置的.<br />
<br />
传送点: <br />
当玩家加入一个怪物竞技场的游戏时，他们会被传送到准备区域中的准备点来选择职业和准备开始游戏（通过点击铁块）.当每个人都准备好的时候，玩家会被传送到竞技场内的竞技场出生点。观察者会被传送到竞技场的观察点来进入观察区域,当游戏结束的时候，玩家和观察者会被传送到他们传送来之前的地方，或者去可选的离开点,传送点会用传送点工具来设置。.<br />
<br />
出生点: <br />
这里的出生点指的是怪物出生的地点.怪物竞技场只会在附近有玩家的出生点产出怪物（十五个方格的半径）.需要注意的是，怪物的数量不随着按照出生点的数量改变，只会因为在配置文件中波数的倍率改变和玩家的数量所改变.出生点可以通过出生点工具来设置。.<br />
<br />
容器: <br />
容器的就是竞技场里的箱子的位置，回收站等。 which contain items that will be renewed when the arena ends. Only registered containers will have their contents <br />
renewed, so it is not enough to simply put a chest in the arena - it also needs to be registered using the Chests tool.<br />
<br />
==设置模式==<br />
We will set up the arena using Setup Mode. When we enter Setup Mode, MobArena will temporarily store our inventory and give us a set of golden tools (the Toolbox), each with a different function. 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.<br />
<br />
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.<br />
<br />
To leave Setup Mode: Type done.<br />
<br />
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.<br />
<br />
In the next section, we will take a look at the different commands available in Setup Mode...<br />
<br />
==设置模式的命令==<br />
<br />
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.<br />
<br />
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.<br />
<br />
done<br />
Leave Setup Mode.<br />
Aliases: end stop done quit<br />
<br />
help<br />
Display help screen.<br />
Aliases: ? h<br />
<br />
missing<br />
Display a list of missing (mandatory) regions, warps, and points.<br />
This command is useful if you have forgotten how far you are in the setup process, and what you still need to set up.<br />
Aliases: miss<br />
<br />
expand <region> <amount> <direction><br />
Expand a region by some amount in some direction.<br />
Valid regions: ar for the arena region, or lr for the lobby region<br />
Valid amounts: positive integers (whole numbers)<br />
Valid directions: up, down, or out<br />
Example: expand ar 5 up<br />
Aliases: exp<br />
<br />
show [<region>|<warp>|<point>]<br />
Show a region, warp, or point(s) as red wool blocks.<br />
Valid regions: ar for the arena region, or lr for the lobby region<br />
Valid warps: arena, lobby, spec, exit<br />
Valid points: spawns (or just sp) for spawnpoints, chests (or just c) for chests<br />
Example: show sp<br />
<br />
==设置时的工具==<br />
<br />
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.<br />
<br />
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.<br />
<br />
===区域工具===<br />
<br />
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.<br />
<br />
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.<br />
<br />
Left-click: Set the first point to be the location of the target block<br />
Right-click: Set the second point to be the location of the target block<br />
<br />
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.<br />
<br />
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.<br />
<br />
===玩家传送点工具===<br />
<br />
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.<br />
<br />
Left-click: Set the currently selected warp on top of the target block<br />
Right-click: Cycle between available warps<br />
<br />
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.<br />
<br />
Note: The arena, lobby, and spectator warps are all required. The exit warp is optional.<br />
<br />
===怪物产生点工具===<br />
<br />
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.<br />
<br />
Left-click: Add a spawnpoint on top of the target block<br />
Right-click: Remove the spawnpoint on top of the target block (if the spawnpoint exists)<br />
<br />
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.<br />
<br />
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.<br />
<br />
===容器工具===<br />
<br />
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.<br />
<br />
Left-click: Register the clicked container (if it wasn't registered)<br />
Right-click: Unregister the clicked container (if it was registered)<br />
<br />
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.<br />
<br />
=命令=<br />
==玩家命令==<br />
<br />
These commands can be issued by all players. They include joining, leaving, spectating and listing arenas as well as listing players.<br />
<br />
/ma join (<arena>) or /ma j (<arena>) - Join the arena with the given name.<br />
/ma leave or /ma l - Leave the current arena, or the spectator area.<br />
/ma notready - Get a list of all players who aren't ready.<br />
/ma spec (<arena>) or /ma s (<arena>) - Spectate the arena with the given name.<br />
/ma arenas - Get a list of all arenas. Green names are enabled, gray names are disabled.<br />
/ma players - Get a list of all arena players.<br />
/ma players <arena> - Get a list of arena players in the specified arena.<br />
/ma class <class> - While in the lobby, manually pick the given class instead of punching signs.<br />
==管理员指令==<br />
<br />
Only ops and the console can issue these commands. They include forcefully starting or ending arenas, enabling/disabling individual arenas or MobArena entirely.<br />
<br />
/ma enable - Enable MobArena.<br />
/ma disable - Disable MobArena.<br />
/ma enable <arena> - Enable the arena with the specified name.<br />
/ma disable <arena> - Disable the arena with the specified name.<br />
/ma force end - Forcefully end all arenas.<br />
/ma force end <arena> - Forcefully end the arena with the specified name; forces all players to leave. <br />
/ma force start <arena> - Forcefully start the arena with the specified name; forces all players who aren't ready to leave.<br />
/ma notready <arena> - Get a list of all players in the given arena who aren't ready.<br />
/ma restore <player> - Restore the inventory of the player with the given name, if possible.<br />
/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.<br />
==建设指令==<br />
<br />
Only ops (and the console, if it makes sense) can issue these commands. They include setting warp points, spawnpoints and region points.<br />
<br />
/ma setup <arena> - Enter Setup Mode for the given arena.<br />
/ma addarena <arena> - Create a new arena-node in the current world.<br />
/ma delarena <arena> - Delete the arena with the given name.<br />
/ma editarena <arena> - Toggle Edit Mode for the given arena.<br />
/ma editarena <arena> [true|false] - Turn on or off Edit Mode for the given arena.<br />
/ma setting <arena> - List all per-arena settings for the given arena.<br />
/ma setting <arena> <setting> - Check the current value of the given setting for the given arena.<br />
/ma setting <arena> <setting> <value> - Set the value of the given setting for the given arena to the given value.<br />
/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 <br />
points in your arena are actually covered by spawnpoints or not.<br />
/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<br />
chest, regardless of any local class chests in arena lobbies. This is useful if you want a global class chest for a class.<br />
/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.<br />
/ma auto-degenerate <arena> - Degenerate the arena with the given name, effectively restoring the patch that was "bulldozed" with the auto-generator.<br />
<br />
=权限=<br />
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.<br />
<br />
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!<br />
<br />
==竞技场权限==<br />
<br />
Did you read the note at the top? If not, read it before you continue.<br />
<br />
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.<br />
<br />
bPermissions: ^mobarena.arenas.default<br />
GroupManager: -mobarena.arenas.default<br />
zPermissions: mobarena.arenas.default: false<br />
<br />
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.<br />
<br />
Still confused? Check the sample setup at the bottom of the page!<br />
<br />
==职业权限==<br />
<br />
Did you read the note at the top? If not, read it before you continue.<br />
<br />
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.<br />
<br />
bPermissions: ^mobarena.classes.knight<br />
GroupManager: -mobarena.classes.knight<br />
zPermissions: mobarena.classes.knight: false<br />
<br />
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.<br />
<br />
As with arenas, I recommend letting everyone enjoy all the classes, unless you have a special reason not to.<br />
<br />
Still confused? Check the sample setup at the bottom of the page!<br />
<br />
==命令权限==<br />
<br />
Did you read the note at the top? If not, read it before you continue.<br />
<br />
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!<br />
<br />
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.<br />
<br />
mobarena.use.join<br />
mobarena.use.leave<br />
mobarena.use.spec<br />
mobarena.use.arenalist<br />
mobarena.use.playerlist<br />
mobarena.use.notready<br />
mobarena.use.class<br />
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.<br />
<br />
mobarena.admin.enable<br />
mobarena.admin.kick<br />
mobarena.admin.restore<br />
mobarena.admin.force<br />
mobarena.admin.teleport<br />
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.<br />
<br />
mobarena.setup.config<br />
mobarena.setup.setup<br />
mobarena.setup.setting<br />
mobarena.setup.addarena<br />
mobarena.setup.removearena<br />
mobarena.setup.editarena<br />
mobarena.setup.spawnpoints<br />
mobarena.setup.containers<br />
mobarena.setup.checkdata<br />
mobarena.setup.checkspawns<br />
mobarena.setup.classchest<br />
mobarena.setup.classes<br />
mobarena.setup.leaderboards<br />
mobarena.setup.autogenerate<br />
mobarena.setup.autodegenerate<br />
Sample setup<br />
<br />
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...<br />
<br />
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:<br />
<br />
default-aux: <-- This is the auxiliary group that is to<br />
permissions: be inherited by the default group and<br />
- essentials.balance the donor group. It is not used for<br />
- essentials.pay anything else.<br />
- essentials.sell<br />
<br />
default: <-- This is the default group. It inherits<br />
inherits: default-aux from default-aux, but also revokes the<br />
permissions: permission for the special class.<br />
- -mobarena.classes.diamondknight<br />
<br />
donor: <-- This is the donor group, which also<br />
inherits: default-aux inherits from default-aux, but it<br />
permissions: does not revoke any class permissions,<br />
- essentials.balance.others which means it has access to all of<br />
- essentials.kit them by default.<br />
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.<br />
=物品语法（Item Syntax待搬运）=<br />
=职业箱子（Class Chests待搬运｝=<br />
=怪物波设置（Formulas待搬运）=<br />
=怪物种类（Monster types待搬运）=<br />
以上内容搬运自英文wiki[https://github.com/garbagemule/MobArena/wiki]</div>Zhwhttps://mineplugin.org/index.php?title=MobArena&diff=874MobArena2015-02-21T11:52:08Z<p>Zhw：/* 建造一个竞技场 */</p>
<hr />
<div>{{待搬运}}<br />
{{Bukkit Plugin Infobox<br />
|版本=v0.96.9<br />
|兼容服务端版本=1.8.1<br />
|网址=http://dev.bukkit.org/bukkit-plugins/mobarena/}}<br />
[[Category:娱乐]][[Category:机械]]<br />
=安装=<br />
安装MobArena其实很简单，只需以下四步:<br />
*关闭服务器<del>咳咳，当然是关你自己的服务器啦</del>.<br />
*从论坛主题或是Bukkit Dev站点的项目页下载jar文件.<br />
*将jar文件拖入服务端的plugins文件夹中.<br />
*重启服务端. <br />
之后，配置文件 (config.yml) 以及一个宣告文本(announcements.yml) 会自动创建在plugins/MobArena/路径下.<br />
文件结构如下:<br />
<br />
plugins/<br />
MobArena.jar<br />
MobArena/<br />
config.yml<br />
announcements.yml<br />
此时此刻, 或许你想直接开始设置竞技场, 但是你需要先看看配置文件，并把它配置成你喜欢的样子<del>就是说，还是根据情况配置一下吧</del>. 你可以在配置文件自定义MobArena的设置，职业，奖励，波数（怪物类型）<br />
<br />
=建立竞技场=<br />
==建造一个竞技场==<br />
完整的竞技场应该包含一个可以选择职业的准备区域，一个竞技场地以及观察点(离开点) <br />
下面是各个选项的讲解<br />
<br />
大厅：<br />
玩家加入游戏之前将会在大厅选择职业.一个建造好的游戏大厅会有每一个职业的选择牌子，玩家通过点击牌子可以获取一个职业, 还有一个铁块, 玩家可以通过点击铁块来表示他们已经准备好开始游戏.牌子必须在第一行写上职业的名字（区分大小写）,但是无论你在另外三行上写什么，都不会被怪物竞技场识别，你是不能写上 ,所以你不会得到确认的信息（如果有，那是另一个插件）<br />
<br />
竞技场地：<br />
这里是玩家和怪物搏斗的地方.竞技场地会有墙，可能会有一个屋顶 , 这样玩家和怪物就不能跑出去了. 这使得玩家们不会只是在竞技场外闲逛。.<br />
<br />
观察点: <br />
当玩家想要观看一场战斗时,他们可以使用/ma spec 命令来传送到竞技场的观察点. 这同样也是竞技场中玩家死去后会传送到的地方,前提是在配置文件中，把 spectate-after-death设置为ture. 这块区域要保证观看者不能走出去闲逛（进入竞技场地或者离远竞技场）因为在观看过程中，玩家是无敌的.<br />
<br />
离开点: <br />
在使用 /ma leave命令后,玩家和观察者会被传送到原来所在的地方,除非竞技场有一个离开点(只是可选). 使用离开点,可以准确控制玩家在游戏后去何处.<br />
<br />
关于区域，传送点等，<br />
<br />
当竞技场建好后，就是设置怪物竞技场的区域和传送点的时候了。在设置它们前，我们先来看看他们有什么作用.<br />
<br />
区域: <br />
一个竞技场需要一个竞技区域,然后还可以有一个准备区域，怪物竞技场会使用这些区域来确保玩家不会作弊（通过破坏竞技场来走出区域）,然后确保怪物竞技场所产生的怪物会在里面产生. 怪物竞技场非常排外（不要局外人）, 所以也最好把不想要的生物排除在外. 区域是通过区域工具来设置的.<br />
<br />
传送点: <br />
当玩家加入一个怪物竞技场的游戏时，他们会被传送到准备区域中的准备点来选择职业和准备开始游戏（通过点击铁块）.当每个人都准备好的时候，玩家会被传送到竞技场内的竞技场出生点。观察者会被传送到竞技场的观察点来进入观察区域,当游戏结束的时候，玩家和观察者会被传送到他们传送来之前的地方，或者去可选的离开点,传送点会用传送点工具来设置。.<br />
<br />
出生点: <br />
这里的出生点指的是怪物出生的地点.怪物竞技场只会在附近有玩家的出生点产出怪物（十五个方格的半径）.需要注意的是，怪物的数量不随着按照出生点的数量改变，只会因为在配置文件中波数的倍率改变和玩家的数量所改变.出生点可以通过出生点工具来设置。.<br />
<br />
Containers: <br />
The containers of an arena are locations of chests, dispensers, etc. which contain items that will be renewed when the arena ends. Only registered containers will have their contents <br />
renewed, so it is not enough to simply put a chest in the arena - it also needs to be registered using the Chests tool.<br />
<br />
==设置模式==<br />
We will set up the arena using Setup Mode. When we enter Setup Mode, MobArena will temporarily store our inventory and give us a set of golden tools (the Toolbox), each with a different function. 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.<br />
<br />
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.<br />
<br />
To leave Setup Mode: Type done.<br />
<br />
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.<br />
<br />
In the next section, we will take a look at the different commands available in Setup Mode...<br />
<br />
==设置模式的命令==<br />
<br />
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.<br />
<br />
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.<br />
<br />
done<br />
Leave Setup Mode.<br />
Aliases: end stop done quit<br />
<br />
help<br />
Display help screen.<br />
Aliases: ? h<br />
<br />
missing<br />
Display a list of missing (mandatory) regions, warps, and points.<br />
This command is useful if you have forgotten how far you are in the setup process, and what you still need to set up.<br />
Aliases: miss<br />
<br />
expand <region> <amount> <direction><br />
Expand a region by some amount in some direction.<br />
Valid regions: ar for the arena region, or lr for the lobby region<br />
Valid amounts: positive integers (whole numbers)<br />
Valid directions: up, down, or out<br />
Example: expand ar 5 up<br />
Aliases: exp<br />
<br />
show [<region>|<warp>|<point>]<br />
Show a region, warp, or point(s) as red wool blocks.<br />
Valid regions: ar for the arena region, or lr for the lobby region<br />
Valid warps: arena, lobby, spec, exit<br />
Valid points: spawns (or just sp) for spawnpoints, chests (or just c) for chests<br />
Example: show sp<br />
<br />
==设置时的工具==<br />
<br />
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.<br />
<br />
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.<br />
<br />
===区域工具===<br />
<br />
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.<br />
<br />
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.<br />
<br />
Left-click: Set the first point to be the location of the target block<br />
Right-click: Set the second point to be the location of the target block<br />
<br />
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.<br />
<br />
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.<br />
<br />
===玩家传送点工具===<br />
<br />
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.<br />
<br />
Left-click: Set the currently selected warp on top of the target block<br />
Right-click: Cycle between available warps<br />
<br />
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.<br />
<br />
Note: The arena, lobby, and spectator warps are all required. The exit warp is optional.<br />
<br />
===怪物产生点工具===<br />
<br />
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.<br />
<br />
Left-click: Add a spawnpoint on top of the target block<br />
Right-click: Remove the spawnpoint on top of the target block (if the spawnpoint exists)<br />
<br />
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.<br />
<br />
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.<br />
<br />
===容器工具===<br />
<br />
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.<br />
<br />
Left-click: Register the clicked container (if it wasn't registered)<br />
Right-click: Unregister the clicked container (if it was registered)<br />
<br />
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.<br />
<br />
=命令=<br />
==玩家命令==<br />
<br />
These commands can be issued by all players. They include joining, leaving, spectating and listing arenas as well as listing players.<br />
<br />
/ma join (<arena>) or /ma j (<arena>) - Join the arena with the given name.<br />
/ma leave or /ma l - Leave the current arena, or the spectator area.<br />
/ma notready - Get a list of all players who aren't ready.<br />
/ma spec (<arena>) or /ma s (<arena>) - Spectate the arena with the given name.<br />
/ma arenas - Get a list of all arenas. Green names are enabled, gray names are disabled.<br />
/ma players - Get a list of all arena players.<br />
/ma players <arena> - Get a list of arena players in the specified arena.<br />
/ma class <class> - While in the lobby, manually pick the given class instead of punching signs.<br />
==管理员指令==<br />
<br />
Only ops and the console can issue these commands. They include forcefully starting or ending arenas, enabling/disabling individual arenas or MobArena entirely.<br />
<br />
/ma enable - Enable MobArena.<br />
/ma disable - Disable MobArena.<br />
/ma enable <arena> - Enable the arena with the specified name.<br />
/ma disable <arena> - Disable the arena with the specified name.<br />
/ma force end - Forcefully end all arenas.<br />
/ma force end <arena> - Forcefully end the arena with the specified name; forces all players to leave. <br />
/ma force start <arena> - Forcefully start the arena with the specified name; forces all players who aren't ready to leave.<br />
/ma notready <arena> - Get a list of all players in the given arena who aren't ready.<br />
/ma restore <player> - Restore the inventory of the player with the given name, if possible.<br />
/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.<br />
==建设指令==<br />
<br />
Only ops (and the console, if it makes sense) can issue these commands. They include setting warp points, spawnpoints and region points.<br />
<br />
/ma setup <arena> - Enter Setup Mode for the given arena.<br />
/ma addarena <arena> - Create a new arena-node in the current world.<br />
/ma delarena <arena> - Delete the arena with the given name.<br />
/ma editarena <arena> - Toggle Edit Mode for the given arena.<br />
/ma editarena <arena> [true|false] - Turn on or off Edit Mode for the given arena.<br />
/ma setting <arena> - List all per-arena settings for the given arena.<br />
/ma setting <arena> <setting> - Check the current value of the given setting for the given arena.<br />
/ma setting <arena> <setting> <value> - Set the value of the given setting for the given arena to the given value.<br />
/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 <br />
points in your arena are actually covered by spawnpoints or not.<br />
/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<br />
chest, regardless of any local class chests in arena lobbies. This is useful if you want a global class chest for a class.<br />
/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.<br />
/ma auto-degenerate <arena> - Degenerate the arena with the given name, effectively restoring the patch that was "bulldozed" with the auto-generator.<br />
<br />
=权限=<br />
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.<br />
<br />
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!<br />
<br />
==竞技场权限==<br />
<br />
Did you read the note at the top? If not, read it before you continue.<br />
<br />
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.<br />
<br />
bPermissions: ^mobarena.arenas.default<br />
GroupManager: -mobarena.arenas.default<br />
zPermissions: mobarena.arenas.default: false<br />
<br />
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.<br />
<br />
Still confused? Check the sample setup at the bottom of the page!<br />
<br />
==职业权限==<br />
<br />
Did you read the note at the top? If not, read it before you continue.<br />
<br />
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.<br />
<br />
bPermissions: ^mobarena.classes.knight<br />
GroupManager: -mobarena.classes.knight<br />
zPermissions: mobarena.classes.knight: false<br />
<br />
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.<br />
<br />
As with arenas, I recommend letting everyone enjoy all the classes, unless you have a special reason not to.<br />
<br />
Still confused? Check the sample setup at the bottom of the page!<br />
<br />
==命令权限==<br />
<br />
Did you read the note at the top? If not, read it before you continue.<br />
<br />
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!<br />
<br />
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.<br />
<br />
mobarena.use.join<br />
mobarena.use.leave<br />
mobarena.use.spec<br />
mobarena.use.arenalist<br />
mobarena.use.playerlist<br />
mobarena.use.notready<br />
mobarena.use.class<br />
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.<br />
<br />
mobarena.admin.enable<br />
mobarena.admin.kick<br />
mobarena.admin.restore<br />
mobarena.admin.force<br />
mobarena.admin.teleport<br />
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.<br />
<br />
mobarena.setup.config<br />
mobarena.setup.setup<br />
mobarena.setup.setting<br />
mobarena.setup.addarena<br />
mobarena.setup.removearena<br />
mobarena.setup.editarena<br />
mobarena.setup.spawnpoints<br />
mobarena.setup.containers<br />
mobarena.setup.checkdata<br />
mobarena.setup.checkspawns<br />
mobarena.setup.classchest<br />
mobarena.setup.classes<br />
mobarena.setup.leaderboards<br />
mobarena.setup.autogenerate<br />
mobarena.setup.autodegenerate<br />
Sample setup<br />
<br />
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...<br />
<br />
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:<br />
<br />
default-aux: <-- This is the auxiliary group that is to<br />
permissions: be inherited by the default group and<br />
- essentials.balance the donor group. It is not used for<br />
- essentials.pay anything else.<br />
- essentials.sell<br />
<br />
default: <-- This is the default group. It inherits<br />
inherits: default-aux from default-aux, but also revokes the<br />
permissions: permission for the special class.<br />
- -mobarena.classes.diamondknight<br />
<br />
donor: <-- This is the donor group, which also<br />
inherits: default-aux inherits from default-aux, but it<br />
permissions: does not revoke any class permissions,<br />
- essentials.balance.others which means it has access to all of<br />
- essentials.kit them by default.<br />
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.<br />
=物品语法（Item Syntax待搬运）=<br />
=职业箱子（Class Chests待搬运｝=<br />
=怪物波设置（Formulas待搬运）=<br />
=怪物种类（Monster types待搬运）=<br />
以上内容搬运自英文wiki[https://github.com/garbagemule/MobArena/wiki]</div>Zhwhttps://mineplugin.org/index.php?title=MobArena&diff=873MobArena2015-02-19T11:46:27Z<p>Zhw：/* 建造一个竞技场 */</p>
<hr />
<div>{{待搬运}}<br />
{{Bukkit Plugin Infobox<br />
|版本=v0.96.9<br />
|兼容服务端版本=1.8.1<br />
|网址=http://dev.bukkit.org/bukkit-plugins/mobarena/}}<br />
[[Category:娱乐]][[Category:机械]]<br />
=安装=<br />
安装MobArena其实很简单，只需以下四步:<br />
*关闭服务器<del>咳咳，当然是关你自己的服务器啦</del>.<br />
*从论坛主题或是Bukkit Dev站点的项目页下载jar文件.<br />
*将jar文件拖入服务端的plugins文件夹中.<br />
*重启服务端. <br />
之后，配置文件 (config.yml) 以及一个宣告文本(announcements.yml) 会自动创建在plugins/MobArena/路径下.<br />
文件结构如下:<br />
<br />
plugins/<br />
MobArena.jar<br />
MobArena/<br />
config.yml<br />
announcements.yml<br />
此时此刻, 或许你想直接开始设置竞技场, 但是你需要先看看配置文件，并把它配置成你喜欢的样子<del>就是说，还是根据情况配置一下吧</del>. 你可以在配置文件自定义MobArena的设置，职业，奖励，波数（怪物类型）<br />
<br />
=建立竞技场=<br />
==建造一个竞技场==<br />
完整的竞技场应该包含一个可以选择职业的准备区域，一个竞技场地以及观察点(离开点) <br />
下面是各个选项的讲解<br />
<br />
大厅: <br />
玩家加入游戏之前将会在大厅选择职业.一个建造好的游戏大厅会有每一个职业的选择牌子，玩家通过点击牌子可以获取一个职业, 还有一个铁块, 玩家可以通过点击铁块来表示他们已经准备好开始游戏. The signs must have the name of the class on the first line (case-sensitive), but you canput whatever you want on the remaining three lines. Note that MobArena does not "register" class sign creation, so you will not get a confirmation message (if you do, it is another plugin interfering).<br />
<br />
Arena floor: <br />
This is where your players will be fighting monsters. The arena floor should be enclosed in walls, and possibly with a roof, such that the players and monsters have no way of getting out. This ensures that players won't be able to just wander out of the arena.<br />
<br />
Spectator area: <br />
When players want to spectate a session, they can use the /ma spec command to get warped to the spectator area of an arena. This is also where arena players are warped to when they die,if spectate-after-death: true in the config-file. The area should be designed so that it is not possible for the spectators to wander out (into the arena or away from the area), because spectators are invincible.<br />
<br />
Exit point: <br />
Upon typing /ma leave, arena players and spectators will be warped to the location they joined from, unless the arena has an exit warp (optional). Using exit points, it is possible to control exactly where players go after a session.<br />
<br />
About regions, warps, etc.<br />
<br />
Once our arena is built, it's time to set up the MobArena regions, warps, and points. Before we do so, let's take a look at what these things are and what MobArena uses them for...<br />
<br />
Regions: <br />
An arena needs an arena region, and optionally a lobby region. MobArena uses the arena region to make sure that players aren't cheating (by kicking them from the arena if they move outside the region), and to make sure that only MobArena's own mobs are spawned inside of it. MobArena is extremely xenophobic (afraid of strangers), so it tries its best to keep unwanted mobs out of the sessions. Regions are set using the Region tools.<br />
<br />
Warps: <br />
When players join a MobArena session, they are teleported to the lobby warp inside the lobby, where they will pick their class and ready up using the ready block (block of iron). When everyone is ready, the players are teleported to the arena warp inside of the arena. Spectators will be teleported to the spectator warp in the spectator area, and when players leave an arena, they will either be teleported to where they joined from, or to the exit warp, if it has been set up. Warps are set using the Warps tool.<br />
<br />
Spawnpoints: <br />
The spawnpoints of an arena are the locations where monsters can spawn from. MobArena will only spawn monsters from spawnpoints that have players nearby (in a 15-block radius). Note that<br />
the number of mobs spawned doesn't depend on how many spawnpoints an arena has - the number of mobs is determined by a formula (see Formulas) that only involves the wave number and <br />
player count (unless you use fixed amounts). Spawnpoints are added using the Spawnpoints tool.<br />
<br />
Containers: <br />
The containers of an arena are locations of chests, dispensers, etc. which contain items that will be renewed when the arena ends. Only registered containers will have their contents <br />
renewed, so it is not enough to simply put a chest in the arena - it also needs to be registered using the Chests tool.<br />
<br />
==设置模式==<br />
We will set up the arena using Setup Mode. When we enter Setup Mode, MobArena will temporarily store our inventory and give us a set of golden tools (the Toolbox), each with a different function. 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.<br />
<br />
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.<br />
<br />
To leave Setup Mode: Type done.<br />
<br />
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.<br />
<br />
In the next section, we will take a look at the different commands available in Setup Mode...<br />
<br />
==设置模式的命令==<br />
<br />
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.<br />
<br />
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.<br />
<br />
done<br />
Leave Setup Mode.<br />
Aliases: end stop done quit<br />
<br />
help<br />
Display help screen.<br />
Aliases: ? h<br />
<br />
missing<br />
Display a list of missing (mandatory) regions, warps, and points.<br />
This command is useful if you have forgotten how far you are in the setup process, and what you still need to set up.<br />
Aliases: miss<br />
<br />
expand <region> <amount> <direction><br />
Expand a region by some amount in some direction.<br />
Valid regions: ar for the arena region, or lr for the lobby region<br />
Valid amounts: positive integers (whole numbers)<br />
Valid directions: up, down, or out<br />
Example: expand ar 5 up<br />
Aliases: exp<br />
<br />
show [<region>|<warp>|<point>]<br />
Show a region, warp, or point(s) as red wool blocks.<br />
Valid regions: ar for the arena region, or lr for the lobby region<br />
Valid warps: arena, lobby, spec, exit<br />
Valid points: spawns (or just sp) for spawnpoints, chests (or just c) for chests<br />
Example: show sp<br />
<br />
==设置时的工具==<br />
<br />
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.<br />
<br />
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.<br />
<br />
===区域工具===<br />
<br />
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.<br />
<br />
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.<br />
<br />
Left-click: Set the first point to be the location of the target block<br />
Right-click: Set the second point to be the location of the target block<br />
<br />
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.<br />
<br />
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.<br />
<br />
===玩家传送点工具===<br />
<br />
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.<br />
<br />
Left-click: Set the currently selected warp on top of the target block<br />
Right-click: Cycle between available warps<br />
<br />
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.<br />
<br />
Note: The arena, lobby, and spectator warps are all required. The exit warp is optional.<br />
<br />
===怪物产生点工具===<br />
<br />
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.<br />
<br />
Left-click: Add a spawnpoint on top of the target block<br />
Right-click: Remove the spawnpoint on top of the target block (if the spawnpoint exists)<br />
<br />
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.<br />
<br />
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.<br />
<br />
===容器工具===<br />
<br />
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.<br />
<br />
Left-click: Register the clicked container (if it wasn't registered)<br />
Right-click: Unregister the clicked container (if it was registered)<br />
<br />
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.<br />
<br />
=命令=<br />
==玩家命令==<br />
<br />
These commands can be issued by all players. They include joining, leaving, spectating and listing arenas as well as listing players.<br />
<br />
/ma join (<arena>) or /ma j (<arena>) - Join the arena with the given name.<br />
/ma leave or /ma l - Leave the current arena, or the spectator area.<br />
/ma notready - Get a list of all players who aren't ready.<br />
/ma spec (<arena>) or /ma s (<arena>) - Spectate the arena with the given name.<br />
/ma arenas - Get a list of all arenas. Green names are enabled, gray names are disabled.<br />
/ma players - Get a list of all arena players.<br />
/ma players <arena> - Get a list of arena players in the specified arena.<br />
/ma class <class> - While in the lobby, manually pick the given class instead of punching signs.<br />
==管理员指令==<br />
<br />
Only ops and the console can issue these commands. They include forcefully starting or ending arenas, enabling/disabling individual arenas or MobArena entirely.<br />
<br />
/ma enable - Enable MobArena.<br />
/ma disable - Disable MobArena.<br />
/ma enable <arena> - Enable the arena with the specified name.<br />
/ma disable <arena> - Disable the arena with the specified name.<br />
/ma force end - Forcefully end all arenas.<br />
/ma force end <arena> - Forcefully end the arena with the specified name; forces all players to leave. <br />
/ma force start <arena> - Forcefully start the arena with the specified name; forces all players who aren't ready to leave.<br />
/ma notready <arena> - Get a list of all players in the given arena who aren't ready.<br />
/ma restore <player> - Restore the inventory of the player with the given name, if possible.<br />
/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.<br />
==建设指令==<br />
<br />
Only ops (and the console, if it makes sense) can issue these commands. They include setting warp points, spawnpoints and region points.<br />
<br />
/ma setup <arena> - Enter Setup Mode for the given arena.<br />
/ma addarena <arena> - Create a new arena-node in the current world.<br />
/ma delarena <arena> - Delete the arena with the given name.<br />
/ma editarena <arena> - Toggle Edit Mode for the given arena.<br />
/ma editarena <arena> [true|false] - Turn on or off Edit Mode for the given arena.<br />
/ma setting <arena> - List all per-arena settings for the given arena.<br />
/ma setting <arena> <setting> - Check the current value of the given setting for the given arena.<br />
/ma setting <arena> <setting> <value> - Set the value of the given setting for the given arena to the given value.<br />
/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 <br />
points in your arena are actually covered by spawnpoints or not.<br />
/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<br />
chest, regardless of any local class chests in arena lobbies. This is useful if you want a global class chest for a class.<br />
/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.<br />
/ma auto-degenerate <arena> - Degenerate the arena with the given name, effectively restoring the patch that was "bulldozed" with the auto-generator.<br />
<br />
=权限=<br />
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.<br />
<br />
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!<br />
<br />
==竞技场权限==<br />
<br />
Did you read the note at the top? If not, read it before you continue.<br />
<br />
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.<br />
<br />
bPermissions: ^mobarena.arenas.default<br />
GroupManager: -mobarena.arenas.default<br />
zPermissions: mobarena.arenas.default: false<br />
<br />
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.<br />
<br />
Still confused? Check the sample setup at the bottom of the page!<br />
<br />
==职业权限==<br />
<br />
Did you read the note at the top? If not, read it before you continue.<br />
<br />
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.<br />
<br />
bPermissions: ^mobarena.classes.knight<br />
GroupManager: -mobarena.classes.knight<br />
zPermissions: mobarena.classes.knight: false<br />
<br />
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.<br />
<br />
As with arenas, I recommend letting everyone enjoy all the classes, unless you have a special reason not to.<br />
<br />
Still confused? Check the sample setup at the bottom of the page!<br />
<br />
==命令权限==<br />
<br />
Did you read the note at the top? If not, read it before you continue.<br />
<br />
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!<br />
<br />
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.<br />
<br />
mobarena.use.join<br />
mobarena.use.leave<br />
mobarena.use.spec<br />
mobarena.use.arenalist<br />
mobarena.use.playerlist<br />
mobarena.use.notready<br />
mobarena.use.class<br />
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.<br />
<br />
mobarena.admin.enable<br />
mobarena.admin.kick<br />
mobarena.admin.restore<br />
mobarena.admin.force<br />
mobarena.admin.teleport<br />
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.<br />
<br />
mobarena.setup.config<br />
mobarena.setup.setup<br />
mobarena.setup.setting<br />
mobarena.setup.addarena<br />
mobarena.setup.removearena<br />
mobarena.setup.editarena<br />
mobarena.setup.spawnpoints<br />
mobarena.setup.containers<br />
mobarena.setup.checkdata<br />
mobarena.setup.checkspawns<br />
mobarena.setup.classchest<br />
mobarena.setup.classes<br />
mobarena.setup.leaderboards<br />
mobarena.setup.autogenerate<br />
mobarena.setup.autodegenerate<br />
Sample setup<br />
<br />
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...<br />
<br />
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:<br />
<br />
default-aux: <-- This is the auxiliary group that is to<br />
permissions: be inherited by the default group and<br />
- essentials.balance the donor group. It is not used for<br />
- essentials.pay anything else.<br />
- essentials.sell<br />
<br />
default: <-- This is the default group. It inherits<br />
inherits: default-aux from default-aux, but also revokes the<br />
permissions: permission for the special class.<br />
- -mobarena.classes.diamondknight<br />
<br />
donor: <-- This is the donor group, which also<br />
inherits: default-aux inherits from default-aux, but it<br />
permissions: does not revoke any class permissions,<br />
- essentials.balance.others which means it has access to all of<br />
- essentials.kit them by default.<br />
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.<br />
=物品语法（Item Syntax待搬运）=<br />
=职业箱子（Class Chests待搬运｝=<br />
=怪物波设置（Formulas待搬运）=<br />
=怪物种类（Monster types待搬运）=<br />
以上内容搬运自英文wiki[https://github.com/garbagemule/MobArena/wiki]</div>Zhwhttps://mineplugin.org/index.php?title=MobArena&diff=869MobArena2015-02-18T08:26:06Z<p>Zhw：</p>
<hr />
<div>{{待搬运}}<br />
{{Bukkit Plugin Infobox<br />
|版本=v0.96.9<br />
|兼容服务端版本=1.8.1<br />
|网址=http://dev.bukkit.org/bukkit-plugins/mobarena/}}<br />
[[Category:娱乐]][[Category:机械]]<br />
=安装=<br />
安装MobArena其实很简单，只需以下四步:<br />
*关闭服务器<del>咳咳，当然是关你自己的服务器啦</del>.<br />
*从论坛主题或是Bukkit Dev站点的项目页下载jar文件.<br />
*将jar文件拖入服务端的plugins文件夹中.<br />
*重启服务端. <br />
之后，配置文件 (config.yml) 以及一个宣告文本(announcements.yml) 会自动创建在plugins/MobArena/路径下.<br />
文件结构如下:<br />
<br />
plugins/<br />
MobArena.jar<br />
MobArena/<br />
config.yml<br />
announcements.yml<br />
此时此刻, 或许你想直接开始设置竞技场, 但是你需要先看看配置文件，并把它配置成你喜欢的样子<del>就是说，还是根据情况配置一下吧</del>. 你可以在配置文件自定义MobArena的设置，职业，奖励，波数（怪物类型）<br />
<br />
=建立竞技场（V0.96后）=<br />
==建造一个竞技场==<br />
一个好的竞技场 包括了一个有职业选择的准备区域，一个竞技场地然后有观看场地或离开点 让我们仔细查看每个选项<br />
<br />
Lobby: <br />
The lobby is where your players will be selecting their classes when they join an arena. A well-formed loby consists of a sign for each class, which the players will click to choose a given class, as well as an iron block, which the players will click when they are ready to start. The signs must have the name of the class on the first line (case-sensitive), but you canput whatever you want on the remaining three lines. Note that MobArena does not "register" class sign creation, so you will not get a confirmation message (if you do, it is another plugin interfering).<br />
<br />
Arena floor: <br />
This is where your players will be fighting monsters. The arena floor should be enclosed in walls, and possibly with a roof, such that the players and monsters have no way of getting out. This ensures that players won't be able to just wander out of the arena.<br />
<br />
Spectator area: <br />
When players want to spectate a session, they can use the /ma spec command to get warped to the spectator area of an arena. This is also where arena players are warped to when they die,if spectate-after-death: true in the config-file. The area should be designed so that it is not possible for the spectators to wander out (into the arena or away from the area), because spectators are invincible.<br />
<br />
Exit point: <br />
Upon typing /ma leave, arena players and spectators will be warped to the location they joined from, unless the arena has an exit warp (optional). Using exit points, it is possible to control exactly where players go after a session.<br />
<br />
About regions, warps, etc.<br />
<br />
Once our arena is built, it's time to set up the MobArena regions, warps, and points. Before we do so, let's take a look at what these things are and what MobArena uses them for...<br />
<br />
Regions: <br />
An arena needs an arena region, and optionally a lobby region. MobArena uses the arena region to make sure that players aren't cheating (by kicking them from the arena if they move outside the region), and to make sure that only MobArena's own mobs are spawned inside of it. MobArena is extremely xenophobic (afraid of strangers), so it tries its best to keep unwanted mobs out of the sessions. Regions are set using the Region tools.<br />
<br />
Warps: <br />
When players join a MobArena session, they are teleported to the lobby warp inside the lobby, where they will pick their class and ready up using the ready block (block of iron). When everyone is ready, the players are teleported to the arena warp inside of the arena. Spectators will be teleported to the spectator warp in the spectator area, and when players leave an arena, they will either be teleported to where they joined from, or to the exit warp, if it has been set up. Warps are set using the Warps tool.<br />
<br />
Spawnpoints: <br />
The spawnpoints of an arena are the locations where monsters can spawn from. MobArena will only spawn monsters from spawnpoints that have players nearby (in a 15-block radius). Note that<br />
the number of mobs spawned doesn't depend on how many spawnpoints an arena has - the number of mobs is determined by a formula (see Formulas) that only involves the wave number and <br />
player count (unless you use fixed amounts). Spawnpoints are added using the Spawnpoints tool.<br />
<br />
Containers: <br />
The containers of an arena are locations of chests, dispensers, etc. which contain items that will be renewed when the arena ends. Only registered containers will have their contents <br />
renewed, so it is not enough to simply put a chest in the arena - it also needs to be registered using the Chests tool.<br />
<br />
==设置模式==<br />
We will set up the arena using Setup Mode. When we enter Setup Mode, MobArena will temporarily store our inventory and give us a set of golden tools (the Toolbox), each with a different function. 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.<br />
<br />
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.<br />
<br />
To leave Setup Mode: Type done.<br />
<br />
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.<br />
<br />
In the next section, we will take a look at the different commands available in Setup Mode...<br />
<br />
==设置模式的命令==<br />
<br />
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.<br />
<br />
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.<br />
<br />
done<br />
Leave Setup Mode.<br />
Aliases: end stop done quit<br />
<br />
help<br />
Display help screen.<br />
Aliases: ? h<br />
<br />
missing<br />
Display a list of missing (mandatory) regions, warps, and points.<br />
This command is useful if you have forgotten how far you are in the setup process, and what you still need to set up.<br />
Aliases: miss<br />
<br />
expand <region> <amount> <direction><br />
Expand a region by some amount in some direction.<br />
Valid regions: ar for the arena region, or lr for the lobby region<br />
Valid amounts: positive integers (whole numbers)<br />
Valid directions: up, down, or out<br />
Example: expand ar 5 up<br />
Aliases: exp<br />
<br />
show [<region>|<warp>|<point>]<br />
Show a region, warp, or point(s) as red wool blocks.<br />
Valid regions: ar for the arena region, or lr for the lobby region<br />
Valid warps: arena, lobby, spec, exit<br />
Valid points: spawns (or just sp) for spawnpoints, chests (or just c) for chests<br />
Example: show sp<br />
<br />
==设置时的工具==<br />
<br />
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.<br />
<br />
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.<br />
<br />
===区域工具===<br />
<br />
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.<br />
<br />
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.<br />
<br />
Left-click: Set the first point to be the location of the target block<br />
Right-click: Set the second point to be the location of the target block<br />
<br />
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.<br />
<br />
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.<br />
<br />
===玩家传送点工具===<br />
<br />
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.<br />
<br />
Left-click: Set the currently selected warp on top of the target block<br />
Right-click: Cycle between available warps<br />
<br />
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.<br />
<br />
Note: The arena, lobby, and spectator warps are all required. The exit warp is optional.<br />
<br />
===怪物产生点工具===<br />
<br />
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.<br />
<br />
Left-click: Add a spawnpoint on top of the target block<br />
Right-click: Remove the spawnpoint on top of the target block (if the spawnpoint exists)<br />
<br />
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.<br />
<br />
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.<br />
<br />
===容器工具===<br />
<br />
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.<br />
<br />
Left-click: Register the clicked container (if it wasn't registered)<br />
Right-click: Unregister the clicked container (if it was registered)<br />
<br />
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.<br />
<br />
=命令=<br />
==玩家命令==<br />
<br />
These commands can be issued by all players. They include joining, leaving, spectating and listing arenas as well as listing players.<br />
<br />
/ma join (<arena>) or /ma j (<arena>) - Join the arena with the given name.<br />
/ma leave or /ma l - Leave the current arena, or the spectator area.<br />
/ma notready - Get a list of all players who aren't ready.<br />
/ma spec (<arena>) or /ma s (<arena>) - Spectate the arena with the given name.<br />
/ma arenas - Get a list of all arenas. Green names are enabled, gray names are disabled.<br />
/ma players - Get a list of all arena players.<br />
/ma players <arena> - Get a list of arena players in the specified arena.<br />
/ma class <class> - While in the lobby, manually pick the given class instead of punching signs.<br />
==管理员指令==<br />
<br />
Only ops and the console can issue these commands. They include forcefully starting or ending arenas, enabling/disabling individual arenas or MobArena entirely.<br />
<br />
/ma enable - Enable MobArena.<br />
/ma disable - Disable MobArena.<br />
/ma enable <arena> - Enable the arena with the specified name.<br />
/ma disable <arena> - Disable the arena with the specified name.<br />
/ma force end - Forcefully end all arenas.<br />
/ma force end <arena> - Forcefully end the arena with the specified name; forces all players to leave. <br />
/ma force start <arena> - Forcefully start the arena with the specified name; forces all players who aren't ready to leave.<br />
/ma notready <arena> - Get a list of all players in the given arena who aren't ready.<br />
/ma restore <player> - Restore the inventory of the player with the given name, if possible.<br />
/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.<br />
==建设指令==<br />
<br />
Only ops (and the console, if it makes sense) can issue these commands. They include setting warp points, spawnpoints and region points.<br />
<br />
/ma setup <arena> - Enter Setup Mode for the given arena.<br />
/ma addarena <arena> - Create a new arena-node in the current world.<br />
/ma delarena <arena> - Delete the arena with the given name.<br />
/ma editarena <arena> - Toggle Edit Mode for the given arena.<br />
/ma editarena <arena> [true|false] - Turn on or off Edit Mode for the given arena.<br />
/ma setting <arena> - List all per-arena settings for the given arena.<br />
/ma setting <arena> <setting> - Check the current value of the given setting for the given arena.<br />
/ma setting <arena> <setting> <value> - Set the value of the given setting for the given arena to the given value.<br />
/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 <br />
points in your arena are actually covered by spawnpoints or not.<br />
/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<br />
chest, regardless of any local class chests in arena lobbies. This is useful if you want a global class chest for a class.<br />
/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.<br />
/ma auto-degenerate <arena> - Degenerate the arena with the given name, effectively restoring the patch that was "bulldozed" with the auto-generator.<br />
<br />
=权限=<br />
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.<br />
<br />
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!<br />
<br />
==竞技场权限==<br />
<br />
Did you read the note at the top? If not, read it before you continue.<br />
<br />
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.<br />
<br />
bPermissions: ^mobarena.arenas.default<br />
GroupManager: -mobarena.arenas.default<br />
zPermissions: mobarena.arenas.default: false<br />
<br />
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.<br />
<br />
Still confused? Check the sample setup at the bottom of the page!<br />
<br />
==职业权限==<br />
<br />
Did you read the note at the top? If not, read it before you continue.<br />
<br />
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.<br />
<br />
bPermissions: ^mobarena.classes.knight<br />
GroupManager: -mobarena.classes.knight<br />
zPermissions: mobarena.classes.knight: false<br />
<br />
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.<br />
<br />
As with arenas, I recommend letting everyone enjoy all the classes, unless you have a special reason not to.<br />
<br />
Still confused? Check the sample setup at the bottom of the page!<br />
<br />
==命令权限==<br />
<br />
Did you read the note at the top? If not, read it before you continue.<br />
<br />
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!<br />
<br />
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.<br />
<br />
mobarena.use.join<br />
mobarena.use.leave<br />
mobarena.use.spec<br />
mobarena.use.arenalist<br />
mobarena.use.playerlist<br />
mobarena.use.notready<br />
mobarena.use.class<br />
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.<br />
<br />
mobarena.admin.enable<br />
mobarena.admin.kick<br />
mobarena.admin.restore<br />
mobarena.admin.force<br />
mobarena.admin.teleport<br />
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.<br />
<br />
mobarena.setup.config<br />
mobarena.setup.setup<br />
mobarena.setup.setting<br />
mobarena.setup.addarena<br />
mobarena.setup.removearena<br />
mobarena.setup.editarena<br />
mobarena.setup.spawnpoints<br />
mobarena.setup.containers<br />
mobarena.setup.checkdata<br />
mobarena.setup.checkspawns<br />
mobarena.setup.classchest<br />
mobarena.setup.classes<br />
mobarena.setup.leaderboards<br />
mobarena.setup.autogenerate<br />
mobarena.setup.autodegenerate<br />
Sample setup<br />
<br />
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...<br />
<br />
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:<br />
<br />
default-aux: <-- This is the auxiliary group that is to<br />
permissions: be inherited by the default group and<br />
- essentials.balance the donor group. It is not used for<br />
- essentials.pay anything else.<br />
- essentials.sell<br />
<br />
default: <-- This is the default group. It inherits<br />
inherits: default-aux from default-aux, but also revokes the<br />
permissions: permission for the special class.<br />
- -mobarena.classes.diamondknight<br />
<br />
donor: <-- This is the donor group, which also<br />
inherits: default-aux inherits from default-aux, but it<br />
permissions: does not revoke any class permissions,<br />
- essentials.balance.others which means it has access to all of<br />
- essentials.kit them by default.<br />
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.<br />
=物品语法（Item Syntax待搬运）=<br />
=职业箱子（Class Chests待搬运｝=<br />
=怪物波设置（Formulas待搬运）=<br />
=怪物种类（Monster types待搬运）=<br />
以上内容搬运自英文wiki[https://github.com/garbagemule/MobArena/wiki]</div>Zhwhttps://mineplugin.org/index.php?title=MobArena&diff=868MobArena2015-02-18T01:28:25Z<p>Zhw：/* 安装 */</p>
<hr />
<div>{{待搬运}}<br />
{{Bukkit Plugin Infobox<br />
|版本=v0.96.9<br />
|兼容服务端版本=1.8.1<br />
|网址=http://dev.bukkit.org/bukkit-plugins/mobarena/}}<br />
[[Category:娱乐]][[Category:机械]]<br />
=安装=<br />
安装MobArena其实很简单，只需以下四步:<br />
*关闭服务器<del>咳咳，当然是关你自己的服务器啦</del>.<br />
*从论坛主题或是Bukkit Dev站点的项目页下载jar文件.<br />
*将jar文件拖入服务端的plugins文件夹中.<br />
*重启服务端. <br />
之后，配置文件 (config.yml) 以及一个宣告文本(announcements.yml) 会自动创建在plugins/MobArena/路径下.<br />
文件结构如下:<br />
<br />
plugins/<br />
MobArena.jar<br />
MobArena/<br />
config.yml<br />
announcements.yml<br />
此时此刻, 或许你想直接开始设置竞技场, 但是你需要先看看配置文件，并把它配置成你喜欢的样子<del>就是说，还是根据情况配置一下吧</del>. 你可以在配置文件自定义MobArena的设置，职业，奖励，波数（怪物类型）<br />
<br />
=建立竞技场（V0.96后）=<br />
==建造一个竞技场==<br />
A well-built arena consists of a lobby for class selection, an arena floor, and either a spectator area or an exit point. Let's go over each one...<br />
<br />
Lobby: <br />
The lobby is where your players will be selecting their classes when they join an arena. A well-formed lobby consists of a sign for each class, which the players will click to choose a given class, as well as an iron block, which the players will click when they are ready to start. The signs must have the name of the class on the first line (case-sensitive), but you canput whatever you want on the remaining three lines. Note that MobArena does not "register" class sign creation, so you will not get a confirmation message (if you do, it is another plugin interfering).<br />
<br />
Arena floor: <br />
This is where your players will be fighting monsters. The arena floor should be enclosed in walls, and possibly with a roof, such that the players and monsters have no way of getting out. This ensures that players won't be able to just wander out of the arena.<br />
<br />
Spectator area: <br />
When players want to spectate a session, they can use the /ma spec command to get warped to the spectator area of an arena. This is also where arena players are warped to when they die,if spectate-after-death: true in the config-file. The area should be designed so that it is not possible for the spectators to wander out (into the arena or away from the area), because spectators are invincible.<br />
<br />
Exit point: <br />
Upon typing /ma leave, arena players and spectators will be warped to the location they joined from, unless the arena has an exit warp (optional). Using exit points, it is possible to control exactly where players go after a session.<br />
<br />
About regions, warps, etc.<br />
<br />
Once our arena is built, it's time to set up the MobArena regions, warps, and points. Before we do so, let's take a look at what these things are and what MobArena uses them for...<br />
<br />
Regions: <br />
An arena needs an arena region, and optionally a lobby region. MobArena uses the arena region to make sure that players aren't cheating (by kicking them from the arena if they move outside the region), and to make sure that only MobArena's own mobs are spawned inside of it. MobArena is extremely xenophobic (afraid of strangers), so it tries its best to keep unwanted mobs out of the sessions. Regions are set using the Region tools.<br />
<br />
Warps: <br />
When players join a MobArena session, they are teleported to the lobby warp inside the lobby, where they will pick their class and ready up using the ready block (block of iron). When everyone is ready, the players are teleported to the arena warp inside of the arena. Spectators will be teleported to the spectator warp in the spectator area, and when players leave an arena, they will either be teleported to where they joined from, or to the exit warp, if it has been set up. Warps are set using the Warps tool.<br />
<br />
Spawnpoints: <br />
The spawnpoints of an arena are the locations where monsters can spawn from. MobArena will only spawn monsters from spawnpoints that have players nearby (in a 15-block radius). Note that<br />
the number of mobs spawned doesn't depend on how many spawnpoints an arena has - the number of mobs is determined by a formula (see Formulas) that only involves the wave number and <br />
player count (unless you use fixed amounts). Spawnpoints are added using the Spawnpoints tool.<br />
<br />
Containers: <br />
The containers of an arena are locations of chests, dispensers, etc. which contain items that will be renewed when the arena ends. Only registered containers will have their contents <br />
renewed, so it is not enough to simply put a chest in the arena - it also needs to be registered using the Chests tool.<br />
<br />
==设置模式==<br />
We will set up the arena using Setup Mode. When we enter Setup Mode, MobArena will temporarily store our inventory and give us a set of golden tools (the Toolbox), each with a different function. 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.<br />
<br />
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.<br />
<br />
To leave Setup Mode: Type done.<br />
<br />
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.<br />
<br />
In the next section, we will take a look at the different commands available in Setup Mode...<br />
<br />
==设置模式的命令==<br />
<br />
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.<br />
<br />
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.<br />
<br />
done<br />
Leave Setup Mode.<br />
Aliases: end stop done quit<br />
<br />
help<br />
Display help screen.<br />
Aliases: ? h<br />
<br />
missing<br />
Display a list of missing (mandatory) regions, warps, and points.<br />
This command is useful if you have forgotten how far you are in the setup process, and what you still need to set up.<br />
Aliases: miss<br />
<br />
expand <region> <amount> <direction><br />
Expand a region by some amount in some direction.<br />
Valid regions: ar for the arena region, or lr for the lobby region<br />
Valid amounts: positive integers (whole numbers)<br />
Valid directions: up, down, or out<br />
Example: expand ar 5 up<br />
Aliases: exp<br />
<br />
show [<region>|<warp>|<point>]<br />
Show a region, warp, or point(s) as red wool blocks.<br />
Valid regions: ar for the arena region, or lr for the lobby region<br />
Valid warps: arena, lobby, spec, exit<br />
Valid points: spawns (or just sp) for spawnpoints, chests (or just c) for chests<br />
Example: show sp<br />
<br />
==设置时的工具==<br />
<br />
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.<br />
<br />
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.<br />
<br />
===区域工具===<br />
<br />
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.<br />
<br />
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.<br />
<br />
Left-click: Set the first point to be the location of the target block<br />
Right-click: Set the second point to be the location of the target block<br />
<br />
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.<br />
<br />
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.<br />
<br />
===玩家传送点工具===<br />
<br />
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.<br />
<br />
Left-click: Set the currently selected warp on top of the target block<br />
Right-click: Cycle between available warps<br />
<br />
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.<br />
<br />
Note: The arena, lobby, and spectator warps are all required. The exit warp is optional.<br />
<br />
===怪物产生点工具===<br />
<br />
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.<br />
<br />
Left-click: Add a spawnpoint on top of the target block<br />
Right-click: Remove the spawnpoint on top of the target block (if the spawnpoint exists)<br />
<br />
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.<br />
<br />
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.<br />
<br />
===容器工具===<br />
<br />
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.<br />
<br />
Left-click: Register the clicked container (if it wasn't registered)<br />
Right-click: Unregister the clicked container (if it was registered)<br />
<br />
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.<br />
=命令=<br />
==玩家命令==<br />
<br />
These commands can be issued by all players. They include joining, leaving, spectating and listing arenas as well as listing players.<br />
<br />
/ma join (<arena>) or /ma j (<arena>) - Join the arena with the given name.<br />
/ma leave or /ma l - Leave the current arena, or the spectator area.<br />
/ma notready - Get a list of all players who aren't ready.<br />
/ma spec (<arena>) or /ma s (<arena>) - Spectate the arena with the given name.<br />
/ma arenas - Get a list of all arenas. Green names are enabled, gray names are disabled.<br />
/ma players - Get a list of all arena players.<br />
/ma players <arena> - Get a list of arena players in the specified arena.<br />
/ma class <class> - While in the lobby, manually pick the given class instead of punching signs.<br />
==管理员指令==<br />
<br />
Only ops and the console can issue these commands. They include forcefully starting or ending arenas, enabling/disabling individual arenas or MobArena entirely.<br />
<br />
/ma enable - Enable MobArena.<br />
/ma disable - Disable MobArena.<br />
/ma enable <arena> - Enable the arena with the specified name.<br />
/ma disable <arena> - Disable the arena with the specified name.<br />
/ma force end - Forcefully end all arenas.<br />
/ma force end <arena> - Forcefully end the arena with the specified name; forces all players to leave. <br />
/ma force start <arena> - Forcefully start the arena with the specified name; forces all players who aren't ready to leave.<br />
/ma notready <arena> - Get a list of all players in the given arena who aren't ready.<br />
/ma restore <player> - Restore the inventory of the player with the given name, if possible.<br />
/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.<br />
==建设指令==<br />
<br />
Only ops (and the console, if it makes sense) can issue these commands. They include setting warp points, spawnpoints and region points.<br />
<br />
/ma setup <arena> - Enter Setup Mode for the given arena.<br />
/ma addarena <arena> - Create a new arena-node in the current world.<br />
/ma delarena <arena> - Delete the arena with the given name.<br />
/ma editarena <arena> - Toggle Edit Mode for the given arena.<br />
/ma editarena <arena> [true|false] - Turn on or off Edit Mode for the given arena.<br />
/ma setting <arena> - List all per-arena settings for the given arena.<br />
/ma setting <arena> <setting> - Check the current value of the given setting for the given arena.<br />
/ma setting <arena> <setting> <value> - Set the value of the given setting for the given arena to the given value.<br />
/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 <br />
points in your arena are actually covered by spawnpoints or not.<br />
/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<br />
chest, regardless of any local class chests in arena lobbies. This is useful if you want a global class chest for a class.<br />
/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.<br />
/ma auto-degenerate <arena> - Degenerate the arena with the given name, effectively restoring the patch that was "bulldozed" with the auto-generator.<br />
<br />
=权限=<br />
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.<br />
<br />
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!<br />
<br />
==竞技场权限==<br />
<br />
Did you read the note at the top? If not, read it before you continue.<br />
<br />
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.<br />
<br />
bPermissions: ^mobarena.arenas.default<br />
GroupManager: -mobarena.arenas.default<br />
zPermissions: mobarena.arenas.default: false<br />
<br />
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.<br />
<br />
Still confused? Check the sample setup at the bottom of the page!<br />
<br />
==职业权限==<br />
<br />
Did you read the note at the top? If not, read it before you continue.<br />
<br />
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.<br />
<br />
bPermissions: ^mobarena.classes.knight<br />
GroupManager: -mobarena.classes.knight<br />
zPermissions: mobarena.classes.knight: false<br />
<br />
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.<br />
<br />
As with arenas, I recommend letting everyone enjoy all the classes, unless you have a special reason not to.<br />
<br />
Still confused? Check the sample setup at the bottom of the page!<br />
<br />
==命令权限==<br />
<br />
Did you read the note at the top? If not, read it before you continue.<br />
<br />
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!<br />
<br />
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.<br />
<br />
mobarena.use.join<br />
mobarena.use.leave<br />
mobarena.use.spec<br />
mobarena.use.arenalist<br />
mobarena.use.playerlist<br />
mobarena.use.notready<br />
mobarena.use.class<br />
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.<br />
<br />
mobarena.admin.enable<br />
mobarena.admin.kick<br />
mobarena.admin.restore<br />
mobarena.admin.force<br />
mobarena.admin.teleport<br />
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.<br />
<br />
mobarena.setup.config<br />
mobarena.setup.setup<br />
mobarena.setup.setting<br />
mobarena.setup.addarena<br />
mobarena.setup.removearena<br />
mobarena.setup.editarena<br />
mobarena.setup.spawnpoints<br />
mobarena.setup.containers<br />
mobarena.setup.checkdata<br />
mobarena.setup.checkspawns<br />
mobarena.setup.classchest<br />
mobarena.setup.classes<br />
mobarena.setup.leaderboards<br />
mobarena.setup.autogenerate<br />
mobarena.setup.autodegenerate<br />
Sample setup<br />
<br />
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...<br />
<br />
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:<br />
<br />
default-aux: <-- This is the auxiliary group that is to<br />
permissions: be inherited by the default group and<br />
- essentials.balance the donor group. It is not used for<br />
- essentials.pay anything else.<br />
- essentials.sell<br />
<br />
default: <-- This is the default group. It inherits<br />
inherits: default-aux from default-aux, but also revokes the<br />
permissions: permission for the special class.<br />
- -mobarena.classes.diamondknight<br />
<br />
donor: <-- This is the donor group, which also<br />
inherits: default-aux inherits from default-aux, but it<br />
permissions: does not revoke any class permissions,<br />
- essentials.balance.others which means it has access to all of<br />
- essentials.kit them by default.<br />
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.<br />
=物品语法（Item Syntax待搬运）=<br />
=职业箱子（Class Chests待搬运｝=<br />
=怪物波设置（Formulas待搬运）=<br />
=怪物种类（Monster types待搬运）=<br />
以上内容搬运自英文wiki[https://github.com/garbagemule/MobArena/wiki]</div>Zhwhttps://mineplugin.org/index.php?title=QuickShop&diff=867QuickShop2015-02-18T01:26:58Z<p>Zhw：/* 简介 */</p>
<hr />
<div>{{待完善}}<br />
{{Bukkit Plugin Infobox<br />
|版本=v4.4<br />
|兼容服务端版本=1.5.2+<br />
|网址=http://dev.bukkit.org/bukkit-plugins/quickshop/<br />
}}<br />
[[Category:经济]]<br />
[[Category:机械]]<br />
=简介=<br />
作者的话：对，我准备好写这个插件了. QuickShop. QuickShop是一个商店插件, 允许玩家通过箱子售卖物品，不需要输入任何命令. 它使得玩家可以很方便地购买任何数量的物品. 事实上, 玩家使用本插件不需要输入任何命令!<br />
<br />
=特性=<br />
操作简单<br />
(可控)在箱子顶部展示物品<br />
支持附带(NBT标签, 附魔属性, 工具耐久度损耗)的物品<del>破斧头卖出去还是破斧头(笑)</del>, 药水和怪物蛋<br />
支持无限库存<br />
支持黑名单 & 忽视权限<br />
支持同时售卖与购买物品<br />
兼容[[Herochat]]<br />
创建商店之前，自动检测一个玩家能否打开箱子!<del>啥东西？</del><br />
<br />
=如何创建一个商店=<br />
*将一个箱子放在地上<br />
*打一下你想用来交易的箱子<br />
*在聊天栏中输入物品的加个(依照提示) <br />
*将你想要售卖的物品放入箱子中<br />
*Done!<br />
<br />
=商店类型转换=<br />
*面对箱子<del>鼠标准星对准箱子就肯定没错了</del><br />
*输入/qs sell或是/qs buy转换商店类型 (可选: 使用/shop替换/qs)<br />
*有必要的话，补充商店的库存物品.<br />
<br />
=如何交易=<br />
*找到商店<br />
*打一下或是右键商店(箱子)<br />
*在聊天栏中输入你想交易的物品数量<br />
Menu Example: Menu<br />
<br />
实例:进入服务器，IP: http://maxgamer.org或是play.maxgamer.org:25571 然后输入/warp market!<del>广告可耻！</del><br />
<br />
=命令=<br />
/qs unlimited - 将鼠标准星所对的商店库存设置为'''无限'''.<br />
/qs setowner <player> - 将商店的所有人改为<player>.<br />
/qs buy - 将鼠标准星所对的商店转变为收购商店<br />
/qs sell - 将鼠标准星所对的商店转变为售卖商店<br />
/qs price <price> - 将鼠标准星所对的商店的交易价格修改为指定值<br />
/qs clean - 将所有库存数量为0的商店移除.<br />
/qs find <item> - 找到(最近的)交易<item> 的商店- 例如 '/qs find dia' 将会找到最近的交易钻石的商店.<br />
/shop - /qs的指令别名(可选)<br />
<br />
=用户权限=<br />
quickshop.use - 基本玩家权限创造'''任何'''商店时使用<br />
quickshop.create.sell - 用于创造基本的售出商店<br />
quickshop.create.buy - 用于可以使用/qs buy 命令(把商店类型改变 售出 ->收购 )<br />
quickshop.create.double - 用于可以创造双箱商店.<br />
quickshop.create.changeprice - 用于可以使用 /qs price命令 (可以改变商店的价格而不去破坏它. 这可能会使得一些店主可以在别人买时快速变价）<br />
quickshop.bypass.ItemID - 可以交易黑名单内物品 (比如基岩)<br />
quickshop.find - 可以用于使用 /qs find <物品>的命令来找到固定种类商店<br />
<br />
=管理权限=<br />
quickshop.unlimited - 可以使用 /quickshop unlimited命令<br />
quickshop.setowner - 允许使用/qs setowner命令<br />
quickshop.other.destroy - 可以破坏别人的快捷商店<br />
quickshop.other.open - 可以敲开别人的商店(拿出和放置)<br />
quickshop.other.price - 可以改变别人的商店的价格<br />
quickshop.refill - 可用命令重新装满别人商店 (基本等于无限物品)<br />
quickshop.empty - 可以用命令清空他人商店内的物品。<br />
quickshop.clean - 清空所有无货商店.<br />
<br />
<br />
Source: Source on Github<br />
<br />
Checkout the config over here.[http://dev.bukkit.org/bukkit-plugins/quickshop/pages/config/ 1] <br />
<br />
<br />
<br />
Have Towny?<br />
<br />
Try out this plugin http://dev.bukkit.org/server-mods/quickshop-towny-interop/ to stop players creating shops outside of Towny shop plots!</div>Zhwhttps://mineplugin.org/index.php?title=QuickShop&diff=866QuickShop2015-02-18T01:26:08Z<p>Zhw：</p>
<hr />
<div>{{待完善}}<br />
{{Bukkit Plugin Infobox<br />
|版本=v4.4<br />
|兼容服务端版本=1.5.2+<br />
|网址=http://dev.bukkit.org/bukkit-plugins/quickshop/<br />
}}<br />
[[Category:经济]]<br />
[[Category:机械]]<br />
=简介=<br />
对，我准备好写这个插件了. QuickShop. QuickShop是一个商店插件, 允许玩家通过箱子售卖物品，不需要输入任何命令. 它使得玩家可以很方便地购买任何数量的物品. 事实上, 玩家使用本插件不需要输入任何命令!<br />
<br />
=特性=<br />
操作简单<br />
(可控)在箱子顶部展示物品<br />
支持附带(NBT标签, 附魔属性, 工具耐久度损耗)的物品<del>破斧头卖出去还是破斧头(笑)</del>, 药水和怪物蛋<br />
支持无限库存<br />
支持黑名单 & 忽视权限<br />
支持同时售卖与购买物品<br />
兼容[[Herochat]]<br />
创建商店之前，自动检测一个玩家能否打开箱子!<del>啥东西？</del><br />
<br />
=如何创建一个商店=<br />
*将一个箱子放在地上<br />
*打一下你想用来交易的箱子<br />
*在聊天栏中输入物品的加个(依照提示) <br />
*将你想要售卖的物品放入箱子中<br />
*Done!<br />
<br />
=商店类型转换=<br />
*面对箱子<del>鼠标准星对准箱子就肯定没错了</del><br />
*输入/qs sell或是/qs buy转换商店类型 (可选: 使用/shop替换/qs)<br />
*有必要的话，补充商店的库存物品.<br />
<br />
=如何交易=<br />
*找到商店<br />
*打一下或是右键商店(箱子)<br />
*在聊天栏中输入你想交易的物品数量<br />
Menu Example: Menu<br />
<br />
实例:进入服务器，IP: http://maxgamer.org或是play.maxgamer.org:25571 然后输入/warp market!<del>广告可耻！</del><br />
<br />
=命令=<br />
/qs unlimited - 将鼠标准星所对的商店库存设置为'''无限'''.<br />
/qs setowner <player> - 将商店的所有人改为<player>.<br />
/qs buy - 将鼠标准星所对的商店转变为收购商店<br />
/qs sell - 将鼠标准星所对的商店转变为售卖商店<br />
/qs price <price> - 将鼠标准星所对的商店的交易价格修改为指定值<br />
/qs clean - 将所有库存数量为0的商店移除.<br />
/qs find <item> - 找到(最近的)交易<item> 的商店- 例如 '/qs find dia' 将会找到最近的交易钻石的商店.<br />
/shop - /qs的指令别名(可选)<br />
<br />
=用户权限=<br />
quickshop.use - 基本玩家权限创造'''任何'''商店时使用<br />
quickshop.create.sell - 用于创造基本的售出商店<br />
quickshop.create.buy - 用于可以使用/qs buy 命令(把商店类型改变 售出 ->收购 )<br />
quickshop.create.double - 用于可以创造双箱商店.<br />
quickshop.create.changeprice - 用于可以使用 /qs price命令 (可以改变商店的价格而不去破坏它. 这可能会使得一些店主可以在别人买时快速变价）<br />
quickshop.bypass.ItemID - 可以交易黑名单内物品 (比如基岩)<br />
quickshop.find - 可以用于使用 /qs find <物品>的命令来找到固定种类商店<br />
<br />
=管理权限=<br />
quickshop.unlimited - 可以使用 /quickshop unlimited命令<br />
quickshop.setowner - 允许使用/qs setowner命令<br />
quickshop.other.destroy - 可以破坏别人的快捷商店<br />
quickshop.other.open - 可以敲开别人的商店(拿出和放置)<br />
quickshop.other.price - 可以改变别人的商店的价格<br />
quickshop.refill - 可用命令重新装满别人商店 (基本等于无限物品)<br />
quickshop.empty - 可以用命令清空他人商店内的物品。<br />
quickshop.clean - 清空所有无货商店.<br />
<br />
<br />
Source: Source on Github<br />
<br />
Checkout the config over here.[http://dev.bukkit.org/bukkit-plugins/quickshop/pages/config/ 1] <br />
<br />
<br />
<br />
Have Towny?<br />
<br />
Try out this plugin http://dev.bukkit.org/server-mods/quickshop-towny-interop/ to stop players creating shops outside of Towny shop plots!</div>Zhwhttps://mineplugin.org/index.php?title=QuickShop&diff=865QuickShop2015-02-18T01:25:27Z<p>Zhw：/* 管理权限 */</p>
<hr />
<div>{{待翻译}}<br />
{{Bukkit Plugin Infobox<br />
|版本=v4.4<br />
|兼容服务端版本=1.5.2+<br />
|网址=http://dev.bukkit.org/bukkit-plugins/quickshop/<br />
}}<br />
[[Category:经济]]<br />
[[Category:机械]]<br />
=简介=<br />
对，我准备好写这个插件了. QuickShop. QuickShop是一个商店插件, 允许玩家通过箱子售卖物品，不需要输入任何命令. 它使得玩家可以很方便地购买任何数量的物品. 事实上, 玩家使用本插件不需要输入任何命令!<br />
<br />
=特性=<br />
操作简单<br />
(可控)在箱子顶部展示物品<br />
支持附带(NBT标签, 附魔属性, 工具耐久度损耗)的物品<del>破斧头卖出去还是破斧头(笑)</del>, 药水和怪物蛋<br />
支持无限库存<br />
支持黑名单 & 忽视权限<br />
支持同时售卖与购买物品<br />
兼容[[Herochat]]<br />
创建商店之前，自动检测一个玩家能否打开箱子!<del>啥东西？</del><br />
<br />
=如何创建一个商店=<br />
*将一个箱子放在地上<br />
*打一下你想用来交易的箱子<br />
*在聊天栏中输入物品的加个(依照提示) <br />
*将你想要售卖的物品放入箱子中<br />
*Done!<br />
<br />
=商店类型转换=<br />
*面对箱子<del>鼠标准星对准箱子就肯定没错了</del><br />
*输入/qs sell或是/qs buy转换商店类型 (可选: 使用/shop替换/qs)<br />
*有必要的话，补充商店的库存物品.<br />
<br />
=如何交易=<br />
*找到商店<br />
*打一下或是右键商店(箱子)<br />
*在聊天栏中输入你想交易的物品数量<br />
Menu Example: Menu<br />
<br />
实例:进入服务器，IP: http://maxgamer.org或是play.maxgamer.org:25571 然后输入/warp market!<del>广告可耻！</del><br />
<br />
=命令=<br />
/qs unlimited - 将鼠标准星所对的商店库存设置为'''无限'''.<br />
/qs setowner <player> - 将商店的所有人改为<player>.<br />
/qs buy - 将鼠标准星所对的商店转变为收购商店<br />
/qs sell - 将鼠标准星所对的商店转变为售卖商店<br />
/qs price <price> - 将鼠标准星所对的商店的交易价格修改为指定值<br />
/qs clean - 将所有库存数量为0的商店移除.<br />
/qs find <item> - 找到(最近的)交易<item> 的商店- 例如 '/qs find dia' 将会找到最近的交易钻石的商店.<br />
/shop - /qs的指令别名(可选)<br />
<br />
=用户权限=<br />
quickshop.use - 基本玩家权限创造'''任何'''商店时使用<br />
quickshop.create.sell - 用于创造基本的售出商店<br />
quickshop.create.buy - 用于可以使用/qs buy 命令(把商店类型改变 售出 ->收购 )<br />
quickshop.create.double - 用于可以创造双箱商店.<br />
quickshop.create.changeprice - 用于可以使用 /qs price命令 (可以改变商店的价格而不去破坏它. 这可能会使得一些店主可以在别人买时快速变价）<br />
quickshop.bypass.ItemID - 可以交易黑名单内物品 (比如基岩)<br />
quickshop.find - 可以用于使用 /qs find <物品>的命令来找到固定种类商店<br />
<br />
=管理权限=<br />
quickshop.unlimited - 可以使用 /quickshop unlimited命令<br />
quickshop.setowner - 允许使用/qs setowner命令<br />
quickshop.other.destroy - 可以破坏别人的快捷商店<br />
quickshop.other.open - 可以敲开别人的商店(拿出和放置)<br />
quickshop.other.price - 可以改变别人的商店的价格<br />
quickshop.refill - 可用命令重新装满别人商店 (基本等于无限物品)<br />
quickshop.empty - 可以用命令清空他人商店内的物品。<br />
quickshop.clean - 清空所有无货商店.<br />
<br />
<br />
Source: Source on Github<br />
<br />
Checkout the config over here.[http://dev.bukkit.org/bukkit-plugins/quickshop/pages/config/ 1] <br />
<br />
<br />
<br />
Have Towny?<br />
<br />
Try out this plugin http://dev.bukkit.org/server-mods/quickshop-towny-interop/ to stop players creating shops outside of Towny shop plots!</div>Zhwhttps://mineplugin.org/index.php?title=QuickShop&diff=864QuickShop2015-02-18T01:21:56Z<p>Zhw：/* 用户权限 */</p>
<hr />
<div>{{待翻译}}<br />
{{Bukkit Plugin Infobox<br />
|版本=v4.4<br />
|兼容服务端版本=1.5.2+<br />
|网址=http://dev.bukkit.org/bukkit-plugins/quickshop/<br />
}}<br />
[[Category:经济]]<br />
[[Category:机械]]<br />
=简介=<br />
对，我准备好写这个插件了. QuickShop. QuickShop是一个商店插件, 允许玩家通过箱子售卖物品，不需要输入任何命令. 它使得玩家可以很方便地购买任何数量的物品. 事实上, 玩家使用本插件不需要输入任何命令!<br />
<br />
=特性=<br />
操作简单<br />
(可控)在箱子顶部展示物品<br />
支持附带(NBT标签, 附魔属性, 工具耐久度损耗)的物品<del>破斧头卖出去还是破斧头(笑)</del>, 药水和怪物蛋<br />
支持无限库存<br />
支持黑名单 & 忽视权限<br />
支持同时售卖与购买物品<br />
兼容[[Herochat]]<br />
创建商店之前，自动检测一个玩家能否打开箱子!<del>啥东西？</del><br />
<br />
=如何创建一个商店=<br />
*将一个箱子放在地上<br />
*打一下你想用来交易的箱子<br />
*在聊天栏中输入物品的加个(依照提示) <br />
*将你想要售卖的物品放入箱子中<br />
*Done!<br />
<br />
=商店类型转换=<br />
*面对箱子<del>鼠标准星对准箱子就肯定没错了</del><br />
*输入/qs sell或是/qs buy转换商店类型 (可选: 使用/shop替换/qs)<br />
*有必要的话，补充商店的库存物品.<br />
<br />
=如何交易=<br />
*找到商店<br />
*打一下或是右键商店(箱子)<br />
*在聊天栏中输入你想交易的物品数量<br />
Menu Example: Menu<br />
<br />
实例:进入服务器，IP: http://maxgamer.org或是play.maxgamer.org:25571 然后输入/warp market!<del>广告可耻！</del><br />
<br />
=命令=<br />
/qs unlimited - 将鼠标准星所对的商店库存设置为'''无限'''.<br />
/qs setowner <player> - 将商店的所有人改为<player>.<br />
/qs buy - 将鼠标准星所对的商店转变为收购商店<br />
/qs sell - 将鼠标准星所对的商店转变为售卖商店<br />
/qs price <price> - 将鼠标准星所对的商店的交易价格修改为指定值<br />
/qs clean - 将所有库存数量为0的商店移除.<br />
/qs find <item> - 找到(最近的)交易<item> 的商店- 例如 '/qs find dia' 将会找到最近的交易钻石的商店.<br />
/shop - /qs的指令别名(可选)<br />
<br />
=用户权限=<br />
quickshop.use - 基本玩家权限创造'''任何'''商店时使用<br />
quickshop.create.sell - 用于创造基本的售出商店<br />
quickshop.create.buy - 用于可以使用/qs buy 命令(把商店类型改变 售出 ->收购 )<br />
quickshop.create.double - 用于可以创造双箱商店.<br />
quickshop.create.changeprice - 用于可以使用 /qs price命令 (可以改变商店的价格而不去破坏它. 这可能会使得一些店主可以在别人买时快速变价）<br />
quickshop.bypass.ItemID - 可以交易黑名单内物品 (比如基岩)<br />
quickshop.find - 可以用于使用 /qs find <物品>的命令来找到固定种类商店<br />
<br />
=管理权限=<br />
quickshop.unlimited - Required to use /quickshop unlimited<br />
quickshop.setowner - Allows use of /qs setowner<br />
quickshop.other.destroy - Allow breaking other peoples QuickShops if they're locked by this plugin<br />
quickshop.other.open - Allow opening (And stealing/Stocking) other players QuickShops<br />
quickshop.other.price - Allow changing price of other people's shops<br />
quickshop.refill - Ability to refill chests using a command (=Unlimited items)<br />
quickshop.empty - Ability to empty chests of all items<br />
quickshop.clean - Permission to purge any shops that have 0 stock.<br />
<br />
<br />
Source: Source on Github<br />
<br />
Checkout the config over here.[http://dev.bukkit.org/bukkit-plugins/quickshop/pages/config/ 1] <br />
<br />
<br />
<br />
Have Towny?<br />
<br />
Try out this plugin http://dev.bukkit.org/server-mods/quickshop-towny-interop/ to stop players creating shops outside of Towny shop plots!</div>Zhwhttps://mineplugin.org/index.php?title=MobArena&diff=847MobArena2015-02-17T03:04:29Z<p>Zhw：/* 建造一个竞技场 */</p>
<hr />
<div>{{待搬运}}<br />
{{Bukkit Plugin Infobox<br />
|版本=v0.96.9<br />
|兼容服务端版本=1.8.1<br />
|网址=http://dev.bukkit.org/bukkit-plugins/mobarena/}}<br />
[[Category:娱乐]][[Category:机械]]<br />
=安装插件=<br />
Installing MobArena is as easy as these four steps:<br />
Stop your server.<br />
Download the jar-file from the forum thread or Bukkit Dev project page.<br />
Place the jar-file in your server's plugins-folder.<br />
Start the server again. This process will generate a config-file (config.yml) and an announcements-file (announcements.yml) in the plugins/MobArena-folder.<br />
The folder structure is thus:<br />
<br />
plugins/<br />
MobArena.jar<br />
MobArena/<br />
config.yml<br />
announcements.yml<br />
At this point in time, you're probably eager to skip ahead to the arena setup page, but make sure to have a look at setting up the config-file to your liking. The config-file is where you customize the MobArena settings, classes, waves, and rewards.<br />
=建立竞技场（V0.96后）=<br />
==建造一个竞技场==<br />
A well-built arena consists of a lobby for class selection, an arena floor, and either a spectator area or an exit point. Let's go over each one...<br />
<br />
Lobby: <br />
The lobby is where your players will be selecting their classes when they join an arena. A well-formed lobby consists of a sign for each class, which the players will click to choose a given class, as well as an iron block, which the players will click when they are ready to start. The signs must have the name of the class on the first line (case-sensitive), but you canput whatever you want on the remaining three lines. Note that MobArena does not "register" class sign creation, so you will not get a confirmation message (if you do, it is another plugin interfering).<br />
<br />
Arena floor: <br />
This is where your players will be fighting monsters. The arena floor should be enclosed in walls, and possibly with a roof, such that the players and monsters have no way of getting out. This ensures that players won't be able to just wander out of the arena.<br />
<br />
Spectator area: <br />
When players want to spectate a session, they can use the /ma spec command to get warped to the spectator area of an arena. This is also where arena players are warped to when they die,if spectate-after-death: true in the config-file. The area should be designed so that it is not possible for the spectators to wander out (into the arena or away from the area), because spectators are invincible.<br />
<br />
Exit point: <br />
Upon typing /ma leave, arena players and spectators will be warped to the location they joined from, unless the arena has an exit warp (optional). Using exit points, it is possible to control exactly where players go after a session.<br />
<br />
About regions, warps, etc.<br />
<br />
Once our arena is built, it's time to set up the MobArena regions, warps, and points. Before we do so, let's take a look at what these things are and what MobArena uses them for...<br />
<br />
Regions: <br />
An arena needs an arena region, and optionally a lobby region. MobArena uses the arena region to make sure that players aren't cheating (by kicking them from the arena if they move outside the region), and to make sure that only MobArena's own mobs are spawned inside of it. MobArena is extremely xenophobic (afraid of strangers), so it tries its best to keep unwanted mobs out of the sessions. Regions are set using the Region tools.<br />
<br />
Warps: <br />
When players join a MobArena session, they are teleported to the lobby warp inside the lobby, where they will pick their class and ready up using the ready block (block of iron). When everyone is ready, the players are teleported to the arena warp inside of the arena. Spectators will be teleported to the spectator warp in the spectator area, and when players leave an arena, they will either be teleported to where they joined from, or to the exit warp, if it has been set up. Warps are set using the Warps tool.<br />
<br />
Spawnpoints: <br />
The spawnpoints of an arena are the locations where monsters can spawn from. MobArena will only spawn monsters from spawnpoints that have players nearby (in a 15-block radius). Note that<br />
the number of mobs spawned doesn't depend on how many spawnpoints an arena has - the number of mobs is determined by a formula (see Formulas) that only involves the wave number and <br />
player count (unless you use fixed amounts). Spawnpoints are added using the Spawnpoints tool.<br />
<br />
Containers: <br />
The containers of an arena are locations of chests, dispensers, etc. which contain items that will be renewed when the arena ends. Only registered containers will have their contents <br />
renewed, so it is not enough to simply put a chest in the arena - it also needs to be registered using the Chests tool.<br />
<br />
==设置模式==<br />
We will set up the arena using Setup Mode. When we enter Setup Mode, MobArena will temporarily store our inventory and give us a set of golden tools (the Toolbox), each with a different function. 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.<br />
<br />
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.<br />
<br />
To leave Setup Mode: Type done.<br />
<br />
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.<br />
<br />
In the next section, we will take a look at the different commands available in Setup Mode...<br />
<br />
==设置模式的命令==<br />
<br />
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.<br />
<br />
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.<br />
<br />
done<br />
Leave Setup Mode.<br />
Aliases: end stop done quit<br />
<br />
help<br />
Display help screen.<br />
Aliases: ? h<br />
<br />
missing<br />
Display a list of missing (mandatory) regions, warps, and points.<br />
This command is useful if you have forgotten how far you are in the setup process, and what you still need to set up.<br />
Aliases: miss<br />
<br />
expand <region> <amount> <direction><br />
Expand a region by some amount in some direction.<br />
Valid regions: ar for the arena region, or lr for the lobby region<br />
Valid amounts: positive integers (whole numbers)<br />
Valid directions: up, down, or out<br />
Example: expand ar 5 up<br />
Aliases: exp<br />
<br />
show [<region>|<warp>|<point>]<br />
Show a region, warp, or point(s) as red wool blocks.<br />
Valid regions: ar for the arena region, or lr for the lobby region<br />
Valid warps: arena, lobby, spec, exit<br />
Valid points: spawns (or just sp) for spawnpoints, chests (or just c) for chests<br />
Example: show sp<br />
<br />
==设置时的工具==<br />
<br />
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.<br />
<br />
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.<br />
<br />
===区域工具===<br />
<br />
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.<br />
<br />
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.<br />
<br />
Left-click: Set the first point to be the location of the target block<br />
Right-click: Set the second point to be the location of the target block<br />
<br />
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.<br />
<br />
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.<br />
<br />
===玩家传送点工具===<br />
<br />
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.<br />
<br />
Left-click: Set the currently selected warp on top of the target block<br />
Right-click: Cycle between available warps<br />
<br />
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.<br />
<br />
Note: The arena, lobby, and spectator warps are all required. The exit warp is optional.<br />
<br />
===怪物产生点工具===<br />
<br />
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.<br />
<br />
Left-click: Add a spawnpoint on top of the target block<br />
Right-click: Remove the spawnpoint on top of the target block (if the spawnpoint exists)<br />
<br />
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.<br />
<br />
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.<br />
<br />
===容器工具===<br />
<br />
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.<br />
<br />
Left-click: Register the clicked container (if it wasn't registered)<br />
Right-click: Unregister the clicked container (if it was registered)<br />
<br />
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.<br />
=命令=<br />
==玩家命令==<br />
<br />
These commands can be issued by all players. They include joining, leaving, spectating and listing arenas as well as listing players.<br />
<br />
/ma join (<arena>) or /ma j (<arena>) - Join the arena with the given name.<br />
/ma leave or /ma l - Leave the current arena, or the spectator area.<br />
/ma notready - Get a list of all players who aren't ready.<br />
/ma spec (<arena>) or /ma s (<arena>) - Spectate the arena with the given name.<br />
/ma arenas - Get a list of all arenas. Green names are enabled, gray names are disabled.<br />
/ma players - Get a list of all arena players.<br />
/ma players <arena> - Get a list of arena players in the specified arena.<br />
/ma class <class> - While in the lobby, manually pick the given class instead of punching signs.<br />
==管理员指令==<br />
<br />
Only ops and the console can issue these commands. They include forcefully starting or ending arenas, enabling/disabling individual arenas or MobArena entirely.<br />
<br />
/ma enable - Enable MobArena.<br />
/ma disable - Disable MobArena.<br />
/ma enable <arena> - Enable the arena with the specified name.<br />
/ma disable <arena> - Disable the arena with the specified name.<br />
/ma force end - Forcefully end all arenas.<br />
/ma force end <arena> - Forcefully end the arena with the specified name; forces all players to leave. <br />
/ma force start <arena> - Forcefully start the arena with the specified name; forces all players who aren't ready to leave.<br />
/ma notready <arena> - Get a list of all players in the given arena who aren't ready.<br />
/ma restore <player> - Restore the inventory of the player with the given name, if possible.<br />
/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.<br />
==建设指令==<br />
<br />
Only ops (and the console, if it makes sense) can issue these commands. They include setting warp points, spawnpoints and region points.<br />
<br />
/ma setup <arena> - Enter Setup Mode for the given arena.<br />
/ma addarena <arena> - Create a new arena-node in the current world.<br />
/ma delarena <arena> - Delete the arena with the given name.<br />
/ma editarena <arena> - Toggle Edit Mode for the given arena.<br />
/ma editarena <arena> [true|false] - Turn on or off Edit Mode for the given arena.<br />
/ma setting <arena> - List all per-arena settings for the given arena.<br />
/ma setting <arena> <setting> - Check the current value of the given setting for the given arena.<br />
/ma setting <arena> <setting> <value> - Set the value of the given setting for the given arena to the given value.<br />
/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 <br />
points in your arena are actually covered by spawnpoints or not.<br />
/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<br />
chest, regardless of any local class chests in arena lobbies. This is useful if you want a global class chest for a class.<br />
/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.<br />
/ma auto-degenerate <arena> - Degenerate the arena with the given name, effectively restoring the patch that was "bulldozed" with the auto-generator.<br />
<br />
=权限=<br />
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.<br />
<br />
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!<br />
<br />
==竞技场权限==<br />
<br />
Did you read the note at the top? If not, read it before you continue.<br />
<br />
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.<br />
<br />
bPermissions: ^mobarena.arenas.default<br />
GroupManager: -mobarena.arenas.default<br />
zPermissions: mobarena.arenas.default: false<br />
<br />
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.<br />
<br />
Still confused? Check the sample setup at the bottom of the page!<br />
<br />
==职业权限==<br />
<br />
Did you read the note at the top? If not, read it before you continue.<br />
<br />
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.<br />
<br />
bPermissions: ^mobarena.classes.knight<br />
GroupManager: -mobarena.classes.knight<br />
zPermissions: mobarena.classes.knight: false<br />
<br />
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.<br />
<br />
As with arenas, I recommend letting everyone enjoy all the classes, unless you have a special reason not to.<br />
<br />
Still confused? Check the sample setup at the bottom of the page!<br />
<br />
==命令权限==<br />
<br />
Did you read the note at the top? If not, read it before you continue.<br />
<br />
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!<br />
<br />
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.<br />
<br />
mobarena.use.join<br />
mobarena.use.leave<br />
mobarena.use.spec<br />
mobarena.use.arenalist<br />
mobarena.use.playerlist<br />
mobarena.use.notready<br />
mobarena.use.class<br />
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.<br />
<br />
mobarena.admin.enable<br />
mobarena.admin.kick<br />
mobarena.admin.restore<br />
mobarena.admin.force<br />
mobarena.admin.teleport<br />
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.<br />
<br />
mobarena.setup.config<br />
mobarena.setup.setup<br />
mobarena.setup.setting<br />
mobarena.setup.addarena<br />
mobarena.setup.removearena<br />
mobarena.setup.editarena<br />
mobarena.setup.spawnpoints<br />
mobarena.setup.containers<br />
mobarena.setup.checkdata<br />
mobarena.setup.checkspawns<br />
mobarena.setup.classchest<br />
mobarena.setup.classes<br />
mobarena.setup.leaderboards<br />
mobarena.setup.autogenerate<br />
mobarena.setup.autodegenerate<br />
Sample setup<br />
<br />
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...<br />
<br />
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:<br />
<br />
default-aux: <-- This is the auxiliary group that is to<br />
permissions: be inherited by the default group and<br />
- essentials.balance the donor group. It is not used for<br />
- essentials.pay anything else.<br />
- essentials.sell<br />
<br />
default: <-- This is the default group. It inherits<br />
inherits: default-aux from default-aux, but also revokes the<br />
permissions: permission for the special class.<br />
- -mobarena.classes.diamondknight<br />
<br />
donor: <-- This is the donor group, which also<br />
inherits: default-aux inherits from default-aux, but it<br />
permissions: does not revoke any class permissions,<br />
- essentials.balance.others which means it has access to all of<br />
- essentials.kit them by default.<br />
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.<br />
=物品语法（Item Syntax待搬运）=<br />
=职业箱子（Class Chests待搬运｝=<br />
=怪物波设置（Formulas待搬运）=<br />
=怪物种类（Monster types待搬运）=<br />
以上内容搬运自英文wiki[https://github.com/garbagemule/MobArena/wiki]</div>Zhwhttps://mineplugin.org/index.php?title=MobArena&diff=846MobArena2015-02-17T03:01:56Z<p>Zhw：/* 建设指令 */</p>
<hr />
<div>{{待搬运}}<br />
{{Bukkit Plugin Infobox<br />
|版本=v0.96.9<br />
|兼容服务端版本=1.8.1<br />
|网址=http://dev.bukkit.org/bukkit-plugins/mobarena/}}<br />
[[Category:娱乐]][[Category:机械]]<br />
=安装插件=<br />
Installing MobArena is as easy as these four steps:<br />
Stop your server.<br />
Download the jar-file from the forum thread or Bukkit Dev project page.<br />
Place the jar-file in your server's plugins-folder.<br />
Start the server again. This process will generate a config-file (config.yml) and an announcements-file (announcements.yml) in the plugins/MobArena-folder.<br />
The folder structure is thus:<br />
<br />
plugins/<br />
MobArena.jar<br />
MobArena/<br />
config.yml<br />
announcements.yml<br />
At this point in time, you're probably eager to skip ahead to the arena setup page, but make sure to have a look at setting up the config-file to your liking. The config-file is where you customize the MobArena settings, classes, waves, and rewards.<br />
=建立竞技场（V0.96后）=<br />
==建造一个竞技场==<br />
A well-built arena consists of a lobby for class selection, an arena floor, and either a spectator area or an exit point. Let's go over each one...<br />
<br />
Lobby: <br />
The lobby is where your players will be selecting their classes when they join an arena. A well-formed lobby consists of a sign for each class, which the players will click to choose a <br />
given class, as well as an iron block, which the players will click when they are ready to start. The signs must have the name of the class on the first line (case-sensitive), but you can<br />
put whatever you want on the remaining three lines. Note that MobArena does not "register" class sign creation, so you will not get a confirmation message (if you do, it is another <br />
plugin interfering).<br />
<br />
Arena floor: <br />
This is where your players will be fighting monsters. The arena floor should be enclosed in walls, and possibly with a roof, such that the players and monsters have no way of getting <br />
out. This ensures that players won't be able to just wander out of the arena.<br />
<br />
Spectator area: <br />
When players want to spectate a session, they can use the /ma spec command to get warped to the spectator area of an arena. This is also where arena players are warped to when they die,<br />
if spectate-after-death: true in the config-file. The area should be designed so that it is not possible for the spectators to wander out (into the arena or away from the area), because<br />
spectators are invincible.<br />
<br />
Exit point: <br />
Upon typing /ma leave, arena players and spectators will be warped to the location they joined from, unless the arena has an exit warp (optional). Using exit points, it is possible to <br />
control exactly where players go after a session.<br />
<br />
About regions, warps, etc.<br />
<br />
Once our arena is built, it's time to set up the MobArena regions, warps, and points. Before we do so, let's take a look at what these things are and what MobArena uses them for...<br />
<br />
Regions: <br />
An arena needs an arena region, and optionally a lobby region. MobArena uses the arena region to make sure that players aren't cheating (by kicking them from the arena if they move <br />
outside the region), and to make sure that only MobArena's own mobs are spawned inside of it. MobArena is extremely xenophobic (afraid of strangers), so it tries its best to keep unwanted<br />
mobs out of the sessions. Regions are set using the Region tools.<br />
<br />
Warps: <br />
When players join a MobArena session, they are teleported to the lobby warp inside the lobby, where they will pick their class and ready up using the ready block (block of iron). When <br />
everyone is ready, the players are teleported to the arena warp inside of the arena. Spectators will be teleported to the spectator warp in the spectator area, and when players leave an <br />
arena, they will either be teleported to where they joined from, or to the exit warp, if it has been set up. Warps are set using the Warps tool.<br />
<br />
Spawnpoints: <br />
The spawnpoints of an arena are the locations where monsters can spawn from. MobArena will only spawn monsters from spawnpoints that have players nearby (in a 15-block radius). Note that<br />
the number of mobs spawned doesn't depend on how many spawnpoints an arena has - the number of mobs is determined by a formula (see Formulas) that only involves the wave number and <br />
player count (unless you use fixed amounts). Spawnpoints are added using the Spawnpoints tool.<br />
<br />
Containers: The containers of an arena are locations of chests, dispensers, etc. which contain items that will be renewed when the arena ends. Only registered containers will have their contents renewed, so it is not enough to simply put a chest in the arena - it also needs to be registered using the Chests tool.<br />
<br />
==设置模式==<br />
We will set up the arena using Setup Mode. When we enter Setup Mode, MobArena will temporarily store our inventory and give us a set of golden tools (the Toolbox), each with a different function. 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.<br />
<br />
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.<br />
<br />
To leave Setup Mode: Type done.<br />
<br />
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.<br />
<br />
In the next section, we will take a look at the different commands available in Setup Mode...<br />
<br />
==设置模式的命令==<br />
<br />
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.<br />
<br />
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.<br />
<br />
done<br />
Leave Setup Mode.<br />
Aliases: end stop done quit<br />
<br />
help<br />
Display help screen.<br />
Aliases: ? h<br />
<br />
missing<br />
Display a list of missing (mandatory) regions, warps, and points.<br />
This command is useful if you have forgotten how far you are in the setup process, and what you still need to set up.<br />
Aliases: miss<br />
<br />
expand <region> <amount> <direction><br />
Expand a region by some amount in some direction.<br />
Valid regions: ar for the arena region, or lr for the lobby region<br />
Valid amounts: positive integers (whole numbers)<br />
Valid directions: up, down, or out<br />
Example: expand ar 5 up<br />
Aliases: exp<br />
<br />
show [<region>|<warp>|<point>]<br />
Show a region, warp, or point(s) as red wool blocks.<br />
Valid regions: ar for the arena region, or lr for the lobby region<br />
Valid warps: arena, lobby, spec, exit<br />
Valid points: spawns (or just sp) for spawnpoints, chests (or just c) for chests<br />
Example: show sp<br />
<br />
==设置时的工具==<br />
<br />
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.<br />
<br />
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.<br />
<br />
===区域工具===<br />
<br />
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.<br />
<br />
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.<br />
<br />
Left-click: Set the first point to be the location of the target block<br />
Right-click: Set the second point to be the location of the target block<br />
<br />
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.<br />
<br />
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.<br />
<br />
===玩家传送点工具===<br />
<br />
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.<br />
<br />
Left-click: Set the currently selected warp on top of the target block<br />
Right-click: Cycle between available warps<br />
<br />
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.<br />
<br />
Note: The arena, lobby, and spectator warps are all required. The exit warp is optional.<br />
<br />
===怪物产生点工具===<br />
<br />
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.<br />
<br />
Left-click: Add a spawnpoint on top of the target block<br />
Right-click: Remove the spawnpoint on top of the target block (if the spawnpoint exists)<br />
<br />
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.<br />
<br />
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.<br />
<br />
===容器工具===<br />
<br />
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.<br />
<br />
Left-click: Register the clicked container (if it wasn't registered)<br />
Right-click: Unregister the clicked container (if it was registered)<br />
<br />
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.<br />
=命令=<br />
==玩家命令==<br />
<br />
These commands can be issued by all players. They include joining, leaving, spectating and listing arenas as well as listing players.<br />
<br />
/ma join (<arena>) or /ma j (<arena>) - Join the arena with the given name.<br />
/ma leave or /ma l - Leave the current arena, or the spectator area.<br />
/ma notready - Get a list of all players who aren't ready.<br />
/ma spec (<arena>) or /ma s (<arena>) - Spectate the arena with the given name.<br />
/ma arenas - Get a list of all arenas. Green names are enabled, gray names are disabled.<br />
/ma players - Get a list of all arena players.<br />
/ma players <arena> - Get a list of arena players in the specified arena.<br />
/ma class <class> - While in the lobby, manually pick the given class instead of punching signs.<br />
==管理员指令==<br />
<br />
Only ops and the console can issue these commands. They include forcefully starting or ending arenas, enabling/disabling individual arenas or MobArena entirely.<br />
<br />
/ma enable - Enable MobArena.<br />
/ma disable - Disable MobArena.<br />
/ma enable <arena> - Enable the arena with the specified name.<br />
/ma disable <arena> - Disable the arena with the specified name.<br />
/ma force end - Forcefully end all arenas.<br />
/ma force end <arena> - Forcefully end the arena with the specified name; forces all players to leave. <br />
/ma force start <arena> - Forcefully start the arena with the specified name; forces all players who aren't ready to leave.<br />
/ma notready <arena> - Get a list of all players in the given arena who aren't ready.<br />
/ma restore <player> - Restore the inventory of the player with the given name, if possible.<br />
/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.<br />
==建设指令==<br />
<br />
Only ops (and the console, if it makes sense) can issue these commands. They include setting warp points, spawnpoints and region points.<br />
<br />
/ma setup <arena> - Enter Setup Mode for the given arena.<br />
/ma addarena <arena> - Create a new arena-node in the current world.<br />
/ma delarena <arena> - Delete the arena with the given name.<br />
/ma editarena <arena> - Toggle Edit Mode for the given arena.<br />
/ma editarena <arena> [true|false] - Turn on or off Edit Mode for the given arena.<br />
/ma setting <arena> - List all per-arena settings for the given arena.<br />
/ma setting <arena> <setting> - Check the current value of the given setting for the given arena.<br />
/ma setting <arena> <setting> <value> - Set the value of the given setting for the given arena to the given value.<br />
/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 <br />
points in your arena are actually covered by spawnpoints or not.<br />
/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<br />
chest, regardless of any local class chests in arena lobbies. This is useful if you want a global class chest for a class.<br />
/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.<br />
/ma auto-degenerate <arena> - Degenerate the arena with the given name, effectively restoring the patch that was "bulldozed" with the auto-generator.<br />
<br />
=权限=<br />
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.<br />
<br />
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!<br />
<br />
==竞技场权限==<br />
<br />
Did you read the note at the top? If not, read it before you continue.<br />
<br />
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.<br />
<br />
bPermissions: ^mobarena.arenas.default<br />
GroupManager: -mobarena.arenas.default<br />
zPermissions: mobarena.arenas.default: false<br />
<br />
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.<br />
<br />
Still confused? Check the sample setup at the bottom of the page!<br />
<br />
==职业权限==<br />
<br />
Did you read the note at the top? If not, read it before you continue.<br />
<br />
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.<br />
<br />
bPermissions: ^mobarena.classes.knight<br />
GroupManager: -mobarena.classes.knight<br />
zPermissions: mobarena.classes.knight: false<br />
<br />
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.<br />
<br />
As with arenas, I recommend letting everyone enjoy all the classes, unless you have a special reason not to.<br />
<br />
Still confused? Check the sample setup at the bottom of the page!<br />
<br />
==命令权限==<br />
<br />
Did you read the note at the top? If not, read it before you continue.<br />
<br />
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!<br />
<br />
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.<br />
<br />
mobarena.use.join<br />
mobarena.use.leave<br />
mobarena.use.spec<br />
mobarena.use.arenalist<br />
mobarena.use.playerlist<br />
mobarena.use.notready<br />
mobarena.use.class<br />
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.<br />
<br />
mobarena.admin.enable<br />
mobarena.admin.kick<br />
mobarena.admin.restore<br />
mobarena.admin.force<br />
mobarena.admin.teleport<br />
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.<br />
<br />
mobarena.setup.config<br />
mobarena.setup.setup<br />
mobarena.setup.setting<br />
mobarena.setup.addarena<br />
mobarena.setup.removearena<br />
mobarena.setup.editarena<br />
mobarena.setup.spawnpoints<br />
mobarena.setup.containers<br />
mobarena.setup.checkdata<br />
mobarena.setup.checkspawns<br />
mobarena.setup.classchest<br />
mobarena.setup.classes<br />
mobarena.setup.leaderboards<br />
mobarena.setup.autogenerate<br />
mobarena.setup.autodegenerate<br />
Sample setup<br />
<br />
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...<br />
<br />
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:<br />
<br />
default-aux: <-- This is the auxiliary group that is to<br />
permissions: be inherited by the default group and<br />
- essentials.balance the donor group. It is not used for<br />
- essentials.pay anything else.<br />
- essentials.sell<br />
<br />
default: <-- This is the default group. It inherits<br />
inherits: default-aux from default-aux, but also revokes the<br />
permissions: permission for the special class.<br />
- -mobarena.classes.diamondknight<br />
<br />
donor: <-- This is the donor group, which also<br />
inherits: default-aux inherits from default-aux, but it<br />
permissions: does not revoke any class permissions,<br />
- essentials.balance.others which means it has access to all of<br />
- essentials.kit them by default.<br />
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.<br />
=物品语法（Item Syntax待搬运）=<br />
=职业箱子（Class Chests待搬运｝=<br />
=怪物波设置（Formulas待搬运）=<br />
=怪物种类（Monster types待搬运）=<br />
以上内容搬运自英文wiki[https://github.com/garbagemule/MobArena/wiki]</div>Zhwhttps://mineplugin.org/index.php?title=MobArena&diff=845MobArena2015-02-17T03:01:27Z<p>Zhw：/* 建造一个竞技场 */</p>
<hr />
<div>{{待搬运}}<br />
{{Bukkit Plugin Infobox<br />
|版本=v0.96.9<br />
|兼容服务端版本=1.8.1<br />
|网址=http://dev.bukkit.org/bukkit-plugins/mobarena/}}<br />
[[Category:娱乐]][[Category:机械]]<br />
=安装插件=<br />
Installing MobArena is as easy as these four steps:<br />
Stop your server.<br />
Download the jar-file from the forum thread or Bukkit Dev project page.<br />
Place the jar-file in your server's plugins-folder.<br />
Start the server again. This process will generate a config-file (config.yml) and an announcements-file (announcements.yml) in the plugins/MobArena-folder.<br />
The folder structure is thus:<br />
<br />
plugins/<br />
MobArena.jar<br />
MobArena/<br />
config.yml<br />
announcements.yml<br />
At this point in time, you're probably eager to skip ahead to the arena setup page, but make sure to have a look at setting up the config-file to your liking. The config-file is where you customize the MobArena settings, classes, waves, and rewards.<br />
=建立竞技场（V0.96后）=<br />
==建造一个竞技场==<br />
A well-built arena consists of a lobby for class selection, an arena floor, and either a spectator area or an exit point. Let's go over each one...<br />
<br />
Lobby: <br />
The lobby is where your players will be selecting their classes when they join an arena. A well-formed lobby consists of a sign for each class, which the players will click to choose a <br />
given class, as well as an iron block, which the players will click when they are ready to start. The signs must have the name of the class on the first line (case-sensitive), but you can<br />
put whatever you want on the remaining three lines. Note that MobArena does not "register" class sign creation, so you will not get a confirmation message (if you do, it is another <br />
plugin interfering).<br />
<br />
Arena floor: <br />
This is where your players will be fighting monsters. The arena floor should be enclosed in walls, and possibly with a roof, such that the players and monsters have no way of getting <br />
out. This ensures that players won't be able to just wander out of the arena.<br />
<br />
Spectator area: <br />
When players want to spectate a session, they can use the /ma spec command to get warped to the spectator area of an arena. This is also where arena players are warped to when they die,<br />
if spectate-after-death: true in the config-file. The area should be designed so that it is not possible for the spectators to wander out (into the arena or away from the area), because<br />
spectators are invincible.<br />
<br />
Exit point: <br />
Upon typing /ma leave, arena players and spectators will be warped to the location they joined from, unless the arena has an exit warp (optional). Using exit points, it is possible to <br />
control exactly where players go after a session.<br />
<br />
About regions, warps, etc.<br />
<br />
Once our arena is built, it's time to set up the MobArena regions, warps, and points. Before we do so, let's take a look at what these things are and what MobArena uses them for...<br />
<br />
Regions: <br />
An arena needs an arena region, and optionally a lobby region. MobArena uses the arena region to make sure that players aren't cheating (by kicking them from the arena if they move <br />
outside the region), and to make sure that only MobArena's own mobs are spawned inside of it. MobArena is extremely xenophobic (afraid of strangers), so it tries its best to keep unwanted<br />
mobs out of the sessions. Regions are set using the Region tools.<br />
<br />
Warps: <br />
When players join a MobArena session, they are teleported to the lobby warp inside the lobby, where they will pick their class and ready up using the ready block (block of iron). When <br />
everyone is ready, the players are teleported to the arena warp inside of the arena. Spectators will be teleported to the spectator warp in the spectator area, and when players leave an <br />
arena, they will either be teleported to where they joined from, or to the exit warp, if it has been set up. Warps are set using the Warps tool.<br />
<br />
Spawnpoints: <br />
The spawnpoints of an arena are the locations where monsters can spawn from. MobArena will only spawn monsters from spawnpoints that have players nearby (in a 15-block radius). Note that<br />
the number of mobs spawned doesn't depend on how many spawnpoints an arena has - the number of mobs is determined by a formula (see Formulas) that only involves the wave number and <br />
player count (unless you use fixed amounts). Spawnpoints are added using the Spawnpoints tool.<br />
<br />
Containers: The containers of an arena are locations of chests, dispensers, etc. which contain items that will be renewed when the arena ends. Only registered containers will have their contents renewed, so it is not enough to simply put a chest in the arena - it also needs to be registered using the Chests tool.<br />
<br />
==设置模式==<br />
We will set up the arena using Setup Mode. When we enter Setup Mode, MobArena will temporarily store our inventory and give us a set of golden tools (the Toolbox), each with a different function. 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.<br />
<br />
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.<br />
<br />
To leave Setup Mode: Type done.<br />
<br />
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.<br />
<br />
In the next section, we will take a look at the different commands available in Setup Mode...<br />
<br />
==设置模式的命令==<br />
<br />
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.<br />
<br />
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.<br />
<br />
done<br />
Leave Setup Mode.<br />
Aliases: end stop done quit<br />
<br />
help<br />
Display help screen.<br />
Aliases: ? h<br />
<br />
missing<br />
Display a list of missing (mandatory) regions, warps, and points.<br />
This command is useful if you have forgotten how far you are in the setup process, and what you still need to set up.<br />
Aliases: miss<br />
<br />
expand <region> <amount> <direction><br />
Expand a region by some amount in some direction.<br />
Valid regions: ar for the arena region, or lr for the lobby region<br />
Valid amounts: positive integers (whole numbers)<br />
Valid directions: up, down, or out<br />
Example: expand ar 5 up<br />
Aliases: exp<br />
<br />
show [<region>|<warp>|<point>]<br />
Show a region, warp, or point(s) as red wool blocks.<br />
Valid regions: ar for the arena region, or lr for the lobby region<br />
Valid warps: arena, lobby, spec, exit<br />
Valid points: spawns (or just sp) for spawnpoints, chests (or just c) for chests<br />
Example: show sp<br />
<br />
==设置时的工具==<br />
<br />
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.<br />
<br />
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.<br />
<br />
===区域工具===<br />
<br />
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.<br />
<br />
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.<br />
<br />
Left-click: Set the first point to be the location of the target block<br />
Right-click: Set the second point to be the location of the target block<br />
<br />
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.<br />
<br />
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.<br />
<br />
===玩家传送点工具===<br />
<br />
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.<br />
<br />
Left-click: Set the currently selected warp on top of the target block<br />
Right-click: Cycle between available warps<br />
<br />
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.<br />
<br />
Note: The arena, lobby, and spectator warps are all required. The exit warp is optional.<br />
<br />
===怪物产生点工具===<br />
<br />
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.<br />
<br />
Left-click: Add a spawnpoint on top of the target block<br />
Right-click: Remove the spawnpoint on top of the target block (if the spawnpoint exists)<br />
<br />
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.<br />
<br />
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.<br />
<br />
===容器工具===<br />
<br />
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.<br />
<br />
Left-click: Register the clicked container (if it wasn't registered)<br />
Right-click: Unregister the clicked container (if it was registered)<br />
<br />
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.<br />
=命令=<br />
==玩家命令==<br />
<br />
These commands can be issued by all players. They include joining, leaving, spectating and listing arenas as well as listing players.<br />
<br />
/ma join (<arena>) or /ma j (<arena>) - Join the arena with the given name.<br />
/ma leave or /ma l - Leave the current arena, or the spectator area.<br />
/ma notready - Get a list of all players who aren't ready.<br />
/ma spec (<arena>) or /ma s (<arena>) - Spectate the arena with the given name.<br />
/ma arenas - Get a list of all arenas. Green names are enabled, gray names are disabled.<br />
/ma players - Get a list of all arena players.<br />
/ma players <arena> - Get a list of arena players in the specified arena.<br />
/ma class <class> - While in the lobby, manually pick the given class instead of punching signs.<br />
==管理员指令==<br />
<br />
Only ops and the console can issue these commands. They include forcefully starting or ending arenas, enabling/disabling individual arenas or MobArena entirely.<br />
<br />
/ma enable - Enable MobArena.<br />
/ma disable - Disable MobArena.<br />
/ma enable <arena> - Enable the arena with the specified name.<br />
/ma disable <arena> - Disable the arena with the specified name.<br />
/ma force end - Forcefully end all arenas.<br />
/ma force end <arena> - Forcefully end the arena with the specified name; forces all players to leave. <br />
/ma force start <arena> - Forcefully start the arena with the specified name; forces all players who aren't ready to leave.<br />
/ma notready <arena> - Get a list of all players in the given arena who aren't ready.<br />
/ma restore <player> - Restore the inventory of the player with the given name, if possible.<br />
/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.<br />
==建设指令==<br />
<br />
Only ops (and the console, if it makes sense) can issue these commands. They include setting warp points, spawnpoints and region points.<br />
<br />
/ma setup <arena> - Enter Setup Mode for the given arena.<br />
/ma addarena <arena> - Create a new arena-node in the current world.<br />
/ma delarena <arena> - Delete the arena with the given name.<br />
/ma editarena <arena> - Toggle Edit Mode for the given arena.<br />
/ma editarena <arena> [true|false] - Turn on or off Edit Mode for the given arena.<br />
/ma setting <arena> - List all per-arena settings for the given arena.<br />
/ma setting <arena> <setting> - Check the current value of the given setting for the given arena.<br />
/ma setting <arena> <setting> <value> - Set the value of the given setting for the given arena to the given value.<br />
/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.<br />
/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.<br />
/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.<br />
/ma auto-degenerate <arena> - Degenerate the arena with the given name, effectively restoring the patch that was "bulldozed" with the auto-generator.<br />
=权限=<br />
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.<br />
<br />
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!<br />
<br />
==竞技场权限==<br />
<br />
Did you read the note at the top? If not, read it before you continue.<br />
<br />
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.<br />
<br />
bPermissions: ^mobarena.arenas.default<br />
GroupManager: -mobarena.arenas.default<br />
zPermissions: mobarena.arenas.default: false<br />
<br />
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.<br />
<br />
Still confused? Check the sample setup at the bottom of the page!<br />
<br />
==职业权限==<br />
<br />
Did you read the note at the top? If not, read it before you continue.<br />
<br />
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.<br />
<br />
bPermissions: ^mobarena.classes.knight<br />
GroupManager: -mobarena.classes.knight<br />
zPermissions: mobarena.classes.knight: false<br />
<br />
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.<br />
<br />
As with arenas, I recommend letting everyone enjoy all the classes, unless you have a special reason not to.<br />
<br />
Still confused? Check the sample setup at the bottom of the page!<br />
<br />
==命令权限==<br />
<br />
Did you read the note at the top? If not, read it before you continue.<br />
<br />
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!<br />
<br />
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.<br />
<br />
mobarena.use.join<br />
mobarena.use.leave<br />
mobarena.use.spec<br />
mobarena.use.arenalist<br />
mobarena.use.playerlist<br />
mobarena.use.notready<br />
mobarena.use.class<br />
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.<br />
<br />
mobarena.admin.enable<br />
mobarena.admin.kick<br />
mobarena.admin.restore<br />
mobarena.admin.force<br />
mobarena.admin.teleport<br />
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.<br />
<br />
mobarena.setup.config<br />
mobarena.setup.setup<br />
mobarena.setup.setting<br />
mobarena.setup.addarena<br />
mobarena.setup.removearena<br />
mobarena.setup.editarena<br />
mobarena.setup.spawnpoints<br />
mobarena.setup.containers<br />
mobarena.setup.checkdata<br />
mobarena.setup.checkspawns<br />
mobarena.setup.classchest<br />
mobarena.setup.classes<br />
mobarena.setup.leaderboards<br />
mobarena.setup.autogenerate<br />
mobarena.setup.autodegenerate<br />
Sample setup<br />
<br />
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...<br />
<br />
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:<br />
<br />
default-aux: <-- This is the auxiliary group that is to<br />
permissions: be inherited by the default group and<br />
- essentials.balance the donor group. It is not used for<br />
- essentials.pay anything else.<br />
- essentials.sell<br />
<br />
default: <-- This is the default group. It inherits<br />
inherits: default-aux from default-aux, but also revokes the<br />
permissions: permission for the special class.<br />
- -mobarena.classes.diamondknight<br />
<br />
donor: <-- This is the donor group, which also<br />
inherits: default-aux inherits from default-aux, but it<br />
permissions: does not revoke any class permissions,<br />
- essentials.balance.others which means it has access to all of<br />
- essentials.kit them by default.<br />
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.<br />
=物品语法（Item Syntax待搬运）=<br />
=职业箱子（Class Chests待搬运｝=<br />
=怪物波设置（Formulas待搬运）=<br />
=怪物种类（Monster types待搬运）=<br />
以上内容搬运自英文wiki[https://github.com/garbagemule/MobArena/wiki]</div>Zhwhttps://mineplugin.org/index.php?title=MobArena&diff=844MobArena2015-02-17T03:00:18Z<p>Zhw：/* 建造一个竞技场 */</p>
<hr />
<div>{{待搬运}}<br />
{{Bukkit Plugin Infobox<br />
|版本=v0.96.9<br />
|兼容服务端版本=1.8.1<br />
|网址=http://dev.bukkit.org/bukkit-plugins/mobarena/}}<br />
[[Category:娱乐]][[Category:机械]]<br />
=安装插件=<br />
Installing MobArena is as easy as these four steps:<br />
Stop your server.<br />
Download the jar-file from the forum thread or Bukkit Dev project page.<br />
Place the jar-file in your server's plugins-folder.<br />
Start the server again. This process will generate a config-file (config.yml) and an announcements-file (announcements.yml) in the plugins/MobArena-folder.<br />
The folder structure is thus:<br />
<br />
plugins/<br />
MobArena.jar<br />
MobArena/<br />
config.yml<br />
announcements.yml<br />
At this point in time, you're probably eager to skip ahead to the arena setup page, but make sure to have a look at setting up the config-file to your liking. The config-file is where you customize the MobArena settings, classes, waves, and rewards.<br />
=建立竞技场（V0.96后）=<br />
==建造一个竞技场==<br />
A well-built arena consists of a lobby for class selection, an arena floor, and either a spectator area or an exit point. Let's go over each one...<br />
<br />
Lobby: <br />
The lobby is where your players will be selecting their classes when they join an arena. A well-formed lobby consists of a sign for each class, which the players will click to choose a given class, as well as an iron block, which the players will click when they are ready to start. The signs must have the name of the class on the first line (case-sensitive), but you can put whatever you want on the remaining three lines. Note that MobArena does not "register" class sign creation, so you will not get a confirmation message (if you do, it is another plugin interfering).<br />
<br />
Arena floor: <br />
This is where your players will be fighting monsters. The arena floor should be enclosed in walls, and possibly with a roof, such that the players and monsters have no way of getting out. This ensures that players won't be able to just wander out of the arena.<br />
<br />
Spectator area: <br />
When players want to spectate a session, they can use the /ma spec command to get warped to the spectator area of an arena. This is also where arena players are warped to when they die, if spectate-after-death: true in the config-file. The area should be designed so that it is not possible for the spectators to wander out (into the arena or away from the area), because spectators are invincible.<br />
<br />
Exit point: <br />
Upon typing /ma leave, arena players and spectators will be warped to the location they joined from, unless the arena has an exit warp (optional). Using exit points, it is possible to control exactly where players go after a session.<br />
<br />
About regions, warps, etc.<br />
<br />
Once our arena is built, it's time to set up the MobArena regions, warps, and points. Before we do so, let's take a look at what these things are and what MobArena uses them for...<br />
<br />
Regions: An arena needs an arena region, and optionally a lobby region. MobArena uses the arena region to make sure that players aren't cheating (by kicking them from the arena if they move outside the region), and to make sure that only MobArena's own mobs are spawned inside of it. MobArena is extremely xenophobic (afraid of strangers), so it tries its best to keep unwanted mobs out of the sessions. Regions are set using the Region tools.<br />
<br />
Warps: When players join a MobArena session, they are teleported to the lobby warp inside the lobby, where they will pick their class and ready up using the ready block (block of iron). When everyone is ready, the players are teleported to the arena warp inside of the arena. Spectators will be teleported to the spectator warp in the spectator area, and when players leave an arena, they will either be teleported to where they joined from, or to the exit warp, if it has been set up. Warps are set using the Warps tool.<br />
<br />
Spawnpoints: The spawnpoints of an arena are the locations where monsters can spawn from. MobArena will only spawn monsters from spawnpoints that have players nearby (in a 15-block radius). Note that the number of mobs spawned doesn't depend on how many spawnpoints an arena has - the number of mobs is determined by a formula (see Formulas) that only involves the wave number and player count (unless you use fixed amounts). Spawnpoints are added using the Spawnpoints tool.<br />
<br />
Containers: The containers of an arena are locations of chests, dispensers, etc. which contain items that will be renewed when the arena ends. Only registered containers will have their contents renewed, so it is not enough to simply put a chest in the arena - it also needs to be registered using the Chests tool.<br />
<br />
==设置模式==<br />
We will set up the arena using Setup Mode. When we enter Setup Mode, MobArena will temporarily store our inventory and give us a set of golden tools (the Toolbox), each with a different function. 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.<br />
<br />
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.<br />
<br />
To leave Setup Mode: Type done.<br />
<br />
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.<br />
<br />
In the next section, we will take a look at the different commands available in Setup Mode...<br />
<br />
==设置模式的命令==<br />
<br />
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.<br />
<br />
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.<br />
<br />
done<br />
Leave Setup Mode.<br />
Aliases: end stop done quit<br />
<br />
help<br />
Display help screen.<br />
Aliases: ? h<br />
<br />
missing<br />
Display a list of missing (mandatory) regions, warps, and points.<br />
This command is useful if you have forgotten how far you are in the setup process, and what you still need to set up.<br />
Aliases: miss<br />
<br />
expand <region> <amount> <direction><br />
Expand a region by some amount in some direction.<br />
Valid regions: ar for the arena region, or lr for the lobby region<br />
Valid amounts: positive integers (whole numbers)<br />
Valid directions: up, down, or out<br />
Example: expand ar 5 up<br />
Aliases: exp<br />
<br />
show [<region>|<warp>|<point>]<br />
Show a region, warp, or point(s) as red wool blocks.<br />
Valid regions: ar for the arena region, or lr for the lobby region<br />
Valid warps: arena, lobby, spec, exit<br />
Valid points: spawns (or just sp) for spawnpoints, chests (or just c) for chests<br />
Example: show sp<br />
<br />
==设置时的工具==<br />
<br />
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.<br />
<br />
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.<br />
<br />
===区域工具===<br />
<br />
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.<br />
<br />
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.<br />
<br />
Left-click: Set the first point to be the location of the target block<br />
Right-click: Set the second point to be the location of the target block<br />
<br />
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.<br />
<br />
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.<br />
<br />
===玩家传送点工具===<br />
<br />
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.<br />
<br />
Left-click: Set the currently selected warp on top of the target block<br />
Right-click: Cycle between available warps<br />
<br />
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.<br />
<br />
Note: The arena, lobby, and spectator warps are all required. The exit warp is optional.<br />
<br />
===怪物产生点工具===<br />
<br />
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.<br />
<br />
Left-click: Add a spawnpoint on top of the target block<br />
Right-click: Remove the spawnpoint on top of the target block (if the spawnpoint exists)<br />
<br />
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.<br />
<br />
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.<br />
<br />
===容器工具===<br />
<br />
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.<br />
<br />
Left-click: Register the clicked container (if it wasn't registered)<br />
Right-click: Unregister the clicked container (if it was registered)<br />
<br />
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.<br />
=命令=<br />
==玩家命令==<br />
<br />
These commands can be issued by all players. They include joining, leaving, spectating and listing arenas as well as listing players.<br />
<br />
/ma join (<arena>) or /ma j (<arena>) - Join the arena with the given name.<br />
/ma leave or /ma l - Leave the current arena, or the spectator area.<br />
/ma notready - Get a list of all players who aren't ready.<br />
/ma spec (<arena>) or /ma s (<arena>) - Spectate the arena with the given name.<br />
/ma arenas - Get a list of all arenas. Green names are enabled, gray names are disabled.<br />
/ma players - Get a list of all arena players.<br />
/ma players <arena> - Get a list of arena players in the specified arena.<br />
/ma class <class> - While in the lobby, manually pick the given class instead of punching signs.<br />
==管理员指令==<br />
<br />
Only ops and the console can issue these commands. They include forcefully starting or ending arenas, enabling/disabling individual arenas or MobArena entirely.<br />
<br />
/ma enable - Enable MobArena.<br />
/ma disable - Disable MobArena.<br />
/ma enable <arena> - Enable the arena with the specified name.<br />
/ma disable <arena> - Disable the arena with the specified name.<br />
/ma force end - Forcefully end all arenas.<br />
/ma force end <arena> - Forcefully end the arena with the specified name; forces all players to leave. <br />
/ma force start <arena> - Forcefully start the arena with the specified name; forces all players who aren't ready to leave.<br />
/ma notready <arena> - Get a list of all players in the given arena who aren't ready.<br />
/ma restore <player> - Restore the inventory of the player with the given name, if possible.<br />
/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.<br />
==建设指令==<br />
<br />
Only ops (and the console, if it makes sense) can issue these commands. They include setting warp points, spawnpoints and region points.<br />
<br />
/ma setup <arena> - Enter Setup Mode for the given arena.<br />
/ma addarena <arena> - Create a new arena-node in the current world.<br />
/ma delarena <arena> - Delete the arena with the given name.<br />
/ma editarena <arena> - Toggle Edit Mode for the given arena.<br />
/ma editarena <arena> [true|false] - Turn on or off Edit Mode for the given arena.<br />
/ma setting <arena> - List all per-arena settings for the given arena.<br />
/ma setting <arena> <setting> - Check the current value of the given setting for the given arena.<br />
/ma setting <arena> <setting> <value> - Set the value of the given setting for the given arena to the given value.<br />
/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.<br />
/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.<br />
/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.<br />
/ma auto-degenerate <arena> - Degenerate the arena with the given name, effectively restoring the patch that was "bulldozed" with the auto-generator.<br />
=权限=<br />
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.<br />
<br />
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!<br />
<br />
==竞技场权限==<br />
<br />
Did you read the note at the top? If not, read it before you continue.<br />
<br />
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.<br />
<br />
bPermissions: ^mobarena.arenas.default<br />
GroupManager: -mobarena.arenas.default<br />
zPermissions: mobarena.arenas.default: false<br />
<br />
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.<br />
<br />
Still confused? Check the sample setup at the bottom of the page!<br />
<br />
==职业权限==<br />
<br />
Did you read the note at the top? If not, read it before you continue.<br />
<br />
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.<br />
<br />
bPermissions: ^mobarena.classes.knight<br />
GroupManager: -mobarena.classes.knight<br />
zPermissions: mobarena.classes.knight: false<br />
<br />
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.<br />
<br />
As with arenas, I recommend letting everyone enjoy all the classes, unless you have a special reason not to.<br />
<br />
Still confused? Check the sample setup at the bottom of the page!<br />
<br />
==命令权限==<br />
<br />
Did you read the note at the top? If not, read it before you continue.<br />
<br />
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!<br />
<br />
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.<br />
<br />
mobarena.use.join<br />
mobarena.use.leave<br />
mobarena.use.spec<br />
mobarena.use.arenalist<br />
mobarena.use.playerlist<br />
mobarena.use.notready<br />
mobarena.use.class<br />
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.<br />
<br />
mobarena.admin.enable<br />
mobarena.admin.kick<br />
mobarena.admin.restore<br />
mobarena.admin.force<br />
mobarena.admin.teleport<br />
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.<br />
<br />
mobarena.setup.config<br />
mobarena.setup.setup<br />
mobarena.setup.setting<br />
mobarena.setup.addarena<br />
mobarena.setup.removearena<br />
mobarena.setup.editarena<br />
mobarena.setup.spawnpoints<br />
mobarena.setup.containers<br />
mobarena.setup.checkdata<br />
mobarena.setup.checkspawns<br />
mobarena.setup.classchest<br />
mobarena.setup.classes<br />
mobarena.setup.leaderboards<br />
mobarena.setup.autogenerate<br />
mobarena.setup.autodegenerate<br />
Sample setup<br />
<br />
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...<br />
<br />
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:<br />
<br />
default-aux: <-- This is the auxiliary group that is to<br />
permissions: be inherited by the default group and<br />
- essentials.balance the donor group. It is not used for<br />
- essentials.pay anything else.<br />
- essentials.sell<br />
<br />
default: <-- This is the default group. It inherits<br />
inherits: default-aux from default-aux, but also revokes the<br />
permissions: permission for the special class.<br />
- -mobarena.classes.diamondknight<br />
<br />
donor: <-- This is the donor group, which also<br />
inherits: default-aux inherits from default-aux, but it<br />
permissions: does not revoke any class permissions,<br />
- essentials.balance.others which means it has access to all of<br />
- essentials.kit them by default.<br />
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.<br />
=物品语法（Item Syntax待搬运）=<br />
=职业箱子（Class Chests待搬运｝=<br />
=怪物波设置（Formulas待搬运）=<br />
=怪物种类（Monster types待搬运）=<br />
以上内容搬运自英文wiki[https://github.com/garbagemule/MobArena/wiki]</div>Zhwhttps://mineplugin.org/index.php?title=MobArena&diff=843MobArena2015-02-17T02:59:45Z<p>Zhw：/* 建造一个竞技场 */</p>
<hr />
<div>{{待搬运}}<br />
{{Bukkit Plugin Infobox<br />
|版本=v0.96.9<br />
|兼容服务端版本=1.8.1<br />
|网址=http://dev.bukkit.org/bukkit-plugins/mobarena/}}<br />
[[Category:娱乐]][[Category:机械]]<br />
=安装插件=<br />
Installing MobArena is as easy as these four steps:<br />
Stop your server.<br />
Download the jar-file from the forum thread or Bukkit Dev project page.<br />
Place the jar-file in your server's plugins-folder.<br />
Start the server again. This process will generate a config-file (config.yml) and an announcements-file (announcements.yml) in the plugins/MobArena-folder.<br />
The folder structure is thus:<br />
<br />
plugins/<br />
MobArena.jar<br />
MobArena/<br />
config.yml<br />
announcements.yml<br />
At this point in time, you're probably eager to skip ahead to the arena setup page, but make sure to have a look at setting up the config-file to your liking. The config-file is where you customize the MobArena settings, classes, waves, and rewards.<br />
=建立竞技场（V0.96后）=<br />
==建造一个竞技场==<br />
A well-built arena consists of a lobby for class selection, an arena floor, and either a spectator area or an exit point. Let's go over each one...<br />
<br />
Lobby: <br />
The lobby is where your players will be selecting their classes when they join an arena. A well-formed lobby consists of a sign for each class, which the players will click to choose a given class, as well as an iron block, which the players will click when they are ready to start. The signs must have the name of the class on the first line (case-sensitive), but you can put whatever you want on the remaining three lines. Note that MobArena does not "register" class sign creation, so you will not get a confirmation message (if you do, it is another plugin interfering).<br />
<br />
Arena floor: <br />
This is where your players will be fighting monsters. The arena floor should be enclosed in walls, and possibly with a roof, such that the players and monsters have no way of getting out. This ensures that players won't be able to just wander out of the arena.<br />
<br />
Spectator area: <br />
When players want to spectate a session, they can use the /ma spec command to get warped to the spectator area of an arena. This is also where arena players are warped to when they die, if spectate-after-death: true in the config-file. The area should be designed so that it is not possible for the spectators to wander out (into the arena or away from the area), because spectators are invincible.<br />
<br />
Exit point: <br />
Upon typing /ma leave, arena players and spectators will be warped to the location they joined from, unless the arena has an exit warp (optional). Using exit points, it is possible to control exactly where players go after a session.<br />
<br />
About regions, warps, etc.<br />
<br />
Once our arena is built, it's time to set up the MobArena regions, warps, and points. Before we do so, let's take a look at what these things are and what MobArena uses them for...<br />
<br />
Regions: An arena needs an arena region, and optionally a lobby region. MobArena uses the arena region to make sure that players aren't cheating (by kicking them from the arena if they move outside the region), and to make sure that only MobArena's own mobs are spawned inside of it. MobArena is extremely xenophobic (afraid of strangers), so it tries its best to keep unwanted mobs out of the sessions. Regions are set using the Region tools.<br />
<br />
Warps: When players join a MobArena session, they are teleported to the lobby warp inside the lobby, where they will pick their class and ready up using the ready block (block of iron). When everyone is ready, the players are teleported to the arena warp inside of the arena. Spectators will be teleported to the spectator warp in the spectator area, and when players leave an arena, they will either be teleported to where they joined from, or to the exit warp, if it has been set up. Warps are set using the Warps tool.<br />
<br />
Spawnpoints: The spawnpoints of an arena are the locations where monsters can spawn from. MobArena will only spawn monsters from spawnpoints that have players nearby (in a 15-block radius). Note that the number of mobs spawned doesn't depend on how many spawnpoints an arena has - the number of mobs is determined by a formula (see Formulas) that only involves the wave number and player count (unless you use fixed amounts). Spawnpoints are added using the Spawnpoints tool.<br />
<br />
Containers: The containers of an arena are locations of chests, dispensers, etc. which contain items that will be renewed when the arena ends. Only registered containers will have their contents renewed, so it is not enough to simply put a chest in the arena - it also needs to be registered using the Chests tool.<br />
<br />
==设置模式==<br />
We will set up the arena using Setup Mode. When we enter Setup Mode, MobArena will temporarily store our inventory and give us a set of golden tools (the Toolbox), each with a different function. 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.<br />
<br />
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.<br />
<br />
To leave Setup Mode: Type done.<br />
<br />
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.<br />
<br />
In the next section, we will take a look at the different commands available in Setup Mode...<br />
<br />
==设置模式的命令==<br />
<br />
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.<br />
<br />
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.<br />
<br />
done<br />
Leave Setup Mode.<br />
Aliases: end stop done quit<br />
<br />
help<br />
Display help screen.<br />
Aliases: ? h<br />
<br />
missing<br />
Display a list of missing (mandatory) regions, warps, and points.<br />
This command is useful if you have forgotten how far you are in the setup process, and what you still need to set up.<br />
Aliases: miss<br />
<br />
expand <region> <amount> <direction><br />
Expand a region by some amount in some direction.<br />
Valid regions: ar for the arena region, or lr for the lobby region<br />
Valid amounts: positive integers (whole numbers)<br />
Valid directions: up, down, or out<br />
Example: expand ar 5 up<br />
Aliases: exp<br />
<br />
show [<region>|<warp>|<point>]<br />
Show a region, warp, or point(s) as red wool blocks.<br />
Valid regions: ar for the arena region, or lr for the lobby region<br />
Valid warps: arena, lobby, spec, exit<br />
Valid points: spawns (or just sp) for spawnpoints, chests (or just c) for chests<br />
Example: show sp<br />
<br />
==设置时的工具==<br />
<br />
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.<br />
<br />
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.<br />
<br />
===区域工具===<br />
<br />
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.<br />
<br />
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.<br />
<br />
Left-click: Set the first point to be the location of the target block<br />
Right-click: Set the second point to be the location of the target block<br />
<br />
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.<br />
<br />
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.<br />
<br />
===玩家传送点工具===<br />
<br />
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.<br />
<br />
Left-click: Set the currently selected warp on top of the target block<br />
Right-click: Cycle between available warps<br />
<br />
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.<br />
<br />
Note: The arena, lobby, and spectator warps are all required. The exit warp is optional.<br />
<br />
===怪物产生点工具===<br />
<br />
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.<br />
<br />
Left-click: Add a spawnpoint on top of the target block<br />
Right-click: Remove the spawnpoint on top of the target block (if the spawnpoint exists)<br />
<br />
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.<br />
<br />
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.<br />
<br />
===容器工具===<br />
<br />
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.<br />
<br />
Left-click: Register the clicked container (if it wasn't registered)<br />
Right-click: Unregister the clicked container (if it was registered)<br />
<br />
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.<br />
=命令=<br />
==玩家命令==<br />
<br />
These commands can be issued by all players. They include joining, leaving, spectating and listing arenas as well as listing players.<br />
<br />
/ma join (<arena>) or /ma j (<arena>) - Join the arena with the given name.<br />
/ma leave or /ma l - Leave the current arena, or the spectator area.<br />
/ma notready - Get a list of all players who aren't ready.<br />
/ma spec (<arena>) or /ma s (<arena>) - Spectate the arena with the given name.<br />
/ma arenas - Get a list of all arenas. Green names are enabled, gray names are disabled.<br />
/ma players - Get a list of all arena players.<br />
/ma players <arena> - Get a list of arena players in the specified arena.<br />
/ma class <class> - While in the lobby, manually pick the given class instead of punching signs.<br />
==管理员指令==<br />
<br />
Only ops and the console can issue these commands. They include forcefully starting or ending arenas, enabling/disabling individual arenas or MobArena entirely.<br />
<br />
/ma enable - Enable MobArena.<br />
/ma disable - Disable MobArena.<br />
/ma enable <arena> - Enable the arena with the specified name.<br />
/ma disable <arena> - Disable the arena with the specified name.<br />
/ma force end - Forcefully end all arenas.<br />
/ma force end <arena> - Forcefully end the arena with the specified name; forces all players to leave. <br />
/ma force start <arena> - Forcefully start the arena with the specified name; forces all players who aren't ready to leave.<br />
/ma notready <arena> - Get a list of all players in the given arena who aren't ready.<br />
/ma restore <player> - Restore the inventory of the player with the given name, if possible.<br />
/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.<br />
==建设指令==<br />
<br />
Only ops (and the console, if it makes sense) can issue these commands. They include setting warp points, spawnpoints and region points.<br />
<br />
/ma setup <arena> - Enter Setup Mode for the given arena.<br />
/ma addarena <arena> - Create a new arena-node in the current world.<br />
/ma delarena <arena> - Delete the arena with the given name.<br />
/ma editarena <arena> - Toggle Edit Mode for the given arena.<br />
/ma editarena <arena> [true|false] - Turn on or off Edit Mode for the given arena.<br />
/ma setting <arena> - List all per-arena settings for the given arena.<br />
/ma setting <arena> <setting> - Check the current value of the given setting for the given arena.<br />
/ma setting <arena> <setting> <value> - Set the value of the given setting for the given arena to the given value.<br />
/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.<br />
/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.<br />
/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.<br />
/ma auto-degenerate <arena> - Degenerate the arena with the given name, effectively restoring the patch that was "bulldozed" with the auto-generator.<br />
=权限=<br />
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.<br />
<br />
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!<br />
<br />
==竞技场权限==<br />
<br />
Did you read the note at the top? If not, read it before you continue.<br />
<br />
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.<br />
<br />
bPermissions: ^mobarena.arenas.default<br />
GroupManager: -mobarena.arenas.default<br />
zPermissions: mobarena.arenas.default: false<br />
<br />
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.<br />
<br />
Still confused? Check the sample setup at the bottom of the page!<br />
<br />
==职业权限==<br />
<br />
Did you read the note at the top? If not, read it before you continue.<br />
<br />
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.<br />
<br />
bPermissions: ^mobarena.classes.knight<br />
GroupManager: -mobarena.classes.knight<br />
zPermissions: mobarena.classes.knight: false<br />
<br />
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.<br />
<br />
As with arenas, I recommend letting everyone enjoy all the classes, unless you have a special reason not to.<br />
<br />
Still confused? Check the sample setup at the bottom of the page!<br />
<br />
==命令权限==<br />
<br />
Did you read the note at the top? If not, read it before you continue.<br />
<br />
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!<br />
<br />
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.<br />
<br />
mobarena.use.join<br />
mobarena.use.leave<br />
mobarena.use.spec<br />
mobarena.use.arenalist<br />
mobarena.use.playerlist<br />
mobarena.use.notready<br />
mobarena.use.class<br />
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.<br />
<br />
mobarena.admin.enable<br />
mobarena.admin.kick<br />
mobarena.admin.restore<br />
mobarena.admin.force<br />
mobarena.admin.teleport<br />
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.<br />
<br />
mobarena.setup.config<br />
mobarena.setup.setup<br />
mobarena.setup.setting<br />
mobarena.setup.addarena<br />
mobarena.setup.removearena<br />
mobarena.setup.editarena<br />
mobarena.setup.spawnpoints<br />
mobarena.setup.containers<br />
mobarena.setup.checkdata<br />
mobarena.setup.checkspawns<br />
mobarena.setup.classchest<br />
mobarena.setup.classes<br />
mobarena.setup.leaderboards<br />
mobarena.setup.autogenerate<br />
mobarena.setup.autodegenerate<br />
Sample setup<br />
<br />
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...<br />
<br />
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:<br />
<br />
default-aux: <-- This is the auxiliary group that is to<br />
permissions: be inherited by the default group and<br />
- essentials.balance the donor group. It is not used for<br />
- essentials.pay anything else.<br />
- essentials.sell<br />
<br />
default: <-- This is the default group. It inherits<br />
inherits: default-aux from default-aux, but also revokes the<br />
permissions: permission for the special class.<br />
- -mobarena.classes.diamondknight<br />
<br />
donor: <-- This is the donor group, which also<br />
inherits: default-aux inherits from default-aux, but it<br />
permissions: does not revoke any class permissions,<br />
- essentials.balance.others which means it has access to all of<br />
- essentials.kit them by default.<br />
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.<br />
=物品语法（Item Syntax待搬运）=<br />
=职业箱子（Class Chests待搬运｝=<br />
=怪物波设置（Formulas待搬运）=<br />
=怪物种类（Monster types待搬运）=<br />
以上内容搬运自英文wiki[https://github.com/garbagemule/MobArena/wiki]</div>Zhwhttps://mineplugin.org/index.php?title=EnchantExtreme&diff=842EnchantExtreme2015-02-17T02:56:16Z<p>Zhw：</p>
<hr />
<div>{{Bukkit Plugin Infobox<br />
|版本=v1.1<br />
|兼容服务端版本=CB1.4.7-R1.0<br />
|网址=http://dev.bukkit.org/bukkit-plugins/enchantextreme/files/<br />
}}<br />
[[Category:娱乐]][[Category:机械]]<br />
[[文件:EnchantExtreme.png]]<br />
此插件测试结果：1.7.2,1.7.10都可用<br />
=功能特性=<br />
附魔任何物品以任何附魔的任何级别.<br />
附魔你手上的物品.<br />
可以设置你手上物品名字和lore（介绍）支持颜色代码.<br />
能获取你手上物品的物品ID.<br />
简单和快捷的游戏内命令.<br />
支持MCStats.<br />
=命令和权限=<br />
/eex <br />
插件主要命令 enchantextreme.eex<br />
/eex list <br />
列出可用的附魔 enchantextreme.eex<br />
/eex help <br />
打开插件的帮助面板 enchantextreme.eex<br />
/eex <物品ID> <附魔名称> <等级> <br />
给你物品栏中的物品附魔 enchantextreme.eex<br />
/eex give <玩家名> <物品ID> <附魔名称> <等级> <br />
给指定玩家一个指定附魔物品 enchantextreme.eex<br />
/eex give <玩家名> <物品ID> <附魔名称> <等级> <名字> <br />
添加一个指定名字的指定附魔物品给指定玩家 enchantextreme.eex<br />
/eex <物品ID> <附魔名称> <等级> <名字> <br />
添加指定物品的附魔并修改名字 enchantextreme.eex<br />
/eex hand <附魔名称> <等级> <br />
附魔你手中的物品 enchantextreme.eex<br />
/eex hand <附魔名称> <等级> <名字> <br />
附魔并命名你手中的物品 enchantextreme.eex<br />
/setname <名字> <br />
修改你手中物品的名字 enchantextreme.setname<br />
/setlore <lore> <br />
修改你手中物品的lore enchantextreme.setlore<br />
/itemid <br />
View the Item ID of the item in your hand enchantextreme.itemid<br />
、Post any requests or suggestions in the comments below. Suggestions may be added to future updates.</div>Zhwhttps://mineplugin.org/index.php?title=%E6%96%87%E4%BB%B6:EnchantExtreme.png&diff=841文件:EnchantExtreme.png2015-02-17T02:56:04Z<p>Zhw：</p>
<hr />
<div></div>Zhwhttps://mineplugin.org/index.php?title=EnchantExtreme&diff=840EnchantExtreme2015-02-17T02:51:57Z<p>Zhw：以“{{Bukkit Plugin Infobox |版本=v1.1 |兼容服务端版本=CB1.4.7-R1.0 |网址=http://dev.bukkit.org/bukkit-plugins/enchantextreme/files/ }} Category:娱乐C...”为内容创建页面</p>
<hr />
<div>{{Bukkit Plugin Infobox<br />
|版本=v1.1<br />
|兼容服务端版本=CB1.4.7-R1.0<br />
|网址=http://dev.bukkit.org/bukkit-plugins/enchantextreme/files/<br />
}}<br />
[[Category:娱乐]][[Category:机械]]<br />
此插件测试结果：1.7.2,1.7.10都可用<br />
=功能特性=<br />
附魔任何物品以任何附魔的任何级别.<br />
附魔你手上的物品.<br />
可以设置你手上物品名字和lore（介绍）支持颜色代码.<br />
能获取你手上物品的物品ID.<br />
简单和快捷的游戏内命令.<br />
支持MCStats.<br />
=命令和权限=<br />
/eex <br />
插件主要命令 enchantextreme.eex<br />
/eex list <br />
列出可用的附魔 enchantextreme.eex<br />
/eex help <br />
打开插件的帮助面板 enchantextreme.eex<br />
/eex <物品ID> <附魔名称> <等级> <br />
给你物品栏中的物品附魔 enchantextreme.eex<br />
/eex give <玩家名> <物品ID> <附魔名称> <等级> <br />
给指定玩家一个指定附魔物品 enchantextreme.eex<br />
/eex give <玩家名> <物品ID> <附魔名称> <等级> <名字> <br />
添加一个指定名字的指定附魔物品给指定玩家 enchantextreme.eex<br />
/eex <物品ID> <附魔名称> <等级> <名字> <br />
添加指定物品的附魔并修改名字 enchantextreme.eex<br />
/eex hand <附魔名称> <等级> <br />
附魔你手中的物品 enchantextreme.eex<br />
/eex hand <附魔名称> <等级> <名字> <br />
附魔并命名你手中的物品 enchantextreme.eex<br />
/setname <名字> <br />
修改你手中物品的名字 enchantextreme.setname<br />
/setlore <lore> <br />
修改你手中物品的lore enchantextreme.setlore<br />
/itemid <br />
View the Item ID of the item in your hand enchantextreme.itemid<br />
、Post any requests or suggestions in the comments below. Suggestions may be added to future updates.</div>Zhwhttps://mineplugin.org/index.php?title=MobArena&diff=839MobArena2015-02-17T02:35:47Z<p>Zhw：</p>
<hr />
<div>{{待搬运}}<br />
{{Bukkit Plugin Infobox<br />
|版本=v0.96.9<br />
|兼容服务端版本=1.8.1<br />
|网址=http://dev.bukkit.org/bukkit-plugins/mobarena/}}<br />
[[Category:娱乐]][[Category:机械]]<br />
=安装插件=<br />
Installing MobArena is as easy as these four steps:<br />
Stop your server.<br />
Download the jar-file from the forum thread or Bukkit Dev project page.<br />
Place the jar-file in your server's plugins-folder.<br />
Start the server again. This process will generate a config-file (config.yml) and an announcements-file (announcements.yml) in the plugins/MobArena-folder.<br />
The folder structure is thus:<br />
<br />
plugins/<br />
MobArena.jar<br />
MobArena/<br />
config.yml<br />
announcements.yml<br />
At this point in time, you're probably eager to skip ahead to the arena setup page, but make sure to have a look at setting up the config-file to your liking. The config-file is where you customize the MobArena settings, classes, waves, and rewards.<br />
=建立竞技场（V0.96后）=<br />
==建造一个竞技场==<br />
A well-built arena consists of a lobby for class selection, an arena floor, and either a spectator area or an exit point. Let's go over each one...<br />
<br />
Lobby: The lobby is where your players will be selecting their classes when they join an arena. A well-formed lobby consists of a sign for each class, which the players will click to choose a given class, as well as an iron block, which the players will click when they are ready to start. The signs must have the name of the class on the first line (case-sensitive), but you can put whatever you want on the remaining three lines. Note that MobArena does not "register" class sign creation, so you will not get a confirmation message (if you do, it is another plugin interfering).<br />
<br />
Arena floor: This is where your players will be fighting monsters. The arena floor should be enclosed in walls, and possibly with a roof, such that the players and monsters have no way of getting out. This ensures that players won't be able to just wander out of the arena.<br />
<br />
Spectator area: When players want to spectate a session, they can use the /ma spec command to get warped to the spectator area of an arena. This is also where arena players are warped to when they die, if spectate-after-death: true in the config-file. The area should be designed so that it is not possible for the spectators to wander out (into the arena or away from the area), because spectators are invincible.<br />
<br />
Exit point: Upon typing /ma leave, arena players and spectators will be warped to the location they joined from, unless the arena has an exit warp (optional). Using exit points, it is possible to control exactly where players go after a session.<br />
<br />
About regions, warps, etc.<br />
<br />
Once our arena is built, it's time to set up the MobArena regions, warps, and points. Before we do so, let's take a look at what these things are and what MobArena uses them for...<br />
<br />
Regions: An arena needs an arena region, and optionally a lobby region. MobArena uses the arena region to make sure that players aren't cheating (by kicking them from the arena if they move outside the region), and to make sure that only MobArena's own mobs are spawned inside of it. MobArena is extremely xenophobic (afraid of strangers), so it tries its best to keep unwanted mobs out of the sessions. Regions are set using the Region tools.<br />
<br />
Warps: When players join a MobArena session, they are teleported to the lobby warp inside the lobby, where they will pick their class and ready up using the ready block (block of iron). When everyone is ready, the players are teleported to the arena warp inside of the arena. Spectators will be teleported to the spectator warp in the spectator area, and when players leave an arena, they will either be teleported to where they joined from, or to the exit warp, if it has been set up. Warps are set using the Warps tool.<br />
<br />
Spawnpoints: The spawnpoints of an arena are the locations where monsters can spawn from. MobArena will only spawn monsters from spawnpoints that have players nearby (in a 15-block radius). Note that the number of mobs spawned doesn't depend on how many spawnpoints an arena has - the number of mobs is determined by a formula (see Formulas) that only involves the wave number and player count (unless you use fixed amounts). Spawnpoints are added using the Spawnpoints tool.<br />
<br />
Containers: The containers of an arena are locations of chests, dispensers, etc. which contain items that will be renewed when the arena ends. Only registered containers will have their contents renewed, so it is not enough to simply put a chest in the arena - it also needs to be registered using the Chests tool.<br />
<br />
==设置模式==<br />
We will set up the arena using Setup Mode. When we enter Setup Mode, MobArena will temporarily store our inventory and give us a set of golden tools (the Toolbox), each with a different function. 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.<br />
<br />
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.<br />
<br />
To leave Setup Mode: Type done.<br />
<br />
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.<br />
<br />
In the next section, we will take a look at the different commands available in Setup Mode...<br />
<br />
==设置模式的命令==<br />
<br />
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.<br />
<br />
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.<br />
<br />
done<br />
Leave Setup Mode.<br />
Aliases: end stop done quit<br />
<br />
help<br />
Display help screen.<br />
Aliases: ? h<br />
<br />
missing<br />
Display a list of missing (mandatory) regions, warps, and points.<br />
This command is useful if you have forgotten how far you are in the setup process, and what you still need to set up.<br />
Aliases: miss<br />
<br />
expand <region> <amount> <direction><br />
Expand a region by some amount in some direction.<br />
Valid regions: ar for the arena region, or lr for the lobby region<br />
Valid amounts: positive integers (whole numbers)<br />
Valid directions: up, down, or out<br />
Example: expand ar 5 up<br />
Aliases: exp<br />
<br />
show [<region>|<warp>|<point>]<br />
Show a region, warp, or point(s) as red wool blocks.<br />
Valid regions: ar for the arena region, or lr for the lobby region<br />
Valid warps: arena, lobby, spec, exit<br />
Valid points: spawns (or just sp) for spawnpoints, chests (or just c) for chests<br />
Example: show sp<br />
<br />
==设置时的工具==<br />
<br />
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.<br />
<br />
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.<br />
<br />
===区域工具===<br />
<br />
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.<br />
<br />
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.<br />
<br />
Left-click: Set the first point to be the location of the target block<br />
Right-click: Set the second point to be the location of the target block<br />
<br />
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.<br />
<br />
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.<br />
<br />
===玩家传送点工具===<br />
<br />
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.<br />
<br />
Left-click: Set the currently selected warp on top of the target block<br />
Right-click: Cycle between available warps<br />
<br />
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.<br />
<br />
Note: The arena, lobby, and spectator warps are all required. The exit warp is optional.<br />
<br />
===怪物产生点工具===<br />
<br />
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.<br />
<br />
Left-click: Add a spawnpoint on top of the target block<br />
Right-click: Remove the spawnpoint on top of the target block (if the spawnpoint exists)<br />
<br />
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.<br />
<br />
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.<br />
<br />
===容器工具===<br />
<br />
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.<br />
<br />
Left-click: Register the clicked container (if it wasn't registered)<br />
Right-click: Unregister the clicked container (if it was registered)<br />
<br />
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.<br />
=命令=<br />
==玩家命令==<br />
<br />
These commands can be issued by all players. They include joining, leaving, spectating and listing arenas as well as listing players.<br />
<br />
/ma join (<arena>) or /ma j (<arena>) - Join the arena with the given name.<br />
/ma leave or /ma l - Leave the current arena, or the spectator area.<br />
/ma notready - Get a list of all players who aren't ready.<br />
/ma spec (<arena>) or /ma s (<arena>) - Spectate the arena with the given name.<br />
/ma arenas - Get a list of all arenas. Green names are enabled, gray names are disabled.<br />
/ma players - Get a list of all arena players.<br />
/ma players <arena> - Get a list of arena players in the specified arena.<br />
/ma class <class> - While in the lobby, manually pick the given class instead of punching signs.<br />
==管理员指令==<br />
<br />
Only ops and the console can issue these commands. They include forcefully starting or ending arenas, enabling/disabling individual arenas or MobArena entirely.<br />
<br />
/ma enable - Enable MobArena.<br />
/ma disable - Disable MobArena.<br />
/ma enable <arena> - Enable the arena with the specified name.<br />
/ma disable <arena> - Disable the arena with the specified name.<br />
/ma force end - Forcefully end all arenas.<br />
/ma force end <arena> - Forcefully end the arena with the specified name; forces all players to leave. <br />
/ma force start <arena> - Forcefully start the arena with the specified name; forces all players who aren't ready to leave.<br />
/ma notready <arena> - Get a list of all players in the given arena who aren't ready.<br />
/ma restore <player> - Restore the inventory of the player with the given name, if possible.<br />
/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.<br />
==建设指令==<br />
<br />
Only ops (and the console, if it makes sense) can issue these commands. They include setting warp points, spawnpoints and region points.<br />
<br />
/ma setup <arena> - Enter Setup Mode for the given arena.<br />
/ma addarena <arena> - Create a new arena-node in the current world.<br />
/ma delarena <arena> - Delete the arena with the given name.<br />
/ma editarena <arena> - Toggle Edit Mode for the given arena.<br />
/ma editarena <arena> [true|false] - Turn on or off Edit Mode for the given arena.<br />
/ma setting <arena> - List all per-arena settings for the given arena.<br />
/ma setting <arena> <setting> - Check the current value of the given setting for the given arena.<br />
/ma setting <arena> <setting> <value> - Set the value of the given setting for the given arena to the given value.<br />
/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.<br />
/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.<br />
/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.<br />
/ma auto-degenerate <arena> - Degenerate the arena with the given name, effectively restoring the patch that was "bulldozed" with the auto-generator.<br />
=权限=<br />
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.<br />
<br />
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!<br />
<br />
==竞技场权限==<br />
<br />
Did you read the note at the top? If not, read it before you continue.<br />
<br />
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.<br />
<br />
bPermissions: ^mobarena.arenas.default<br />
GroupManager: -mobarena.arenas.default<br />
zPermissions: mobarena.arenas.default: false<br />
<br />
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.<br />
<br />
Still confused? Check the sample setup at the bottom of the page!<br />
<br />
==职业权限==<br />
<br />
Did you read the note at the top? If not, read it before you continue.<br />
<br />
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.<br />
<br />
bPermissions: ^mobarena.classes.knight<br />
GroupManager: -mobarena.classes.knight<br />
zPermissions: mobarena.classes.knight: false<br />
<br />
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.<br />
<br />
As with arenas, I recommend letting everyone enjoy all the classes, unless you have a special reason not to.<br />
<br />
Still confused? Check the sample setup at the bottom of the page!<br />
<br />
==命令权限==<br />
<br />
Did you read the note at the top? If not, read it before you continue.<br />
<br />
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!<br />
<br />
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.<br />
<br />
mobarena.use.join<br />
mobarena.use.leave<br />
mobarena.use.spec<br />
mobarena.use.arenalist<br />
mobarena.use.playerlist<br />
mobarena.use.notready<br />
mobarena.use.class<br />
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.<br />
<br />
mobarena.admin.enable<br />
mobarena.admin.kick<br />
mobarena.admin.restore<br />
mobarena.admin.force<br />
mobarena.admin.teleport<br />
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.<br />
<br />
mobarena.setup.config<br />
mobarena.setup.setup<br />
mobarena.setup.setting<br />
mobarena.setup.addarena<br />
mobarena.setup.removearena<br />
mobarena.setup.editarena<br />
mobarena.setup.spawnpoints<br />
mobarena.setup.containers<br />
mobarena.setup.checkdata<br />
mobarena.setup.checkspawns<br />
mobarena.setup.classchest<br />
mobarena.setup.classes<br />
mobarena.setup.leaderboards<br />
mobarena.setup.autogenerate<br />
mobarena.setup.autodegenerate<br />
Sample setup<br />
<br />
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...<br />
<br />
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:<br />
<br />
default-aux: <-- This is the auxiliary group that is to<br />
permissions: be inherited by the default group and<br />
- essentials.balance the donor group. It is not used for<br />
- essentials.pay anything else.<br />
- essentials.sell<br />
<br />
default: <-- This is the default group. It inherits<br />
inherits: default-aux from default-aux, but also revokes the<br />
permissions: permission for the special class.<br />
- -mobarena.classes.diamondknight<br />
<br />
donor: <-- This is the donor group, which also<br />
inherits: default-aux inherits from default-aux, but it<br />
permissions: does not revoke any class permissions,<br />
- essentials.balance.others which means it has access to all of<br />
- essentials.kit them by default.<br />
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.<br />
=物品语法（Item Syntax待搬运）=<br />
=职业箱子（Class Chests待搬运｝=<br />
=怪物波设置（Formulas待搬运）=<br />
=怪物种类（Monster types待搬运）=<br />
以上内容搬运自英文wiki[https://github.com/garbagemule/MobArena/wiki]</div>Zhw