MC-107824End Gateway shows beacon beam every 2400 ticks even if no entity teleported
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
[Mod] tryashtar 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
- Works As Intended
Meri Diana
weirdo- 28
- 18
- Confirmed
- World generation
- beacon beam end-gateway gateway
16w39b - 19w39a
16w39b 16w39c 16w40a 16w41a 16w42a 16w43a 16w44a 1.11-pre1 1.11 16w50a 1.11.2 17w06a 17w15a 17w16a 17w16b 17w17a 17w17b 17w18a 17w18b 1.12-pre1 1.12-pre2 1.12-pre3 1.12-pre4 1.12-pre5 1.12-pre6 1.12-pre7 1.12 1.12.1-pre1 1.12.1 1.12.2-pre1 1.12.2-pre2 1.12.2 17w43a 17w43b 17w45b 17w46a 17w47a 17w47b 17w48a 18w01a 18w03b 18w05a 18w16a 18w19a 18w21a 18w22a 1.13-pre1 1.13-pre2 1.13-pre4 1.13-pre6 1.13-pre7 1.13-pre8 1.13 1.13.1-pre1 1.13.1 1.13.2 18w47b 18w48a 18w48b 18w49a 19w02a 19w03a 19w03b 19w03c 19w04b 19w05a 19w06a 19w07a 1.14.1 1.14.2-pre2 1.14.2-pre3 1.14.4 19w39a
Created Issue:
End Gateway repeatedly spits out the beacon effect
What I expected to happen was...:
A beautiful warped texture for decoration, using it in fancy flooring and for a custom portalWhat actually happened was...:
A beautiful warped texture for decoration making the beacon particle effect at random, ruining it's desired effectsSteps to Reproduce:
1. Find/Setblock end gateway
2. Watch itLook, I know it may be helpful for survival mode, but I didn't see this listed anywhere, and it's ruining some of my builds. Call me selfish, but again, I never saw this addition anywhere in changelogs, and it's very annoying, wondering if I should wait for a fix or just find something else for the desired effect. Probably won't be able to find something for that, though.
Environment
OSX, latest released java
![[Mod] Neko](../../../data/avatars/users/92901.png){kind=small}
End Gatewayrepeatedly spits out the beacon effectEnd Gateway shows beacon beam every 2400 ticks even if no entity teleported
What I expected to happen was...:
A beautiful warped texture for decoration, using it in fancy flooring and for a custom portalWhat actually happened was...:
A beautiful warped texture for decoration making the beacon particle effect at random, ruining it's desired effectsSteps to Reproduce:
1. Find/Setblock end gateway
2. Watch itLook, I know it may be helpful for survival mode, but I didn't see this listed anywhere, and it's ruining some of my builds. Call me selfish, but again, I never saw this addition anywhere in changelogs, and it's very annoying, wondering if I should wait for a fix or just find something else for the desired effect. Probably won't be able to find something for that, though.
Code analysis by Marcono1234 in this comment.
What I expected to happen was...:
A beautiful warped texture for decoration, using it in fancy flooring and for a custom portalWhat actually happened was...:
A beautiful warped texture for decoration making the beacon particle effect at random, ruining it's desired effectsSteps to Reproduce:
1. Find/Setblock end gateway
2. Watch itLook, I know it may be helpful for survival mode, but I didn't see this listed anywhere, and it's ruining some of my builds. Call me selfish, but again, I never saw this addition anywhere in changelogs, and it's very annoying, wondering if I should wait for a fix or just find something else for the desired effect. Probably won't be able to find something for that, though.
Code analysis by Marcono1234 in this comment.
How to reproduce
- Use the following command
/setblock ~2 ~ ~ end_gateway default replace {Age:4780L}→ The beam appears one second (20 ticks) after the end gateway was placed, despite no entity being teleported
Code analysis by Marcono1234 in this comment.
![[Mod] Michael Wobst](../../../data/avatars/users/37868.png){kind=small}
is duplicated by
is duplicated by
![[Mod] Les3awe](../../../data/avatars/users/79847.png){kind=small}
OSX, latest released java
How to reproduce
- Use the following command
/setblock ~2 ~ ~ end_gateway default replace {Age:4780L}→ The beam appears one second (20 ticks) after the end gateway was placed, despite no entity being teleported
[Mod] tryashtar mentioned a workaround for the time being:
Set the end gateway's age to a negative value, e.g. -999 999 999 sets it to about 1 year, 7 months realtime.
Example for already-placed gateways:/blockdata X Y Z {Age:-999999999}Example new gateway with negative age:
/setblock X Y Z minecraft:end_gateway 0 replace {Age:-999999999}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 CommandBlock 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 by Marcono1234 in this comment.
How to reproduce
- Use the following command
/setblock ~2 ~ ~ end_gateway default replace {Age:4780L}→ The beam appears one second (20 ticks) after the end gateway was placed, despite no entity being teleported
[Mod] tryashtar mentioned a workaround for the time being:
Set the end gateway's age to a negative value, e.g. -999 999 999 sets it to about 1 year, 7 months realtime.
Example for already-placed gateways:/blockdata X Y Z {Age:-999999999}Example new gateway with negative age:
/setblock X Y Z minecraft:end_gateway 0 replace {Age:-999999999}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 by Marcono1234 in this comment.
How to reproduce
- Use the following command
/setblock ~2 ~ ~ end_gateway default replace {Age:4780L}→ The beam appears one second (20 ticks) after the end gateway was placed, despite no entity being teleported
[Mod] tryashtar mentioned a workaround for the time being:
Set the end gateway's age to a negative value, e.g. -999 999 999 sets it to about 1 year, 7 months realtime.
Example for already-placed gateways:/blockdata X Y Z {Age:-999999999}Example new gateway with negative age:
/setblock X Y Z minecraft:end_gateway 0 replace {Age:-999999999}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).
Please note a current bug, if you want to use the /fill-command on gateways with e.g. Age or other data like ExitPortal ExactTeleport:
Bug since 17w18a, the workaround with a negative Age will only work if you use /setblock or change existing gateways via /blockdata, but it will not work via /fill of more than 1 block.It seems like sometimes only the block (a single one) on the most positive coordinate will get the data (data = in this case Age, and, in case you also set them, the ExitPortal and the ExactTeleport in the gateway), there might be instances where not a single one of the blocks get any data.
To clarify: This fill-bug affects all dataholders, not only end gateways.
Please see:
MC-116973
Code analysis by Marcono1234 in this comment.
How to reproduce
- Use the following command
/setblock ~2 ~ ~ end_gateway default replace {Age:4780L}→ The beam appears one second (20 ticks) after the end gateway was placed, despite no entity being teleported
[Mod] tryashtar mentioned a workaround for the time being:
Set the end gateway's age to a negative value
, e.g. -999 999 999 sets it to about 1 year, 7 months realtime.
Example for already-placed gateways:/blockdata X Y Z {Age:-999999999}Example new gateway with negative age:
/setblock X Y Z minecraft:end_gateway 0 replace {Age:-999999999}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).
Please note a current bug, if you want to use the /fill-command on gateways with e.g. Age or other data like ExitPortal ExactTeleport:
Bug since 17w18a, the workaround with a negative Age will only work if you use /setblock or change existing gateways via /blockdata, but it will not work via /fill of more than 1 block.It seems like sometimes
only the block (a single one) on the most positive coordinate will get the data(data = in this case Age, and, in case you also set them, the ExitPortaland theExactTeleport in the gateway), there might be instances where not a single one of the blocks get any data.To clarify: This fill-bug affects all dataholders, not only end gateways.
Please see:
MC-116973
Code analysis by Marcono1234
inthis comment.How to reproduce
- Use the following command
/setblock ~2 ~ ~ end_gateway default replace {Age:4780L}→ The beam appears one second (20 ticks) after the end gateway was placed, despite no entity being teleported
Workaround
[Mod] tryashtar 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.
How to reproduce
- Use the following command
/setblock ~2 ~ ~ end_gateway default replace {Age:4780L}→ The beam appears one second (20 ticks) after the end gateway was placed, despite no entity being teleported
Workaround
[Mod] tryashtar 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.
How to reproduce
Use the following command
/setblock ~2 ~ ~ end_gateway default replace {Age:4780L}→ The beam appears one second (20 ticks) after the end gateway was placed, despite no entity being teleported
Workaround
[Mod] tryashtar 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.
There seems to be a bug concerning the fill-command for dataholders since 17w18a, which means the workaround as described in the bugpost with a negative Age will only work if you use /setblock or change existing gateways via /blockdata, but it will not work via /fill of more than 1 block.
It seems like sometimes only the block (a single one) on the most positive coordinate will get the data (data = in this case Age, and, in case you also set them, the ExitPortal and the ExactTeleport in the gateway), but I'm still trying to figure out the totality of this bug, there might be instances where not a single one of the blocks get any data.
To clarify: This fill-bug affects all dataholders, not only end gateways.
I just ran into it by chance in 17w18b, and it's luckily already posted here on the bugtracker:
MC-116973
So just heads up for you, in case you'd use the workaround in the bugpost and would want to use a /fill
is duplicated by
Confirmed for pre-1.
Confirmed for 1.11 release.
Confirmed for 16w50a.
Confirmed for 17w15a.
Oh, and confirmed for 17w16a and 17w16b of course
(And also here the offer to overtake the bugpost to update it more frequently, if the original reporter still doesn't etc.)
Marcono1234 I told you Mojira people a few times, you can do whatever you please with my bugposts' description, especially you seem to be frequently codereading, can exchange info with the other helpers and mods, and thus have a deeper insight into everything than I can have, so no worries about anything
I think it's good to know the possible maximum Age (not even sure if it's in the MC Wiki), it's up to the user's discretion which to set, but it's always good to know the maximum, as there are so many different ones in CBing, depending what it is, so let's leave it at that, for informational reasons.
Thanks, have a good day
[Mod] Michael Wobst Thank you
(I find this bug (or intentional change?) important to be fixed for mapmakers and will definitely keep an eye on it.)
How to reproduce
Use the following command
/setblock ~2 ~ ~ end_gateway default replace {Age:4780L}→ The beam appears one second (20 ticks) after the end gateway was placed, despite no entity being teleported
Workaround
[Mod] tryashtar 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.
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
[Mod] tryashtar 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.
![[Mod] tryashtar](../../../data/avatars/users/41963.png){kind=small}
is duplicated by
![[Helper] Lord_Quadrato](../../../data/avatars/users/26105.png){kind=small}
![[Mod] Pokechu22](../../../data/avatars/users/92931.png){kind=small}
![[Mojang] Nathan Adams](../../../data/assets/gravatar/dinnerbone.png){kind=small}
![[Mod] j_p_smith](../../../data/avatars/users/92851.png){kind=small}
History.url
Sorry, just saw MC-107824 (I'm bad in finding bugposts >;[) - will add info in there, if needed.
This can be resolved as dupe.
From what I know currently, purple end gateway portal block beams should only occur if the gateways are created or set freshly, or if something teleported (when the corresponding gateway block's beam shines yellow, until 16w39a), or if you reset their Age via command-means.
However, I just found by chance they emit a purple beam each 2 minutes (counting from when it was set/its Age; tested in 16w44a); I have never seen that behaviour in previous versions and am currently not sure if I just overlooked it, but if this is a newer bug, I might go back to see in which version it started to occur.
I quickly also tested it in 1.10.2 Vanilla, and there the beam does not occur within a timespan of about 6 minutes, so I'm assuming it's really something that changed throughout the 1.11 snapshots.
Video that proves the behaviour in 1.11 (16w44a) https://youtu.be/bea6rbEkGDE
I fiddled a lot with end gateway portal blocks in the 1.9 snapshots, release and 1.10.x release versions, so I would really wonder if I overlooked that behaviour back then, but it's always a possibility, although my quick test in 1.10.2 does say otherwise.
Steps to reproduce
1. setblock single gateway blocks or fill an area with them
/fill ~-4 ~-2 ~-4 ~3 ~2 ~3 end_gateway 0
2. Wait for 2 minutes, and you should see a purple beam occuring again.
If you set the end gateway portalblocks manually/single, the beam will occur according to their age, e.g. if you set 2 blocks with 5 seconds apart from each other, the beam of the second gateway will occur 5 seconds after the first one.
I also tested it by filling an area with end gateways in 1.10.2 Vanilla, went back into that world in 16w44a, and the gateway portalblocks emit that purple beam after 2 minutes. So I'm assuming this would happen also in other worlds, as soon as they update to 1.11, unless it gets fixed before.
Thank you for your report!
However, this issue has been resolved as a Duplicate of MC-107824.
It has been linked to this report. If you have additional information, please add it to that report.
Please search before reporting, as it's likely that one exists already.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – 📖 Game Wiki
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.
Added screenshots, thanks for reminding me @Marcono1234
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 for
Please change the title to "End Gateway shows beacon beam every 2400 ticks even if no entity teleported"
How to reproduce
/setblock ~2 ~ ~ end_gateway default replace {Age:4780L}→ The beam appears one second (20 ticks) after the end gateway was placed, despite no entity being teleported
Please link to this comment in the description
The following is based on a decompiled version of Minecraft 1.10 using MCP 9.30.
This happens because the added a condition that end gateways act every 2400 ticks as if an entity was just teleported. It is also implemented in a way that this happens even if an entity teleported in the same tick (if instead of else if).
Affected class:
Can you please add the way to reproduce described in this comment as well
This may have something to do with the random end gateways that show up in the outer lands starting 16w39a, maybe for them to be seen easier.
Bug still exists in 16w41a
Bug still exists in 16w42a
I see this too except I did not know it had a set time
Video that proves this behaviour (in 16w44a) https://www.youtube.com/watch?v=bea6rbEkGDE
Just ran into it by chance. It does NOT occur for me in 1.10.2 though, and this bug says it would be 1.10.2 as well?
I waited for at least 6 minutes, and as it occurs each 2 minutes, it should have shown up, but it didn't for me, in 1.10.2.
You don't have to insert any Age when you setblock or fill an area with the gateway portalblocks to reproduce, it will occur already with this basic command, periodically each 2 minutes, but not in 1.10.2:
Confirmed for 1.11.2
I think it's WAI to easier find where is end portal block randomly placed in end.
It's hopefully not WaI, as this ruins a bunch of contraptions for mapmakers.
In case it is WaI due to Survival, maybe there could be an additional workaround for Creative, e.g. an additional tag or something along those lines for mapmakers, so it doesn't behave each 2400 ticks as if an entity would have been teleported.
Gave ticket to Meri Diana
Meri (or anyone), if this bug is giving you trouble, here's a workaround until it's fixed:
/blockdata X Y Z {Age:-9223372036854775807L}It doesn't fire when at a negative multiple of 2400, so running that once for each block should keep it behaving nicely for 14,623,560,400 years or so
[Mod] tryashtar I didn't think of offering a workaround for the time being as I was too convinced it is not WaI and they'd fix it asap
You're of course right, and I'll add it to the description, but will also mention the consequences of this negative age method, just to make sure everyone can figure if this works for their specific usage.
For most people this is surely a good workaround for now!
Thank you!
@Meri Diana I removed some parts of the description to make the report more compact and to make it easier to get a quick overview. I hope you are fine with that.
Using -9223372036854775808L as Age might be a bit ridiculous. If you think it is, feel free to replace that with a lower suggested value again.
Confirmed for 1.13pre4.
Confirmed for 1.13-pre6.
Confirmed for 1.13-pre7.
Confirmed for 1.13-pre8.
Confirmed for 1.13.
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.
Confirmed for 1.14.4.