ElectroBleach
- ElectroBleach
- electrobleach
- Europe/Stockholm
- Yes
- No
MC-112151
WEB-3081![[Mojang] Web Team](../../../data/avatars/users/10122.svg){kind=small}
REALMS-5290When water is placed between floor-mounted slabs of any sort, it's side faces become transparent.
How to reproduce:
- Create a 3x3 area with slabs. The bottoms should be flush with the ground.
- Break the center slab, leaving a 1x1x1 area.
- Fill the center hole with water.
Villages generate without paths in superflat worlds
Seed: 5058645759635674204
Teleport: /tp @s 239 17 341 -114.1 17
Also affects spider webs, snow (not the full block), pressure plates, buttons, levers, banners, rails, and tripwire hooks (when placed adjacent to a rising/falling shulker box top).
The bug
If a player has something copied to their clipboard, they open chat, leave the field blank and press Ctrl+C, it'll overwrite what was previously in the clipboard despite no text being selected. This also occurs when using signs, the creative inventory search bar, as well as the command block/structure block GUIs.
This did not happen in 1.12, but has persisted from release 1.13 hitherto.
The bug
If a player has something copied to their clipboard, they open chat, leave the field blank and press Ctrl+C, it'll overwrite what was previously in the clipboard despite no text being selected. This also occurs when
using signs, the creative inventory search bar, as well as the command block/structure block GUIs.
This did not happen in 1.12, but has persisted from release 1.13 hitherto.The bug
If a player has something copied to their clipboard, they open chat, leave the field blank and press Ctrl+C, it'll overwrite what was previously in the clipboard despite no text being selected. This also occurs when editing signs, in the creative inventory search bar, as well as in the command block and structure block GUIs.
Has persisted from release 1.13 hitherto.
Does REALMS-5498 describe your issue?
What exactly does your reference to 1.14.4 mean?
The Bug
Soul Fire extinguishes when the block beneath it is set to any block that isn’t Soul Fire conducive. This is inconsistent with normal Fire, which updates to Soul Fire when the block beneath it is set to Soul Sand/Soul Soil. According to MC-31100, which was updated recently, Fire is meant to respond to block updates, which Soul Fire—a variant of Fire—doesn't do in the same way as its counterpart.
How to Reproduce:
- Place Soul Sand/Soul Soil close to a block of Netherrack and light a fire atop both.
- Replace the Netherrack block with Soul Soil using the setblock or fill command.
Observe.- Replace the Soul Soil/Soul Sand with Netherrack using the setblock of fill command.
Observe.The Bug
Soul Fire extinguishes when the block beneath it is set to any block that isn’t Soul Fire conducive. This is inconsistent with normal Fire, which updates to Soul Fire when the block beneath it is set to Soul Sand/Soul Soil. According to MC-31100, which was updated recently, Fire is meant to respond to block updates, which Soul Fire—a variant of Fire—doesn't do in the same way as its counterpart.
How to Reproduce:
- Place Soul Sand/Soul Soil close to a block of Netherrack and light a fire atop both.
- Replace the Netherrack block with Soul Soil using the setblock or fill command.
- Replace the Soul Soil/Soul Sand with Netherrack using the setblock of fill command.
→
Notice how the two behave differently
The Bug
Soul
Fire extinguishes when the block beneath it is set to any block that isn’tSoulFire conducive. This is inconsistent with normalFire, which updates toSoulFire when the block beneath it is set toSoulSand/SoulSoil. According to MC-31100, which was updated recently,Fire is meant to respond to block updates, whichSoulFire—a variant ofFire—doesn't do in the same way as its counterpart.
How to Reproduce:
- Place
SoulSand/SoulSoil close to a block ofNetherrack and light a fire atop both.- Replace the
Netherrack block withSoulSoil using the setblock or fill command.- Replace the
SoulSoil/SoulSand withNetherrack using the setblock of fill command.→
The Bug
Soul fire extinguishes when the block beneath it is set to any block that isn’t soul fire conducive. This is inconsistent with normal fire, which updates to soul fire when the block beneath it is set to soul sand/soul soil. According to MC-31100, which was updated recently, fire is meant to respond to block updates, which soul fire—a variant of fire—doesn't do in the same way as its counterpart.
How to Reproduce:
- Place soul sand/soul soil close to a block of netherrack and light a fire atop both.
- Replace the netherrack block with soul soil using the setblock or fill command.
- Replace the soul soil/soul sand with netherrack using the setblock of fill command.
→
The Bug
Soul fire extinguishes when the block beneath it is set to any block that isn’t soul fire conducive. This is inconsistent with normal fire, which updates to soul fire when the block beneath it is set to soul sand/soul soil. According to MC-31100, which was updated recently, fire is meant to respond to block updates, which soul fire—a variant of fire—doesn't do in the same way as its counterpart.
How to Reproduce:
- Place soul sand/soul soil close to a block of netherrack and light a fire atop both.
- Replace the netherrack block with soul soil using the setblock or fill command.
- Replace the soul soil/soul sand with netherrack using the setblock of fill command.
→
The Bug
Soul fire extinguishes when the block beneath it is set to any block that isn’t soul fire conducive. This is inconsistent with normal fire, which updates to soul fire when the block beneath it is set to soul sand/soul soil.
How to Reproduce:
- Place soul sand/soul soil close to a block of netherrack and light a fire atop both.
- Replace the netherrack block with soul soil using the setblock or fill command.
- Replace the soul soil/soul sand with netherrack using the setblock of fill command.
→
The Bug
Soul fire extinguishes when the block beneath it is set to any block that isn’t soul fire conducive. This is inconsistent with normal fire, which updates to soul fire when the block beneath it is set to soul sand/soul soil.
How to Reproduce:
- Place soul sand/soul soil close to a block of netherrack and light a fire atop both.
- Replace the netherrack block with soul soil using the setblock or fill command.
- Replace the soul soil/soul sand with netherrack using the setblock of fill command.
→
the two behave differentlyThe Bug
Soul fire extinguishes when the block beneath it is set to any block that isn’t soul fire conducive. This is inconsistent with normal fire, which updates to soul fire when the block beneath it is set to soul sand/soul soil.
How to Reproduce:
- Place soul sand/soul soil close to a block of netherrack and light a fire atop both.
- Replace the netherrack block with soul soil using the setblock or fill command.
- Replace the soul soil/soul sand with netherrack using the setblock of fill command.
→
The Bug
Soul fire extinguishes when the block beneath it is set to any block that isn’t soul fire conducive. This is inconsistent with normal fire, which updates to soul fire when the block beneath it is set to soul sand/soul soil.
How to Reproduce:
- Place soul sand/soul soil close to a block of netherrack and light a fire atop both.
- Replace the netherrack block with soul soil using the setblock or fill command.
- Replace the soul soil/soul sand with netherrack using the setblock of fill command.
→
realms-upload.log
The Issue
The Minecraft.net login page title is inconsistent between its loading state (green square animation playing) and its loaded state. This seems to affect all languages.
How to Reproduce
- Visit Minecraft.net
- Pay attention to the name of the tab you're in.
- Click on "LOG IN"
Note: The effect is exacerbated in Chrome.
To remain consistent with the rest of the site, the page title should always read "Log in | Minecraft."
The Issue
The Minecraft.net login page title is inconsistent between its loading state (green square animation playing) and its loaded state. This seems to affect all languages.
How to Reproduce
- Visit Minecraft.net
- Pay attention to the name of the tab you're in.
- Click on "LOG IN"
shouldget set to "Login | Minecraft" and then change to "Log in | Minecraft."Note: The effect is exacerbated in Chrome.
To remain consistent with the rest of the site, the page title should always read "Log in | Minecraft."
The Issue
The Minecraft.net login page title is inconsistent between its loading state (green square animation playing) and its loaded state. This seems to affect all languages.
How to Reproduce
- Visit Minecraft.net
- Pay attention to the name of the tab you're in.
- Click on "LOG IN"
Note: The effect is exacerbated in Chrome.
To remain consistent with the rest of the site, the page title should always read "Log in | Minecraft."
There is an indubitable TPS bug in this pre-release. I've been getting ~16TPS in empty superflat worlds while having my render distance set to 17. When setting my render distance to two, I receive ~18.5TPS. A friend of mine tested their TPS in a superflat world and got similar results. When in one of my maps – which utilizes mainly functions for mechanics – I get 6TPS on average; this would run at 20TPS beforehand. This didn't seem to occur during any of the previous pre-releases.
Can confirm this as an issue. It seems as if bees can land at any y-position <= 0, like you said. Bees that freeze in the void continue to have an "OnGround" value set to 0, indicating they shouldn't have landed. Bees summoned under y = 0 freeze automatically and bees that fly from y > 0 to y < 0 freeze after about 5 seconds of being in the region. After landing in the void, bees act as if their AI is disabled. After a frozen bee is teleported back above y = 0, their AI returns.
Confirmed for 1.15.1 Pre-release 1
Confirmed for 1.15.1 pre-release 1.
Additional note: When baby bees are confined within transparent blocks, they're able to pass through said blocks when becoming adults. Baby/adult bees not changing state are not affected by this issue.
Note: Occurs when the player is adjacent to a block with an active, rapidly moving piston (sticky or normal) head. Players do not become stuck in the piston head when adjacent to the gray piston "base" block. Occurs when a piston is activated every <= 2 ticks. Piston begins acting as it should after the activation clock has been set to 3 ticks.
Almost positive this is WAI
Not sure what you're trying to describe, that is, if there is indeed something unusual happening here. Fence gate blocks are meant to float above the ground even without "support" from adjoining fences.
Haven't been able to reproduce this. Have you considered it a byproduct of MC-164594? Otherwise, this is a duplicate of
MC-168008.Confirmed for 1.15.1
Confirmed for 1.15.1
Fixed in 1.16.100.54 Beta
If you're able to, can you name the resource pack you're using?
Also affects 1.16.3
Affects 1.16.3
Hello!
This affects release 1.16.3.
Also affects
Hello!
First, reports are only accepted in English. Second, your report is incomplete. Please provide additional information, such as a detailed list of steps that can be used to reproduce your issue, logs, etc., so it can be analyzed properly.
Can confirm. Yaw is reset to 0.
Hello! Unfortunately, this report seems to duplicate
MC-118616.Hi!
This issue seems to duplicate
MC-144036.Hello! I can confirm the presence of this issue in release 1.16.3.
Hi! I can't seem to reproduce your issue in the version specified. Would you be able to provide a world download and/or a crash report to aid in debugging?
Hi! I can confirm the presence of this issue in release 1.16.3.
Hello! I can confirm the presence of this issue in release 1.16.3.