Thorns Minecraft: Is This Armor Enchantment Worth It?

The thorns enchantment in Minecraft is one of the most controversial in the game. On paper, the idea is appealing: every mob or player that hits you takes damage in return. In practice, the reality is more nuanced. Thorns consumes durability at an alarming rate, does not trigger with every hit, and the damage dealt remains modest. As a result, the Minecraft community is divided between those who swear Thorns is essential and those who consider it a trap. This guide objectively analyzes the thorns enchantment in Minecraft: exact mechanics, probability calculations, impact on durability, and final verdict.

Thorns: How Do Reflected Damages Work?

Thorns is an armor enchantment that inflicts automatic damage to the attacker when the wearer is hit. The enchantment triggers passively, without player action. The wearer receives damage normally (reduced by armor and protection), and the attacker suffers bonus return damage.

The triggering mechanic works as follows: with each hit received, the game checks each piece of armor worn separately. Each piece with Thorns has an independent chance to trigger. If at least one piece triggers, the attacker takes damage. If multiple pieces trigger simultaneously, only the piece with the highest level of Thorns determines the damage (no damage stacking between pieces).

The damage inflicted by Thorns is fixed: 1 to 4 damage (0.5 to 2 hearts) with each trigger, regardless of the enchantment level. The level of Thorns affects the probability of triggering, not the damage.

Thorns works against all types of direct attacks: mob melee, player attacks, arrows, and projectiles. It does not trigger against environmental damage (fall, fire, drowning, explosion without direct contact).

Thorns applies to the 4 pieces of armor: helmet, chestplate, leggings, and boots. It is compatible with all other armor enchantments (Protection, Unbreaking, Mending, exclusive enchantments). It can be obtained on the enchantment table with 15 bookshelves, through enchanted books, or from a librarian villager.

Levels I to III: Probability of Triggering Damage

Each level of Thorns increases the probability of triggering per piece of armor by 15%.

Level Chance per Piece Damage if Triggered
Thorns I 15% 1-4 damage (0.5-2 hearts)
Thorns II 30% 1-4 damage (0.5-2 hearts)
Thorns III 45% 1-4 damage (0.5-2 hearts)

The damage does not change between levels. Only the frequency of triggering increases. Thorns I inflicts the same 1-4 damage as Thorns III but triggers 3 times less often.

When the player wears Thorns III on all 4 pieces of armor, the probability that at least one piece triggers with each hit received is calculated as follows: 1 - (1 - 0.45)^4 = 90.9%. In other words, almost every hit received inflicts damage on the attacker.

Configuration Chance of Triggering per Hit Received
Thorns III on 1 piece 45.0%
Thorns III on 2 pieces 69.8%
Thorns III on 3 pieces 83.4%
Thorns III on 4 pieces 90.9%

With full Thorns III armor, the average reflected damage per hit received is about 2.27 damage (1.14 hearts). It's modest: a zombie on Normal difficulty inflicts 3 damage per hit and has 20 HP. It would take about 9 hits received to kill it solely with Thorns. The player would take about 3 to 5 effective damage (after armor reduction) per hit during this time, or 27 to 45 damage received to kill a single zombie passively. It's clearly less efficient than killing it in 2 sword strikes.

Major Drawback: Thorns Accelerates Armor Degradation

The real problem with Thorns is its durability cost. Each time Thorns triggers on a piece of armor, that piece loses 2 additional durability points on top of the durability lost from the hit received (1 point).

Without Thorns, receiving a hit consumes 1 durability point on a random piece of armor. With Thorns III on all 4 pieces, receiving a hit consumes 1 normal durability point + 2 additional points on each piece that triggers (on average 1.8 pieces out of 4). The average cost per hit received goes from 1 to about 4.6 durability points spread across the 4 pieces.

Configuration Durability Lost per Hit Received (Average) Degradation Factor
Without Thorns 1 point (1 random piece) ×1
Thorns III on 1 piece 1 + 0.9 = ~1.9 points ×1.9
Thorns III on 4 pieces 1 + 3.6 = ~4.6 points (spread) ×4.6

The armor degrades about 4 to 5 times faster with full Thorns III than with armor without Thorns. For Netherite armor (555 durability per piece), this means:

Netherite Piece Hits Before Breaking (Without Thorns) Hits Before Breaking (Thorns III ×4)
Without Unbreaking ~555 ~120
With Unbreaking III ~2,220 ~480
With Unbreaking III + Mending Infinite (if sufficient XP) Infinite (but XP consumed faster)

With Unbreaking III + Mending, the armor never breaks, but the XP flow is consumed more quickly to compensate for the accelerated degradation. A player wearing full Thorns III + Mending on all pieces must ensure they earn enough XP to maintain the armor. In practice, killing mobs in combat (which triggers Thorns) provides enough XP to compensate.

Without Mending, Thorns is a durability sink that destroys armor in a few gaming sessions. This is the main reason why the community advises against Thorns for players who do not yet have Mending on all their pieces.

Thorns + Unbreaking III: Compensating for Durability

The combination of Unbreaking III + Thorns III mitigates the durability problem without eliminating it.

Unbreaking III reduces durability consumption by 60% on average for armor pieces. Each durability point consumed by Thorns has a 60% chance of not being deducted. This does not change the number of Thorns triggers but reduces the effective wear.

With Unbreaking III, Netherite armor goes from about 120 hits before breaking (Thorns III ×4, without Unbreaking) to about 480 hits. It's better, but an active player in combat can easily receive 480 hits in a few sessions. The definitive solution remains Unbreaking III + Mending.

In the absence of Mending, the player can limit Thorns to one piece of armor (typically the chestplate, which has the highest durability). This reduces the probability of triggering to 45% instead of 90.9%, but limits the accelerated degradation to one piece. It's an acceptable compromise in mid-game.

The recommended progressive strategy:

Game Phase Thorns Configuration
Early (iron/diamond, no Mending) No Thorns
Mid (diamond, Unbreaking III, no Mending) Thorns III on 1 piece max (chestplate)
Late (Netherite, Unbreaking III + Mending) Thorns III on 4 pieces (optional)

Is Thorns Really Useful? (Debate and Community Opinion 2026)

The Minecraft community is deeply divided on Thorns. Here are the arguments from both sides.

Arguments for Thorns: the reflected damage is free and passive. The player does nothing: every mob that hits them takes damage automatically. Against hordes of mobs (Pillager raid, spawner, night on the surface), Thorns helps kill weak enemies without spending weapon durability. In PvP, Thorns damage adds to sword damage, increasing the player's total DPS. Against a player who attacks quickly (sword with high attack speed), Thorns triggers with each hit and accumulates significant damage.

Arguments against Thorns: the average damage (2.27 per hit received) is weak compared to sword damage (11+ with Sharpness V Netherite). Thorns does not kill mobs; it slightly weakens them. The durability degradation is a real problem without Mending. Thorns also prevents certain farming strategies: mobs killed by Thorns do not drop XP or "player-killed" loot in some configurations, which breaks mob farms. Finally, Thorns interferes with Enderman farms because touching an Enderman triggers its teleportation, and Thorns damage counts as a "touch."

The verdict in 2026: Thorns is a luxury end-game enchantment. If you already have Mending + Unbreaking III on all your armor pieces and no longer worry about durability, Thorns III is a pleasant bonus that adds some passive damage without real downside. If you don't have Mending or use mob farms, avoid Thorns.

On a multiplayer PvP server, Thorns gains more value because every point of damage inflicted on an opponent counts. A Minecraft hosting with custom combat plugins can adjust Thorns damage to make it more or less impactful depending on the desired balance.

Thorns Enchantment FAQ

Does Thorns work against arrows?

Yes. Thorns triggers against projectiles (arrows, Ghast fireballs, Shulker projectiles). The distant attacker takes return damage even if they are far from the wearer. It's one of the rare cases where Thorns is useful in defensive PvP.

Do Thorns damage increase with level?

No. The damage remains fixed at 1-4 (average 2.5) regardless of the level. Only the probability of triggering increases: 15% per level per piece. Thorns III triggers more often than Thorns I but inflicts the same damage when it triggers.

Does Thorns kill mobs? Are drops affected?

Yes, Thorns can deliver the fatal blow to a mob. Mobs killed by Thorns count as "player-killed" and drop XP and loot normally. However, in some automatic farm configurations, Thorns can interfere with kill timing and cause issues.

Does Thorns affect Endermen?

Yes, and it's a problem. When an Enderman hits a player with Thorns, the return damage hits the Enderman, causing it to teleport immediately. This makes Endermen very difficult to fight and breaks Enderman farms based on grouping. Players who regularly face Endermen should avoid Thorns.

Can Thorns be applied to a shield?

No. Thorns is exclusive to the 4 pieces of armor (helmet, chestplate, leggings, boots). It cannot be applied to a shield, even via an anvil.

Is Thorns useful against the Wither or Ender Dragon?

Against the Wither, Thorns triggers when the Wither attacks in melee (phase 2, below 50% health). The return damage is marginal compared to the boss's 300/600 HP. Against the Ender Dragon, Thorns does not work because the dragon does not deal damage through classic direct contact (its charges use a special mechanic).

Is Thorns available on Bedrock Edition?

Yes. Thorns works identically on Java Edition and Bedrock Edition. The probability mechanics and damage are the same.