Shield blocking is delayed
Linked Issues
is duplicated by28
- Unresolved
Greg Milson
Pablo
- 124
- 62
- Confirmed
Normal
- Gameplay
- Player
- block delay shield
1.9.2 - 1.21.4
1.9.2 16w14a 16w15a 16w15b 1.9.3-pre3 1.9.3 1.9.4 16w20a 16w21b 1.10-pre1 1.10 1.10.1 1.10.2 1.11.2 17w06a 1.12 1.12.1-pre1 1.12.1 1.12.2 18w19b 18w21b 18w22a 18w22b 18w22c 1.13-pre1 1.13-pre2 1.13-pre4 1.13-pre5 1.13-pre7 1.13 18w30a 18w30b 18w31a 18w32a 1.13.1 1.13.2-pre1 1.13.2 19w03c 19w04b 19w08b 19w09a 19w11b 19w12b 19w13a 19w13b 1.14-pre2 1.14-pre3 1.14-pre4 1.14-pre5 1.14 1.14.2 1.14.3-pre3 1.14.4 19w40a 1.15.2 20w08a 20w10a 20w20b 1.16.1 20w27a 1.16.2-rc1 1.16.3 1.16.4-pre2 1.16.4 20w46a 20w51a 21w03a 1.16.5 21w05b 21w06a 21w07a 21w11a 21w14a 21w15a 21w18a 1.17 1.17.1 21w38a 21w40a 1.18.1 1.18.2 22w15a 1.19 1.19.2 1.19.3 23w05a 1.20 1.20.1 1.20.2 23w42a 23w43b 23w44a 23w45a 23w46a 1.20.3-pre2 1.20.3 1.20.4-rc1 24w05b 24w14a 1.20.6-rc1 1.20.6 24w18a 1.21 1.21.4
Created Issue:
Shield blocking is delayed
If you use a shield (usually right clicking), it will not block until a second has elapsed, so it does not protect you instantly.
To recreate this issue, follow these steps:
1. On survival mode, spawn a skeleton.
2. When it shoot you, block with a shield.
You will not stop the arrow and it will deal damage to you.
is duplicated by
is duplicated by
relates to
duplicates
is duplicated by
duplicates
If you use a shield (usually right clicking), it will not block until a second has elapsed, so it does not protect you instantly.
To recreate this issue, follow these steps:
1.On survival mode, spawn a skeleton.
2. When it shoot you, block with a shield.
You will not stop the arrow and it will deal damage to you.
is duplicated by
Still applies to version 1.12.2.
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
Duplicate of MC-100949.
also relates to MC-100949
Thank you for your report!
However, this issue is a Duplicate of MC-100949.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – 📖 Game Wiki
Thank you for your report!
However, this issue is a Duplicate of MC-100949.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – 📖 Game Wiki
The bug
Enemies like Zombies and Endermen are sometimes suddenly attacking quickly 2 times in a row instead of at their normal attack-rate. (Melee attacks only as far as I know). Sometimes the attack animation or sound won't even play.
This can seemingly mess with blocking too, though it could also just be MC-100949
Code analysis
Code analysis by Chumbanotz can be found in this comment.
Thank you for your report!
However, we are already tracking this issue, and this report is a Duplicate of MC-100949, which is a report that has not been resolved yet.
If you want, you can upvote the parent ticket, and enable watching to receive any updates about it - if you believe you have any information that may be important for this issue, please leave a comment on the parent. Please also use the search function in the future to prevent duplicate reports.
Quick Links:
📓 Issue Guidelines – 🛠 Community Support – 📧 Customer Support – ✍️ Feedback and Suggestions – 📖 Game Wiki
💬 Mojira Subreddit – 💬 Mojira Discord
Duplicate of MC-100949
Thank you for your report!
However, we are already tracking this issue, and this report is a Duplicate of MC-100949, which is a report that has not been resolved yet.
If you want, you can upvote the parent ticket, and enable watching to receive any updates about it - if you believe you have any information that may be important for this issue, please leave a comment on the parent. Please also use the search function in the future to prevent duplicate reports.
Quick Links:
📓 Issue Guidelines – 🛠 Community Support – 📧 Customer Support – ✍️ Feedback and Suggestions – 📖 Game Wiki
💬 Mojira Subreddit – 💬 Mojira Discord
This issue is already being tracked at MC-100949.
This is most likely a duplicate of MC-100949, judging by the information you've provided in this ticket.
Thank you for your report!
We're tracking this issue in MC-100949, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
Duplicate of MC-100949.
Does MC-100949 describe your issue?
In that case, this ticket is a duplicate of MC-100949
Does MC-100949 describe your issue?
Would MC-100949 happen to describe your issue?
Most likely a duplicate of MC-100949.
We are not calling you a duper! Please read MC-100949 and the duplicate reports to see if that describes the problem.
Thank you for your report!
We're tracking this issue in MC-100949, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
– I am a bot. This action was performed automatically! The ticket was resolved by one of our moderators, and I left this message to give more information to you.
Does MC-100949 describe your issue?
I'm quite certain in saying that this is a duplicate of MC-100949. ![]()
Thank you for your report!
We're tracking this issue in MC-100949, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
– I am a bot. This action was performed automatically! The ticket was resolved by one of our moderators, and I left this message to give more information to you.
Duplicates MC-100949
Does MC-100949 describe your issue?
Is this perhaps MC-100949? Shield blocking isn't instant, but there's a small delay.
This is also currently being tracked on Java MC-100949.
Since at least 1.18 (according to other reports) there has been an issue with shields not instantly blocking any incoming damage when activated. This causes there to be a slight visual and practical delay when the shield is used.
Steps to reproduce:
- Spawn in a zombie and coax it into attacking you.
- With your shield in hand, try and block any attacks.
Observed results:
There'll be a slight delay between when the shield is first activated to when it starts blocking any damage.
Expected results:
The shield should immediately start blocking any damage when used.
Duplicate of MC-100949
Thank you for your report!
We're tracking this issue in MC-100949, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
– I am a bot. This action was performed automatically! The ticket was resolved by one of our moderators, and I left this message to give more information to you.
Does MC-100949 describe your issue?
Thank you for your report!
We're tracking this issue in MC-100949, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
Thank you for your report!
We're tracking this issue in MC-100949, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
Hi there! Would MC-100949 happen to describe the issue that you're experiencing here? If not, please could you provide a video recording demonstrating this behavior occurring while the F3 debug screen is enabled? Supplying this information would greatly assist in diagnosing the potential problem here. Thanks in advance!
This issue is being temporarily closed as Awaiting Response. Once the requested information has been delivered, the report will be reopened automatically.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
Thank you for your report!
We're tracking this issue in MC-100949, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
Are you sure you didn't experience MC-100949 instead?
Thank you for your report!
We're actually already tracking this issue in MC-100949, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote or any additional information to the main ticket it would be appreciated.
Please be sure to use the search feature before creating a ticket to see if the issue has already been reported.
Quick Links:
📓 Bug Tracker Guidelines – 🛠 Community Support – 📧 Mojang Support – ✍️ Feedback and Suggestions – 💬 Mojira Discord
Duplicate of MC-100949
Thank you for your report!
We're tracking this issue in MC-100949, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support (Technical Issues) – 📧 Microsoft Support (Account Issues)
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
– I am a bot. This action was performed automatically! The ticket was resolved by one of our moderators, and I left this message to give more information to you.
Thank you for your report!
We're tracking this issue in MC-100949, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support (Technical Issues) – 📧 Microsoft Support (Account Issues)
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
Thank you for your report!
We're tracking this issue in MC-100949, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support (Technical Issues) – 📧 Microsoft Support (Account Issues)
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
Thank you for your report!
We're tracking this issue in MC-100949, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support (Technical Issues) – 📧 Microsoft Support (Account Issues)
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
Please do not mark unreleased versions as affected.
You don't have access to them yet.
Still applies to version 1.9.4. Does anyone know if this is actually a bug or it's intended purpose?
It happens even when you block before the arrow shoots, I always hit the skeleton when his bow is empty, and have to pull up shield as soon as he charges another arrow, if I'm too late the arrow ignores the shield.
Confirmed for release 1.10
Duplicate of
MC-97772Forward resolving
MC-97772to here.Still affects 1.12.2, although the Minecraft Wiki at the very least treats this as intended behavior; there was .5s after raising shield before it was effective in early 1.9 snapshots, but this was reduced to .25s before 1.9's release. If the delay is longer than this, and isn't due to some form of lag, then it's a definitely a bug.
But even if it is intended, it shouldn't existWhat the wiki states is irrelevant. It only states the current behavior, not intended behavior. And as such is not a relyable source regarding if it's intended or not.
Still an issue in 18w21b
Greg Milson, ticket is yours now.
It is actually a feature. It is unknown why they would have such a stupid mechanic but thats how the mojang works
Source that this is intended?
Please do not mark unreleased versions as affected.
You don't have access to them yet.
I don't know if it's intended, but have no sense.
The main problem is that there is a desynchronization between what the player sees and what happens in the game. The player is seeing that he raised the shield in time to block that arrow, but the arrow hits him and makes him lose life points.
If the player is seeing that he is protected, he must not lose the points of life.
There is already a delay since the player presses the button until the shield rises (the visual animation time)
This feels completly wrong. As Dídac said, the animation should be synced with the intended action in-game. Also, having this feature fixed would feel rewarding for the skills of the player; defending in the last second is an act of reflexes, and the gaming community when rewarded for their skills gives back to the game whichi finally means, a better image for the game itself.
Probably the younger players wont care about this and keep playing as pretended by the limitations, but the more adult community will turn away from a game that displays and ignores this "spaghetti code" behaviour. By the end of the day, this means advertising and finally, a bigger and more mature community.
This affects especially the PvP and PvE players, which makes up the fighting and adventure sides of the game.
Confirmed to be fixed in a future version
:
https://twitter.com/jeb_/status/1136935340827127813
Affects versions 20w20a and 20w20b as well. This is the one bug I want to be fixed, I literally don't use shields because of this bug and it's beginning to really frustrate me.
Affects 1.16.1
In 20w27a
The way i play the game, this bug seems like it should have far more ubiquity. That reaction time is pretty much pointless when blocking, that you're effectively punished for doing something to the same effect as parrying, is pretty dumb. But fix it on your own time, Mojang!

Can confirm in 20w51a.
Can confirm in 21w03a.
Can confirm in 21w05b.
Can confirm in 21w06a.
Can confirm in 21w07a.
I thought this was an intended feature
Can confirm in 21w11a.
Can confirm in 21w14a.
Can confirm in 21w18a
Can confirm in 1.17.
Can confirm in 21w38a
Not sure if developers intended for shield blocking to be instantaneous or if they intended for there to be a delay. Either way, current functionality is insufficient because with the delay we have right now, it is not shown to the player, therefore the instantaneous shield blocking we see is misleading – a potential fix if developers wish to keep a delay functionality is to maybe make an animation that shows the delay, and the animation only ends once the delay is over and the shield is in blocking position. If this is the route we go, it would also be essential for pvp that this animation and its timing is correctly visible to other players as well.
Just attached 2 more vids recorded in 1.17.1, latest release at time of typing this, which show this happening in melee cases as the existing vids were with projectiles.
Can confirm in both 21w39a and 21w40a.
Also Megalodab in this video that does code analysis of this issue I assume it is intended. In short, there is an arbitrary 250ms delay after you hold up a shield until it is permitted to block attacks. I don't know how you would add this to the description like how other reports have a Code analysis section but maybe someone else knows how.
In any case I feel like the delay should be removed entirely (which from what I can understand would involve just changing a 5 to a 0) rather than syncing the animation to the delay because it just adds unneeded jank to the shield and makes you play arbitrarily slow with it, not just with pvp, but also with pve fighting multiple skeletons, for example.
Yeah I agree zeta I’d prolly want the instantaneous option
In 22w15a and in 1.18.2
Affects 1.19
Can confirm in 1.19.2.
yes finally
To the people who say this might be intended, Mojang can easily clear that up by marking this issue as "Works as Intended".
However they keep it open for unknown reasons (as far as we know), which leads me to believe it was intended.
Can confirm in 23w05a
Confirmed in 1.20
This should be WAI, in the combat tests this was intentionally changed and discussed by Jeb. It will not be changed for the current combat system, as it is intended there.
@SeaOfPixels If this is WAI then it should not play the pull up animation until after whatever time it can start blocking attacks so it doesn't just lift up the shield to find out it won't work right away.
Confirmed in 1.20.2.
If you guys didn't know, shields have a cooldown of 0.25 seconds before blocking damage so unfortunately, it does not block instantly.
Can also confirm in 23w42a
There's nothing more annoying than blocking a skeleton arrow only to still get hit by it, and it gets annoying having to pre emptively block and wait for the skeleton to shoot
Confirmed in 23w43a and 23w43b
Confirmed in 23w44a
Also confirmed in 23w45a
Confirmed in 23w46a
Confirmed in 1.20.3-pre2
Confirmed in 1.20.3
Can confirm in 1.20.4 Release Candidate 1
Confirmed in 24w05b
Confirmed in 24w14a
Confirmed in 1.20.6-rc1
Confirmed in 24w18a
grab a shield in your non-dominant (or dominant) hand and try to block instantly
In 25w04a shields now have a component which determines how long it takes for the shield to start blocking, and the default is 0, however, that doesn't seem to actually work and shields still have the delay.
This should probably now be marked as intended as despite the tag existing, a spawned item with a set delay of 0 works.
/give @p diamond_sword[minecraft:blocks_attacks={block_delay_seconds:0}]This item can block damage and reflect noticeably faster than a vanilla shield, which means the shield should have a specified value of 0.25 in the block delay seconds property. Assuming this item works properly and can be verified, that would mean that the way shields work is considered intentional.
Shields are intended to have a block delay of 0.25 seconds, as can be seen now in the default components of the item:
This seems like it should be marked as intended.