How to reproduce
Use the following command
/setblock ~2 ~ ~ end_gateway{Age:4780L}
→ The beam appears one second (20 ticks) after the end gateway was placed, despite no entity being teleported
Workaround
@unknown mentioned a workaround for the time being:
Set the end gateway's Age
to a negative value for example -9223372036854775808L since that is the lowest long
value possible and is about 14623560433 years in the real world.
Note: Be aware that this workaround will also remove any beam occurrence even if an entity enters that gateway
(as long as the gateway got a negative Age
value).
If you do need a beam whenever an entity enters the gateway, but want to additionally prevent the currently periodically recurring beam each 2400 ticks, set e.g. a command block contraption with a timer that resets the gateway's age to 200 (timer at maximum at 2199 ticks = 1 minute and 49,95 seconds realtime).
Code analysis
See this comment.
Linked issues
is duplicated by 4
Attachments
Comments 27
Didn't the beacon beams stop after some time? They should like I said before only appear when an entity was teleported
It does go back into the block, but then it will shoot out again at random, no rhyme or reason. Doesn't matter if something goes inside of it or if it was freshly spawned/rendered. Try spawning a bunch of them and just look at them? It's what happened for me. Tried removing them all and putting new ones in too, bug still occurs.
Yes. I am seeing the same thing. I use them as "transporter pads" in my overworld, and they are now randomly spitting out beacon beams.
Confirmed, just ran into this when investigating some other stuff. Note that this is the purple beam for teleporting an entity and not the magenta initial spawn beam, and the gateway will also not teleport entities while this purple beam is visible.
End gateways only show a beacon beam when an entity is teleported or if it was just created. If you are talking about something different please attach a screenshot and if possible mark the thing you did not expect.