Hi. I have the same problem, I upgraded to Windows 11 and now I have the same error when entering minecraft. Have you solved this problem? Can you help me?
Recently I almost lost a village of 30+ villagers. The village is walled and sealed completely. If I am within walls, everything is fine. I save and quit as many times as I can - no problems. Two days ago I went outside the walls, spent about 2 Minecraft days outside, exited the game whilst outside, loaded and found that all but 3 villagers disappeared. I restored the population, expanded it to over 40 villagers and 5 golems. Today I left the walls again, spent outside 1 Minecraft night, had to close the game. When I opened the game again and came back within walls, the entire population of 40+ villagers plus golems were lost! Not to mention the fact that a lot of resources to make them dimond gold etc went to waste. Ah yeah and since the entire village is dead now, I can not regenerate them, and what is the point they will disappear again anyways. This issue is going around for some time now and is still not fixed. It takes a lot out of the gaming process.
The game keeps updating but, there is still no solution to the problem the world I am playing is still crushing after loading, and it looks like no one is even looking into it. I spent over a year building this world, am I correct to assume that all that time have gone to waste and I should just drop minecraft altogether??
Maybe you guys can tell me what I can help you with, like recreating or making videos of my three bug reports. Anything to help because these 3 bugs are are screwing with this big project I want to do. Please take a look and see what you can do. I do apologize.
Yes, I've changed it to 1.5 Minecraft as well. I made a new machine where every TNT goes through the same number of repeaters, when lit they have an explosion time difference. Please let me know if you think it's the lengths of the redstone wire... I will test that too.
Yes, I've changed it to 1.5 Minecraft as well, where TNT still bugs out and will at random times destroy the little machine. I use sticky pistons to be able to move the blocks back faster and repeat. (Both kinds of pistons have the same result) I realize repeaters may not run in sync, this TNT/piston bug does not care if repeaters are used, except for the time delay repeater which is used to fix the problem... along with the blocks between the pistons and the TNT.
Hi. I have the same problem, I upgraded to Windows 11 and now I have the same error when entering minecraft. Have you solved this problem? Can you help me?
Recently I almost lost a village of 30+ villagers. The village is walled and sealed completely. If I am within walls, everything is fine. I save and quit as many times as I can - no problems. Two days ago I went outside the walls, spent about 2 Minecraft days outside, exited the game whilst outside, loaded and found that all but 3 villagers disappeared. I restored the population, expanded it to over 40 villagers and 5 golems. Today I left the walls again, spent outside 1 Minecraft night, had to close the game. When I opened the game again and came back within walls, the entire population of 40+ villagers plus golems were lost! Not to mention the fact that a lot of resources to make them dimond gold etc went to waste. Ah yeah and since the entire village is dead now, I can not regenerate them, and what is the point they will disappear again anyways. This issue is going around for some time now and is still not fixed. It takes a lot out of the gaming process.
Thank you!
The game keeps updating but, there is still no solution to the problem the world I am playing is still crushing after loading, and it looks like no one is even looking into it. I spent over a year building this world, am I correct to assume that all that time have gone to waste and I should just drop minecraft altogether??
Apologies, I can't keep up the good work of bug reports, I forgot my Jira
account and want to unsubscribe from updates. Thanks.
On Sun, Dec 6, 2015 at 12:01 PM, [Mod] Kumasasa (JIRA) <[email protected]>
wrote:
> [Mod] Kumasasa
> <https://bugs.mojang.com/secure/ViewProfile.jspa?name=kumasasa> resolved
> an issue as Awaiting Response
>
> Is this still an issue in the current Minecraft Snapshot 15w49b or
> later? If so, please update the affected versions in order to best aid
> Mojang ensuring bugs are still valid in the latest releases/pre-releases.
> Minecraft <https://bugs.mojang.com/browse/MC> / [image: Bug]
> <https://bugs.mojang.com/browse/MC-11449> MC-11449
> <https://bugs.mojang.com/browse/MC-11449> Repeaters update very
> differently <https://bugs.mojang.com/browse/MC-11449> Change By: [Mod]
> Kumasasa <https://bugs.mojang.com/secure/ViewProfile.jspa?name=kumasasa> Resolution:
> Awaiting Response Status: Reopened Resolved [image: Add Comment]
> <https://bugs.mojang.com/browse/MC-11449#add-comment> Add Comment
> <https://bugs.mojang.com/browse/MC-11449#add-comment> This message was
> sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) [image: Atlassian logo]
>
Where do I go to issue something other than a bun on this great site?
Maybe you guys can tell me what I can help you with, like recreating or making videos of my three bug reports. Anything to help because these 3 bugs are are screwing with this big project I want to do. Please take a look and see what you can do. I do apologize.
I really hope this works as intended, it's in my favor.
wowowowowowowowow awesome I love it
Yes, I've changed it to 1.5 Minecraft as well. The TNT still at random times destroys the cannon by using these charge combinations: 1&2, 2&3.
Yes, I've changed it to 1.5 Minecraft as well. I made a new machine where every TNT goes through the same number of repeaters, when lit they have an explosion time difference. Please let me know if you think it's the lengths of the redstone wire... I will test that too.
Yes, I've changed it to 1.5 Minecraft as well, where TNT still bugs out and will at random times destroy the little machine. I use sticky pistons to be able to move the blocks back faster and repeat. (Both kinds of pistons have the same result) I realize repeaters may not run in sync, this TNT/piston bug does not care if repeaters are used, except for the time delay repeater which is used to fix the problem... along with the blocks between the pistons and the TNT.
Brilliant setup, thanks for helping me with some of the bugs I really care about.