/attribute

It reads or changes an attribute of one entity, such as maximum health or movement speed. It is not the same as a potion effect.

Yes, provided the player supports the attribute. Changing maximum health does not necessarily restore the player's current health immediately.

Yes, it works with supported mobs. The selected entity must actually have the requested attribute, otherwise Minecraft reports an error.

An attribute defines an entity property, while effects may temporarily modify its final value. The /effect and /attribute commands serve different purposes.

The target argument requires a single entity. Use separate executions, such as an appropriate /execute command, to process multiple targets.

It retrieves the base value of the selected attribute. This is useful when you need the underlying setting without modifiers.

It retrieves the total attribute value after applicable modifiers. The result can differ from the base get value.

It writes a new base attribute value for the selected entity. The value must satisfy the limits of that particular attribute.

It restores the attribute base value to its default. It is not designed to remove every additional attribute modifier.

Use its registered identifier, such as minecraft:max_health. Availability depends on the Minecraft version and entity type.

Run /attribute @s minecraft:max_health base get as a player. It returns the base maximum-health attribute value.

For example, /attribute @s minecraft:max_health base set 30 sets the base value to 30. Check current health separately afterward.

Run /attribute @s minecraft:max_health base reset. This restores the base setting but does not remove independent modifiers.

Use /attribute @s minecraft:movement_speed base get. The number is an attribute value, not a direct speed measurement in kilometres per hour.

Supported versions provide the minecraft:scale attribute for suitable entities. Check its allowed range and whether the entity supports it.

It is a separate adjustment that affects the resulting attribute value. Multiple modifiers can interact with the base value according to their operations.

Use modifier add with a unique ID, amount, and operation. Check that the same modifier ID does not already exist.

Use modifier remove with the exact identifier of an existing modifier. This is different from resetting the base attribute value.

Modern Java uses add_value, add_multiplied_base, and add_multiplied_total. Each applies the modifier amount differently.

It scales the returned command result. Reading the attribute with a scale does not change the entity's actual attribute.

The selector may match no entity or multiple entities instead of exactly one. Check the target and result limit.

The attribute ID may be incorrect or unavailable in the game version. The selected entity may also lack that attribute.

Other modifiers and game limits can affect the result. Compare base get with plain get after making the change.

The modifier ID may already exist or an argument may be invalid. Check the identifier, numeric value, and operation name.

Java 1.20.5 renamed modifier operations. Older add or multiply syntax from legacy guides may no longer work.

Java 1.21 replaced the older UUID and name arguments with a single modifier identifier. Older instructions need adaptation.

Java Edition 1.21.4 introduced base reset. Older versions require another method for restoring the base value.

It normally requires permission level 2. Ordinary players on public servers cannot freely modify other players' attributes.

Extreme attribute values can disrupt movement, balance, or entity interactions. Test changes in a separate world first.

Record the original base value and affected modifier IDs before changing anything. Restore them with base reset or exact values afterward.