FelixR
- FelixR
- JIRAUSER779937
- Europe/Stockholm
- Yes
- No
MC-274023
As a result of MC-272122 , the main menu panorama for 1.21 is missing a ladder at the bottom of the left ladder shown within the room. The screenshots show the main menu panorama with the missing ladder, with one screenshot edited to circle the location of the missing ladder.
Edit: I have seen Moesh's comment on
MC-266441stating that missing ladders and some other missing blocks are deliberate and intended for the player to replace, so I think this is likely Working As Intended.
As a result of MC-272122, the main menu panorama for 1.21 is missing a ladder at the bottom of the left ladder shown within the room. The screenshots show the main menu panorama with the missing ladder, with one screenshot edited to circle the location of the missing ladder.
Edit: I have seen Moesh's comment on
MC-266441stating that missing ladders and some other missing blocks are deliberate and intended for the player to replace, so I think this is likely Working As Intended.
As a result of MC-272122, the main menu panorama for 1.21 is missing a ladder at the bottom of the left ladder shown within the room. The screenshots show the main menu panorama with the missing ladder, with one screenshot edited to circle the location of the missing ladder.
Edit: I have now seen Moesh's comment on
MC-266441stating that missing ladders and some other missing blocks are deliberate and intended for the player to replace, so I think this is likely Working As Intended.
As a result of MC-272122, the main menu panorama for 1.21 is missing a ladder at the bottom of the left ladder shown within the room. The screenshots show the main menu panorama with the missing ladder, with one screenshot edited to circle the location of the missing ladder.
Edit: I have now seen Moesh's comment on
MC-266441stating that missing ladders and some other missing blocks are deliberate and intended for the player to replace, soI think this is likely Working As Intended.As a result of MC-272122, the main menu panorama for 1.21 is missing a ladder at the bottom of the left ladder shown within the room. The screenshots show the main menu panorama with the missing ladder, with one screenshot edited to circle the location of the missing ladder.
Edit: I have now seen Moesh's comment on
MC-266441stating that missing ladders and some other missing blocks are deliberate and intended for the player to replace and because of this I think this is likely Working As Intended.
As a result of MC-272122, the main menu panorama for 1.21 is missing a ladder at the bottom of the left ladder shown within the room. The screenshots show the main menu panorama with the missing ladder, with one screenshot edited to circle the location of the missing ladder.
Edit: I have now seen Moesh's comment on
MC-266441stating that missing ladders and some other missing blocks are deliberate and intended for the player to replaceand because ofthis I think this is likely Working As Intended.As a result of MC-272122, the main menu panorama for 1.21 is missing a ladder at the bottom of the left ladder shown within the room. The screenshots show the main menu panorama with the missing ladder, with one screenshot edited to circle the location of the missing ladder.
Edit: I have now seen Moesh's comment on
MC-266441stating that missing ladders and some other missing blocks are deliberate and intended for the player to replace. Due to this, I think this is likely Working As Intended.
As a result of MC-272122, the main menu panorama for 1.21 is missing a ladder at the bottom of the left ladder shown within the room. The screenshots show the main menu panorama with the missing ladder, with one screenshot edited to circle the location of the missing ladder.
Edit: I have now seen Moesh's comment on
MC-266441stating that missing ladders and some other missing blocks are deliberate and intended for the player to replace. Due to this, I think this is likely Working As Intended.
As a result of MC-272122, the main menu panorama for 1.21 is missing a ladder at the bottom of the left ladder shown within the room. The screenshots show the main menu panorama with the missing ladder, with one screenshot edited to circle the location of the missing ladder.
Edit: I have now seen Moesh's comment on
MC-266441stating that missing ladders and some other missing blocks are deliberate and intended for the player to replace.Due to this, I think this is likely Working As Intended.As a result of MC-272122, the main menu panorama for 1.21 is missing a ladder at the bottom of the left ladder shown within the room. The screenshots show the main menu panorama with the missing ladder, with one screenshot edited to circle the location of the missing ladder.
Edit: I have now seen Moesh's comment on
MC-266441stating that missing ladders and some other missing blocks are deliberate and intended for the player to replace. Therefore, I think this is likely Working As Intended.
Using the "execute in..." command to exit the End while the ender dragon is still alive causes the" Ender Dragon" health bar to briefly remain displaying after returning tothe OverworldUsing the "execute in..." command to exit the End while the ender dragon is still alive causes the" Ender Dragon" health bar to briefly reappear in the Overworld
When using the command "/execute in minecraft:overworld run tp [player] ~ ~ ~" to exit the End while the ender dragon is still alive, the "Ender Dragon" health bar displays for a split second after teleporting to the
overworld on most occasions. It does not display in the loading screen. Although it affects both specified versions, it appears to occur with much more consistency in 1.21 Pre-Release 3 than in 1.20.6.Steps to Reproduce:
1. Place yourself in the End via a method of your choice, whether it be via portal or a "/execute" command.2. Use the command "/execute in minecraft:overworld run tp [player] ~ ~ ~" to teleport yourself back to the overworld while the ender dragon is still alive.
3. Observe that the ender dragon's health bar may reappear in the overworld for a split second after the loading screen has disappeared. Note that it is not visible in the loading screen itself.
Note that it may take multiple attempts to observe this bug.
When using the command "/execute in minecraft:overworld run tp [player] ~ ~ ~" to exit the End while the ender dragon is still alive, the "Ender Dragon" health bar displays for a split second after teleporting to the Overworld on most occasions. It does not display in the loading screen. Although it affects both specified versions, it appears to occur with much more consistency in 1.21 Pre-Release 3 than in 1.20.6.
Steps to Reproduce:
1. Place yourself in the End via a method of your choice, whether it be via portal or a "/execute" command.2. Use the command "/execute in minecraft:overworld run tp [player] ~ ~ ~" to teleport yourself back to the overworld while the ender dragon is still alive.
3. Observe that the ender dragon's health bar may reappear in the overworld for a split second after the loading screen has disappeared. Note that it is not visible in the loading screen itself.
Note that it may take multiple attempts to observe this bug.
When using the command "/execute in minecraft:overworld run tp [player] ~ ~ ~" to exit the End while the ender dragon is still alive, the "Ender Dragon" health bar displays for a split second after teleporting to the Overworld on most occasions. It does not display in the loading screen. Although it affects both specified versions, it appears to occur with much more consistency in 1.21 Pre-Release 3 than in 1.20.6.
Steps to Reproduce:
1. Place yourself in the End via a method of your choice, whether it be via portal ora"/execute" command.2. Use the command "/execute in minecraft:overworld run tp [player] ~ ~ ~" to teleport yourself back to the overworld while the ender dragon is still alive.
3. Observe that the ender dragon's health bar may reappear in the overworld for a split second after the loading screen has disappeared. Note that it is not visible in the loading screen itself.
Note that it may take multiple attempts to observe this bug.
When using the command "/execute in minecraft:overworld run tp [player] ~ ~ ~" to exit the End while the ender dragon is still alive, the "Ender Dragon" health bar displays for a split second after teleporting to the Overworld on most occasions. It does not display in the loading screen. Although it affects both specified versions, it appears to occur with much more consistency in 1.21 Pre-Release 3 than in 1.20.6.
Steps to Reproduce:
1. Place yourself in the End via a method of your choice, whether it be via portal or the "/execute" command.2. Use the command "/execute in minecraft:overworld run tp [player] ~ ~ ~" to teleport yourself back to the overworld while the ender dragon is still alive.
3. Observe that the ender dragon's health bar may reappear in the overworld for a split second after the loading screen has disappeared. Note that it is not visible in the loading screen itself.
Note that it may take multiple attempts to observe this bug.
When using the command "/execute in minecraft:overworld run tp [player] ~ ~ ~" to exit the End while the ender dragon is still alive, the "Ender Dragon" health bar displays for a split second after teleporting to the Overworld on most occasions. It does not display in the loading screen. Although it affects both specified versions, it appears to occur with much more consistency in 1.21 Pre-Release 3 than in 1.20.6.
Steps to Reproduce:
1. Place yourself in the End via a method of your choice, whether it be via portal or the "/execute" command.2. Use the command "/execute in minecraft:overworld run tp [player] ~ ~ ~" to teleport yourself back to the overworld while the ender dragon is still alive.
3. Observe that the ender dragon's health bar may reappear in the overworld for a split second after the loading screen has disappeared. Note that it is not visible in the loading screen itself.
Note that it may take multiple attempts to observe this bug.When using the command "/execute in minecraft:overworld run tp [player] ~ ~ ~" to exit the End while the ender dragon is still alive, the "Ender Dragon" health bar displays for a split second after teleporting to the Overworld on most occasions. It does not display in the loading screen. Although it affects both specified versions, it appears to occur with much more consistency in 1.21 Pre-Release 3 than in 1.20.6.
Steps to Reproduce:
1. Place yourself in the End via a method of your choice, whether it be via portal or the "/execute" command.2. Use the command "/execute in minecraft:overworld run tp [player] ~ ~ ~" to teleport yourself back to the overworld while the ender dragon is still alive.
3. Observe that the ender dragon's health bar may reappear in the overworld for a split second after the loading screen has disappeared. Note that it is not visible in the loading screen itself.
It may take multiple attempts to observe this bug.
When using the command "/execute in minecraft:overworld run tp [player] ~ ~ ~" to exit the End while the ender dragon is still alive, the "Ender Dragon" health bar displays for a split second after teleporting to the Overworld on most occasions. It does not display in the loading screen. Although it affects both specified versions, it appears to occur with much more consistency in 1.21 Pre-Release 3 than in 1.20.6.
Steps to Reproduce:
1. Place yourself in the End via a method of your choice, whether it be via portal or the "/execute" command.2. Use the command "/execute in minecraft:overworld run tp [player] ~ ~ ~" to teleport yourself back to the overworld while the ender dragon is still alive.
3. Observe that the ender dragon's health bar may reappear in the overworld for a split second after the loading screen has disappeared. Note that it is not visible in the loading screen itself.
It may take multiple attempts to observe this bug as it does not occur 100% of the time.
When using the command "/execute in minecraft:overworld run tp [player] ~ ~ ~" to exit the End while the ender dragon is still alive, the "Ender Dragon" health bar displays for a split second after teleporting to the Overworld on most occasions. It does not display in the loading screen. Although it affects both specified versions, it appears to occur with much more consistency in 1.21 Pre-Release 3 than in 1.20.6.
It also affects 1.21 Pre-Release 1, where the health bar seems to appear for fractionally longer in the Overworld.
Steps to Reproduce:
1. Place yourself in the End via a method of your choice, whether it be via portal or the "/execute" command.2. Use the command "/execute in minecraft:overworld run tp [player] ~ ~ ~" to teleport yourself back to the overworld while the ender dragon is still alive.
3. Observe that the ender dragon's health bar may reappear in the overworld for a split second after the loading screen has disappeared. Note that it is not visible in the loading screen itself.
It may take multiple attempts to observe this bug as it does not occur 100% of the time.
When using the command "/execute in minecraft:overworld run tp [player] ~ ~ ~" to exit the End while the ender dragon is still alive, the "Ender Dragon" health bar displays for a split second after teleporting to the Overworld on most occasions. It does not display in the loading screen. Although it affects both specified versions, it appears to occur with much more consistency in 1.21 Pre-Release 3 than in 1.20.6.
It also affects 1.21 Pre-Release 1 and 1.21 Pre-Release 2, where the health bar seems to appear for fractionally longer in the Overworld in both versions.
Steps to Reproduce:
1. Place yourself in the End via a method of your choice, whether it be via portal or the "/execute" command.2. Use the command "/execute in minecraft:overworld run tp [player] ~ ~ ~" to teleport yourself back to the overworld while the ender dragon is still alive.
3. Observe that the ender dragon's health bar may reappear in the overworld for a split second after the loading screen has disappeared. Note that it is not visible in the loading screen itself.
It may take multiple attempts to observe this bug as it does not occur 100% of the time.
Using the "execute in..." command to exit the End while the ender dragon is still alive causes the" Ender Dragon" health bar to briefly reappear in the Overworld and Nether
When using the command "/execute in minecraft:overworld run tp [player] ~ ~ ~" to exit the End while the ender dragon is still alive, the "Ender Dragon" health bar displays for a split second after teleporting to the Overworld on most occasions.
It does not displayin theloading screen. Although it affects both specified versions, it appears to occur with much more consistency in 1.21 Pre-Release 3 than in 1.20.6.It also affects 1.21 Pre-Release 1 and 1.21 Pre-Release 2, where the health bar seems to appear for fractionally longer in the Overworld in both versions.
Steps to Reproduce:
1. Place yourself in the End via a method of your choice, whether it be via portal or the "/execute" command.2. Use the command "/execute in minecraft:overworld run tp [player] ~ ~ ~" to teleport yourself back to the overworld while the ender dragon is still alive.
3. Observe that the ender dragon's health bar may reappear in the overworld for a split second after the loading screen has disappeared. Note that it is not visible in the loading screen itself.
It may take multiple attempts to observe this bug as it does not occur 100% of the time.
When using the command "/execute in minecraft:overworld run tp [player] ~ ~ ~" to exit the End while the ender dragon is still alive, the "Ender Dragon" health bar displays for a split second after teleporting to the Overworld on most occasions. The same occurs if using the command to teleport directly to the Nether ("/execute in minecraft:netherrun tp [player] ~ ~ ~").It does not display in the loading screen. Although it affects both specified versions, it appears to occur with much more consistency in 1.21 Pre-Release 3 than in 1.20.6.
It also affects 1.21 Pre-Release 1 and 1.21 Pre-Release 2, where the health bar seems to appear for fractionally longer in the Overworld in both versions.
Steps to Reproduce:
1. Place yourself in the End via a method of your choice, whether it be via portal or the "/execute" command.2. Use the command "/execute in minecraft:overworld run tp [player] ~ ~ ~" to teleport yourself back to the overworld while the ender dragon is still alive.
3. Observe that the ender dragon's health bar may reappear in the overworld for a split second after the loading screen has disappeared. Note that it is not visible in the loading screen itself.
It may take multiple attempts to observe this bug as it does not occur 100% of the time.
When using the command "/execute in minecraft:overworld run tp [player] ~ ~ ~" to exit the End while the ender dragon is still alive, the "Ender Dragon" health bar displays for a split second after teleporting to the Overworld on most occasions. The same occurs if using the command to teleport directly to the Nether ("/execute in minecraft:netherrun tp [player] ~ ~ ~").
Itdoes not display in the loading screen. Although it affects both specified versions, it appears to occur with much more consistency in 1.21 Pre-Release 3 than in 1.20.6.It also affects 1.21 Pre-Release 1 and 1.21 Pre-Release 2, where the health bar seems to appear for fractionally longer in the Overworld in both versions.
Steps to Reproduce:
1. Place yourself in the End via a method of your choice, whether it be via portal or the "/execute" command.2. Use the command "/execute in minecraft:overworld run tp [player] ~ ~ ~" to teleport yourself back to the overworld while the ender dragon is still alive.
3. Observe that the ender dragon's health bar may reappear in the overworld for a split second after the loading screen has disappeared. Note that it is not visible in the loading screen itself.
It may take multiple attempts to observe this bug as it does not occur 100% of the time.
When using the command "/execute in minecraft:overworld run tp [player] ~ ~ ~" to exit the End while the ender dragon is still alive, the "Ender Dragon" health bar displays for a split second after teleporting to the Overworld on most occasions. The same occurs if using the command to teleport directly to the Nether ("/execute in minecraft:netherrun tp [player] ~ ~ ~"). The health bar does not display in the loading screen. Although it affects both specified versions, it appears to occur with much more consistency in 1.21 Pre-Release 3 than in 1.20.6.
It also affects 1.21 Pre-Release 1 and 1.21 Pre-Release 2, where the health bar seems to appear for fractionally longer in the Overworld in both versions.
Steps to Reproduce:
1. Place yourself in the End via a method of your choice, whether it be via portal or the "/execute" command.2. Use the command "/execute in minecraft:overworld run tp [player] ~ ~ ~" to teleport yourself back to the overworld while the ender dragon is still alive.
3. Observe that the ender dragon's health bar may reappear in the overworld for a split second after the loading screen has disappeared. Note that it is not visible in the loading screen itself.
It may take multiple attempts to observe this bug as it does not occur 100% of the time.
When using the command "/execute in minecraft:overworld run tp [player] ~ ~ ~" to exit the End while the ender dragon is still alive, the "Ender Dragon" health bar displays for a split second after teleporting to the Overworld on most occasions. The same occurs if using the command to teleport directly to the Nether ("/execute in minecraft:netherrun tp [player] ~ ~ ~"). The health bar does not display in the loading screen. Although
it affects both specified versions, it appears to occur with much more consistency in 1.21 Pre-Release 3 than in 1.20.6.It also affects 1.21 Pre-Release 1 and 1.21 Pre-Release 2, where the health bar seems to appear for fractionally longer in the Overworld in both versions.
Steps to Reproduce:
1. Place yourself in the End via a method of your choice, whether it be via portal or the "/execute" command.2. Use the command "/execute in minecraft:overworld run tp [player] ~ ~ ~" to teleport yourself back to the overworld while the ender dragon is still alive.
3. Observe that the ender dragon's health bar may reappear in the overworld for a split second after the loading screen has disappeared. Note that it is not visible in the loading screen itself.
It may take multiple attempts to observe this bug as it does not occur 100% of the time.
When using the command "/execute in minecraft:overworld run tp [player] ~ ~ ~" to exit the End while the ender dragon is still alive, the "Ender Dragon" health bar displays for a split second after teleporting to the Overworld on most occasions. The same occurs if using the command to teleport directly to the Nether ("/execute in minecraft:netherrun tp [player] ~ ~ ~"). The health bar does not display in the loading screen. Although the bug affects both specified versions, it appears to occur with much more consistency in 1.21 Pre-Release 3 than in 1.20.6.
It also affects 1.21 Pre-Release 1 and 1.21 Pre-Release 2, where the health bar seems to appear for fractionally longer in the Overworld in both versions.
Steps to Reproduce:
1. Place yourself in the End via a method of your choice, whether it be via portal or the "/execute" command.2. Use the command "/execute in minecraft:overworld run tp [player] ~ ~ ~" to teleport yourself back to the overworld while the ender dragon is still alive.
3. Observe that the ender dragon's health bar may reappear in the overworld for a split second after the loading screen has disappeared. Note that it is not visible in the loading screen itself.
It may take multiple attempts to observe this bug as it does not occur 100% of the time.
When using the command "/execute in minecraft:overworld run tp [player] ~ ~ ~" to exit the End while the ender dragon is still alive, the "Ender Dragon" health bar displays for a split second after teleporting to the Overworld on most occasions. The same occurs if using the command to teleport directly to the Nether ("/execute in minecraft:netherrun tp [player] ~ ~ ~"). The health bar does not display in the loading screen. Although the bug affects both specified versions, it appears to occur with much more consistency in 1.21 Pre-Release 3 than in 1.20.6.
It also affects 1.21 Pre-Release 1 and 1.21 Pre-Release 2, where the health bar seems to appear for fractionally longer in the Overworld/Nether in both versions.
Steps to Reproduce:
1. Place yourself in the End via a method of your choice, whether it be via portal or the "/execute" command.2. Use the command "/execute in minecraft:overworld run tp [player] ~ ~ ~" to teleport yourself back to the overworld while the ender dragon is still alive.
3. Observe that the ender dragon's health bar may reappear in the overworld for a split second after the loading screen has disappeared. Note that it is not visible in the loading screen itself.
It may take multiple attempts to observe this bug as it does not occur 100% of the time.
When using the command "/execute in minecraft:overworld run tp [player] ~ ~ ~" to exit the End while the ender dragon is still alive, the "Ender Dragon" health bar displays for a split second after teleporting to the Overworld on most occasions. The same occurs if using the command to teleport directly to the Nether ("/execute in minecraft:nether run tp [player] ~ ~ ~"). The health bar does not display in the loading screen. Although the bug affects both specified versions, it appears to occur with much more consistency in 1.21 Pre-Release 3 than in 1.20.6.
It also affects 1.21 Pre-Release 1 and 1.21 Pre-Release 2, where the health bar seems to appear for fractionally longer in the Overworld/Nether in both versions.
Steps to Reproduce:
1. Place yourself in the End via a method of your choice, whether it be via portal or the "/execute" command.2. Use the command "/execute in minecraft:overworld run tp [player] ~ ~ ~" to teleport yourself back to the overworld while the ender dragon is still alive.
3. Observe that the ender dragon's health bar may reappear in the overworld for a split second after the loading screen has disappeared. Note that it is not visible in the loading screen itself.
It may take multiple attempts to observe this bug as it does not occur 100% of the time. In order to reproduce for the Nether, simply replace "overworld" with "nether" in the specified command in step 2.
When using the command "/execute in minecraft:overworld run tp [player] ~ ~ ~" to exit the End while the ender dragon is still alive, the "Ender Dragon" health bar displays for a split second after teleporting to the Overworld on most occasions. The same occurs if using the command to teleport directly to the Nether ("/execute in minecraft:nether run tp [player] ~ ~ ~"). The health bar does not display in the loading screen. Although the bug affects both specified versions, it appears to occur with much more consistency in 1.21 Pre-Release 3 than in 1.20.6.
It also affects 1.21 Pre-Release 1 and 1.21 Pre-Release 2, where the health bar seems to appear for fractionally longer in the Overworld/Nether in both versions.
Steps to Reproduce:
1. Place yourself in the End via a method of your choice, whether it be via portal or the "/execute" command.2. Use the command "/execute in minecraft:overworld run tp [player] ~ ~ ~" to teleport yourself back to the
overworld while the ender dragon is still alive.3. Observe that the ender dragon's health bar may reappear in the overworld for a split second after the loading screen has disappeared. Note that it is not visible in the loading screen itself.
It may take multiple attempts to observe this bug as it does not occur 100% of the time. In order to reproduce for the Nether, simply replace "overworld" with "nether" in the specified command in step 2.
When using the command "/execute in minecraft:overworld run tp [player] ~ ~ ~" to exit the End while the ender dragon is still alive, the "Ender Dragon" health bar displays for a split second after teleporting to the Overworld on most occasions. The same occurs if using the command to teleport directly to the Nether ("/execute in minecraft:nether run tp [player] ~ ~ ~"). The health bar does not display in the loading screen. Although the bug affects both specified versions, it appears to occur with much more consistency in 1.21 Pre-Release 3 than in 1.20.6.
It also affects 1.21 Pre-Release 1 and 1.21 Pre-Release 2, where the health bar seems to appear for fractionally longer in the Overworld/Nether in both versions.
Steps to Reproduce:
1. Place yourself in the End via a method of your choice, whether it be via portal or the "/execute" command.2. Use the command "/execute in minecraft:overworld run tp [player] ~ ~ ~" to teleport yourself back to the Overworld while the ender dragon is still alive.
3. Observe that the ender dragon's health bar may reappear in the overworld for a split second after the loading screen has disappeared. Note that it is not visible in the loading screen itself.
It may take multiple attempts to observe this bug as it does not occur 100% of the time. In order to reproduce for the Nether, simply replace "overworld" with "nether" in the specified command in step 2.
When using the command "/execute in minecraft:overworld run tp [player] ~ ~ ~" to exit the End while the ender dragon is still alive, the "Ender Dragon" health bar displays for a split second after teleporting to the Overworld on most occasions. The same occurs if using the command to teleport directly to the Nether ("/execute in minecraft:nether run tp [player] ~ ~ ~"). The health bar does not display in the loading screen. Although the bug affects both specified versions, it appears to occur with much more consistency in 1.21 Pre-Release 3 than in 1.20.6.
It also affects 1.21 Pre-Release
1 and 1.21 Pre-Release 2, where the health bar seems to appear for fractionally longer in the Overworld/Nether in both versions.Steps to Reproduce:
1. Place yourself in the End via a method of your choice, whether it be via portal or the "/execute" command.2. Use the command "/execute in minecraft:overworld run tp [player] ~ ~ ~" to teleport yourself back to the Overworld while the ender dragon is still alive.
3. Observe that the ender dragon's health bar may reappear in the overworld for a split second after the loading screen has disappeared. Note that it is not visible in the loading screen itself.
It may take multiple attempts to observe this bug as it does not occur 100% of the time. In order to reproduce for the Nether, simply replace "overworld" with "nether" in the specified command in step 2.
When using the command "/execute in minecraft:overworld run tp [player] ~ ~ ~" to exit the End while the ender dragon is still alive, the "Ender Dragon" health bar displays for a split second after teleporting to the Overworld on most occasions. The same occurs if using the command to teleport directly to the Nether ("/execute in minecraft:nether run tp [player] ~ ~ ~"). The health bar does not display in the loading screen. Although the bug affects both specified versions, it appears to occur with much more consistency in 1.21 Pre-Release 3 than in 1.20.6.
It also affects 1.21 Pre-Release version 1, 2, and 4, where the health bar seems to appear for fractionally longer in the Overworld/Nether in both versions.
Steps to Reproduce:
1. Place yourself in the End via a method of your choice, whether it be via portal or the "/execute" command.2. Use the command "/execute in minecraft:overworld run tp [player] ~ ~ ~" to teleport yourself back to the Overworld while the ender dragon is still alive.
3. Observe that the ender dragon's health bar may reappear in the overworld for a split second after the loading screen has disappeared. Note that it is not visible in the loading screen itself.
It may take multiple attempts to observe this bug as it does not occur 100% of the time. In order to reproduce for the Nether, simply replace "overworld" with "nether" in the specified command in step 2.
When using the command "/execute in minecraft:overworld run tp [player] ~ ~ ~" to exit the End while the ender dragon is still alive, the "Ender Dragon" health bar displays for a split second after teleporting to the Overworld on most occasions. The same occurs if using the command to teleport directly to the Nether ("/execute in minecraft:nether run tp [player] ~ ~ ~"). The health bar does not display in the loading screen. Although the bug affects both specified versions, it appears to occur with much more consistency in 1.21 Pre-Release 3 than in 1.20.6.
It also affects 1.21 Pre-Release versions 1, 2, and 4, where the health bar seems to appear for fractionally longer in the Overworld/Nether in both versions.
Steps to Reproduce:
1. Place yourself in the End via a method of your choice, whether it be via portal or the "/execute" command.2. Use the command "/execute in minecraft:overworld run tp [player] ~ ~ ~" to teleport yourself back to the Overworld while the ender dragon is still alive.
3. Observe that the ender dragon's health bar may reappear in the overworld for a split second after the loading screen has disappeared. Note that it is not visible in the loading screen itself.
It may take multiple attempts to observe this bug as it does not occur 100% of the time. In order to reproduce for the Nether, simply replace "overworld" with "nether" in the specified command in step 2.
Using the command "/execute in minecraft:[dimension] run tp [player] ~ ~ ~" in order to switch dimensions causes the player to fall even when flying in creative mode. This does not affect the 1.21 Pre-Release versions.
Steps to reproduce:
- Make sure the player is flying before proceeding with the following steps.
- Use the command "/execute in minecraft
;[dimension] run tp [player] ~ ~ ~" to teleport the player to another dimension, replacing "[dimension]" with the desired dimension and "[player]" with the player's name.- Observe that the playing falls after completing the teleport command, despite the player flying when the command was executed.
Using the command "/execute in minecraft:[dimension] run tp [player] ~ ~ ~" in order to switch dimensions causes the player to fall even when flying in creative mode. This does not affect the 1.21 Pre-Release versions.
Steps to reproduce:
- Make sure the player is flying before proceeding with the following steps.
- Use the command "/execute in minecraft:[dimension] run tp [player] ~ ~ ~" to teleport the player to another dimension, replacing "[dimension]" with the desired dimension and "[player]" with the player's name.
- Observe that the playing falls after completing the teleport command, despite the player flying when the command was executed.
Using the command "/execute in minecraft:[dimension] run tp [player] ~ ~ ~" in order to switch dimensions causes the player to fall even when flying in creative mode. This does not affect the 1.21 Pre-Release versions.
Steps to reproduce:
- Make sure the player is flying before proceeding with the following steps.
- Use the command "/execute in minecraft:[dimension] run tp [player] ~ ~ ~" to teleport the player to another dimension, replacing "[dimension]" with the desired dimension and "[player]" with the player's name.
- Observe that the playing falls after
completingthe teleportcommand, despite the player flying when the command was executed.Using the command "/execute in minecraft:[dimension] run tp [player] ~ ~ ~" in order to switch dimensions causes the player to fall even when flying in creative mode. This does not affect the 1.21 Pre-Release versions.
Steps to reproduce:
- Make sure the player is flying before proceeding with the following steps.
- Use the command "/execute in minecraft:[dimension] run tp [player] ~ ~ ~" to teleport the player to another dimension, replacing "[dimension]" with the desired dimension and "[player]" with the player's name.
- Observe that the playing falls after the teleport is complete, despite the player flying when the command was executed.
Using "/execuite in..." to switch dimensions causes the play to fall when flying
Using the command "/execute in minecraft:[dimension] run tp [player] ~ ~ ~" in order to switch dimensions causes the player to fall even when flying in creative mode.
This does not affect the 1.21 Pre-Release versions.Steps to reproduce:
- Make sure the player is flying before proceeding with the following steps.
- Use the command "/execute in minecraft:[dimension] run tp [player] ~ ~ ~" to teleport the player to another dimension, replacing "[dimension]" with the desired dimension and "[player]" with the player's name.
- Observe that the playing falls after the teleport is complete, despite the player flying when the command was executed.
Using the command "/execute in minecraft:[dimension] run tp [player] ~ ~ ~" in order to switch dimensions causes the player to fall even when flying in creative mode.
This does not affect the 1.21 Pre-Release versions.
Steps to reproduce:
- Make sure the player is flying before proceeding with the following steps.
- Use the command "/execute in minecraft:[dimension] run tp [player] ~ ~ ~" to teleport the player to another dimension, replacing "[dimension]" with the desired dimension and "[player]" with the player's name.
- Observe that the playing falls after the teleport is complete, despite the player flying when the command was executed.
Using the command "/execute in minecraft:[dimension] run tp [player] ~ ~ ~" in order to switch dimensions causes the player to fall even when flying in creative mode.
This behaviour does not affect the 1.21 Pre-Release versions.
Steps to reproduce:
- Make sure the player is flying before proceeding with the following steps.
- Use the command "/execute in minecraft:[dimension] run tp [player] ~ ~ ~" to teleport the player to another dimension, replacing "[dimension]" with the desired dimension and "[player]" with the player's name.
- Observe that the playing falls after the teleport is complete, despite the player flying when the command was executed.
Using the command "/execute in minecraft:[dimension] run tp [player] ~ ~ ~" in order to switch dimensions causes the player to fall even when flying in creative mode.
This behaviour does not affect the 1.21 Pre-Release versions, only 1.20.6.
Steps to reproduce:
- Make sure the player is flying before proceeding with the following steps.
- Use the command "/execute in minecraft:[dimension] run tp [player] ~ ~ ~" to teleport the player to another dimension, replacing "[dimension]" with the desired dimension and "[player]" with the player's name.
- Observe that the playing falls after the teleport is complete, despite the player flying when the command was executed.
Using the command "/execute in minecraft:[dimension] run tp [player] ~ ~ ~" in order to switch dimensions causes the player to fall even when flying in creative mode.
This behaviour does not affect the 1.21 Pre-Release versions, only 1.20.6 and versions prior.
Steps to reproduce:
- Make sure the player is flying before proceeding with the following steps.
- Use the command "/execute in minecraft:[dimension] run tp [player] ~ ~ ~" to teleport the player to another dimension, replacing "[dimension]" with the desired dimension and "[player]" with the player's name.
- Observe that the playing falls after the teleport is complete, despite the player flying when the command was executed.
On occasion, attempting to use an ender pearl to teleport through an End portal will simply result in the ender pearl passing through the portal as if it were not there, instead teleporting the player when it impacts the ground below the portal. This is particularly noticeable when throwing the pearl directly downwards toward the portal. It also seems to be more likely when using an angle that would result in the ender pearl impacting the side of an end portal frame block.
Steps to reproduce:
- Activate an End portal.
- Throw an ender pearl into the portal.
- Observe that the ender pearl may simply pass through the portal and attempt to teleport the player to the ground below the portal, instead of taking the player directly to the End dimension.
This is more easily observed in creative mode, where this can be tested while flying and will usually cause the player to teleport just above the portal when the ender pearl attempt fails. I have had this occur many times in a row during testing when using an angle that involves throwing the ender pearl directly downwards at the portal. It appears to occur with almost complete consistency when at a distance of approximately 10 or more blocks from the portal, although this aspect could be intentional.
On occasion, attempting to use an ender pearl to teleport through an End portal will simply result in the ender pearl passing through the portal as if it were not there, instead teleporting the player when it impacts the ground below the portal. This is particularly noticeable when throwing the pearl directly downwards toward the portal. It also seems to be more likely when using an angle that would result in the ender pearl impacting the side of an end portal frame block.
Steps to reproduce:
- Activate an End portal.
- Throw an ender pearl into the portal.
- Observe that the ender pearl may simply pass through the portal and attempt to teleport the player to the ground below the portal, instead of taking the player directly to the End dimension.
This is more easily observed in creative mode, where this can be tested while flying and will usually cause the player to teleport just above the portal when the ender pearl attempt fails. I have had this occur many times in a row during testing when using an angle that involves throwing the ender pearl directly downwards at the portal. It appears to occur
with almost complete consistency when at a distance of approximately 10 or more blocks from the portal, although this aspect could be intentional.On occasion, attempting to use an ender pearl to teleport through an End portal will simply result in the ender pearl passing through the portal as if it were not there, instead teleporting the player when it impacts the ground below the portal. This is particularly noticeable when throwing the pearl directly downwards toward the portal. It also seems to be more likely when using an angle that would result in the ender pearl impacting the side of an end portal frame block.
Steps to reproduce:
- Activate an End portal.
- Throw an ender pearl into the portal.
- Observe that the ender pearl may simply pass through the portal and attempt to teleport the player to the ground below the portal, instead of taking the player directly to the End dimension.
This is more easily observed in creative mode, where this can be tested while flying and will usually cause the player to teleport just above the portal when the ender pearl attempt fails. I have had this occur many times in a row during testing when using an angle that involves throwing the ender pearl directly downwards at the portal. It appears to occur more commonly when at a distance of approximately 10 or more blocks from the portal.
2024-06-08_12.36.36.png
When a soul lantern is broken or is in the process of breaking, the particles of the regular lantern are shown. This is recreated simply by placing a soul lantern and breaking it, either in survival mode or creative mode. After some testing, it appears that this bug was introduced in 1.20 and has been present in every release version since.
When a soul lantern is broken or is in the process of breaking, the particles of the regular lantern are shown. This is recreated simply by placing a soul lantern and breaking it, either in survival mode or creative mode. After some testing, it appears that this bug was most recently introduced in 1.20 Pre-Release 1 and has been present in every release version since.
When a soul lantern is broken or is in the process of breaking, the particles of the regular lantern are shown. This is recreated simply by placing a soul lantern and breaking it, either in survival mode or creative mode. After some testing, it appears that this bug was most recently introduced in 1.20 Pre-Release 1 and has been present in every release version since.
When a soul lantern is broken or is in the process of breaking, the particles of the regular lantern are shown. This is recreated simply by placing a soul lantern and breaking it, either in survival mode or creative mode. After some testing, it appears that this bug was most recently introduced in 1.20 Pre-Release 1 and has been present in every release version since and possibly every development version.
When a soul lantern is broken or is in the process of breaking, the particles of the regular lantern are shown. This is recreated simply by placing a soul lantern and breaking it, either in survival mode or creative mode. After some testing, it appears that this bug was most recently introduced in 1.20 Pre-Release 1 and has been present in every release version since and possibly every development version.
Edit: Rather confusingly, I am no longer able to reproduce this bug in the current version.
When a soul lantern is broken or is in the process of breaking, the particles of the regular lantern are shown. This is recreated simply by placing a soul lantern and breaking it, either in survival mode or creative mode. After some testing, it appears that this bug was most recently introduced in 1.20 Pre-Release 1 and has been present in every release version since and possibly every development version.
Edit: Rather confusingly, I am no longer able to reproduce this bug in the current version.
When a soul lantern is broken or is in the process of breaking, the particles of the regular lantern are shown. This is recreated simply by placing a soul lantern and breaking it, either in survival mode or creative mode. After some testing, it appears that this bug was most recently introduced in 1.20 Pre-Release 1 and has been present in every release version since and possibly every development version.
Edit: Rather confusingly, I am no longer able to reproduce this bug in the current version. I am not sure why this is. I was originally running shaders in the world I first encountered the bug in, however it still occurred even with shaders off and when I reopened the same world in vanilla 1.21. Unfortunately I cannot remember if I encountered the bug in a 1.21 world that I did not previously run shaders in.
When a soul lantern is broken or is in the process of breaking, the particles of the regular lantern are shown. This is recreated simply by placing a soul lantern and breaking it, either in survival mode or creative mode. After some testing, it appears that this bug was most recently introduced in 1.20 Pre-Release 1 and has been present in every release version since and possibly every development version.
Edit: Rather confusingly, I am no longer able to reproduce this bug in the current version. I am not sure why this is. I was originally running shaders in the world I first encountered the bug in, however it still occurred even with shaders off and when I reopened the same world in vanilla
1.21. Unfortunately I cannot remember if I encountered the bug in a 1.21 world that I did not previously run shaders in.
When a soul lantern is broken or is in the process of breaking, the particles of the regular lantern are shown. This is recreated simply by placing a soul lantern and breaking it, either in survival mode or creative mode. After some testing, it appears that this bug was most recently introduced in 1.20 Pre-Release 1 and has been present in every release version since and possibly every development version.
Edit: Rather confusingly, I am no longer able to reproduce this bug in the current version. I am not sure why this is. I was originally running shaders in the world I first encountered the bug in, however it still occurred even with shaders off and when I reopened the same world in vanilla. Unfortunately I cannot remember if I encountered the bug in a 1.21 world that I did not previously run shaders in.
When a soul lantern is broken or is in the process of breaking, the particles of the regular lantern are shown. This is recreated simply by placing a soul lantern and breaking it, either in survival mode or creative mode. After some testing, it appears that this bug was most recently introduced in 1.20 Pre-Release 1 and has been present in every release version since and possibly every development version.
Edit: Rather confusingly, I am no longer able to reproduce this bug in the current version. I am not sure why this is. I was originally running shaders in the world I first encountered the bug in, however it still occurred even with shaders off and when I reopened the same world in vanilla. Unfortunately I cannot remember if I encountered the bug in a 1.21 world that I did not previously run shaders in. I have not been able to reproduce the bug by running a world in shaders and then running it in vanilla.
When a soul lantern is broken or is in the process of breaking, the particles of the regular lantern are shown. This is recreated simply by placing a soul lantern and breaking it, either in survival mode or creative mode. After some testing, it appears that this bug was most recently introduced in 1.20 Pre-Release 1 and has been present in every release version since and possibly every development version.
Edit: Rather confusingly, I am no longer able to reproduce this bug in the current version. I am not sure why this is. I was originally running shaders in the world I first encountered the bug in, however it still occurred even with shaders off and when I reopened the same world in vanilla. Unfortunately I cannot remember if I encountered the bug in a 1.21 world that I did not previously run shaders in. I have not been able to reproduce the bug by running a 1.21 world in shaders and then running it in vanilla, although I can still recreate it in 1.20 version of the game.
When a soul lantern is broken or is in the process of breaking, the particles of the regular lantern are shown. This is recreated simply by placing a soul lantern and breaking it, either in survival mode or creative mode. After some testing, it appears that this bug was most recently introduced in 1.20 Pre-Release 1 and has been present in every release version since and possibly every development version.
Edit: Rather confusingly, I am no longer able to reproduce this bug in the current version. I am not sure why this is. I was originally running shaders in the world I first encountered the bug in, however it still occurred even with shaders off and when I reopened the same world in vanilla. Unfortunately I cannot remember if I encountered the bug in a 1.21 world that I did not previously run shaders in. I have not been able to reproduce the bug by running a 1.21 world in shaders and then running it in vanilla, although I can still recreate it in 1.20 versions of the game.
When a soul lantern is broken or is in the process of breaking, the particles of the regular lantern are shown. This is recreated simply by placing a soul lantern and breaking it, either in survival mode or creative mode. After some testing, it appears that this bug was most recently introduced in 1.20 Pre-Release 1 and has been present in every release version since and possibly every development version.
Edit: Rather confusingly, I am no longer able to reproducethis bugin the current version. I am not sure why this is. I was originally running shaders in the world I first encountered the bug in, however it still occurred even with shaders off and when I reopened the same world in vanilla. Unfortunately I cannot remember if I encountered the bug in a 1.21 world that I did not previously run shaders in. I have not been able to reproduce the bug by running a 1.21 world in shaders and then running it in vanilla, although I can still recreate it in 1.20 versions of the game.Please see final edit below.
When a soul lantern is broken or is in the process of breaking, the particles of the regular lantern are shown. This is recreated simply by placing a soul lantern and breaking it, either in survival mode or creative mode. After some testing, it appears that this bug was most recently introduced in 1.20 Pre-Release 1 and has been present in every release version since and possibly every development version.
Edit: Rather confusingly, I am no longer able to reproduce this bug in the current version. I am not sure why this is. I was originally running shaders in the world I first encountered the bug in, however it still occurred even with shaders off and when I reopened the same world in vanilla. Unfortunately I cannot remember if I encountered the bug in a 1.21 world that I did not previously run shaders in. I have not been able to reproduce the bug by running a 1.21 world in shaders and then running it in vanilla, although I can still recreate it in 1.20 versions of the game.
Final edit: After 45 minutes of researching this "bug", I have realised that I had a resource pack installed from Vanilla Tweaks that was causing this issue due to it being slightly outdated. From this I have concluded that I should go to bed. Please mark as invalid.
Please see final edit below.When a soul lantern is broken or is in the process of breaking, the particles of the regular lantern are shown. This is recreated simply by placing a soul lantern and breaking it, either in survival mode or creative mode. After some testing, it appears that this bug was most recently introduced in 1.20 Pre-Release 1 and has been present in every release version since and possibly every development version.
Edit: Rather confusingly, I am no longer able to reproduce this bug in the current version. I am not sure why this is. I was originally running shaders in the world I first encountered the bug in, however it still occurred even with shaders off and when I reopened the same world in vanilla. Unfortunately I cannot remember if I encountered the bug in a 1.21 world that I did not previously run shaders in. I have not been able to reproduce the bug by running a 1.21 world in shaders and then running it in vanilla, although I can still recreate it in 1.20 versions of the game.
Final edit: After 45 minutes of researching this "bug", I have realised that I had a resource pack installed from Vanilla Tweaks that was causing this issue due to it being slightly outdated. From this I have concluded that I should go to bed. Please mark as invalid.
Issue report is invalid, please see final edit below.
When a soul lantern is broken or is in the process of breaking, the particles of the regular lantern are shown. This is recreated simply by placing a soul lantern and breaking it, either in survival mode or creative mode. After some testing, it appears that this bug was most recently introduced in 1.20 Pre-Release 1 and has been present in every release version since and possibly every development version.
Edit: Rather confusingly, I am no longer able to reproduce this bug in the current version. I am not sure why this is. I was originally running shaders in the world I first encountered the bug in, however it still occurred even with shaders off and when I reopened the same world in vanilla. Unfortunately I cannot remember if I encountered the bug in a 1.21 world that I did not previously run shaders in. I have not been able to reproduce the bug by running a 1.21 world in shaders and then running it in vanilla, although I can still recreate it in 1.20 versions of the game.
Final edit: After 45 minutes of researching this "bug", I have realised that I had a resource pack installed from Vanilla Tweaks that was causing this issue due to it being slightly outdated. From this I have concluded that I should go to bed. Please mark as invalid.
Issue report is invalid, please see final edit below.
When a soul lantern is broken or is in the process of breaking, the particles of the regular lantern are shown. This is recreated simply by placing a soul lantern and breaking it, either in survival mode or creative mode. After some testing, it appears that this bug was most recently introduced in 1.20 Pre-Release 1 and has been present in every release version since and possibly every development version.
Edit: Rather confusingly, I am no longer able to reproduce this bug in the current version. I am not sure why this is. I was originally running shaders in the world I first encountered the bug in, however it still occurred even with shaders off and when I reopened the same world in vanilla. Unfortunately I cannot remember if I encountered the bug in a 1.21 world that I did not previously run shaders in. I have not been able to reproduce the bug by running a 1.21 world in shaders and then running it in vanilla, although I can still recreate it in 1.20 versions of the game.
Final edit: After 45 minutes of researching this "bug", I have realised that I had a resource pack installed from Vanilla Tweaks that was causing this issue due to it being slightly outdated. From this I have concluded that I should go to bed. Please mark as invalid.
Issue report is invalid, please see final edit below.
When a soul lantern is broken or is in the process of breaking, the particles of the regular lantern are shown. This is recreated simply by placing a soul lantern and breaking it, either in survival mode or creative mode. After some testing, it appears that this bug was most recently introduced in 1.20 Pre-Release 1 and has been present in every release version since and possibly every development version.
Edit: Rather confusingly, I am no longer able to reproduce this bug in the current version. I am not sure why this is. I was originally running shaders in the world I first encountered the bug in, however it still occurred even with shaders off and when I reopened the same world in vanilla. Unfortunately I cannot remember if I encountered the bug in a 1.21 world that I did not previously run shaders in. I have not been able to reproduce the bug by running a 1.21 world in shaders and then running it in vanilla, although I can still recreate it in 1.20 versions of the game.
Final edit: After 45 minutes of researching this "bug", I have realised that I had a resource pack installed from Vanilla Tweaks that was causing this issue due to it being slightly outdated. From this I have concluded that I should go to bed. Please mark as invalid.
Issue report is invalid, please see final edit below.
When a soul lantern is broken or is in the process of breaking, the particles of the regular lantern are shown. This is recreated simply by placing a soul lantern and breaking it, either in survival mode or creative mode. After some testing, it appears that this bug was most recently introduced in 1.20 Pre-Release 1 and has been present in every release version since and possibly every development version.
Edit: Rather confusingly, I am no longer able to reproduce this bug in the current version. I am not sure why this is. I was originally running shaders in the world I first encountered the bug in, however it still occurred even with shaders off and when I reopened the same world in vanilla. Unfortunately I cannot remember if I encountered the bug in a 1.21 world that I did not previously run shaders in. I have not been able to reproduce the bug by running a 1.21 world in shaders and then running it in vanilla, although I can still recreate it in 1.20 versions of the game.
Final edit: After 45 minutes of researching this "bug", I have realised that I had a resource pack installed from Vanilla Tweaks that was causing this issue
due toit being slightly outdated. From this I have concluded that I should go to bed. Please mark as invalid.Issue report is invalid, please see final edit below.
When a soul lantern is broken or is in the process of breaking, the particles of the regular lantern are shown. This is recreated simply by placing a soul lantern and breaking it, either in survival mode or creative mode. After some testing, it appears that this bug was most recently introduced in 1.20 Pre-Release 1 and has been present in every release version since and possibly every development version.
Edit: Rather confusingly, I am no longer able to reproduce this bug in the current version. I am not sure why this is. I was originally running shaders in the world I first encountered the bug in, however it still occurred even with shaders off and when I reopened the same world in vanilla. Unfortunately I cannot remember if I encountered the bug in a 1.21 world that I did not previously run shaders in. I have not been able to reproduce the bug by running a 1.21 world in shaders and then running it in vanilla, although I can still recreate it in 1.20 versions of the game.
Final edit: After 45 minutes of researching this "bug", I have realised that I had a resource pack installed from Vanilla Tweaks that was causing this issue as a result of it being slightly outdated. From this I have concluded that I should go to bed. Please mark as invalid.
Health not regenerating despite full hunger bar and naturalRegeneration being set to true
Health not regenerating despite full hunger bar and naturalRegeneration being set totrueHealth not regenerating despite full hunger bar and naturalRegeneration being set to True
Under circumstances I am not certain of, the health bar will not regenerate to full health despite a full hunger bar. This is with the naturalRegeneration being set to True and without being affected by any status effects. I encountered this problem while raiding End Cities in version 1.21, originally in a modded version but I have verified that the problem persists in Vanilla. It appears to occur when fighting many shulkers at once, namely in the fat_tower_middle and fat_tower_base structures, which contain a high abundance of shulkers. This is on a vanilla multiplayer server.
Steps to reproduce
Locate an End city and find its fat_tower_middle and fat_tower_base segments, if it has them.- In survival mode, fight the shulkers.
- Health may not regenerate despite a full hunger bar.
I have not tested these steps to reproduce, since I encountered this issue during normal gameplay they are simply the conditions under which the issue occurred for me and are therefore the conditions I consider to be mostly likely to reproduce the possible bug.
If there is something I may be missing here, please let me know. I have not encountered this problem before and I am not aware of any legitimate reason for it to occur.
Under circumstances I am not certain of, the health bar will not regenerate to full health despite a full hunger bar. This is with the naturalRegeneration being set to True and without being affected by any status effects. I encountered this problem while raiding End Cities in version 1.21, originally in a modded version but I have verified that the problem persists in Vanilla. It appears to occur when fighting many shulkers at once, namely in the fat_tower_middle and fat_tower_base structures, which contain a high abundance of shulkers. This is on a vanilla multiplayer server.
Steps to reproduce
- In the End dimension, locate an End city and find its fat_tower_middle and fat_tower_base segments, if it has them. It may help to be in a multiplayer server.
- In survival mode, fight the shulkers.
- Health may not regenerate despite a full hunger bar.
I have not tested these steps to reproduce, since I encountered this issue during normal gameplay they are simply the conditions under which the issue occurred for me and are therefore the conditions I consider to be mostly likely to reproduce the possible bug.
If there is something I may be missing here, please let me know. I have not encountered this problem before and I am not aware of any legitimate reason for it to occur.
Under circumstances I am not certain of, the health bar will not regenerate to full health despite a full hunger bar. This is with the naturalRegeneration being set to True and without being affected by any status effects. I encountered this problem while raiding End Cities in version 1.21, originally in a modded version but I have verified that the problem persists in Vanilla. It appears to occur when fighting many shulkers at once, namely in the fat_tower_middle and fat_tower_base structures, which contain a high abundance of shulkers. Health appears to regenerate as normal when only fighting a few mobs at once. This is on a vanilla multiplayer server, with no datapacks installed.
Steps to reproduce
- In the End dimension, locate an End city and find its fat_tower_middle and fat_tower_base segments, if it has them. It may help to be in a multiplayer server.
- In survival mode, fight the shulkers.
- Health may not regenerate despite a full hunger bar.
I have not tested these steps to reproduce, since I encountered this issue during normal gameplay they are simply the conditions under which the issue occurred for me and are therefore the conditions I consider to be mostly likely to reproduce the possible bug.
If there is something I may be missing here, please let me know. I have not encountered this problem before and I am not aware of any legitimate reason for it to occur.
Under circumstances I am not certain of, the health bar will not regenerate to full health despite a full hunger bar. This is with the naturalRegeneration being set to True and without being affected by any status effects. I encountered this problem while raiding End Cities in version 1.21, originally in a modded version but I have verified that the problem persists in Vanilla. It appears to occur when fighting many shulkers at once, namely in the fat_tower_middle and fat_tower_base structures, which contain a high abundance of shulkers. Health appears to regenerate as normal when only fighting a few mobs at once. This is on a vanilla multiplayer server, with no datapacks installed. Disabling all my resource packs also has no effect.
Steps to reproduce
- In the End dimension, locate an End city and find its fat_tower_middle and fat_tower_base segments, if it has them. It may help to be in a multiplayer server.
- In survival mode, fight the shulkers.
- Health may not regenerate despite a full hunger bar.
I have not tested these steps to reproduce, since I encountered this issue during normal gameplay they are simply the conditions under which the issue occurred for me and are therefore the conditions I consider to be mostly likely to reproduce the possible bug.
If there is something I may be missing here, please let me know. I have not encountered this problem before and I am not aware of any legitimate reason for it to occur.
Under circumstances I am not certain of, the health bar will not regenerate to full health despite a full hunger bar. This is with the naturalRegeneration being set to True
and without being affected by any statuseffects. I encountered this problem while raiding End Cities in version 1.21, originally in a modded version but I have verified that the problem persists in Vanilla. It appears to occur when fighting many shulkers at once, namely in the fat_tower_middle and fat_tower_base structures, which contain a high abundance of shulkers. Health appears to regenerate as normal when only fighting a few mobs at once. This is on a vanilla multiplayer server, with no datapacks installed. Disabling all my resource packs also has no effect.Steps to reproduce
- In the End dimension, locate an End city and find its fat_tower_middle and fat_tower_base segments, if it has them. It may help to be in a multiplayer server.
- In survival mode, fight the shulkers.
- Health may not regenerate despite a full hunger bar.
I have not tested these steps to reproduce, since I encountered this issue during normal gameplay they are simply the conditions under which the issue occurred for me and are therefore the conditions I consider to be mostly likely to reproduce the possible bug.
If there is something I may be missing here, please let me know. I have not encountered this problem before and I am not aware of any legitimate reason for it to occur.
Under circumstances I am not certain of, the health bar will not regenerate to full health despite a full hunger bar. This is with the naturalRegeneration being set to True and without being affected by any status effects. Using the command /gamerule naturalRegeneration true has no effect. I encountered this problem while raiding End Cities in version 1.21, originally in a modded version but I have verified that the problem persists in Vanilla. It appears to occur when fighting many shulkers at once, namely in the fat_tower_middle and fat_tower_base structures, which contain a high abundance of shulkers. Health appears to regenerate as normal when only fighting a few mobs at once. This is on a vanilla multiplayer server, with no datapacks installed. Disabling all my resource packs also has no effect.
Steps to reproduce
- In the End dimension, locate an End city and find its fat_tower_middle and fat_tower_base segments, if it has them. It may help to be in a multiplayer server.
- In survival mode, fight the shulkers.
- Health may not regenerate despite a full hunger bar.
I have not tested these steps to reproduce, since I encountered this issue during normal gameplay they are simply the conditions under which the issue occurred for me and are therefore the conditions I consider to be mostly likely to reproduce the possible bug.
If there is something I may be missing here, please let me know. I have not encountered this problem before and I am not aware of any legitimate reason for it to occur.
Under circumstances I am not certain of, the health bar will not regenerate to full health despite a full hunger bar. This is with the naturalRegeneration being set to True and without being affected by any status effects. Using the command /gamerule naturalRegeneration true has no effect. I encountered this problem while raiding End Cities in version 1.21, originally in a modded version but I have verified that the problem persists in Vanilla. It appears to occur when fighting many shulkers at once, namely in the fat_tower_middle and fat_tower_base structures, which contain a high abundance of shulkers. Health appears to regenerate as normal when only fighting a few mobs at once. This is on a vanilla multiplayer server, with no datapacks installed. Disabling all my resource packs also has no effect.
Steps to reproduce
- In the End dimension, locate an End city and find its fat_tower_middle and fat_tower_base segments, if it has them. It may help to be in a multiplayer server.
- In survival mode, fight the shulkers.
- Health may not regenerate despite a full hunger bar.
I have not tested these steps to reproduce, since I encountered this issue during normal gameplay they are simply the conditions under which the issue occurred for me and are therefore the conditions I consider to be mostly likely to reproduce the possible bug. I believe that eating causes the natural regeneration of hearts to resume, which is possible with golden apples if the hunger bar is full.
If there is something I may be missing here, please let me know. I have not encountered this problem before and I am not aware of any legitimate reason for it to occur.
Under circumstances I am not certain of, the health bar will not regenerate to full health despite a full hunger bar. This is with the naturalRegeneration being set to True and without being affected by any status effects. Using the command /gamerule naturalRegeneration true has no effect. I encountered this problem while raiding End Cities in version 1.21, originally in a modded version but I have verified that the problem persists in Vanilla. It appears to occur when fighting many shulkers at once, namely in the fat_tower_middle and fat_tower_base structures, which contain a high abundance of shulkers. Health appears to regenerate as normal when only fighting a few mobs at once. This is on a vanilla multiplayer server, with no datapacks installed. Disabling all my resource packs also has no effect.
Steps to reproduce
- In the End dimension, locate an End city and find its fat_tower_middle and fat_tower_base segments, if it has them. It may help to be in a multiplayer server.
- In survival mode, fight the shulkers.
- Health may not regenerate despite a full hunger bar.
I have not tested these steps to reproduce, since I encountered this issue during normal gameplay they are simply the conditions under which the issue occurred for me and are therefore the conditions I consider to be mostly likely to reproduce the possible bug. I believe that eating causes the natural regeneration of hearts to resume, which is possible with golden apples if the hunger bar is full.
If there is something I may be missing here, please let me know. I have not encountered this problem before and I am not aware of any legitimate reason for it to occur.
Update: By deliberately consuming some hunger points by jumping in place, the natural heart regeneration has resumed. I am wondering if this is just a slight quirk of the regeneration system.
Edit: As FelixR stated, the image attached shows you spawning a wolf where wolves don't spawn. Therefore, it defaults to the pale wolf variant, which is intended.
Cannot reproduce - in a forest biome, woods wolves spawn. I'd assume it's the same everywhere else.
Is the world you tested this in upgraded from a previous version?
FelixR I also cannot reproduce this; visited five bastions, and all of them had gold blocks.
![[Mod] Greymagic27](../../../data/avatars/users/92875.png){kind=small}
Please attach your launcher_log.txt file after experiencing that error FelixR
I can confirm a similar issue I had transferring a 1.20.4 world from Realms to a multiplayer server. It caused all inventory items to disappear and reset the player's spawn to 0 0 0, although chests and furnaces remained unaffected. There did not appear to be a fix for it but I was able to find that it was apparently a recent issue arising from that version, if I recall correctly.
Can confirm in 1.20.6.
Can confirm in 1.21 Pre-Release 1, can also confirm that it does not occur in 1.20.6.
That's just adventure mode
you cannot break blocks unless you have tools that are set to do so. It is not intended for normal gameplay.
Can confirm. As Lunarian states, this also means that all of the crystals atop the obsidian pillars have already exploded, which appears to happen before the player appears in the End after entering the portal.
Can confirm. I had it occur after going through 3 or 4 times, but then could no reproduce it with further testing in a newly created world. Does not seem to occur consistenly and not quite sure under what conditions it is triggered.
Can confirm, also affects 1.21 Pre-Release 1. It does not affect 1.20.6.
Cannot reproduce it either:
Just encountered this myself, can confirm. Only thing I have been able to gather is that the advancement being awarded strongly correlates with the teleport sound effect not being played when the pearl is thrown into the portal.
Can confirm in 1.21 Pre-Release 2, 1.21 Pre-Release 1, 1.20.6 and 1.20.5.
Can confirm memory allocation peaking at over 1600mb/s after travelling through the gateway using an ender pearl, although it did not occur 100% of the time. Likewise, travelling through the gateway using the trapdoor method also results in memory allocation spikes on occasion, peaking at over 1800mb/s. Can also confirm ender pearl occasionally failing to teleport the player through the portal, on one occasion failing twice in a row using the same angle to throw. Although the latter issue is not extremely common, it does occur at a noticeable rate. Tested in 1.21 Pre-Release 2.
We'll see if this particular one is intentional, I have realised now that there are other differences in blocks in the menu panorama which I think are deliberate, which does give better context to the missing ladder. However I agree that if MC-272122 does get changed then the same should be done for this one
Can confirm, comparing it to 1.20.6 it does appear to be fractionally faster.
I have tested for the bug in all the Pre-Release versions and although it is not present in them, I decided to report it because it is not (as far as I know) mentioned in the changelogs and therefore its removal may not be known or intentional. Additionally, since Pre-Releases are development versions of the game I consider this issue to still be relevant, as the tracker is intended to be used for both the latest release version and the latest development version.
Can also confirm in 1.21 Pre-Release 3. Tested a few times and had it happen every time.
Can confirm in 1.21 Pre-Release 4.
Cannot reproduce. Are you only attempting to spawn them within a single biome e.g. plains? The variant of wolf that is spawned is dependent on the biome it spawns in, even when done in creative. In the screenshot, it appears that you are only attempting to spawn them in a biome in which they do indeed appear the classic pale variant. Granted, you do say that you previously had worlds with wolf variations.
Can confirm.
Also just something that might make it easier to replicate - I recommend lighting the TNT in the portal frame, and then lighting the portal itself. Makes it much easier
Cannot confirm - visited a couple of bastion remnants, including a treasure remnant, and found gold blocks. Appears to be normal to me but I could be wrong.
Actually, I don't think the custom loot table is the cause. After some testing, I've realised that it appears to be referring to the number of types of items dropped, not the actual number of items. I've tested this with other mobs and it seems that if only one type of item is dropped, it states the number of that item dropped, and if it is more than one item, it states the number of types of items dropped. This is the case in the screenshot you have shared therefore I do not think that this is a bug, although the output text could perhaps use some clarity e.g. "Dropped 2 item types...".
Can only confirm that hezagooboi, but not a helicopter.
I think that the likely reason some of the chunks have changed is because of the changes to world generation over the various updates, meaning that different terrain generates with the same seed. However, that would require the chunks to have not already been loaded, whereas in your case they clearly have been.
I've tried creating worlds in 1.20.4 and spawning wolves in them, then upgrading the worlds to 1.20.5 and directly to 1.20.6 to see if this has any effect on the wolf spawning, but I still could not reproduce the issue. The wolves I spawned in the world in 1.20.4 remained pale, as expected, but any more that I spawned reflected their corresponding biomes. Glad turning it off and on again fixed it though!
Can confirm, just got it in 1.21 survival for the first time and realised it doesn't feel like the description fits the situation anymore.
Can confirm in 1.21. I would love to see watercolor.png being used, it seems much more intuitive and less likely to become convoluted.
Can confirm, I recieved the same error: image-2024-06-30-18-42-29-733.png
However, I do not think this is a crash as such, but rather another type of error. I can't say what though as I do not have the experience.
Done! Renamed it "launcher_log1.txt" to differentiate.
Can confirm in 1.21.
Cannot confirm in 1.21. The portal simply does not activate.
Can confirm in 1.21
Can confirm, though I think this is a duplicate of
MC-150224.Can confirm, I encountered this naturally while attempting to transport a zombie villager.
Can confirm in 1.21.
According to the Wiki:
"In Java Edition, this timer ranges from 20 seconds to 55 seconds, whereas in Bedrock Edition it is always 25 seconds. The forgiveness timer does not advance for zombified piglins in unloaded chunks."
Is it possible that they are not losing aggression either because they are out of render distance or, as you state, they are in a different dimension and therefore unloaded? If that were the case, the timer may not be expiring before you return given that it can be up to 55 seconds and you say you have tested up to 60 seconds.
Can confirm.
Can confirm.
Cannot reproduce. Elytra appears to work normally with fireworks.
Can confirm.
Can confirm.
Can confirm.