Instructor Snow
- InstructorSnow
- JIRAUSER517504
- Europe/Stockholm
- Yes
- No
So when you try to go in a portal in creative while being pushed by a sand pusher, you are there client side but it serves side. After 25 seconds or so, you get teleported back to the nether portal and this time you are really there. The game will regenerate a portal if there’s not an existing one. During the 25 seconds where you are bugged, you can interact with entities, but they don’t see you as being where you are, they see you kind of inside the portal. They can inflict you damage, but you will only get it after the 25 seconds. I don’t understand everything that’s happening, and I would appreciate if anyone would help me. (Btw this is partially caused by the sand pusher, even though this time it wasn’t active at all. It went back to normal after I relogged.) When there’s no existing portal in the nether, it will teleport me in a location that seems to be corresponding to my overworld portal coordinates. It will not recreate a portal until it snaps me back after ≈ 25 seconds (which are actually random), where it will create the portal. Watch a demonstration there : https://youtu.be/35oOw8GkL90
So when you try to go in a portal in creative while being pushed by a sand pusher, you are there client side but not server side, meaning you can’t go through a nether portal for exemple. After 25 seconds or so, you get teleported back to the nether portal and this time you are really there. The game will regenerate a portal if there’s not an existing one. During the 25 seconds where you are bugged, you can interact with entities, but they don’t see you as being where you are, they see you kind of inside the portal. They can inflict you damage, but you will only get it after the 25 seconds. I don’t understand everything that’s happening, and I would appreciate if anyone would help me. (Btw this is partially caused by the sand pusher, even though this time it wasn’t active at all. It went back to normal after I relogged.) When there’s no existing portal in the nether, it will teleport me in a location that seems to be corresponding to my overworld portal coordinates. It will not recreate a portal until it snaps me back after ≈ 25 seconds (which are actually random), where it will create the portal. Watch a demonstration there : [https://youtu.be/35oOw8GkL90
]Expected result :
You are well in the nether and everything is normal.Actual result :
You are kind of in between dimensions, in the nether client side and in the overworld server side.How to reproduce :
It happens randomly in my world, so I don’t know how to reproduce it.



If mon griefing was of, it’s normal they wouldn’t pick up gold that’s WAI
I think that's WAI
Sadly that's WAI
Why can't people understand it's WAI ? Like you can make a feedback post asking for zoglins not to attack Armor stands but it's not a bug, it's a feature, not that complicated to understand
None of the "block updates" stated are block updates. The problem does not come from the observer. You can test it using other BUDs, they won't detect them either, meaning they aren't block updates.
I mean logically the Bedrock should stop the blast, but since when is Minecraft logic 😆
Nevermind this is a duplicate
Also affects arrows
Doesn't happen all the time
Yeah, it happens in many different scenarios, the one with obs detecting the dropper is just the easiest to reproduce
Still affects 1.16.220
It probably does, but if the player wants to have worse performance for more render distance they should be able to choose so
What's described by Jess makes total sense to me and is probably working as intended (or at least i really hope it is), but what GH showed is really strange though
But it's absolutely not what you describe...
You should rename it to "comparators dont transmit Redstone signal from redstone dust powered by a trapped chest"
Steps to reproduce : 1) place down a trapped chest 2) place a line of dust coming from it 3) place a comparator 4) open the trapped chest
Expected result : the comparator activates and powers blocks in front of it
Observed result : the comparator doesn't react at all