This has been a thing for some time... I know at the very least I experienced it in 1.12.2 (pre MC-127238).
I can reproduce in 1.14 release, but for more info: it only seems to happen if there's a gap between the beacon and the first stained glass block.
If the stained glass is right up against the beacon, it works as before, setting the colour of the beam.
But if there's an air gap, seems like now the beacon beam is treated like it's been coloured white, and gets averaged with the the first glass block it comes across, giving this much paler colour.
[media]
In 1.13 both of these beams would be solid red.
Kept failing for me with Java 10 (Oracle JDK). Tried with -Xss1m, didn't work, -Xss2m did work, but a subsequent restart didn't.
Java 8 (Oracle, 8u172) works.
Same issue with my world where I killed the dragon and no egg appears and my world was also transferred to the new version
BTW, I no longer see the StatusLogger errors after going through the above workaround.
The problem is the jar has two files with the same name:
META-INF/org/apache/logging/log4j/core/config/plugins/Log4j2Plugins.dat
Using the following did the trick for me:
unzip <jar> META-INF/org/apache/logging/log4j/core/config/plugins/Log4j2Plugins.dat
which then asks me if I want to replace the first with the second--I say no.
Then:
zip -d <jar> META-INF/org/apache/logging/log4j/core/config/plugins/Log4j2Plugins.dat
and again:
zip -d <jar> META-INF/org/apache/logging/log4j/core/config/plugins/Log4j2Plugins.dat
And then:
jar -uvf <jar> META-INF/org/apache/logging/log4j/core/config/plugins/Log4j2Plugins.dat
Ugh, I hate that this is marked as duplicate when it is clearly different from the issue that is supposedly duplicates. Quartz slabs showing up as grey (while other quartz shows up as white) is very different from a complaints that many blocks are grey.
a simple "please add in the crash report in your message." would have worked just fine. we're all not bug reporting experts. also how about adding in that autofilled message for the user to add in the crash report? doesnt really matter now anyways. after restarting my computer for a 3rd time it is working now.
Ahh! Yes that's ok - thanks for the link fix! I was really scratching my head over it haha 😃
Hmm weird that it would have two totally different triggers then IMO
No it isn't a duplicate of that bug. I literally updated to the new snapshot version. The item selected was already on my pickaxe. I attempted to break (not PLACE) a block. The game crashed. So how is this then a duplicate of a bug involving the game duplicating blocks that are being placed when I was attempting to break a block with a tool...?
Edit: the issue is now fixed in the "B" version the snapshot
I am having this issue as well on the Windows 10 version of Bedrock. In addition there is seemingly no way to get out of the chat other than to close the entire program.