Alexis
- plymethwill
- plymethwill
- Europe/Berlin
- Yes
- No
Deleted Comment:
Please reopen, I can't play when this happens to me every 5 minutes. It has gotten better, but I still blame Xisuma for them reintroducing the bug.
Deleted Comment:
And when I come back from the break will my report still be invalid and my issue ignored? You actually think that game behavior is ok. Alright.
Deleted Comment:
I'll just speak with realms support and maybe they can either add a closer server or talk with a dev and get this "not a bug" fixed
I have also seen this happen with sheep, and other entities. After killing an entity I relog and another one is there with the drops from the last one in my inventory. Did it with a sheep in a fenced area.
Spawn rate is still broken in prerelease 4
So having 20 villagers with 20 lecterns each in a separate space isn't working in pre release 5. A villager that has a lectern in front of it will still choose his job site somewhere else he can't get to. Only 1 villager has been able to restock in this setup.
From those villagers, most had their job site on a block that does not contain any workbench, but had one before. It has not changed for many. So destroying the workbench does not update their job site either.
It is intended behavior for chunks that are already generated. They will stay the same, you can delete the specific chunks and have them reload with an updated village.
An instance of the bug keeps ocurring to me on a multiplayer server, where I am afk fishing in a spot, not moving, and people come and leave the server, and the chunk I am in gets dark when I come back to check on my game.
Only skylight works on these chunks, since that is what probably was fixed on pre release 3
It seems this is one of the easiest bugs to reproduce with villagers, the other one that is way easier is the villagers breeding anyway without beds. So its good that it is finally fixed for the next version
Villagers get their profession only from time 2000 to 9000, so when the world is generated its time is less than 2000 for like 100 seconds. After that it will be working time so they search for a job.
Why was this issue closed? Should I make a new one when this is happening to me?
Will we have to wait until 1.15 to get a fix?
I dont agree, i dont pillar up enough times as the times I instamine. I have bad experiences with both, but ghost blocks is the worst offender here.
Yall have servers close to you and it shows. Us who dont have any realm server closer than 200ms suffer from this. If it takes falling off pilars I GLADLY take it again. Because I can just not 1block pillar up to take a screenshot, while trying to flatten a hill brings a ton of frustration. Thank you for taking this into consideration.
Happens with dirt and stone when on high latency with my testing.
I know that, yes, what about a fix for the dizzyness?
-edit: This is comment was regarding the invalid status on the report
Closest official servers to me is on the East coast of the United States, 8000 km away from me.
Well, if I had to release 1.16 and this was still not fixed, I would not release.
I remember the last time this was fixed, people were falling off 1x1 pillars, seems like the game forced you off the block. After a xisumavoid video on it that got fixed, now we dont see the block but dont get pushed off of it, and we are back to square one.
Can confirm, after closing and opening the map the beacon is reset. I am on 1.18 rc3.
What happened in my testing.
Going away from the chunk where the beacon is did not stop the issue from happening.
Changing from haste 2 to haste+regeneration and closing will revert the effect to haste 2, the previous effect.
But some conditions have to be met for it not to save.
For example: not changing any other block in the same chunk. you can place blocks in adjacent chunks to no effect.
But if the block placed is on the border of an adjacent chunk to the beacon's chunk, then the effect is saved properly.
Could conclude that adding a random block anywhere in the chunk (or bordering it) saves the effect and prevents the issue.
I believe modifying a beacon's effect is not sending a signal that something was changed in the chunk. So its not being saved when you close the game.
Can confirm, after closing and opening the map the beacon is reset. I am on 1.18 rc3.
What happened in my testing.
Going away from the chunk where the beacon is did not stop the issue from happening.
Changing from haste 2 to haste+regeneration and closing will revert the effect to haste 2, the previous effect.
But some conditions have to be met for it not to save.
For example: not changing any other block in the same chunk. you can place blocks in adjacent chunks to no effect.
But if the block placed is on the border of an adjacent chunk to the beacon's chunk, then the effect is saved properly.
Could conclude that adding a random block anywhere in the chunk (or bordering it) saves the effect and prevents the issue.
I believe modifying a beacon's effect is not sending a signal that something was changed in the chunk. So its not being saved when you close the game.
I cannot create a profile from the launcher. Xbox says I own java edition and bedrock. Is there a way to also create the profile from Minecraft.net? Because there is no option to do it from the web for me. Edit: Sent the report under Technical, Downloads and Instalation. The link posted above redirects to a general bug report. Is it supposed to do that?
Additional data I can report is that since 3 days ago the launcher now only says play demo, and my xbox account doesnt show that I own java edition anymore. I hope this is related to eventually fixing the issue, and nothing more. If this behaviour wasn't the intended I wanted to report it so at least you guys know about it. Since I can't reproduce this bug anymore.
I was experiencing the issue of create profile, and since 3 days or so ago, it went to saying play demo. Is there anything I can send as well?
Well, actually support did help. I had a microsoft account created using the gmail.com account i used with mojang, and java edition went straight to that account, even though i specified a new microsoft account during migration...