gary cousins
- gazmo9
- gazmo9
- Europe/Stockholm
- Yes
- No
gary cousins, "from scratch" means "in a newly created world". If you haven't reset the world on your server, the bug would have stayed from your world you had previously unless you reset the complete chunk cache.
durward2003, that's an interesting question. Indeed, I cannot find anyone stating that this issue occurred in a new world from 1.14-pre3 or 1.14-pre4.
Quinn Bast, thanks for the experiments! However, I haven't been able to reproduce this that way myself in singleplayer. I think it's quite clear that this is related to chunk loading though.
I also want to remind anyone that this is not a discussion forum. If you don't have anything constructive to add to this ticket, please don't post a comment.
Reopened.
gary cousins, this is a bug tracker and not a discussion forum. If you don't have anything constructive to add to the report, please don't comment here. Consider this a warning.
To anyone who is experiencing this bug in 1.14.2-pre2 after having optimized the world with erasing the cache: If you want to help us with solving this issue for good, please read this comment by [Mojang] Georgii Gavrichev (that's the same comment as in the "Please read" box above). Just commenting "I have this issue as well" is not helpful.
had this issue in pre 1 and 2, tried pre-3 this morning on our server and all seemed good, its now afternoon and i went back on only to see the dark patches again, torches there but no light, and mobs able to spawn there.
hi im not great with server controls but you said to fix it do this, Multiplayer: Start the server.jar with the following command:
java -jar server.jar --forceUpgrade --eraseCache. how do i do this on a rented server?
this happened to us too. we updated from 1.13.2 to 1.14 and as a mod on here told me to fix it we had to optimize world and clear cache from a world that hadn't been opened in any 1.14 snapshots which we did but we still have this problem, and as the poster said portals seem to affect this.
still getting this issue in 1.14 full release. we updated from 1.13.2 to 1.14 full, optimized world and cleared cache, but it is still happening, please sort this out.
i hope we aren't going to have to wait months for 1.14.1 to fix this issue, its pretty much game breaking and was known about in all the 1.14 pre-releases
well dinnerbone said they were hoping to get a beta of 1.14.1 done by the end of the week or early next week so my guess is that, thats the earliest we may get a fix, but seeing as it still says unresolved and wasn't fixed in the pre-releases im not getting my hopes up. my faith in mojang has severely diminished with this update as, like tarek said it does make the game unplayable and it shouldn't of been in the full release after not being fixed in the pre's, which as far as i understand is the whole point of having pre-releases. the least they could of done was to have fixed this asap and put out a hotfix, the other bugs are still a pain but they dont make it unplayable like this one does.
As much as i love mojang, it would be nice, considering how bad this bug is, if we got some kind of acknowledgement from them about it, and perhaps an update as to how the fix is going because it seems to be taking a very long time and is causing a lot of grief for a lot of players.
seriously? theres a 1.14.1 pre release and this bug isn't fixed? why fix little bugs first when theres game breaking bugs like this?
i agree they do, but the bug has been on going since the first 1.14 pre-release so its not like they haven't had time, perhaps if they just gave an update on how the fix is coming people would be less annoyed.
thanks for the reply Georgii i appreciate knowing that you are trying to fix this. the question i have now though is, if you cant find an exact cause for this then does that mean people with this problem, updating a 1.13.2 world, will have to start fresh worlds on 1.14?
having read about the slime chunk theroy i decided to check that in our world and although it has affected slime chunks it has also affected non-slime chunks. though it does seem to be close to slime chunks if that means anything.
well as far as pre-release 2, the notes dont say its fixed plus it still says unresolved on here so im guessing its not fixed. i did however notice this on there pre-release notes, Update: We've now released 1.14.1 pre-release 2 which fixes a few issues. Unless any major show stopper pops up, we aim to release 1.14.1 on Monday, May 13th. I would hope this means it should be fixed this week as i would say this bug is a major show stopper.
if its worse, then it could be a good thing as they can hopefully see what they changed between releases and maybe narrow down the cause
yeah we had most of our black spots turn up after coming out of nether portals too. i hope this is fixed by tomorrow when they hope to release 1.14.1
Our server experienced the bug in all 1.14 pre-releases hence why we are very annoyed it was allowed to stay in the full release
sorry let me rephrase, we experienced the bug in each pre-release using a 1.13.2 world that hadn't been updated with each pre-release, ding the optimized world erased cache trick too.
1.14.1 is out, no mention of a fix (which is ridiculous considering they said it wouldn't release if theres a show stopping bug, which this is) any confirmation on if it is still occurring or not? hopefully it isnt cos i cant see them updating to 1.14.2 for a few months.
the specs idea is interesting, as it would explain why some people get it and some dont, or maybe server settings are different to single player? i can say from experience though that when ive tried it on our sever it was only me on at that time so the only chunks loading/loaded would be the ones im in and spawn chunks if that helps at all.
i wonder if this is somehow connected to
MC-151082, https://bugs.mojang.com/projects/MC/issues/MC-151082?filter=allopenissuesreading the comments there it seems server lag and tick rates get progressively worse and happens more when moving a good distance which sounds kinda familiar
does replacing all the lights actually stop it happening again?
ah ok, thank you.
just noticed this bug is 4 months old now lol
hey guys i just been looking in to spigot for 1.14 (though its not released yet) and came across this, https://hub.spigotmc.org/jira/browse/SPIGOT-4884?filter=-9
it seems they have fixed the problem so maybe the people dealing with the bug may want to get in touch with them to find out how they fixed it.
tried the latest spigot and it took alot longer than normal but then the dark patches came back ;(
Thats a shame, i was so hoping someone would have a fix, 4 months and still no closer to a fix.
could the devs not join someones world that it affects, or someones world where its easily reproduced? maybe then they can get the info they need? also thanks for the update violine1101, im sure they are working on it and hope they will fix it soon, but i think we can all agree that 1.14 shouldn't of been released in the first place with such a bad bug.
another thought, could the devs whip us up a version of 1.14 that DOESNT have the new lighting engine? not saying that its the cause but we could at least rule it out.
its fixed? 1.14.2 pre 1 says it is. if it is in fact fixed i would love to know what the cause was.
thats a shame, i really hoped it was sorted out. i could give a download of our world if it helps but i dont know what triggers the bug, as sometimes it takes some time before the bug appears so i wouldnt be able to provide a download of just befor it happens, and i dont really want to update to 1.14.2 pre 1 to test it if theres people saying its not fixed as our server members are already very annoyed from all this going back and forth.
i was really hoping to celebrate minecrafts 10 yr birthday in 1.14 too. oh well better reopen the bug i guess its a shame we cant get a refund of our time wasted with this bug.
@Christopher Fry i hope its done for 1.14.2 too but its become evidently apparent that the minecraft higher ups don't have a problem releasing full updates with 4 months old game breaking bugs and though i'm sure the guys working to fix this bug are working hard to find a fix i wouldn't get your hopes up, all the people on our server did, especially the times it was supposedly fixed, only for them to be dashed with every release.