Minecraft:Combat - Revision history

SyncBot: Sync: updated from Minecraft

2026-08-11T11:25:22Z

Sync: updated from Minecraft

← Older revision		Revision as of 11:25, 11 August 2026
Line 18:		Line 18:
	*** [[Minecraft:Melee attack#Crushing blow\|Crushing blow]]		*** [[Minecraft:Melee attack#Crushing blow\|Crushing blow]]
	*** [[Minecraft:Melee attack#Smash attack\|Smash attack]]		*** [[Minecraft:Melee attack#Smash attack\|Smash attack]]
	*** [[Minecraft:Melee attack#Jab attack\|Jab attack]]
	*** [[Minecraft:Melee attack#Charge attack\|Charge attack]]		*** [[Minecraft:Melee attack#Charge attack\|Charge attack]]
	* [[Minecraft:Ranged attack]]		* [[Minecraft:Ranged attack]]
Line 56:		Line 55:
	\|Axes have lower attack damages than swords due to the absence of the attack cooldown.		\|Axes have lower attack damages than swords due to the absence of the attack cooldown.
	\|-		\|-
	\|Spear jab ~~attacks~~ have a version of the attack cooldown where attacking is not possible until reaching 100% charge.		\|Spear [[Minecraft:jab attack]]s have a version of the attack cooldown where attacking is not possible until reaching 100% charge.
	\|Spear jab attacks have a [[Minecraft:use cooldown]] instead of an attack cooldown, mimicking the forced cooldown behavior.		\|Spear jab attacks have a [[Minecraft:use cooldown]] instead of an attack cooldown, mimicking the forced cooldown behavior.
	\|-		\|-
Line 132:		Line 131:
	\|-		\|-
	\|Crossbows do not have a firing delay after becoming fully charged, and do not have a recharging delay after firing.		\|Crossbows do not have a firing delay after becoming fully charged, and do not have a recharging delay after firing.
	\|Crossbows have a several tick delay after ~~becominng~~ fully charged where they cannot be fired, and a similar delay after firing where they cannot be recharged again, effectively giving them a lower fire rate than ''Java Edition''.<ref>{{bug\|MCPE-239075\|\|There is a delay between charging and firing crossbows\|Unresolved}}</ref>		\|Crossbows have a several tick delay after becoming fully charged where they cannot be fired, and a similar delay after firing where they cannot be recharged again, effectively giving them a lower fire rate than ''Java Edition''.<ref>{{bug\|MCPE-239075\|\|There is a delay between charging and firing crossbows\|Unresolved}}</ref>
	\|-		\|-
	! colspan=2 \|Sharpness damage		! colspan=2 \|Sharpness damage

SyncBot: Sync: updated from Minecraft

2026-06-20T11:06:31Z

Sync: updated from Minecraft

← Older revision		Revision as of 11:06, 20 June 2026
Line 576:		Line 576:
	\|{{HistoryLine\|\|\|dev=16w05b\|The attack cooldown damage reduction formula has been adjusted a second time, with reduction now being a quadratic 20%–100%, bringing it to its modern functionality.		\|{{HistoryLine\|\|\|dev=16w05b\|The attack cooldown damage reduction formula has been adjusted a second time, with reduction now being a quadratic 20%–100%, bringing it to its modern functionality.
	\|Armor calculations have been adjusted a third time, with the damage reduction no longer falling off below 20% of its maximum.}}		\|Armor calculations have been adjusted a third time, with the damage reduction no longer falling off below 20% of its maximum.}}
	\|{{HistoryLine\|\|1.9.1\|dev=pre1\|Armor damage calculations have been adjusted a fourth time, with the introduction of [[Minecraft:armor toughness]] that is exclusive to diamond armor, bringing armor damage calculation to its modern functionality.\|[[Minecraft:Shield]]s no longer take durability damage when blocking attacks that deal {{hp\|2}} or less.}}		\|{{HistoryLine\|\|1.9.1\|dev=pre1\|Armor damage calculations have been adjusted a fourth time, with the introduction of [[Minecraft:armor toughness]] that is exclusive to diamond armor, bringing armor damage calculation to its modern functionality.\|[[Minecraft:Shield]]s no longer take durability damage when blocking attacks that deal {{hp\|2}} or less.\|Missing attacks no longer triggers the attack cooldown (reverted in 1.9.1 pre2)}}
			\|{{HistoryLine\|\|\|dev=pre2\|Missing attacks once again triggers the attack cooldown.\|It is now impossible to attack unless the weapon has reached at least 75% cooldown percentage (reverted in 1.9.1's full release).}}
	\|{{HistoryLine\|\|1.11\|dev=16w35a\|Shields have been rebalanced.\|Shields now block 100% of [[Minecraft:damage]]/[[Minecraft:Knockback (mechanic)\|knockback]]/debuffs dealt in melee combat.		\|{{HistoryLine\|\|1.11\|dev=16w35a\|Shields have been rebalanced.\|Shields now block 100% of [[Minecraft:damage]]/[[Minecraft:Knockback (mechanic)\|knockback]]/debuffs dealt in melee combat.
	\|Shields are now always disabled 100% of the time when blocking an attack from an axe-wielding mob or player.		\|Shields are now always disabled 100% of the time when blocking an attack from an axe-wielding mob or player.

SyncBot: Sync: updated from Minecraft

2026-06-17T11:07:44Z

Sync: updated from Minecraft

@@ Line 7: / Line 7: @@
 == Mechanics ==
 * [[Minecraft:Melee attack]]
 * [[Minecraft:Ranged attack]]
 * [[Minecraft:Armor]]
 * [[Minecraft:Food]]
 == Combat system ==

SyncBot: Sync: updated from Minecraft

2026-06-16T11:03:09Z

Sync: updated from Minecraft

← Older revision		Revision as of 11:03, 16 June 2026
Line 86:		Line 86:
	\|Shields are not lowered if the user attacks while shielding.		\|Shields are not lowered if the user attacks while shielding.
	\|Shields are lowered if the user attacks while shielding.		\|Shields are lowered if the user attacks while shielding.
			\|-
			\|When a player's shield is disabled, that player becomes immune to knockback for 10 ticks, due to the invulnerability timer triggering despite no damage being taken.<ref name="note">{{bug\|MC-268147\|\|Disabling/Breaking shield triggers invulnerability tick behavior, despite player not turning red\|Unresolved}}</ref>
			\|When a player's shield is disabled, that player does not become immune to knockback for 10 ticks, as the invulnerability timer does not trigger.
	\|-		\|-
	! colspan=2 \|Crossbow behavior		! colspan=2 \|Crossbow behavior

SyncBot: Sync: updated from Minecraft

2026-05-30T11:03:05Z

Sync: updated from Minecraft

← Older revision		Revision as of 11:03, 30 May 2026
Line 170:		Line 170:
	\|The {{hp\|2.5}} damage per level of Smite and Bane of Arthropods is not rounded down.		\|The {{hp\|2.5}} damage per level of Smite and Bane of Arthropods is not rounded down.
	\|The {{hp\|2.5}} damage per level of Smite and Bane of Arthropods is rounded down, making level I, III, and V weaker than ''Java Edition''.		\|The {{hp\|2.5}} damage per level of Smite and Bane of Arthropods is rounded down, making level I, III, and V weaker than ''Java Edition''.
			\|-
			! colspan=2 \|Snowballs and eggs against players
			\|-
			! ''Java Edition'' !! ''Bedrock Edition''
			\|-
			\|[[Minecraft:Snowball]]s and [[Minecraft:egg]]s do not affect players, dealing no knockback.<ref>{{bug\|MC-3179\|\|Snowballs, Enderpearls and Eggs do not knockback players in multiplayer\|Works As Intended}}</ref>
			\|Snowballs and eggs affect players, dealing knockback.
	\|-		\|-
	! colspan=2 \|Spear hit registration		! colspan=2 \|Spear hit registration
Line 176:		Line 183:
	\|-		\|-
	\|Spear hit registration requires significant distance between the user and the target, especially when using charge attacks at lower movement speeds.<ref>{{bug\|MC-308274\|\|Spear charge attacks are much less lenient than Bedrock Edition\|Unresolved}}</ref>		\|Spear hit registration requires significant distance between the user and the target, especially when using charge attacks at lower movement speeds.<ref>{{bug\|MC-308274\|\|Spear charge attacks are much less lenient than Bedrock Edition\|Unresolved}}</ref>
	\|Spear hit registration is much more ~~leniant~~, allowing for repeated charge attack connections despite minimal distance and low movement speed.		\|Spear hit registration is much more lenient, allowing for repeated charge attack connections despite minimal distance and low movement speed.
	\|}		\|}

SyncBot: Sync: updated from Minecraft

2026-05-26T11:05:28Z

Sync: updated from Minecraft

← Older revision		Revision as of 11:05, 26 May 2026
Line 42:		Line 42:
	\|-		\|-
	\|[[Minecraft:Saturation boost]] exists, which heals {{hp\|1}} by consuming {{hunger\|1.5}} saturation when at full hunger, and activates every 0.5 seconds (10 ticks).\|\|Saturation boost does not exist, which drastically slows the rate of health regeneration and makes [[Minecraft:saturation]] only relevant for lessening the frequency of needing to eat.		\|[[Minecraft:Saturation boost]] exists, which heals {{hp\|1}} by consuming {{hunger\|1.5}} saturation when at full hunger, and activates every 0.5 seconds (10 ticks).\|\|Saturation boost does not exist, which drastically slows the rate of health regeneration and makes [[Minecraft:saturation]] only relevant for lessening the frequency of needing to eat.
	\|-
	~~! colspan=2 \|Critical hits and sprint-knockback attacks~~
	\|-
	~~! ''Java Edition'' !! ''Bedrock Edition''~~
	\|-
	\|[[Minecraft:Critical hit]]s and [[Minecraft:sprint-knockback attack]]s cannot be performed simultaniously, as the sprint-knockback attack takes priority.\|\|Critical hits and sprint-knockback attacks can be performed simultaniously.
	\|-		\|-
	! colspan=2 \|Critical hits and sprint-knockback attacks		! colspan=2 \|Critical hits and sprint-knockback attacks
Line 77:		Line 71:
	\|The Sweeping Edge enchantment does not exist.		\|The Sweeping Edge enchantment does not exist.
	\|-		\|-
	! colspan=2 \|Shield ~~activation and knockback~~		! colspan=2 \|Shield functionality
	\|-		\|-
	! ''Java Edition'' !! ''Bedrock Edition''		! ''Java Edition'' !! ''Bedrock Edition''
Line 86:		Line 80:
	\|Shields do not deal knockback to attackers.		\|Shields do not deal knockback to attackers.
	\|Shields deal knockback to attackers, even if the attack was from an axe which stunned the shield.		\|Shields deal knockback to attackers, even if the attack was from an axe which stunned the shield.
			\|-
			\|Shields can be activated at any time, even if an attack was just performed.
			\|Shields cannot be activated if an attack was recently performed.{{checkthecode\|For how many ticks?}}
			\|-
			\|Shields are not lowered if the user attacks while shielding.
			\|Shields are lowered if the user attacks while shielding.
	\|-		\|-
	! colspan=2 \|Crossbow behavior		! colspan=2 \|Crossbow behavior

SyncBot: Sync: updated from Minecraft

2026-05-20T11:06:44Z

Sync: updated from Minecraft

@@ Line 30: / Line 30: @@
 |Spear jab attacks have a version of the attack cooldown where attacking is not possible until reaching 100% charge.
 |Spear jab attacks have a [[Minecraft:use cooldown]] instead of an attack cooldown, mimicking the forced cooldown behavior.
 |-
 ! colspan=2 |Saturation boost
@@ Line 36: / Line 42: @@
 |-
 |[[Minecraft:Saturation boost]] exists, which heals {{hp|1}} by consuming {{hunger|1.5}} saturation when at full hunger, and activates every 0.5 seconds (10 ticks).||Saturation boost does not exist, which drastically slows the rate of health regeneration and makes [[Minecraft:saturation]] only relevant for lessening the frequency of needing to eat.
 |-
 ! colspan=2 |Critical hits and sprint-knockback attacks
@@ Line 151: / Line 163: @@
 |Doing a sprint-knockback attack plays a unique sound.
 |Doing a sprint-knockback attack does not play a unique sound.
 |}

SyncBot: Sync: updated from Minecraft

2026-05-17T11:03:30Z

Sync: updated from Minecraft

← Older revision		Revision as of 11:03, 17 May 2026
Line 85:		Line 85:
	\|Firework rockets do not explode on impact with blocks or entities, instead sliding across the ground.<ref>{{bug\|MCPE-52675\|\|Fireworks do not explode on impact with entity and blocks\|Unresolved}}</ref>		\|Firework rockets do not explode on impact with blocks or entities, instead sliding across the ground.<ref>{{bug\|MCPE-52675\|\|Fireworks do not explode on impact with entity and blocks\|Unresolved}}</ref>
	\|-		\|-
	\|Continuing to hold {{Control\|use}} after firing a crossbow causes it to begin recharging again~~, and crossbows do not have a firing delay after becoming fully charged, and do not have a recharging delay after firing~~.		\|Continuing to hold {{Control\|use}} after firing a crossbow causes it to begin recharging again.
	\|Continuing to hold {{Control\|use}} after firing a crossbow does not cause it to begin recharging, as the input must be released and then inputed again. ~~There~~ is ~~also small~~ delay after fully ~~charging~~ a ~~crossbow~~ where it cannot be fired ~~despite being fully charged~~, and a similar delay after firing ~~a crossbow~~ where it cannot be recharged again.<ref>{{bug\|MCPE-~~238829~~\|\|~~Continuing to hold the use key with~~ a ~~crossbow after firing it does not start the~~ charging ~~phase,~~ and ~~both~~ firing ~~and charging are delayed~~\|Unresolved}}</ref> ~~These bugs cause crossbows to effectively charge and fire slower than in ''Java Edition''.~~		\|Continuing to hold {{Control\|use}} after firing a crossbow does not cause it to begin recharging, as the input must be released and then inputed again.<ref>{{bug\|MCPE-25778\|\|Input is unresponsive when held after changing states\|Won't Fix}}</ref>
			\|-
			\|Crossbows do not have a firing delay after becoming fully charged, and do not have a recharging delay after firing.
			\|Crossbows have a several tick delay after becominng fully charged where they cannot be fired, and a similar delay after firing where they cannot be recharged again, effectively giving them a lower fire rate than ''Java Edition''.<ref>{{bug\|MCPE-239075\|\|There is a delay between charging and firing crossbows\|Unresolved}}</ref>
	\|-		\|-
	! colspan=2 \|Sharpness damage		! colspan=2 \|Sharpness damage
Line 114:		Line 117:
	\|-		\|-
	\|Projectiles are launched the same tick that they are fired.		\|Projectiles are launched the same tick that they are fired.
	\|Projectiles are launched several ticks after they are fired, causing a desync.<ref>{{bug\|MCPE-~~238830~~\|\|Projectiles ~~are launched several ticks after they are inputted to fire~~\|Unresolved}}</ref>		\|Projectiles are launched several ticks after they are fired, causing a desync.<ref>{{bug\|MCPE-174685\|\|Projectiles lag behind the player's current looking direction\|Unresolved}}</ref>
	\|-		\|-
	! colspan=2 \|Durability		! colspan=2 \|Durability
Line 134:		Line 137:
	\|-		\|-
	\|A charge attack can be initiated instantly after doing a jab attack.		\|A charge attack can be initiated instantly after doing a jab attack.
	\|There is a several tick delay after doing a jab attack where a charge attack cannot be initiated.<ref>{{bug\|MCPE-~~238831~~\|\|~~There is a several tick delay after jab attacking where a charge attack cannot be initiated~~\|Unresolved}}</ref>		\|There is a several tick delay after doing a jab attack where a charge attack cannot be initiated.<ref>{{bug\|MCPE-233837\|\|Spear's Charge Attack After Using Lunge Is Too Delayed Compared to Java\|Unresolved}}</ref>
	\|-		\|-
	\|Charge attacks do not display critical hit particles when connecting.		\|Charge attacks do not display critical hit particles when connecting.

SyncBot: Sync: updated from Minecraft

2026-05-16T11:04:33Z

Sync: updated from Minecraft

← Older revision		Revision as of 11:04, 16 May 2026
Line 508:		Line 508:
	\|Armor damage reduction calculations have been adjusted a second time, with the maximum damage reduction returning back to 80%, and the damage reduction can no longer decrease below 25% due to the strength of an incoming attack.}}		\|Armor damage reduction calculations have been adjusted a second time, with the maximum damage reduction returning back to 80%, and the damage reduction can no longer decrease below 25% due to the strength of an incoming attack.}}
	\|{{HistoryLine\|\|\|dev=16w05b\|The attack cooldown damage reduction formula has been adjusted a second time, with reduction now being a quadratic 20%–100%, bringing it to its modern functionality.		\|{{HistoryLine\|\|\|dev=16w05b\|The attack cooldown damage reduction formula has been adjusted a second time, with reduction now being a quadratic 20%–100%, bringing it to its modern functionality.
	\|Armor calculations have been adjusted a third time, with the damage reduction no longer falling off below 20% of its maximum, bringing ~~the calculations~~ to ~~their~~ modern functionality.}}		\|Armor calculations have been adjusted a third time, with the damage reduction no longer falling off below 20% of its maximum.}}
			\|{{HistoryLine\|\|1.9.1\|dev=pre1\|Armor damage calculations have been adjusted a fourth time, with the introduction of [[Minecraft:armor toughness]] that is exclusive to diamond armor, bringing armor damage calculation to its modern functionality.\|[[Minecraft:Shield]]s no longer take durability damage when blocking attacks that deal {{hp\|2}} or less.}}
	\|{{HistoryLine\|\|1.11\|dev=16w35a\|Shields have been rebalanced.\|Shields now block 100% of [[Minecraft:damage]]/[[Minecraft:Knockback (mechanic)\|knockback]]/debuffs dealt in melee combat.		\|{{HistoryLine\|\|1.11\|dev=16w35a\|Shields have been rebalanced.\|Shields now block 100% of [[Minecraft:damage]]/[[Minecraft:Knockback (mechanic)\|knockback]]/debuffs dealt in melee combat.
	\|Shields are now always disabled 100% of the time when blocking an attack from an axe-wielding mob or player.		\|Shields are now always disabled 100% of the time when blocking an attack from an axe-wielding mob or player.

SyncBot: Sync: updated from Minecraft

2026-05-15T11:03:49Z

Sync: updated from Minecraft

← Older revision		Revision as of 11:03, 15 May 2026
Line 28:		Line 28:
	\|Axes have lower attack damages than swords due to the absence of the attack cooldown.		\|Axes have lower attack damages than swords due to the absence of the attack cooldown.
	\|-		\|-
	\|~~Spears~~ jab attacks have a version of the attack cooldown where attacking is not possible until reaching 100% charge.		\|Spear jab attacks have a version of the attack cooldown where attacking is not possible until reaching 100% charge.
	\|~~Spears~~ jab attacks have a [[Minecraft:use cooldown]] instead of an attack cooldown, mimicking the forced cooldown behavior.		\|Spear jab attacks have a [[Minecraft:use cooldown]] instead of an attack cooldown, mimicking the forced cooldown behavior.
	\|-		\|-
	! colspan=2 \|Saturation boost		! colspan=2 \|Saturation boost