Currently, mobs that can’t use the spear’s charge attack also don’t use the spear’s jab attack properly, not playing the animation, hitting multiple mobs at once, triggering lunge, or being affected by the cooldown, instead treating it like a sword or other melee weapon. Also, the attack ranges aren’t applied on Bedrock, but are on Java, which on Java results in mobs standing too close to each other to attack.
Steps to Reproduce:
Get a command to replace the mainland slot of a mob (I used skeleton) with a spear.
For testing lunge, also use /enchant.
Then either use an entity that will be automatically targeted (Iron Golem in my case), or use /damage @e 0 stalagmite entity @e[type=<entity to target>,c=1]
Expected Result:
I expected that the mobs would properly use the jab attack, with the expected differences in how it works.
Actual Result:
The mobs attacked using a standard melee attack, something players can’t actually do with a spear.
While skeletons with spears is only possible with commands, the reason I discovered this is because foxes can’t properly use the jab attack either, not hitting multiple entities at once, which I wanted to use for an automatic XP farm.
Unable to attach video directly, will try through comments
Attachments
Comments 3
Memttm
Thank you for your report!
However, this issue is Invalid.
This behavior is consistent between Bedrock Edition and Java Edition. This means you have posted a feature request or a suggestion. This site is for bug reports only. For suggestions, please visit Minecraft Suggestions on Reddit or visit the Feedback website.
Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📧 Suggestions – 📖 Minecraft Wiki
I disagree that this is a feature request, as a spear is meant to have a charge and jab attack, using it as a standard melee weapon isn’t intended. An issue appearing on bedrock and java doesn't always mean it is an issue, it just means that the developers hadn’t thought about this when coding it. There are many bug reports I have seen which occurred on both bedrock and java, and so have separate bug reports for both versions. If this behavior is intended, it should be reported as intended by official Mojang documentation.
Also, the behavior between both versions isn’t entirely consistent, as the different attack max and min range applies to java but not bedrock, tracked in the seperate report MCPE-233932. Overall, I don’t think this should be classed as invalid for being mostly conststent between versions, and if it is works as intended then that should be decided by the Mojang devs. This issue looks to me like an area that the devs just forgot about. Also, this issue could affect weapons with custom attack behavior, whether they are using the charge or jab attack properties, or other properties existing now or later.