Confirmed for 1.13.1-Pre-1
I also have this bug, but it only freezes my minecraft, it doesn't freeze my computer. If I hit Apple+Tab I can tab out and Force Quit Minecraft without any issue, but it is rather annoying to have the game freeze up when trying to make a resourcepack for a datapack quite often...
Also, I started using the Options/Resource Packs way too, but then I froze once like that too today!
I don't play Bedrock, only Java, but it seems the only video I found on each biome having a specific color came from bedrock edition. I was almost CERTAIN that I had played on a snapshot that had this feature...
If it's only a bedrock feature then I suppose I'm sorry for wasting your time... My mistake. Though I really hope I'm right in thinking it's a java feature, I was so happy when I saw it introduced.
Again, sorry if I wasted your time, if I'm mistaken that is.
(This might be the video I was remembering, and it's obviously on bedrock edition: https://youtu.be/wfmeP7LNz-4?t=9m54s)
Am I mistaken in thinking that was a feature? I am almost CERTAIN I remember there being distinct biome water colors for practically each biome... Yet I can't find what snapshot that came in... I remember seeing it in both a youtube video, and playing on a snapshot that had that... I distinctly remember both the Taiga and Desert water colors being particularly nicer.
This is a feature isn't it?
Oceans, Beaches, and Swamps all work for me, it's just the secondary biomes, the ones that were added this update, which don't work for me. Such as the neat Desert Water which should look more cyan/teal if I'm not mistaken, or taigas which had a distinct color which I forget now.
I don't have any of the other biomes which are new to the update. I only have the biomes which we had ≥ 1.12 (Oceans, beaches, swamps, [I don't think Rivers work for me right now however, since they seem to have the same color as the regular oceans, and I think they were slightly distinct before if I'm not mistaken?])
Well the screenshots should be added in the list now, I took two with F3 open. I think they just appear as enormous if I post them in the comments
Hello,
I'll get a screenshot shortly.
I was not using a resource pack, however I found a snapshot-compatible resourcepack to test if that would help, and it didn't (either the bug still persisted or the resourcepack didn't have biome colored water, didn't check [John Smith Legacy]). I also figured it could have to do with something in the default resourcepack, I opened one of the bins or asset folders not too long ago, was wondering if that had anything to do with, so I created an entirely new minecraft folder in Application Support, but that didn't fix the bug. I also looked back at 18w15a, and it seems like I don't have the water colors then either. I forget when biome water colors were added, but I've tested versions 15a, 20a, 21b, and 22a and I find the bug in all of them.
I'll go take the screenshot now.
@Conner Steppie,
Good observation, but not really, as I don't have the biome colored water to begin with. (I do in oceans and swamps, but not secondary biomes like Deserts, Taigas, Plains, Extreme Hills, etc, which all used to have their own specific colors in one of the snapshots)
I can confirm this is true, my redstone race mechanism just failed on me in survival, and when I went to check on it I saw I had to manually update the blocks for them to send the signal through.
Sorry, originally it didn't seem the same, and another thing, I figured out why it's been crashing, it's not the server, it was simply because:
Either the world was created with custom world generation using the singleplayer world gen options
OR-
The world was made in a snapshot version
I'll check out the other post to see if that was resolved or not, but I'm wondering if there's a way to uncorrupt the world...
This is not a duplicate, nor is it a resolved issue! I can't run my server on any computer without it crashing when no players are on, so I can't have a dedicated server!
I have this same problem, not only that, but when no players are on in my server, it sometimes turns off on it's own, saying that the Java runtime exception, or something along those lines...
SEEMS to be fixed in 1.13.1-Pre1