The bug
When the arrows, tridents and projectiles rate of fire is too fast, it can't be teleported by the portal, end gateway and nether portal.
Code analysis
Code analysis by @unknown can be found in this comment.
Related issues
is duplicated by
MC-240353
Projectiles thrown through end portal are not teleported to the end.
MC-272622
Ender pearls thrown into end gateways occasionally fail to teleport the player or, when they succeed, occasionally cause very heavy memory usage
MC-272780
Ender pearls can sometimes pass through nether portal blocks without crossing through dimensions
MC-272835
Ender pearls thrown through the gates of Hell may not teleport
MC-272836
Sometimes, ender pearls passing through a nether portal will pass through the portal instead of being teleported to the nether
MC-272998
Using an ender pearl to teleport through an End portal does not work consistently
relates to
MC-191947
Entities that tick in nether portal for one gametick don't get sent to the nether
MC-196897
Entities that move (Velocity) into a nether portal don't get sent to the nether in the same gametick
MC-272782
Sometimes ender pearls can pass through portals but not land until the player loads the chunks near the portal
MC-275638
It is still possible to go through portals without being teleported when going quickly enough by throwing riptide tridents
MC-276016
Throwing an ender pearl into the exit portal sometimes sends you to the world spawn point
testing discovered
Attachments
Comments
migrated
migrated
Can confirm.
[Mod] markderickson
Hi there!
Does MC-191947 describe the issue?
[Mod]Les3awe
@@unknown, is not.
[Mod]Les3awe
This issue is about the projectile acceleration too fast, causing the portal to fail detect the projectile.
Jeuv
This also seems quite location dependent. Moving closer to or further away from the portal changes whether the projectile goes through the portal or not. My hypothesis is that this is because projectiles don't check if they passed through a portal between two ticks.
Avoma
Can confirm in 20w51a.
Avoma
Can confirm in 21w03a.
Avoma
Can confirm in 21w05a.
Avoma
Can confirm in 21w05b.
Avoma
Can confirm in 21w06a.
Avoma
Can confirm in 21w07a. Video attached.
Avoma
Can confirm in 21w11a.
ampolive
Can confirm in 1.17.1.
ampolive
Can confirm in 21w42a.
lovexyn0827
This is why it happens:
In Minecraft 1.16.1 and earlier versions, thrown projects checks if the OUTLINE shapes of blocks, to find potential collisions and chances to be teleported ("hit" a nether_portal block, for example)(See ThrowableProjectile.tick()). A portal has its non-empty OUTLINE shapes though it has no collision box which can stop regular entity movement, so thrown projectiles can always detect if it can be teleported no matter how high their velocity is.
But in 1.16.2-pre1, something was changed. The OUTLINE shape get no longer used in collision checks, instead, the COLLIDER shape has been used since then (See ThrowableProjectile.tick() & ProjectileUtil.getHitResult()). However, portals has empty COLLIDER shapes, so the teleporting check became dead code. And entities only stays in some seperated points, thus if the velocity of a thrown projectile entity is greater than 1 bloch per tick, it may pass through the portal if it failed to be teleported in the Entity.handleNetherPortal() method.
Suggestions to solve it:
The change may be intended to fix MC-73884, simply changing it back is not a good idea. But a addional ray trace may be introduced when the speed of the entity is higher than 1 block pre tick, just like what falling_blocks of concrete powder do.
[Mod]Les3awe
Still in the 24w33a.
[media][media]
[Mod]Les3awe
Shugoh