Mc Görünmez Blok Kodu

— Select all entities whose hitbox contains the point (1,2,3).

• (sadece bedrock için) Örnekler:

— Select all entities whose feet are within the block region (1~5, 2~7, 3~9).

— Select all entities whose feet contains the point (1, 2, 3).

• It is possible to combine selection by distance and selection by volume, in which case the command select targets only within the overlap of both regions (within certain radius/i of the volume's initial point and not outside the defined volume).

Skora Bağlı Hedef Seçimi

• - Filter target selection based on their scores in the specified objectives.

• All tested objectives are in a single tag, with a list of individual score selectors between braces afterward. The selectors inside the braces support ranges.

— Select all entities with a score in objective myscore of exactly ten.

— Select all entities with a score in objective myscore of between ten and 12 (inclusive).

— Select all entities with a score in objective myscore of five or greater.

— Select all entities with a score in objective myscore of 15 or less.

— Select all entities with a score in objective foo of exactly ten, and a score in objective bar of between one and five (inclusive).

Şunlara da bakın: furthest and random] — Selects all slime ball item entities.

is the same as . The latter is simpler and reduces CPU load.

• Note: When matching string form of namespaced IDs within a tag, the namespace cannot be omitted. Hence cannot find any item entities as the  id field always contains a namespaced ID-converted string.

Gelişim Basamaklarına Bağlı Hedef Seçimi

• — Select all targets that match the specified advancement and value.

• — Select all targets that match the specified advancement and value.

• The argument name is the advancement ID (namespace can be left out when namespaced ). The value is true or false.

• For advancements with one criterion, testing for that criterion always gives the same results as testing for the advancement.

— Selects players who have achieved the advancement minecraft:story/form_obsidian.

— Selects players who haven't achieved the advancement .

— Selects players who had armored with iron helmet. The selected players needn't be wearing iron helmet when selected, and needn't have achieved the advancement .

is the same as .

Koşula Bağlı Hedef Seçimi

• — Select all targets that match the specified predicate.

• — Select all targets that fail to match the specified predicate.

• Since 19w38a, selectors can use predicates in the argument.

— Selects players who match the predicate.

— Selects entities who do not match the predicate.

Veri Etiketleri[]

Ana makale: NBT format

A data tag is a tree-shaped data structure that can be described starting with attribute-value pairs enclosed in curly braces. One common usage of data tags (sadece java için) is in commands, used to specify complex data for any entity.

A data tag consists of zero or more attribute-value pairs delimited by commas and enclosed in curly braces. Each attribute-value pair consists of an attribute name and the attribute's value, separated by a colon. Some values, however, may themselves contain attribute-value pairs, allowing a data tag to describe a hierarchical data structure.

Example:

The data structures that data tags describe are the same ones used in Minecraft's save files. These data structures are described in other articles and commands expect data tags to use the same attribute names (which are case-sensitive):

The defined data structures also expect the values to be of the correct type.

Some commands may require that a number's type be specified by adding a letter (B, S, L, F, D) to the end of the value. For example, for a short, for a float, etc. (This doesn't work with I for int.) The letter can be uppercase or lowercase. When no letter is used and Minecraft can't tell the type from context, it assumes double if there's a decimal point, int if there's no decimal point and the size fits within 32 bits, or string if neither is true. A square-bracketed literal is assumed to be a list unless an identifier is used: for an int array and for a long array.

When commands such as are used to match data tags, they check only for the presence of the provided tags in the target entity/block/item. This means that the entity/block/item can have additional tags and still match. This is true even for lists and arrays: the order of a list is not acknowledged, and as long as every requested element is in the list, it matches even if there are additional elements.

Raw JSON Metni[]

Ana makale: Raw JSON text format

The and commands use the raw JSON text format to display texts.

Also, Some values of arguments in NBT structures are using JSON format.

MC-JavaSürümü'ndeki ID Değişkenleri[]

Şunlara da bakın: Namespaced ID § Conversion from string

This feature is exclusive to Java Edition.

Şablon:Article other

Many commands have arguments that identify particular types of blocks, items, entities, advancemewadawd, bossbars, effects, enchantments and so on. In the command syntax below, these typically appear as elements named , , or the like, which are replaced with identifiers such as in the examples. These IDs all have namespaces. All original Minecraft contents are namespaced while contents from mods or data packs have other namespaces. Namespace prefix of IDs namespaced can be omitted for most situations; however, in certain cases, such as NBT data tag matching, full namespaced ids are required.

A single argument looks like this:

The format of parameters is , in which block states and data tags can be omitted when they are not needed.

• Namespaced ID is required (though if namespace isn't set it defaults to ).
• Block states are inside , comma-separated and must be properties/values supported by the blocks. They are optional.
  • is a syntax error, because doesn't have .
  • is a syntax error, because 's is a number between 0 and 15.
• Data tags are inside . It's optional.
• In the context of "conditions"/testing for blocks, only the states provided are tested.
  • If command tests , it checks only power, but ignores other states such as .
• In the context of setting blocks, any states provided are set, but anything omitted retain their default values, depending on the block.
  • If command sets , it is set to 15, but is a default value (in this case, set to ).
• In the context of "conditions"/testing for blocks, it can also be the namespace ID of block tag with the prefix of , such as .

A single argument that looks like this:

The format of parameters is , in which data tags can be omitted when not needed.

• Namespaced ID is required (though if namespace isn't set it defaults to ).
• Data tags are inside . It's optional.

Java Versiyonu'ndaki Bağımsız Değişken Çeşitleri Listesi[]

Ana makale: Java Edition list of argument types

These are the argument types Java Sürümü sürümünde.

Komutların Özet Listesi[]

The table below summarizes all commands, including upcoming ones. Click a column heading to sort by that column. Click the link in the first unit of each row to get detailed usage of each command.

Silinmiş ve Geri Alınmış Komutlar[]