Sorry again. Here’s the world and pack:
What the hell… this must be the only report I didn’t attach such to. I’ll recreate it and get on that tonight. Sorry.
@tryahstar: yeah, there were 6 different bugs I saw with faceLocation. The other 5 aren’t close matches, but this report may duplicate MCPE-223452.
However, I’m not fully certain of such. I’m not 100% confident in the diagnosis in the report. Further, the report didn’t include example screenshots, videos, or packs, which makes it hard for me to tell.
If you think it’s close enough, I could move things over.
@Thelarrikin, this was fixed in the 1.26.10.20 Preview for you, too, right?
I covered this bug without realizing this was already filed over at MCPE-236344. I included an example world, behavior pack, and screenshots in such.
Whoops. Not sure how I missed that one. Thanks.
Tested on Preview 1.26.10.23: I can’t recreate this on my high-end Windows 11 device.
I can confirm this bug, at least in the y-direction. @jKakub, do you need a testing pack/world.
🐛 Confirmed on Preview 1.26.10.23. Yikes!
@Baslod, I’ve added more information and connected the dots a bit better.
@GoldenHelmet:
The content log warning is just a warning to advise the content creator that the block they defined as a redstone producer cannot actually produce any redstone power because it is not sufficiently defined.
Actually, content log warnings go beyond just being warnings in one case: the Marketplace. Studios are not allowed to submit content that issues loading warnings.
I am arguing that the bug in question is that any warning is thrown at all. And although my stance is that the warning should not be emitted, if this is intentional, I’d rather them:
Fail to load the block entirely.
Update all documentation to indicate that it is required.
Oops, I missed this when I filed my request. Here’s my duplicate: MCPE-234801.
Didn’t catch that one when reporting. Thank you, @phizlip.
Additional information pertaining to the Creator Platform is available at MCPE-234648 .
Here’s a video demonstration of this having been fixed:
Tested on Preview 1.21.80.27, I can confirm this issue has been fixed. The only remaining vanilla orientation state that doesn’t update correctly in structures or features is huge_mushroom_bits.
Oof, sorry that took so long. I attached the world to the report alongside testing instructions.
Sure, let me whip something together tonight.
This was indeed seemingly fixed with Preview 1.21.20.21.
@Greymagic27, this issue has been fixed.