Self-explanatory. One source block and one flowing block generate, but the rest doesn't.
Linked issues
is duplicated by 12
Attachments
Comments 14
@Grum sorry for the ambiguity. just load up a world, set yourself to spectator mode, and fly around until you spot a water/lava spring in a ravine or something. The source block and first flowing block generate fine, but you need to manually update the flowing block for it to keep flowing downwards like it should. Also happens with some lava springs in the nether- rather than flow downwards towards the floor, the flowing lava block just sits there until updated.
Reproducible. Created once more the same seed 2732436332148727145 and used teleport to the coordinates in the screenshot.
I think you're describing two separate bugs, and I'd link them if I weren't too lazy to go and find the right ones. Basically, there's one where flowing water/lava doesn't visually appear for a couple of minutes, and I'm guessing you ran into this with the lava spring since it showed up fine for me. The second is where chunks themselves have this behavior, almost like every block in the chunk is turned into a barrier block, invisible yet present.
@clam lol. You are right, the lava starts to flow after a short time. Good remark.
((The game behavior must have changed now that you game me this knowledge 😃 ))
I tested again with 14w27b, 26c and 25b and in all cases after teleport to the location the lava started to flow after a short time (less than 2 minutes). When I noticed this behavior first time, I was exploring the area. Possibly the time to update can be longer when people play normally, exploring around. If is long enough, maybe it doesn't start at all.
Regarding the second problem I didn't even tried to report it. I mentioned it because it was preventing me to see the lava and its behavior 🙂
Is this still a concern in the current Minecraft version? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases. If this has been done, we can reopen the issue.
Keep in mind that the "Resolved"-Status on this ticket just means "Answered", and that we are waiting for further information on whether this issue still exists or not. We will reopen it as soon as the requested information has been delivered.
Stumbled upon this old thing again- it was fixed even before 1.8.
EDIT: Necrobumping a topic causes a bot to reopen it. Whoops.
Unsure what you mean with this.
What did you do, what did you expect, what happened instead?