Jeff
- tensecz
- tensecz@yahoo.com
- America/Los_Angeles
- Yes
- No
MC-144240
I opened a world in 19w07a that I've been adding to using most of the 1.14 snapshots . My well-lit and fenced village was overrun by mobs during the first 19w07a night, which kept the golums busy. It turned out that none of the torches were affecting the block light level. However, when I replaced a torch in 19w07a, the new torch had the expected light level. See attached screenshots.
What I expected to happen was...:
I expected 19w07a torch block light levels to be the same as they been in previous snapshots and releases.What actually happened was...:
Torches placed in earlier snapshots had block light level of 0 when I opened the world in 19w07a.Steps to Reproduce:
1. Create a world in a snapshot earlier than 19w07a
2. Place a torch and note the block light level
3. Open the world in 19w07a and note the torch block light level. I see 0.4. Replace the torch in 19w07a and note the torch block light level. I see expected value, e.g.13 when standing 2 blocks away
My full 4 layer beacon gives me two buffs, but not the achievement. 1.16.4 on a Realm.
Confirmed 18w15a. Started by lightning. Burned down woodland mansion near spawn. I could not place water fast enough in creative mode to save it. Unplayable lag with 3 chunk render distance.
Windows 7 PC, Java edition
fire started in survival
seed 960570313
First time this bug bit me was in 19w07a. I've maintained and added to the same world save throughout the 1.14 snapshots without seeing this before. Confirmed that a restart does not fix light levels. Replacing the light source does fix the level.
Cave torches that I replaced yesterday in 19w07a are now reset to light level 0 after I visited the Nether today, even though I turned off the day/night cycle and the weather cycle.
FWIW, I did search. I found other bugs involving ticking entities, but they all involved some player action. In my case there was no player action. The game crashed immediately after I joined the world.
I have a single player world with this "keeping entity" bug. I'm still using my 19w07a save because of the "ticking entity" bug. I tried killing everything but me ( kill @e[type=!player] ), then quit out of Minecraft, then relaunched the game, and found that many villagers, 2 iron golums, and a horse were reanimated. So I killed them with my sword, one at a time. Again I quit out of the game, then went back in. And again, the villagers, golums, and horse were back.
The log shows many instances of "keeping entity" warnings.
My understanding is that I need to remove the offending entities with a world editor, but MCEdit is not ready for 1.14 snapshots.
I followed Matthew's solution (
MC-145413), and it worked! I no longer have duplicate entity entries in the log, and the places where I could not place a block now accept blocks. It did take some time to copy UUIDs from the log and paste them into /TP commands, but probably only a couple of hours. I placed command blocks to kill zombies, villagers, and iron gollums. It took more than 10 command iterations to kill the last of the duplicate villagers and zombies.Peter, I read your bug thread. I have not had any new duplicated entities since finding and killing all of them. I'm running single player Minecraft on an older desktop pc (Intel i7-3770, 16 GB RAM, GTX 780Ti, 2560x1440 monitor. Video settings are towards the slower, fancier end of the spectrum (11x11 blending, 24 chunk render). My game play is not laggy, so maybe that's why I haven't had entity duplication since killing all the dupes? I've also stayed out of the Nether because some have proposed that Nether visits cause the light emitting block bug. Maybe I'd get duplication if I caused my base chunks to unload and reload?
Happened to me today (8 Dec). Quitting out of Minecraft and relaunching 3 times did not resolve it. Rebooting the PC did, but I agree with the comment about the particular steps not being important. It seems like the bug is caused by planetary alignment.
This is a possibly unnecessary reminder for all of you who have been bit by this bug to vote for it (upper right corner of the window). I expect Mojang prioritizes their bug fixing by how many people are affected by the bug. As of this moment, this bug is not assigned to any bug fixer.
Avoma, I'm not saying you are wrong, but if that is the case, then voting is utterly pointless. As a US citizen, I'm hoping that is not the case!
I've been reading all the comments on this bug since it happened to me. It seems likely that the bug is on the server side, and that none of the tricks anybody does on the client side are actually solving the problem. I think the only thing the tricks accomplish is to spend some time. It may be that simply closing Minecraft and finding something else to do for 30 minutes (or an hour, or whatever) would work just as well as the trick.
Aric Goe - I don't think there is anything you can do except wait a few minutes and try again. Each time somebody posts a possible solution (such as rebooting) that worked, somebody else will say that they tried it and it didn't work for them. All of these attempted fixes take some time to complete, and I think it's just the passage of time that resolves the problem.
Excellent news, sam, but it makes me wonder what this web site is for. As I write this, it still says "unassigned" in the upper right corner.
Another dissatisfied Realms customer, Mojang! A customer who can't use the product I paid for. First it was the 429 error, but that block usually didn't last very long. Your new bug has locked me out all morning.
Lloyd Wright: But when I had the 429 error, I was finally able to connect with the same IP. You may have identified a clue, but there's probably more to it than a specific IP address. FWIW, I've been playing at least once a day since my 429 report (near the top of the comment list), and the 429 error has happened only one time.
Mod violine1101 posted above "By posting more requests you're not getting Mojang's attention, ..." Another poster implied that Mojang does not pay attention to the number of votes for fixing a bug.
What is the purpose of this forum?
Thanks to Antho Foxo for posting the workaround. It turned out that all of my hives and nests were in one chunk, and adding a single (hidden underground) hopper clock fixed the despawning issue.
This is happening in my single player world for both 23w13a and again today in 23w14a.