Ravagers have a bad attack reach
Analysis and behavior patch demo provided in comment.
In java edition,those mobs can bite you from 3 blocks radius but here in bedrock edition they need to be more closer in order to attack you,this makes them so much easier for armless players,so it's necessery to increase their attack reach or making them more faster,they should be a real challenge for players and a dead loss.
Video:
https://youtu.be/J9LQHrupP4M
Linked Issues
is blocked by1
is duplicated by7
MCPE-80643Ravager hitbox is too small while attacking DuplicateMCPE-82222The Ravager's attack range is too smallDuplicateMCPE-84354Ravager is completely brokenDuplicateMCPE-106832Ravagers ram attack has less attack rangeDuplicateMCPE-112092Ravager Attack RangeDuplicateMCPE-117803The attack range of the ravager (or the ravager itself) is faultyDuplicateMCPE-156024Ravager attacks sometimes not workDuplicate
![[Mod] GoldenHelmet](../../../data/avatars/users/18951.svg){kind=small}
- Fixed
adnan dakir- 41
- 19
- Confirmed
- 208804
- Multiple
- Android 9.0
1.19.0.33 Preview - 1.18.31
1.19.0.33 Preview 1.19.0.32 Beta 1.18.33 Hotfix 1.18.32 1.18.20.27 Beta 1.17.11 Hotfix 1.16.210.59 Beta 1.16.210.53 Beta 1.16.200.56 Beta 1.16.0.68 Beta 1.16.0.66 Beta 1.16.0.64 Beta 1.16.0.63 Beta 1.14.2.50 Beta 1.14.1 Hotfix 1.14.60 Hotfix 1.16.0 1.16.100 1.16.201 Hotfix 1.18.12 Hotfix 1.18.31- 1.19.40
Created Issue:
Ravagers have a bad attack reach
In java edition,those mobs can bite you from 3 blocks radius but here in bedrock edition they need to be more closer in order to attack you,this makes them so much easier for armless players,so it's necessery to increase their attack reach or making them more faster.
![[Bot] Arisa](../../../data/assets/gravatar/mustek2.png){kind=small}
In java edition,those mobs can bite you from 3 blocks radius but here in bedrock edition they need to be more closer in order to attack you,this makes them so much easier for armless players,so it's necessery to increase their attack reach or making them more faster,they should be a real challenge for players and a dead loss.
![[Mod] OcelotOnesie](../../../data/avatars/users/43220.png){kind=small}
is duplicated by
![[Bot] Arisa](../../../data/avatars/users/43007.png){kind=small}
is duplicated by
In java edition,those mobs can bite you from 3 blocks radius but here in bedrock edition they need to be more closer in order to attack you,this makes them so much easier for armless players,so it's necessery to increase their attack reach or making them more faster,they should be a real challenge for players and a dead loss.
Video:
https://youtu.be/J9LQHrupP4M
is duplicated by
![[MCQA] v-weszaj](../../../data/avatars/users/18941.svg){kind=small}
is duplicated by
is duplicated by
is duplicated by
![[Helper] lillybeacon](../../../data/avatars/users/93893.png){kind=small}
is blocked by
relates to
Checked here and apparently their Knockback Resistance was increase in Java during Pre-release 6 while in Bedrock Edition it stayed unchanged, apparently in Java it was increased to 80% while in BE it's still in 50% which may also affect how well they fight and properly use their reach
ravager fixed.mp4is duplicated by
relates to
Analysis and behavior patch demo provided in comment.
In java edition,those mobs can bite you from 3 blocks radius but here in bedrock edition they need to be more closer in order to attack you,this makes them so much easier for armless players,so it's necessery to increase their attack reach or making them more faster,they should be a real challenge for players and a dead loss.
Video:
https://youtu.be/J9LQHrupP4M
relates to
Thank you for your report!
We're actually already tracking this issue at MCPE-60680, so I will resolve and link this ticket 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:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – ✍️ Feedback and Suggestions – 📖 Game Wiki
Thank you for your report!
We're actually already tracking this issue at MCPE-60680, so I will resolve and link this ticket 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:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – ✍️ Feedback and Suggestions – 📖 Game Wiki
Thank you for your report!
We're actually already tracking this issue at MCPE-60680, so I will resolve and link this ticket 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:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – ✍️ Feedback and Suggestions – 📖 Game Wiki
Thank you for your report!
We're actually already tracking this issue at MCPE-60680, so I will resolve and link this ticket 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 actually already tracking this issue at MCPE-60680, so I will resolve and link this ticket 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 MCPE-60680, 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! Please report any issues on Discord or Reddit
The ravager in Bedrock Edition this collision box:
"minecraft:collision_box": {
"height": 1.9,
"width": 1.2
},
The collision box in Java, on the other hand, is height 2.2, width 1.95.
If I had to guess, I would surmise that the Bedrock collision box was set based on
- 1.9 height being the default for mobs in Bedrock.
- 1.2 width based on how wide the ravager is visually side-to-side, i.e. the literal meaning of "width".
The Java width of 1.95 is a much better balance between the ravager's literal "width" and length. With a 1.95 game width you can bump ravagers from the side without quite touching them visually. That may seem like bug, but its negative impact is more than compensated for by the positive impact of a more accurate collision font-to-back. Moreover, giving ravagers a 1.95 width fixes their visual attack reach extending farther than their actual ability to hit (MCPE-60680).
This issue appears to be caused by more fundamental issues:
MCPE-91147MCPE-45531(which causesMCPE-60680)MCPE-48145MCPE-136616(i.e. iron golems giving too much vertical knockback to begin with)
When I use a behavior pack to fix MCPE-45531 and MCPE-48145 (making the Ravager collision and speed match Java), then the ravager is always able to bite the iron golem once before the iron golem retaliates. However, due to MCPE-91147 and MCPE-136616 the iron golem then always hits the ravager 3 times in the air before it lands.
This is tracked at MCPE-60680 now. It's actually caused by ravagers on Bedrock having a collision box that's 2/3 the width of ravagers on Java. Attack reach is determined by multiplying by the collision box.
Thank you for your report!
We're tracking this issue in MCPE-60680, 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.
When a ravager bites, it slows to a stop, launches its head forward and shuts its jaw. Roughly when it closes its jaw is when the damage is actually given to its target. This differs greatly from java edition, in which the attack damages the target immediately after beginning its attack animation. Due to this bug, simply walking away from an attacking ravager will nearly always guarantee safety, since the stopping at the start of the attack gives ample time to escape the attack range of the ravager before it actually bites and delivers damage. I also believe this is a separate issue from MCPE-60680, since that concerns their reach rather than the timing at which damage is given
Steps to reproduce:
1. Find a ravager in survival mode by any means
2. Allow it to chase you until it gets close enough to bite, at which point continue walking away from it
Expected result: The ravager should deal damage to you immediately after it bites
Actual result: The bite is way too easy to avoid because of the damage timing not matching java, and will not hit the player consistently in this scenario
Doesn't it make sense that the damage is given as the bite closes? It sounds like the bug is in Java.
About it being easy to dodge, that seems just as much a result of MCPE-60680 and MCPE-48145, as what is described here. Due to 60680 (really MCPE-45531) the attack reach does not match the animation, so you have to be inside of its head to take damage.
As can be seen from the video I've attached below that the ravager have a shorter reach than to Bedrock Edition.
This should be a valid parity issue, because ravagers attack reach, hitbox and movement speed were changed in Bedrock 1.19.40. (MCPE-60680, MCPE-45531 and MCPE-48145)
Confirmed for 1.16.0
Affects 1.16.20.50
Affects 1.16.1
The reason why that happens is because in Bedrock Edition their hitbox is smaller, which also affects their reach multiplier! In BE their height is 1.9 instead of 2.2 and their width is 1.5 instead of 1.95! That's why their reach is bad...
I believe the too-short attack reach for ravagers would be fixed entirely by fixing the too-short collision box for ravagers (
MCPE-45531) and the too-slow speed (MCPE-48145). The video below shows ravagers with movement speed and collision box changed to match Java (0.4 speed and 1.95 x 2.2collision).
Ravager attack with fixed collision box and speed.mp4
However, if you set the attack range multiplier to 2.5 as suggested by the comment above then ravagers can hit 5 blocks away from where they stand (i.e. a ravager standing on a floating block can hit a villager standing on a floating block with 4 air blocks in-between), which is far beyond the visual reach of their head.
Yea , checked again and tested, apparently i was wrong about the reach Multiplier! The hitbox size being smaller than it should is what greatly affects the reach of the Ravager
RunOut: Could you please make a new report with the vanilla-parity label about the Ravager knockback? I am not able to confirm it since I don't have Java, but if you make a report another moderator can follow up on that.
Ok then
Affects 1.17.40.20
Affects 1.18.20.27
As seen in the video you can notice that the Ravager's attack on Bedrock Edition has a delay and that's why you can easily avoid the attack while the Ravager is performing it, if you set the attack delay to 0(on BE it has a delay of 0.5) it acts similar to Java! Because of the delay Villagers and the player can easily avoid a attack from the Ravager even when they should've clearly take damage
But still, when compared to Java they still lack some reach! That's fixed when their hitbox is changed to a width of 1.95(and height of 2.2) and while it might look like it hits a little further than it should it's exactly how it's in Java
Added a video showing a Ravager on Java with the hitbox being shown while they attack a Villager to better compare it with how it's on Bedrock Edition
By making the changes mentioned earlier by me the Bedrock one will have the exact same reach and attack
Added a video where i tested the changes i mentioned(including a fix to their to movement speed for more accurare testing), hopefully can help in the comparison
Affects Beta 1.18.30.26 and Preview 1.18.30.27
Affects 1.19.10
This was fixed in 1.19.40 by the fix to
MCPE-45531, and to a lesser extentMCPE-48145.