Glenn A
Comments
For me it had no effect. Problem persists.
Makes sense to check for the blocks, however even after the beam starts the effect is not applied and the GUI buttons stay inactive.
I noticed it doesn't happen with newly created beacons close to my original ones. But recreating the affected beacons doesn't solve it. I removed the beacon and the whole pyramid, but the same problem appears after it is created again.
Maybe it is a location based problem? I also found a similar description in MC-148059
I'm now attaching a minimal 1.13.2 world which presents the problem after upgrading to 1.14-pre5. Beacon is at
-859,14,332.While reducing this world I found that snow layers now apparently block skylight. I'm not sure if this is intended or how much it is related to the beacon problem. In this case they do have glass and a single snow layer on top — not a problem in 1.13.
So my first reaction was opening this test world in 1.13.2 and removing the snow layers, leaving only the glass. To my surprise, it still didn't work in 1.14. Skylight level is back to 15, proving snow was the one blocking it. But still didn't work I then proceeded to recreate the test world, reopen in 1.13.2 and remove the glass and snow leaving full sky access. When opening this one in 1.14, it works.
After opening this world "as is" directly in 1.14 the effects may be on (reminiscent of the saved player data maybe?). However they will run out since the beacon is not working (at least to me that's what happens). Eventually, after a long time the beam itself may be on again still with no effect.
This is all very inconsistent though: sometimes the beam did not activate at all, specially after saving and reloading in 1.14.