[MC-1942] Lava remnants not dissipating after removing source block Created: 02/Nov/12  Updated: 03/May/17  Resolved: 14/Dec/12

Status: Resolved
Project: Minecraft: Java Edition
Component/s: None
Affects Version/s: Minecraft 1.4.2
Fix Version/s: None

Type: Bug
Reporter: Yamaraj Assignee: Unassigned
Resolution: Duplicate Votes: 7
Labels: None
Environment:

OS: Windows 7 Ultimate x64
Java: Version 7 update 9


Attachments: Zip Archive Sandbox.zip    
Issue Links:
Duplicate
duplicates MC-4631 Lava decay fails to schedule block up... Resolved
Confirmation Status: Unconfirmed
Game Mode: Creative

 Description   

I was attempting to build a tower-like structure on which I intended to place source lava blocks at the top in such a manner that the lava would spread down the tower's sides. However, no matter what situation I try, when I remove the source lava block, the lava always stops dissipating at some point (usually on the floor) and I am left with lava which never disappears completely. I have attached my save folder for the world I was working on and left a sign with instructions.

Other thoughts: Behavior of fluids has been very frustrating to all Minecraft players for a long time now and it would be great to see an improvement on it soon.



 Comments   
Comment by Niels Boehm [ 17/Dec/12 ]

In the other issue, the comment refers to the wiki (which is community-run and not a 100% reliable source of information), which mentions that lava will eventually disappear when there are no source blocks - I do not doubt that.

What we are seeing instead is that the lava creates new source blocks in certain circumstances (further down the lava stream) that were not created by the player and which obviously don't disappear by themselves and must be manually removed.

That's what happens in the attached Sandbox savegame and it's also what I see a lot in my games.

Anyway, we will probably not get any attention here, since this issue is marked as "Resolved". And I'm not 100% sure if the other issue (MC-4631) is exactly the same, as its description seems a little vague to me.

@Yamaraj maybe - as original reporter of the issue - you can reopen it and clarify that what we're experiencing isn't explained by the wiki?

Comment by Aiden [ 16/Dec/12 ]

Yes, it may be the same issue
However, if both are labeled as duplicates, then it won't be fixed.

In the other it is called to be correct behaviour, however this is something that I, and probably most of the others who contributed to this, call to be a bug, or a part of the game that needs revisiting

Comment by Anon Ymus [ 16/Dec/12 ]

But it's the same issue.

Comment by Yamaraj [ 16/Dec/12 ]

I do not see how my bug report is "resolved". The supposed "duplicate issue" (https://mojang.atlassian.net/browse/MC-4631) has no relation with the problem reported by me.

Comment by Niels Boehm [ 08/Dec/12 ]

The point is that when you remove the placed lava again and it ebbs away along the contour it sometimes leaves lava source blocks (block ID 10) behind. Obviously, those will never go away unless manually removed. You can test that if you have SinglePlayerCommands (with WorldEdit included) and optionally WECUI. Put a selection around where the lava got stuck and use the //distr command. That will show you how many lava source blocks (ID 10) and stationary lava blocks (ID 11) are in the selection.

However, as to why it does that I can provide no insights.

Comment by nathan Dukes (Inactive) [ 29/Nov/12 ]

this happened to me 3 days ago and the lava is stil there. even if I log out and come back later its still flowing there. I NEVER GOES AWAY!

Comment by Yamaraj [ 29/Nov/12 ]

Well, I've left the game running for at least an hour or more with no lava disappearing.

I do agree with Aiden though, the lava should at least disappear at the same rate it was generated.

Comment by Aiden [ 13/Nov/12 ]

the creation of lava flow blocks works perfectly, I think the fix is just working out how to do that in reverse.

If it disappeared at the same rate and behavior that it appeared at, I believe most of us, if not all would be happy

Comment by Leland Dantzler [ 12/Nov/12 ]

That is not a good fix. Lava and water behave completely differently in real life, but most importantly you'd have lava rushing down hillsides instead of moving slowly. Not a great idea at all, in my opinion.

Comment by Anon Ymus [ 12/Nov/12 ]

The fix for this is probably just to unify water and lava physics (aside from burning, drowning, etc.).

Comment by Aiden [ 12/Nov/12 ]

Pouring water on it simply turns it into stone, which is not always the case that we want.

I can confirm this also happens in survival, it created a huge mess that took hours to clean up, all because the one block didn't stop flowing after the source was removed.

I would expect maybe 10s per block of flowing lava to disappear? About the same rate that it forms at.

because in reality lava does flow much slower than water, but infinite propagation doesn't make sense.

Comment by Caio Netto [ 08/Nov/12 ]

While I confirm this, I also confirm the wiki entry that it WILL disappear, it only takes some time to. But maybe it's taking too long?

Comment by Kumasasa [ 02/Nov/12 ]

Yes, I know. Sorry.

Comment by Leland Dantzler [ 02/Nov/12 ]

Kumasasa, this site isn't for coming up with workarounds. It's for reporting bugs.

Comment by Kumasasa [ 02/Nov/12 ]

Pour water on it

Comment by David [ 02/Nov/12 ]

This bug is there for several versions. Would be nice to finally see it fixed.

EDIT: It seems like big pieces of flowing lava act like source blocks. Flowing lava will disappear if it's "cut in this fashion:
X = stone/gravel/whathever
L = flowing lava

x|L|x|L|x
L|x|L|x|L
x|L|x|L|x

Hope you get what I mean.

Comment by Leland Dantzler [ 02/Nov/12 ]

From the wiki: "Contrary to popular belief, lava cannot remain forever with out a source block. It may take several hours, but it will always disappear." It likely will just take a long time, so I would say this bug is "By Design"/"Won't Fix".

Generated at Sun Jan 12 11:56:10 UTC 2025 using Jira 9.12.2#9120002-sha1:301bf498dd45d800842af0b84230f1bb58606c13.