Teleport with chorus fruit does not create an extra trail of particles

I know this could be considered a feature request, but
I checked the tickets MC-2157,MC-10369,MC-84517,MC-102881,MC-185017,MC-258347 and decided to report.
For context, it's possible that the initial chorus fruit was designed to spawn particles from the initial location to the destination location (like to dragon eggs and enderman), but due to MC-10369,MC-84517 it didn't show up properly and MC-10369 eventually fixed it. When teleported, particles appeared only at the location after teleporting.

This is a feature request.

I would like to request reconsideration of MC-260379, which was previously closed as a feature request.

While investigating MC-258347, I found that the behavior reported in MC-260379 does not appear to be an independent visual feature. The relevant teleport particle effect is handled through entity event 46 in LivingEntity. Its particle handling is shared, with no entity-specific branch that gives Endermen a particle trail while intentionally limiting players or foxes to destination-only particles.

This was also observable during testing. Modifying the shared event 46 handling caused the behavior of Endermen, players, and foxes to change together. Intermediate fixes for one case affected the others, demonstrating that these behaviors are coupled through the common handling rather than implemented as independent effects.

I was eventually able to restore the event 46 teleport trail through a common implementation. Endermen, players teleporting with chorus fruit, and foxes teleporting after eating chorus fruit all receive the restored behavior without requiring separate entity-specific particle exceptions. The resulting implementation has remained stable during repeated testing.

This is relevant to the classification of MC-260379. If MC-258347 is fixed at the shared event 46 level, the behavior described in MC-260379 can be restored as a natural consequence of the same fix. Keeping the Enderman trail while deliberately retaining destination-only particles for players and foxes would instead require additional entity-specific exceptions.

Therefore, restoring MC-260379 does not necessarily constitute adding a new feature. The shared code path, the lack of an original entity-specific distinction, and the results of a working common fix provide technical grounds to reconsider its previous classification as a feature request.I would like to request reconsideration of MC-260379, which was previously closed as a feature request.

While investigating MC-258347, I found that the behavior reported in MC-260379 does not appear to be an independent visual feature. The relevant teleport particle effect is handled through entity event 46 in LivingEntity. Its particle handling is shared, with no entity-specific branch that gives Endermen a particle trail while intentionally limiting players or foxes to destination-only particles.

This was also observable during testing. Modifying the shared event 46 handling caused the behavior of Endermen, players, and foxes to change together. Intermediate fixes for one case affected the others, demonstrating that these behaviors are coupled through the common handling rather than implemented as independent effects.

I was eventually able to restore the event 46 teleport trail through a common implementation. Endermen, players teleporting with chorus fruit, and foxes teleporting after eating chorus fruit all receive the restored behavior without requiring separate entity-specific particle exceptions. The resulting implementation has remained stable during repeated testing.

This is relevant to the classification of MC-260379. If MC-258347 is fixed at the shared event 46 level, the behavior described in MC-260379 can be restored as a natural consequence of the same fix. Keeping the Enderman trail while deliberately retaining destination-only particles for players and foxes would instead require additional entity-specific exceptions.

Therefore, restoring MC-260379 does not necessarily constitute adding a new feature. The shared code path, the lack of an original entity-specific distinction, and the results of a working common fix provide technical grounds to reconsider its previous classification as a feature request.

When chorus fruit was introduced, it directly called the shared EntityLivingBase teleportation method, which already generated 128 portal particles interpolated from the original position to the destination.

Chorus fruit has used the shared LivingEntity teleport method since its introduction in 1.9, where the same method already contained the 128-particle teleport trail.
In 19w14a, MC-10369 moved this existing trail from server-side particle spawning to client-side entity event 46 rather than introducing a new visual effect.
Foxes introduced in the same 1.14 era also use chorus fruit through this shared path, making an intentional player-only exclusion inconsistent with the implementation.