Zombified Piglins riding striders can despawn, leaving saddled striders
Zombified Piglins spawned as riding striders despawn when there is no player nearby but saddled striders remain.


Environment
openjdk version "11.0.6" 2020-01-14
Linked Issues
is duplicated by1
Created Issue:
Zombified Piglins riding striders can despawn living saddled striders alone.
Zombified Piglins spawned as riding striders despawn when there is no player nearby but saddled striders remain.
Environment
openjdk version "11.0.6" 2020-01-14
Zombified Piglins riding striders can despawn living saddled stridersalone.Zombified Piglins riding striders can despawn, leaving saddled striders.
Zombified Piglins riding striders can despawn, leaving saddled striders.
is duplicated by
Thank you for your report!
We're tracking this issue as MC-178013, so this ticket is being resolved and linked as a duplicate.
That ticket has already been resolved as Fixed.
In this case, that means striders spawned in earlier versions may still have a saddle with no rider, but it should not happen anymore with newly spawned striders.
If you haven't already, you might like to make use of the search feature to see if the issue has already been reported.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – ✍️ Feedback and Suggestions – 📖 Game Wiki
The bug
Starting with 20w18a some mobs do not count to the mob cap anymore if they are a passenger (e.g. riding a minecart).
The following mobs are not affected:
- Mobs which can be part of a raid (e.g. witch)
- Fish
Reproduction steps
- Open the debug screen (F3)
The following steps refer to the "M:" ("Monster") mob category shown in the line starting with "SC:" on the left below "Local difficulty:" and above "Sounds:". - Spawn a husk
The husk is counted for the "Monster" category - Spawn a husk riding a minecart
/summon minecart ~ ~ ~ {Passengers:[{id:husk}]}
The husk is not counted - Destroy the minecart
Now the husk is counted
Code analysis
20w19a, Mojang names
In 20w18a net.minecraft.world.entity.Mob.requiresCustomPersistence() was changed to return whether the mob is a passenger instead of always returning false. This might have been done to fix MC-178013, since this method is also used to determine whether a mob can despawn, but has the probably unintended side-effect described in this bug report.
Additionally it is not consistent whether passenger mobs count to the mob cap, because the classes overriding requiresCustomPersistence() do not consider the parent result.