查看“MobArena”的源代码

{{待搬运}}
{{Bukkit Plugin Infobox
|版本=v0.96.9
|兼容服务端版本=1.8.1
|网址=http://dev.bukkit.org/bukkit-plugins/mobarena/}}
=安装插件=
Installing MobArena is as easy as these four steps:
 Stop your server.
 Download the jar-file from the forum thread or Bukkit Dev project page.
 Place the jar-file in your server's plugins-folder.
 Start the server again. This process will generate a config-file (config.yml) and an announcements-file (announcements.yml) in the plugins/MobArena-folder.
The folder structure is thus:

 plugins/
     MobArena.jar
     MobArena/
         config.yml
         announcements.yml
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.
=建立竞技场（V0.96后）=
==建造一个竞技场==
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...

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).

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.

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.

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.

About regions, warps, etc.

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...

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.

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.

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.

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.

==设置模式==
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.

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

To leave Setup Mode: Type done.

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

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

==设置模式的命令==

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

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

done
 Leave Setup Mode.
 Aliases: end stop done quit

help
 Display help screen.
 Aliases: ? h

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

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

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

==设置时的工具==

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

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

===区域工具===

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

===容器工具===

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

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

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

These commands can be issued by all players. They include joining, leaving, spectating and listing arenas as well as listing players.

 /ma join (<arena>) or /ma j (<arena>) - Join the arena with the given name.
 /ma leave or /ma l - Leave the current arena, or the spectator area.
 /ma notready - Get a list of all players who aren't ready.
 /ma spec (<arena>) or /ma s (<arena>) - Spectate the arena with the given name.
 /ma arenas - Get a list of all arenas. Green names are enabled, gray names are disabled.
 /ma players - Get a list of all arena players.
 /ma players <arena> - Get a list of arena players in the specified arena.
 /ma class <class> - While in the lobby, manually pick the given class instead of punching signs.
==管理员指令==

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

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

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

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

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

==竞技场权限==

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

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

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

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

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

==职业权限==

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

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

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

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

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

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

==命令权限==

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

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

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

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

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

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

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

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

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

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

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