Dripstone does not connect properly when placed with /fill command
Summary:
Using the /fill command with dripstone causes dripstone to not connect properly.
Step to reproduce:
- Open chat tap
- Using commands (can copy):
/fill ~ ~ ~ ~ 255 ~ pointed_dripstone ["hanging":false]
Observed Results:
Dripstone is not connected properly.
Expected results:
Dripstone should be connected properly.
Created Issue:
Placing dripstone with fill commands will not connecting properly
Summary:
New bugs found, Using fill commands with dripstone causing dripstone will not connect properly.
Step to reproduce:
- Open chat tap
- Using commands (can copy):
/fill ~ ~ ~ ~ 255 ~ pointed_dripstone
Observed Results:
Dripstone will not connected.
Expected results:
Dripstone should will be connected properly.
Summary:
New bugs found, Using fill commands with dripstone causing dripstone will not connect properly.
Step to reproduce:
- Open chat tap
- Using commands (can copy):
/fill ~ ~ ~ ~ 255 ~ pointed_dripstone
Observed Results:
Dripstone will not connected.
Expected results:
Dripstone should will be connected properly.
Summary:
New bugs found, Using fill commands with dripstone causing dripstone will not connect properly.
Step to reproduce:
- Open chat tap
- Using commands (can copy):
/fill ~ ~ ~ ~ 255 ~ pointed_dripstone
Observed Results:
Dripstone will not connected.
Expected results:
Dripstone should will be connected properly.
Summary:
New bugs found, Using fill commands with dripstone causing dripstone will not connect properly.
Step to reproduce:
- Open chat tap
- Using commands (can copy):
/fill ~ ~ ~ ~ 255 ~ pointed_dripstone
Observed Results:
Dripstone will not connected.
Expected results:
Dripstone should will be connected properly.
Summary:
New bugs found, Using fill commands with dripstone causing dripstone will not connect properly.
Step to reproduce:
- Open chat tap
- Using commands (can copy):
/fill ~ ~ ~ ~ 255 ~ pointed_dripstone "hanging":false
Observed Results:
Dripstone will not connected.
Expected results:
Dripstone should will be connected properly.
Summary:
New bugs found,Using fill commandswith dripstone causingdripstonewillnot connect properly.Step to reproduce:
- Open chat tap
- Using commands (can copy):
/fill ~ ~ ~ ~ 255 ~ pointed_dripstone "hanging":false
Observed Results:
Dripstone
willnot connected.Expected results:
Dripstone should
willbe connected properly.Summary:
Using the /fill command with dripstone causes dripstone to not connect properly.
Step to reproduce:
- Open chat tap
- Using commands (can copy):
/fill ~ ~ ~ ~ 255 ~ pointed_dripstone ["hanging":false]
Observed Results:Dripstone is not connected properly.
Expected results:
Dripstone should be connected properly.
Placing dripstone with fill commands willnot connectingproperlyDripstone does not connect properly when placed with /fill command
Summary:
Using the /fill command with dripstone causes dripstone to not connect properly.
Step to reproduce:
- Open chat tap
- Using commands (can copy):
/fill ~ ~ ~ ~ 255 ~ pointed_dripstone ["hanging":false]
Observed Results:Dripstone is not connected properly.
Expected results:
Dripstone should be connected properly.
Summary:
Using the /fill command with dripstone causes dripstone to not connect properly.
Step to reproduce:
- Open chat tap
- Using commands (can copy):
/fill ~ ~ ~ ~ 255 ~ pointed_dripstone ["hanging":false]Observed Results:
Dripstone is not connected properly.
Expected results:
Dripstone should be connected properly.
This may be a side effect of MCPE-118779. If you build the pointed dripstone column by actually placing blocks (so that it joins correctly), then when you break the bottom block does it work correctly?
Thank you for asking and not just closing the report)
I noticed this bug during testing just MCPE-118779 and I can confidently say that it does not affect the result of my report in any way. The fact is that this is a new mechanic in Java as well, since other objects of the same kind break gradually (both in Java and in bedrock) and only pointed dripstone breaks instantly in the Java version.

I can confirm!
Unable to reproduce in 1.16.220.50 due to
MCPE-119722