Particles emitted from dragon egg when teleporting are not pointing in the correct direction
The Bug
When you cause a dragon egg to teleport (such as by clicking on it), the teleportation particles point in a random direction and not to the actual location of the dragon egg.
Steps to Reproduce
- Give yourself a dragon egg and place it down.
/give @s minecraft:dragon_egg
- Interact with the dragon egg, (right-click by default) to make it teleport.
- Take note of the particles produced upon doing this and what direction they're pointing in.
- Locate where the dragon egg is and check whether the particles pointed in the correct direction.
Observed Behavior
Particles produced from a dragon egg upon interacting with it don't point in the direction of where the egg was teleported to.
Expected Behavior
Particles produced from a dragon egg upon interacting with it would point in the direction of where the egg was teleported to.
Code Analysis
Code analysis by Marcono1234 can be found in this comment, and code analysis by Ismael Rosillo can be found in this comment.
Linked Issues
is duplicated by5
MC-44656ender egg particles not pointing where they mustDuplicateMC-84535Dragon Egg particles don't go in the direction of the egg itselfDuplicateMC-132232dragon egg teleports not in the same place that the line of particles showsDuplicateMC-166964Dragon egg disappearsDuplicateMC-168966the dragon egg particals do not line up with the dragon egg when it teleportsDuplicaterelates to7
MC-114217Lightning strikes are randomized server and client side resulting in too short or too long lightning strikes client sideConfirmedMC-258347Enderman's teleport no longer creates an extra trail of particles
NormalMC-160Dragon egg particles are missingFixedMC-248666Particles produced from dragon eggs teleporting cannot be seen by other playersNormalMC-84517Chorus fruit particles not showing in correct positionFixedMC-260379Teleport with chorus fruit does not create an extra trail of particlesInvalidMC-2663Enderman particles bug orientationIncomplete
![[Mod] Avoma](../../../data/avatars/users/86198.png){kind=small}
- Unresolved
![[Mod] Sonicwave](../../../data/avatars/users/94627.png)
[Mod] Sonicwave
Jose Angel Guzman Moreno- 88
- 29
- Confirmed
Low- Gameplay
- Particles
- 12w18a dragon_egg
1.4.2 - 1.21.4
1.4.2 1.4.7 13w05b 1.5 1.7.4 14w03b 14w34d 1.8 1.8.1-pre2 1.8.1-pre5 15w31c 15w49b 1.9 1.9.1-pre1 1.9.1-pre2 1.9.1-pre3 1.10.2 16w32a 16w32b 16w33a 16w35a 1.11.2 17w06a 17w17b 1.12-pre6 1.12 1.12.1 1.12.2 17w43a 17w45b 17w46a 17w47a 17w47b 17w48a 17w50a 18w01a 18w02a 18w03b 18w05a 18w06a 18w08b 18w11a 18w16a 18w21a 1.13-pre1 1.13-pre5 1.13-pre6 1.13-pre7 1.13-pre8 1.13-pre10 1.13 18w31a 1.13.1 1.13.2 18w48a 18w48b 18w49a 18w50a 19w02a 19w03a 19w03b 19w03c 19w04a 19w04b 19w05a 19w06a 19w07a 19w08b 19w09a 19w11a 19w11b 19w12a 19w12b 19w13a 19w13b 19w14a 19w14b 1.14-pre1 1.14-pre2 1.14-pre3 1.14-pre4 1.14-pre5 1.14 1.14.1-pre2 1.14.1 1.14.2 1.14.3-pre1 1.14.3-pre2 1.14.3-pre3 1.14.3-pre4 1.14.3 1.14.4-pre1 1.14.4-pre2 1.14.4-pre3 1.14.4-pre4 1.14.4-pre5 1.14.4-pre6 1.14.4-pre7 1.14.4 19w34a 19w35a 19w37a 19w38b 19w38a 19w39a 19w40a 19w41a 19w42a 19w44a 19w45a 19w45b 19w46a 19w46b 1.15-pre1 1.15-pre2 1.15-pre3 1.15-pre4 1.15-pre5 1.15-pre7 1.15 1.15.1 1.15.1-pre1 1.15.2-pre1 1.15.2-pre2 1.15.2 20w06a 20w07a 20w08a 20w09a 20w10a 20w11a 20w12a 20w13a 20w13b 20w14a 20w15a 20w16a 20w17a 20w18a 20w19a 20w20b 20w21a 20w22a 1.16-pre1 1.16-pre2 1.16-pre3 1.16-pre4 1.16-pre5 1.16-pre6 1.16-pre7 1.16-pre8 1.16-rc1 1.16 1.16.1 20w27a 20w28a 20w29a 20w30a 1.16.2-pre1 1.16.2-pre2 1.16.2-pre3 1.16.2-rc1 1.16.2-rc2 1.16.2 1.16.3-rc1 1.16.3 1.16.4-pre1 1.16.4-pre2 1.16.4-rc1 1.16.4 20w45a 20w46a 20w48a 20w49a 20w51a 21w03a 1.16.5 21w05a 21w05b 21w06a 21w07a 21w08b 21w10a 21w11a 21w13a 21w14a 21w15a 21w16a 21w17a 21w18a 21w19a 21w20a 1.17-pre2 1.17-rc2 1.17 1.17.1-rc1 1.17.1 21w37a 21w39a 21w40a 21w42a 21w44a 1.18-pre4 1.18-rc3 1.18 1.18.1-rc1 1.18.1 22w07a 1.18.2 22w12a 1.19-pre1 1.19 22w24a 1.19.1 1.19.2 22w43a 1.19.3 23w05a 23w06a 1.19.4-pre3 1.19.4 23w14a 23w17a 1.20-rc1 1.20 1.20.1 23w31a 1.20.2 23w40a 23w43a 1.20.3-pre2 1.20.4 24w12a 24w21b 1.21-rc1 1.21 24w33a 1.21.1 24w44a 1.21.4-pre1 1.21.4
Created Issue:
The Dragon's has a bug when you hit the egg particles out to the side and the egg to another
The Dragon's has a bug when you hit the egg particles out to the side and the egg to another
Environment
fu
relates to
![[Mod] Ezekiel (ezfe)](../../../data/assets/gravatar/ezekielelin.jpeg){kind=small}
is duplicated by
![[Mod] CubeTheThird](../../../data/assets/gravatar/cubethethird.jpeg){kind=small}
is duplicated by
relates to
The Dragon's has a bug when you hit the egg particles out to the side and the egg to another
![[Mod] Michael Wobst](../../../data/avatars/users/37868.png){kind=small}
The Dragon's has a bug when you hit the egg particles out to the side and the egg to another
The Dragon's has a bug when you hit the egg particles out to the side and the egg to another
Code analysis by Marcono1234 can be found in this comment.
TheDragon's has a bug when you hit the egg particles out to the side and the egg to another
Code analysis by Marcono1234 can be found in this comment.
When you cause a dragon egg to teleport by clicking on
Code analysis by Marcono1234 can be found in this comment.
The following is based on decompiled version of Minecraft 1.9 using MCP 9.24 beta. All method and class names are the names used in the decompiled version.
The reason why this happens is probably the fix of
MC-160. That bug probably occurred due to the problem described inMC-10369. I assume at this point the method creating the particles was changed to create the particles client side only. The problem is that the net.minecraft.block.BlockDragonEgg.teleport(World, BlockPos) method which is responsible for this is called by client and server. The client uses it for creating the particles, the server for setting the dragon egg. Both call the method java.util.Random.nextInt(int) which returns different coordinates for the client and the server.
This could be solved by having the server creating the particles.
When you cause a dragon egg to teleport by clicking on
Code analysis by Marcono1234 can be found in this comment.
The following is based on decompiled version of Minecraft 1.9 using MCP 9.24 beta. All method and class names are the names used in the decompiled version.
The reason why this happens is probably the fix of
MC-160. That bug probably occurred due to the problem described inMC-10369. I assume at this point the method creating the particles was changed to create the particles client side only. The problem is that the net.minecraft.block.BlockDragonEgg.teleport(World, BlockPos) method which is responsible for this is called by client and server. The client uses it for creating the particles, the server for setting the dragon egg. Both call the method java.util.Random.nextInt(int) which returns different coordinates for the client and the server.
This could be solved by having the server creating the particles.When you cause a dragon egg to teleport (such as by clicking on it), the teleportation particles point in a random direction and not to the actual location of the dragon egg.
Code analysis by Marcono1234 can be found in this comment.
The following is based on decompiled version of Minecraft 1.9 using MCP 9.24 beta. All method and class names are the names used in the decompiled version.
The reason why this happens is probably the fix of
MC-160. That bug probably occurred due to the problem described inMC-10369. I assume at this point the method creating the particles was changed to create the particles client side only. The problem is that the net.minecraft.block.BlockDragonEgg.teleport(World, BlockPos) method which is responsible for this is called by client and server. The client uses it for creating the particles, the server for setting the dragon egg. Both call the method java.util.Random.nextInt(int) which returns different coordinates for the client and the server.
This could be solved by having the server creating the particles.
![[Mod] Les3awe](../../../data/avatars/users/79847.png){kind=small}
When you cause a dragon egg to teleport (such as by clicking on it), the teleportation particles point in a random direction and not to the actual location of the dragon egg.
Code analysis by Marcono1234 can be found in this comment.
The following is based on decompiled version of Minecraft 1.9 using MCP 9.24 beta. All method and class names are the names used in the decompiled version.
The reason why this happens is probably the fix of
MC-160. That bug probably occurred due to the problem described inMC-10369. I assume at this point the method creating the particles was changed to create the particles client side only. The problem is that the net.minecraft.block.BlockDragonEgg.teleport(World, BlockPos) method which is responsible for this is called by client and server. The client uses it for creating the particles, the server for setting the dragon egg. Both call the method java.util.Random.nextInt(int) which returns different coordinates for the client and the server.
This could be solved by having the server creating the particles.The bug
When you cause a dragon egg to teleport (such as by clicking on it), the teleportation particles point in a random direction and not to the actual location of the dragon egg.
Code analysis
Code analysis by Marcono1234 can be found in this comment.
![[Mod] tryashtar](../../../data/avatars/users/41963.png){kind=small}
![[Mod] Neko](../../../data/avatars/users/92901.png){kind=small}
is duplicated by
![[Mod] NeunEinser](../../../data/avatars/users/39263.png){kind=small}
Particles emitted fromDragonEgg when teleporting are not pointing in the correct direction.Particles emitted from dragon egg when teleporting are not pointing in the correct direction
![[Mod] Urielsalis](../../../data/assets/gravatar/urielsalis.jpeg){kind=small}
![[Mod] violine1101](../../../data/avatars/users/92858.png){kind=small}
![[Mojang] Nathan Adams](../../../data/assets/gravatar/dinnerbone.png){kind=small}
![[Helper] Jack McKalling](../../../data/avatars/users/92859.png){kind=small}
is duplicated by
is duplicated by
![[Mod] SPGoding](../../../data/avatars/users/44622.png){kind=small}
![[Mod] Chandler](../../../data/assets/gravatar/triwonder81.png){kind=small}
![[Mod] Jarl-Penguin](../../../data/avatars/users/92849.png){kind=small}
![[Mojang] Adrian Östergård](../../../data/assets/gravatar/nighter.jpeg){kind=small}
Low![[Helper] Johnibur](../../../data/avatars/users/28381.png){kind=small}
[Mojang] Adrian Östergård Why is this intended? A comment would be helpful. This is not only inconsistent with e.g. endermen, I also fail to see any point in those particles if they don't actually point in the right direction.
![[Mojang] slicedlime](../../../data/assets/gravatar/slicedlime.jpeg){kind=small}
relates to
[Mod] Chandler wants to marry [Mod] LateLag
DrownedZombie wants to marry Fabian Röling
[~Awesoman3000] wants to marry [Mojang] Adrian Östergård
[Mod] markderickson wants to marry [Mod] Anthony Cicinelli
[Mod] violine1101 wants to marry Dmitry Konev
Galaxy_2Alex wants to marry bugsbugsbugs
[Mod] Avoma wants to marry SlicedBlock
[Mojang] slicedlime wants to marry [Mod] SPGoding
W_V wants to marry [Mod] EVGENSYPERPRO
[Mod] tryashtar wants to marry [Mod] Neko
[Helper] Jack McKalling wants to marry [Mod] redstonehelper
[Mod] Sonicwave wants to marry [Mod] Ezekiel (ezfe).
Duplicate of MC-2157
Duplicate of MC-2157.
Confirmed; relates to MC-2157.
Thank you for your report!
We're actually already tracking this issue in MC-2157, so I resolved and linked 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 in the future to see if the issue has already been reported.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – 📖 Game Wiki
particles are not connected to the actual movement tho (MC-2157)
but i guess it being possible to tp there confirms it
HubbiGamingTV Could you please not go through tons of tickets, making either obvious/redundant (MC-201, MC-1531, MC-3266, MC-1673, …) or incorrect (MC-180, MC-212, MC-2157, MC-2112, MC-2791, MC-1297, …) statements? I got lots of mails from your comments over night, followed by a bunch of mails of people correcting you. Please only contribute if you actually have new and relevant information, not baseless speculation. Also, if you want go through all currently open bugs, prepare some meals first, because you'll need a really long time for 8375 reports…
The Bug
When the player eats the chorus fruit and teleports, particles do not spawn from the old location to the new location, instead particles only appear at the new location.
I think it relates to MC-2157,MC-102881,MC-185017, and MC-258347.
Steps to reproduce
1. eat chorus fruit
2. check where particles appear
Expected behavior
Particles appear from the player's old location to the new location.(like the last image of MC-10369)
P.S.
This could also be a form of potential fix for MC-185017.
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.
Please clarify. What exactly is the bug here?
When you hit a placed dragons egg and it teleports, the particles emitted often do not lead in the direction the egg moved. Nor away from. In fact, it seems a little inconsistent overall, and it would be good to have them pointing in the direction of travel.
After hitting the egg directly underneath me, the attached screenshot was the result.
Confirmed in 13w05b
Is this still a concern in the current Minecraft version 1.6.4 / Launcher version 1.2.5 ? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases.
Confirmed in 1.7.4
Confirmed for 14w32d
Confirmed in 1.8.
Confirmed for 1.8.1-pre2.
Confirmed for 1.8.1-pre5.
MC-84535confirms for 15w31c.Confirmed for 15w49b
Confirmed for
Please link to this comment in the description
The following is based on decompiled version of Minecraft 1.9 using MCP 9.24 beta. All method and class names are the names used in the decompiled version.
The reason why this happens is probably the fix of
MC-160. That bug probably occurred due to the problem described inMC-10369. I assume at this point the method creating the particles was changed to create the particles client side only. The problem is that the net.minecraft.block.BlockDragonEgg.teleport(World, BlockPos) method which is responsible for this is called by client and server. The client uses it for creating the particles, the server for setting the dragon egg. Both call the method java.util.Random.nextInt(int) which returns different coordinates for the client and the server.This could be solved by having the server creating the particles.
Confirmed for 1.10.2
Is already marked as affected...
Confirmed for 16w32b
EDIT: oh lol i didn't see your comment until after i said confirmed for 16w32b
I wonder if there are plans to fix this for 1.11?
Also marked as affected...
Yes I know. If I had seen your comment earlier I wouldn't have also said confirmed for "16w32b".
Confirmed for 17w17b
Confirmed for 1.12-pre6
Confirmed for 1.12.
Ticket is yours now, [~ericz1]
Confirmed for 1.12.2
Is already marked as affected.
After receiving six mails because of this, I want to make it clear: hzmi, please check the affected version list at the top of the report before submitting such a comment, you're sending multiple mails with each of those comments, in total about 100 mails were just caused by you and FVBico. Even though it might look like it, the comments are not the place to keep track of the versions.
Can confirm in 1.13-pre5.
Please keep the affected versions up-to-date.
can reproduce in 1.13-pre6
can reproduce in 1.13-pre7
can reproduce in 1.13-pre8
can reproduce in 1.13-pre10
Confirmed for 1.13.1.
Confirmed for 18w49a
Confirmed for 18w50a
Confirmed for 19w02a
Confirmed for 19w03a
Confirmed for 19w03b
Confirmed for 19w03c
Comfirmed for 19w04a
Confirmed for 19w04b and 19w05a
Confirmed for 19w06a
Confirmed for 19w07a
Confirmed for 19w09a
Confirmed for 19w11a
Confirmed for 19w11b
Confirmed for 19w12a
Confirmed for 19w12b
Confirmed for 19w13a
Confirmed for 19w13b
Confirmed for 19w14a
Confirmed for 19w14b
Confirmed for 1.14 pre-1
Confirmed for 1.14 pre-2
Confirmed for 1.14 pre-3
Confirmed for 1.14 pre-4
Confirmed for 1.14 pre-5
Confirmed for 1.14
Confirmed for 1.14.1 pre-1
Confirmed for 1.14.1 pre-2
Confirmed for 1.14.1
Confirmed in 19w45b.
Confirmed in 1.16-pre3.
Confirmed in 1.16-pre5.
Confirmed in 1.16-pre6.
Confirmed in 1.16-pre7.
Can confirm in 20w48a.
Can confirm in 21w05a.
Can confirm in 21w05b.
Attached a vidoe showing how it used to work in 1.2.5, MC-2157 How it used to work in 1.2.5.mp4
Can confirm in 1.17.1 Release Candidate 1.
Can confirm in 21w37a.
I am able to confirm this behavior in 21w39a. Here are some extra details regarding this issue.
The Bug:
Particles produced from a dragon egg upon interacting with it don't point in the direction of where the egg was teleported to.
Steps to Reproduce:
Observed Behavior:
Particles produced from a dragon egg upon interacting with it don't point in the direction of where the egg was teleported to.
Expected Behavior:
Particles produced from a dragon egg upon interacting with it would point in the direction of where the egg was teleported to.
Can confirm in 21w40a.
Can confirm in 21w42a.
Can confirm in 21w44a.
Affects 1.18-pre4.
Can confirm in 1.18.1.
Can confirm in 1.18.2.
Can confirm in 1.19 prerelease-1
Can confirm in 1.19.
Can confirm in 1.19.1.
Can confirm in 1.19.2.
Can confirm in 23w05a
Can confirm in 23w06a
Can confirm in 1.20.2 and 1.20.3 Pre-release 2. Regarding the proposed fix by ~marcono1234, there's a problem which makes it unviable, as it creates way too many single particles, and each one is sent by the server to every player (client) near the egg, which definitely would lag the server.
So the rest of this comment will adress an alternate fix, which has been already tested on my modified client and seems to work fine without creating lag. Here it is:
The concept of this fix is to basically let server tell the client that it has to create various teleport particles from one position to another. For this we are going to take advantage of the LevelEvent feature, which consists of sending packet ClientBoundLevelEventPacket from server to client (so now we are reducing from hundreds of packets to a single one), but since not everything is perfect, I had to modify level event's integer "data" parameter to use a long number, since we want to store the destination position on the packet witout altering this feature's behaviour (this is why I'm not suggesting to add another BlockPos parameter to the packet, because otherwise it would break this feature for any other part of the game using it and would add more weight), so now we can use the got destination position's BlockPos.asLong() directly at BlockDragonEgg.teleport(BlockState, Level, BlockPos) and through "LevelEvent" the client will handle the teleport particles correctly at LevelRenderer.levelEvent(int, BlockPos, int).
Code attachment depicting the classes I changed (excluding all LevelEvent methods' changes to "data" parameter, from integer numbers to long ones). From decompiled minecraft 1.19.3 by MCP Reborn using official mapping and my own parameter names.
Also, in these examples I assigned "1999" as the id of this level event type I added (also present in net.minecraft.level.block.LevelEvent.DRAGON_EGG_TELEPORT).
In short, instead of creating the particles by the server like Marcono said, we are making the client create them to reduce packet usage, while also fixing this bug.