Diferencia entre revisiones de «Comandos»

Las opciones disponibles se muestran separadas por una barra vertical: |

help [página|nombre del comando]
? [página|nombre del comando]

Muestra algunos de los comandos disponibles o información adicional al usar nombre del comando (no se muestran todos). Nota: los comandos multijugador no aparecen en los juegos de un solo jugador, aunque esté abierto a jugadores en LAN.

Tiene éxito si página es válido o no se especifican. Técnicamente falla si se especifica nombre del comando, aunque se muestra el uso del comando.

me <acción …>

Permite describir una acción de manera narrativa que aparecería en el chat de esta forma: “nombre del jugador” “acción que dice que realiza” (ejemplo: Clappercito escribe: /me se toma un zumo, entonces aparecerá en el chat: *Clappercito se toma un zumo.) Si se utiliza un selector de objetivo multi-persona (por ejemplo, @a) con acción, la lista de nombres tendrá el siguiente formato: "nombre1 nombre2 nombre3", o "nombre1 nombre2" para dos nombres. Por lo tanto, independientemente del número de los selectores de objetivo que se utilicen en acción, este comando sólo dará el mensaje una sola vez.

Todos los selectores de objetivo (por ejemplo, @p) en acción deben evaluarse.

tell <jugador> <mensaje privado …>
msg <jugador> <mensaje privado …>
w <jugador> <mensaje privado …>

Se usa para mandar un mensaje privado corto a un jugador en el servidor. Muy útil en servidores si es necesario pedir/decir algo de/a otro jugador sin que otros jugadores lo vean. Si se utiliza el selector de objetivo multi-persona (por ejemplo, @a) en mensajes privados, la lista de nombres tendrá el siguiente formato: "nombre1 nombre2 nombre3", o "nombre1 nombre2"para dos nombres. Por lo tanto, independientemente del número de los selectores de destino que se utilicen en mensaje privado, este comando sólo dará el mensaje una sola vez - sin embargo, un selector para jugador puede enviar un mensaje a varias personas (que tengan parte del mismo nombre).

Todos los selectores de objetivo (por ejemplo, @p) con mensaje privado debe evaluarse, y el jugador debe estar en línea.

trigger <objectivo> <add|set> <valor>

Se utiliza junto con /tellraw para que los jugadores activen los sistemas hechos por los operadores o los creadores de mapas. El objetivo debe ser un objetivo habilitado del marcador del criterio de "trigger". El valor dado es o se añade a su valor actual, o se convierte en su nuevo valor, en función de si el segundo argumento es add o set. El valor del objetivo sólo se cambia para el jugador que utiliza el comando.

El trigger se agregará en la 1.8 y está disponible actualmente sólo en las snapshots.

El objetivo debe contar con los criterios de "trigger" y el jugador que ejecuta el comando debe ser capaz de modificar el objetivo.

achievement give <stat_name> [jugador]

Da a un jugador un logro, y todos los requisitos para los logros previos, o incrementar una estadística en 1. stat_name debe utilizar achievement.achievement_name, donde achievement_name es un logro válido (ver Marcador o Logros para los nombres válidos), o stat.statistic_name, donde statistic_name es una estadística válida (ver Marcador para estadísticas válidas). Si el jugador no se especifica, el logro/estadística se dará al ejecutor del comando.

stat_name debe ser un nombre de logro/estadística válida. El jugador no es opcional en los bloques de comandos y el jugador debe estar en línea.

blockdata <x> <y> <z> <dataTag>

Edits the data tags of the block at the location x, y, z. For more information on data tags, see the Data tags section.

The blockdata command will be added in 1.8 and is currently available only in the snapshots.

dataTag must be a valid argument at the block located at x, y, z.

clear [player] [item] [data] [maxCount] [dataTag]

Clears the inventory of player (defaults to the executing player if unspecified) of the specified item:data, with the specified dataTag. Does not remove more than maxCount items. If no optional tags are specified, the entire inventory is cleared.

The maxCount and dataTag arguments will be added in 1.8 and are currently available only in the snapshots.

At least zero item(s) must be removed, and player must be online. Can output a comparator signal if successfully cleared item(s). data can be set to -1 to clear regardless of Damage value, and maxCount can be set to -1 to clear all of the selected item.

clone <x1> <y1> <z1> <x2> <y2> <z2> <x> <y> <z> [mode] [mode2]

Clones the given area. The destination is (x, y, z), where the blocks are placed going into positive coordinate values.

mode can be:

• replace - (the default), which copies all blocks.
• masked - which copies all non-air blocks.
• filtered - which removes any unnecessary blocks and replaces them with air.

mode2 can be:

• move - where it replaces the cloned blocks with air (on filtered you must include what blocks to be filtered out).
• force - which makes the command execute even if the area being cloned overlaps with the area blocks being cloned to (on filtered you must include what blocks to be filtered out).
• normal - (on filtered you must include what blocks to be filtered out).

The clone command will be added in 1.8 and is currently available only in the snapshots.

The area being cloned and the area where the cloned blocks are going must both be rendered, must not overlap, and must be within the 32768 block limit (including air blocks)

debug <start|stop>

Starts a new debug profiling session or stops the session currently running. It notifies about potential performance bottlenecks in the console when active and creates a profiler results file in the folder debug when stopped.

Can only stop if a session is running. Cannot be used in a command block.

defaultgamemode <mode>

Sets the default game mode that is shown on the world selection menu. New players that join the world will be put into the default game mode; i.e., if the default game mode is creative, new players will start in creative. This command cannot enable or disable Hardcore mode.

mode must be a valid game mode: survival, creative, adventure, or spectator. The game modes can be abbreviated to "s/c/a/sp" or "0/1/2/3" respectively.

difficulty <new difficulty>

Changes the difficulty for as long as the server is running. If the server is restarted, the difficulty will go back to whatever difficulty is set in server.properties.

new difficulty must be a valid difficulty: peaceful, easy, normal, or hard. The difficulties can be abbreviated to "p/e/n/h" or "0/1/2/3" respectively.

effect <player> <effect> [seconds] [amplifier] [hideParticles]

Gives the targeted player (or entity, via the @e target selector) the specified effect for the specified time (default is 30 seconds). Effects have a limit of 1,000,000 seconds, and the amplifier field has a limit of 255. Effect id's can be found on the potion effects page. Setting seconds to 0 clears this effect. If you put the amplifier to a number of a variably high value, it will not give the desired amplifier. Setting hideParticles to true hides effect particles, if value not given, defaults to false.

If clearing an effect, the player must have this effect. effect must be a valid effect. player must be online.

effect <player> clear

Clears all effects on player (or entity, via the @e target selector).

At least one effect must be removed, and player must be online.

enchant <player> <enchantment ID> [level]

Enchants the item that the player is currently holding, according to enchantment ID. Note that this works within the normal limitations of enchanting items. Enchantments can only be applied to items which can normally receive that specific enchantment. Enchantment levels can not be above the normal highest achievable for the selected enchantment. Conflicting or overpowering enchantment combinations usually prevented are also prevented with this command.

The enchantment ID must be valid, the level must be valid for this enchantment (unless the held item is also invalid), the held item must be able to accept this enchantment, the held item cannot have conflicting enchantments, and player must be online.

execute <entity> <x> <y> <z> <command …>

Runs command as though it were executed by entity, and as though entity were located at x, y, z. The command will be run as though the entity has operator-level permission.

The execute command will be added in 1.8 and is currently available only in the snapshots.

entity must resolve to one or more valid entities (including players, who must be online if specified by name). x and z must be within the range -30,000,000 to 30,000,000 (inclusive). command must execute successfully.

Runs command as though it were executed by entity, and as though entity were located at x, y, z. It will only run command if the specified block is located at x2, y2, z2, starting from x, y, z for relative coordinates. The command will be run as though the entity has operator-level permission.

The execute command will be added in 1.8 and is currently available only in the snapshots.

entity must resolve to one or more valid entities (including players, who must be online if specified by name). x and z must be within the range -30,000,000 to 30,000,000 (inclusive). The specified block must be found at x2, y2, z2. command must execute successfully.

fill <x1> <y1> <z1> <x2> <y2> <z2> <TileName> [dataValue] [oldBlockHandling] [dataTag]

Fills the given area with a block specified by TileName, dataValue, and dataTag. oldBlockHandling mode is either destroy, keep, hollow, or outline.

• replace - Destroys any blocks within the target location and replaces them with "TileName", without dropping item entities.
• destroy - Destroys any blocks within the target location, dropping them as item entities, and replacing them with "TileName".
• keep - Only replaces air blocks found in the fill area with "TileName".
• hollow - Wraps only the outer layer of the fill area, creating a square box of "TileName", and replacing all blocks inside of the box area with air. Containers inside of the box will drop their contents, but not their block.
• outline - Wraps only the outer layer of the fill area, creating a square box of "TileName". (Leaves all blocks leftover inside the box area alone and doesn't destroy them)

The fill command will be added in 1.8 and is currently available only in the snapshots.

A starting point and an end point must be input followed by a block. Your feet (y-value), will be the point where blocks will begin to fill. Chunks must be loaded and can only fill within a 32768 block limit (including air blocks)

fill <x1> <y1> <z1> <x2> <y2> <z2> <TileName> <dataValue> replace [replaceTileName] [replaceDataValue]

Replaces all blocks matching replaceTileName and replaceDataValue in a given area with TileName and dataValue. If replaceTileName and replaceDataValue are not given, any block will be replaced. Note that the replace operation does not support a dataTag argument if replaceTileName is given (use above syntax instead to replace any block and have dataTag support).

The fill command will be added in 1.8 and is currently available only in the snapshots.

A starting point and an end point must be input followed by a block. Your feet (y-value), will be the point where blocks will begin to fill. Chunks must be loaded and can only fill within a 32768 block limit (including air blocks)

gamemode <mode> [player]

Changes the game mode for player. If no player is given, it will set your own gamemode.

mode must be a valid game mode: survival, creative, adventure, or spectator. The game modes can be abbreviated to "s/c/a/sp" or "0/1/2/3" respectively.

player must currently be online. player is not optional for command blocks.

gamerule <rule name>
gamerule <rule name> [value]

Activates or deactivates the rule name. If value is not given, displays the current status of rule name.

Available rules are:

• commandBlockOutput - Whether command blocks should notify admins when they perform commands
• doDaylightCycle - Whether time progresses
• doFireTick - Whether fire should spread and naturally extinguish
• doMobLoot - Whether mobs should drop items
• doMobSpawning - Whether mobs should naturally spawn
• doTileDrops - Whether blocks should have drops
• keepInventory - Whether the player should keep items in their inventory after death
• mobGriefing - Whether Creepers, Endermen, Ghasts, Withers and Villagers should be able to change blocks or zombies, skeletons, and Zombie Pigmen can pick up items
• naturalRegeneration - Whether the player can regenerate health naturally if their hunger is full enough

The following rules will be added in 1.8 and are currently available only in the snapshots:

• logAdminCommands - Whether to log admin commands to server log
• randomTickSpeed - How often a random tick occurs, such as plant growth, leaf decay, etc. Can be 0 to disable random updates
• sendCommandFeedback - Whether the feedback from commands executed by a player should show up in chat
• showDeathMessages - Whether a message appears in chat when a player dies

Valid value for all gamerules are true or false, except randomTickSpeed which can be any non-negative integer.

Succeeds in all cases - even absent/invalid rule name or a property besides true or false.

give <player> <item> [amount] [data] [dataTag]

Spawns amount (defaults to 1) of the item defined by item with the specified data (defaults to 0) at the location of player, using dataTag for the "tag" NBT tag. For example typing /give John planks 30 1 {display:{Lore:["Wooden planks"]}} will give a player called John 30 blocks of Spruce Wood Planks with Lore that says "Wooden planks".

item must be a valid ID or item name, amount must be from 0 to 64, and player must be online.

kill [player|entity]

Inflicts 1000 ( × 500) void damage to the target, killing the target instantly even if in Creative mode (a high-level Resistance effect cannot protect the player either). The text "Ouch! That looks like it hurt." will be displayed after executing. Useful when lost, stuck, or to restore health and hunger (assuming you can get your items back easily or the keepInventory gamerule is set to "true"). If player|entity is not specified, the player running the command will be killed.

The player|entity argument will be added in 1.8 and is currently available only in the snapshots.

player|entity is not optional in command blocks.

particle <name> <x> <y> <z> <xd> <yd> <zd> <speed> [count] [player|entity]

Spawns particles in a given area or at a given player/entity.

The particle command will be added in 1.8 and is currently available only in the snapshots.

name must be a valid particle name. x and z must be within the range -30,000,000 to 30,000,000 (inclusive). player|entity is not optional in command blocks.

playsound <sound> <player> [x] [y] [z] [volume] [pitch] [minimumVolume]

Plays the selected sound to the selected player. The value of sound is any event defined in sounds.json (for example, mob.pig.say). Note that Resource Packs may add their own events to sounds.json; the command will successfully play these. File names are not used by this command; it strictly uses the events defined in sounds.json (which may not even be similar to the original file names and paths), and thus a resource pack adding new sound files must define events for them (this is not necessary when replacing old sounds which are already in defined events). If an event contains multiple sounds, this command will select randomly between them (chances are modified by each sound's "weight" property), just as the game normally would. For example, "mob.pig.say" will play one of several pig sounds at random, because the event has multiple sounds associated with it.

The coordinates x, y, and z are the coordinates to play the sound from. If prefixed with "~", they will be relative to the player's current location. Note that "~" is shorthand for "~0", and thus "~ ~ ~" can be used as a substitute for the player's current location.

The volume argument controls the distance from which a sound may be heard. At values less than 1.0, the sound will be quieter and have a smaller sphere within which it may be heard. At values greater than 1.0, the sound will not actually grow louder, but its audible range (a 16-block radius at 1.0) will be multiplied by volume. There will always be a gradual falloff to silence based on distance from the center of the sphere.

The minimumVolume argument controls the volume of the sound for players outside its normal audible sphere. If the player is outside the normal sphere, the sound will instead be centered some short distance (<4 blocks) from the player, and minimumVolume will determine its volume.

The pitch argument alters both the pitch and the duration of the sound (which means that it's actually changing its speed).

player must be online, volume must be at least 0.0, pitch must be between 0.0 and 2.0 (inclusive), minimumVolume must be between 0.0 and 1.0 (inclusive), and the player must be able to hear the sound from where it is played.

publish

Opens your single-player game for LAN friends to join. This command appears in the singleplayer cheats.

Cannot be used in a command block.

replaceitem block [x] [y] [z] <slot> <item> [amount] [data] [dataTag]

Replaces an item in a certain slot of a container block with another item.

The slot argument must be slot.container.* (where * is replaced with a number for the correct inventory slot).

The replaceitem command will be added in 1.8 and is currently available only in the snapshots.

The block must be a container block and the slot and item arguments must be correct.

replaceitem entity <selector> <slot> <item> [amount] [data] [dataTag]

Replaces an item in a certain slot of an entity (player or mob) with another item.

The slot argument must be one of (where * is replaced with a number for the correct inventory slot):

• slot.armor.feet|legs|chest|head
• slot.enderchest.*
• slot.horse.armor|chest.*|saddle
• slot.hotbar.*
• slot.inventory.*
• slot.villager.*
• slot.weapon

slot.equipment.* is not currently a valid argument, but mob equipment can be replaced with slot.armor.* or slot.weapon (listed above).

The replaceitem command will be added in 1.8 and is currently available only in the snapshots.

The player must be online and the slot and item arguments must be correct.

say <message …>

Broadcasts message to all players on the server. If a multi-person target selector (e.g., @a) is used, the list of names is formatted as "name1, name2, and name3", or "name1 and name2" for two names. Therefore, regardless of any target selectors which are used, this command will only output once.

All target selectors (e.g., @p) in the message must evaluate.

scoreboard <objectives|players|teams>

See Scoreboard for more information. Scoreboard-specific commands.

Main Article

seed

Displays the seed. This command can always be used in single-player mode, regardless of whether cheats are enabled or not.

Always succeeds (if user is a command block, player in singleplayer, or server op).

setblock <x> <y> <z> <TileName> [dataValue] [oldBlockHandling] [dataTag]

Places the block in the x, y and z coordinates specified.

TileName must exist, dataValue must exist if specified, oldBlockHandling must be either replace, keep or destroy if specified and dataTag must evaluate if specified.

setworldspawn
setworldspawn <x> <y> <z>

Sets the world's spawn to the specified coordinates. The worldspawn is where you first spawn and where you respawn if you die and your bed is missing or obstructed. If no coordinates are specified, the world spawn will be set to the executor's current location. Note that a 10 chunk (160 block) radius around the worldspawn is kept loaded at all times. However this only applies if the chunks are already loaded when it is set. Setting it to a place where no player is will NOT cause the area to load. Also compasses (which in minecraft point to the worldspawn rather than north) will not update to the change until you reload the world.

x, y, and z must be within the range -30,000,000 to 30,000,000 (inclusive). x, y, and z are not optional in command blocks.

spawnpoint
spawnpoint <player>
spawnpoint <player> <x> <y> <z>

Sets the spawnpoint of that player to that position, or to the current position if x y and z are not specified. player is optional if x y z are not specified; will set the spawnpoint of the user to their current location. NOTE: Spawnpoint coordinates must be specified in integers. No decimals.

Sleeping in a bed will also set a spawn point where the bed is, but you can only sleep in beds at night or when it rains.

player must be online, and x, y, and z must be within the range -30,000,000 to 30,000,000 (inclusive).

spreadplayers <x> <z> <spreadDistance> <maxRange> <respectTeams> <player …>

This command allows players to spread out over a long or short distance.

x and z mark the center of the area across which players are to be spread.

spreadDistance is the rough minimum distance players will be spread apart.

maxRange is the maximum distance from x, z where players will be put. Note that this distance is not a circular radius; it represents the maximum distance on either coordinate (thus forming a box ranging from x-maxRange to x+maxRange and z-maxRange to z+maxRange).

respectTeams may be true or false, and represents whether players should be moved individually or teams should be kept together.

player is the list of players to spread. Names are separated by spaces.

x and z must be within the range -30,000,000 to 30,000,000 (exclusive), spreadDistance must be at least 0, maxRange must be at least 1.0 greater than spreadDistance, and there must not be too many players to fit within the area. If maxRange is larger than 30,000,000, the command can fail with even one player if it attempts to place them outside the world boundary). Players do not spread to lava.

summon <EntityName> [x] [y] [z] [dataTag]

Spawns an entity. For example, to create a charged creeper named Powered Creeper at the player's current location:

/summon Creeper ~ ~ ~ {powered:1,CustomName:Powered Creeper}

x and z must fall within the range -30,000,000 to 30,000,000 (inclusive), and y must be at least 0. If coordinates aren't specified the entity will spawn at the player's location (or inside a command block if the command was executed by one).

tellraw <player> <raw json message>

Sends a JSON message to specified player(s), allowing formatting and clickable actions in chat text. Color defaults to white and all formatting (bold, italic, etc.) defaults to false.

player must be online, and the message text must be correctly coded in JSON.

testfor <player> [dataTag]

Used to test whether the given player (or entity, by the @e target selector) could be located, and whether it has all tags specified by dataTag. A redstone comparator as output from a command block with this command will indicate the number of players/entities matched by it. For example, "testfor @a[r=3]" will output the number of players within 3 meters of the command block, and added in snapshot 14w02a, "testfor @e[type=Arrow,r=3] {inGround:1b}" will output the number of arrows stuck in a block within 3 meters.

player and dataTag must be valid and match some entity if specified.

testforblock <x> <y> <z> <TileName> [dataValue] [dataTag]

Used to test whether a particular block is in the x, y and z coordinates specified. Datatags will not work unless a special syntax is used to specify what type of NBT tag is used (s for Short, b for Byte, l for Long, f for Float and d for Double). Also all relevant tags must be included even if they are unused (e.g.: Chest contents must include Slot, id, Damage, and Count.)

TileName must exist, dataValue must exist if specified, and dataTag must evaluate if specified.

testforblocks <x1> <y1> <z1> <x2> <y2> <z2> <x> <y> <z> [mode]

Compares the blocks at two locations in cuboid regions. (x1, y1, z1) and (x2, y2, z2) specifies the lowest and highest coordinate corners of the source region (the block pattern to check for), and (x, y, z) specifies the lowest coordinate corner of the destination region (the region to be checked).

mode is masked (air blocks in the source region will match any block in the destination region) or all (all blocks must match exactly, even air).

The testforblocks command will be added in 1.8 and is currently available only in the snapshots.

x1, z1, x2, z2, x, and z must fall within the range -29,999,984 to 29,999,984 (inclusive). y must be 0 to 189, and y2 must be 0 to 187.

time set <value>

Sets the world time. value is an integer between 0 and 24000, inclusive, where 0 is dawn, 6000 midday, 12000 dusk and 18000 midnight. value can be greater than 24000; in this case, the time of day wraps around, but the moon's phase is advanced. However, setting the time "backward" (earlier than the current time) does not change the moon. "time set day" sets the time to 1000, and "time set night" sets the time to 13000.

value must be 0 or positive, or day or night.

time add <value>

Increments the world time, as above.

value must be 0 or positive. The daytime wraps, and the moon's phase advances; adding 24000 will advance the moon's phase by one day.

title <player> clear

Removes title from player.

The title command will be added in 1.8 and is currently available only in the snapshots.

player must be a valid online player.

title <player> reset

Resets subtitle, fadeIn time, stay time, and fadeOut time for player.

The title command will be added in 1.8 and is currently available only in the snapshots.

player must be a valid online player.

title <player> subtitle <raw json title>

Sets the subtitle text for player. This is only displayed if a title is on the player's screen at the same time (can be empty).

The title command will be added in 1.8 and is currently available only in the snapshots.

player must be a valid online player. raw json title must be a single word of text (not delimited by curly brackets) or a valid json specification.

title <player> times <fadeIn> <stay> <fadeOut>

Sets the time in game ticks for title (and optional subtitle) to fade in, persist, and fade out, for player.

The title command will be added in 1.8 and is currently available only in the snapshots.

player must be a valid online player.

title <player> title <raw json title>

Sets the title text for player and shows the title (optionally, with prespecified subtitle). Titles are displayed in the middle of your screen.

The title command will be added in 1.8 and is currently available only in the snapshots.

player must be a valid online player. raw json title must be a single word of text (not delimited by curly brackets) or a valid json specification.

toggledownfall

Toggles rain and snow.

Always succeeds.

tp [target player] <destination player>

Teleports target player (or entity, by the @e target selector) to the location of destination player (or entity, by the @e target selector). If no player/entity is specified, it will teleport yourself.

target player is not optional in command blocks. Both players must be online.

tp [target player] <x> <y> <z> [<y-rot> <x-rot>]

Teleports target player (or entity, by the @e target selector – or yourself if no player/entity is specified) to coordinates x,y,z. Can also relatively move the player/entity by adding the ~ character before the coordinate value. For example typing /tp John ~3 64 ~3 will teleport a player called John 3 blocks away from his current x and z, and to y 64. Additionally, y-rot and x-rot may optionally be used to specify the yaw and pitch in degrees - these also accept ~.

The rotation arguments will be added in 1.8 and are currently available only in the snapshots.

x and z must fall within the range -30,000,000 to 30,000,000 (exclusive), and y must be at least 0. target player is not optional in command blocks, and the player must be online.

weather <clear|rain|thunder> [duration in seconds]

Changes the weather for the specified duration.

duration in seconds must be at least 1, and cannot be greater than 1,000,000, and a valid weather condition must be provided.

worldborder add <sizeInBlocks> [timeInSeconds]

Adds blocks to the current size of the world border. Can use negative (-) numbers to subtract the size of the border.

The worldborder command will be added in 1.8 and is currently available only in the snapshots.

Always succeeds even if the worldborder isn't set.

worldborder center <x> <z>

Sets the center of the world border.

The worldborder command will be added in 1.8 and is currently available only in the snapshots.

x and z must fall within the range -30,000,000 to 30,000,000 (exclusive).

worldborder damage amount <damagePerBlock>

Sets the amount of damage inflicted per second per block past the world border buffer (defaults to 0.2). For example, if damagePerBlock is 0.1, a player 5 blocks outside the world border buffer will take 0.5 damage per second (damage less than half a heart might not change the visual health display, but will still accumulate).

The worldborder command will be added in 1.8 and is currently available only in the snapshots.

damagePerBlock must be at least 0.0.

worldborder damage buffer <sizeInBlocks>

Sets the buffer distance outside the world border before damage begins to be inflicted (defaults to 5.0).

The worldborder command will be added in 1.8 and is currently available only in the snapshots.

sizeInBlocks must be at least 0.0.

worldborder set <sizeInBlocks> [timeInSeconds]

Sets the diameter of the world border. sizeInBlocks is the new diameter. timeInSeconds is the number of seconds it should take for the border to move from its previous location to the new location. If timeInSeconds is not specified, the diameter changes immediately.

The worldborder command will be added in 1.8 and is currently available only in the snapshots.

sizeInBlocks must fall within the range 1 to 60,000,000 (inclusive).

worldborder warning distance <blocks>

Sets the distance inside the world border where visual warning of world border proximity begins (defaults to 5).

The worldborder command will be added in 1.8 and is currently available only in the snapshots.

blocks must be at least 0.

worldborder warning time <seconds>

Sets the time before a moving world border intersects the player when visual warning of the world border starts (defaults to 15). For example, if seconds is 5, players will get a visual warning when the moving world border is 5 seconds or less away from passing their position.

The worldborder command will be added in 1.8 and is currently available only in the snapshots.

seconds must be at least 0.

xp <amount> [player]

Gives the specified user the given number of orbs. Maximum is 2,147,483,647 per command. Negative amounts may not be used to remove experience points.

amount can be at most 2,147,483,647. player is not optional in command blocks, and player must be online.

xp <amount>L [player]

Gives player the amount number of experience levels. Maximum is 2,147,483,647 — if a player is given levels pushing them past this limit, they get reset to 0. Negative amounts may be used to remove experience levels.

amount must be between -2,147,483,648 and 2,147,483,647, inclusive. player is not optional in command blocks, and player must be online.