Marker

Markers are entities intended for use in data packs and map-making. They can only be created with the /summon command.

Marker

Health points	None
Behavior	None
Hitbox size	None

{
    "title": "Marker",
    "rows": [
        {
            "field": "None",
            "label": "(link to Health article, displayed as Health points)"
        },
        {
            "field": "None",
            "label": "Behavior"
        },
        {
            "field": "None",
            "label": "(link to Hitbox article, displayed as Hitbox size)"
        }
    ],
    "invimages": [],
    "images": [
        "blank.png"
    ]
}

Behavior

Markers are intended to have minimal behavior. Markers do not move, do not take damage, and cannot be given status effects. Markers do not make sounds, but sculk sensors can trigger when they are killed. They cannot support passengers (even when summoned with a Passengers tag, the passengers are not created).

Markers do not cause any updates. Markers only exist on the server side, so they do not render. Using the debug key combination F3 + B, which normally draws the hitboxes of all visible entities, does not show a hitbox for a marker. Using F3 + I while aiming at a marker does not copy the entity data to the clipboard. They do not count toward the E-value (total amount of entities) listed on the debug screen. Markers do not obstruct the placement of blocks, nor do they push players or other entities away from their own position. Markers can be saved in structures via structure blocks.

Data values

ID

Java Edition:

Entity	Identifier	[hide]Translation key
Marker	marker	entity.minecraft.marker

Entity data

Markers have entity data associated with them that contain various properties of the entity.

• [NBT Compound / JSON Object] Entity data
  • Tags common to all entities see Template:Nbt inherit/entity/template[show]

History

August 25, 2014							Searge "definitely [hints] at a marker entity in the future".
[hide]Java Edition
1.17			21w15a				Added markers.

Issues

Issues relating to "Marker" are maintained on the bug tracker. Issues should be reported and viewed there.

See also

• Display entity