[MC-1591] Water/Lava isn't a liquid? Created: 01/Nov/12  Updated: 28/Mar/23  Resolved: 02/Nov/12

Status: Closed
Project: Minecraft: Java Edition
Component/s: None
Affects Version/s: Minecraft 1.4.1, Minecraft 1.4.2, Minecraft 1.4.3
Fix Version/s: None

Type: Bug
Reporter: robertoccu Assignee: Unassigned
Resolution: Won't Fix Votes: 1
Labels: None

Attachments: PNG File 2012-11-01_13.45.39.png     PNG File 2012-11-01_13.46.36.png     PNG File 2012-11-01_13.47.19.png     PNG File 2012-11-01_13.50.07.png     PNG File 2012-11-01_13.50.31.png     PNG File 2012-11-01_13.51.52.png     PNG File 2012-11-01_13.52.58.png     PNG File 2012-11-01_13.53.12.png     PNG File 2012-11-01_13.54.36.png     PNG File 2012-11-01_13.54.40.png     PNG File 2012-11-01_13.56.57.png    
Issue Links:
Duplicate
is duplicated by MC-12440 Lava leaves gap between itself and a ... Resolved
is duplicated by MC-49475 Water on slabs and interacting with s... Resolved
is duplicated by MC-64279 submerged slabs and stairs Resolved
is duplicated by MC-66695 water treats slabs as full blocks Resolved
is duplicated by MC-99563 Water bug Resolved
is duplicated by MC-106087 Paintings and Item Frames do not remo... Resolved
Confirmation Status: Unconfirmed

 Description   

The water with some blocks looks like a solid block; the water doesn't cover blocks (slabs, stairs...) and looks bad. Only the 'Item frame' block is covered by water and looks good.



 Comments   
Comment by Kumasasa [ 07/Feb/13 ]

Closed.
This is no discussion forum here.

Comment by Thomas Rohloff [ 07/Feb/13 ]

Everybody here should read: http://www.minecraftforum.net/topic/1583885-blocks-like-ladders-and-water/ - Making fences covered by water is as simple as extending their data value. These data value would then be used by the client to render the water and by the server for its water flowing code (to see the block as water (or air if no extended data values are there) instead of fence in that codepath so water will flow through it). The most complicate thing would be to tell the water flow code that it doesn't have to give water data values to the fence but extend the fence data value, but that shouldn't be a big deal and when done it should be easily extendable for other blocks.

Comment by Christopher Hartwell [ 07/Feb/13 ]

I think the way to solve this issue is to graphically put water in over the items that should be submerged, such that the item 'Block' still exists, but appears to be submerged. This would make for some odd phenomenon, however, which would be unfortunately difficult to fix, such as water actually being air where a sign block is placed, and water not flowing further. The way to fix this, I guess, would be to include a part in the game where if a 'graphical water' has an empty space to any side(except up) open, it will place a non source water flow.

Oh, and I do vote for having sugarcane not following the new ideas for water physics. I like underwater farms/ airlocks!

Comment by George Gates [ 07/Feb/13 ]

I don't really understand your second part, mind re-wording it?

Comment by James Wright [ 07/Feb/13 ]

I still disagree. In your example, you explain how water once worked as it was intended to, but that doesn't mean that after fences were made it wasn't behaving in unintentional ways. What happened was that when fences were added there was two methods to deal with its interaction with water at that time. 1, Fence gets destroyed by water; 2, fences hold back water. #2 was the lesser of 2 evils.

I'll draw your attention again to the top of the page. "Won't fix" does not mean "Nothing's broken" it means "We realize something is broken, but we aren't going to fix it for various reasons." I think its okay that Mojang to chose this. But I also think its okay that some people wish Mojang would find a way to around Minecraft's technical limitation. Perhaps, for example, finding a way to add clipping(collision) to entities that prevents player/mob movement but not water.(and then making fences and such into entities instead of blocks)

edit: changed some pronouns to be more specific, but I'm not clear on what was confusing. (I have that problem sometimes with my writing)

Comment by George Gates [ 06/Feb/13 ]

The case is B because water was programmed as a block, on purpose. In most cases like dirt and stone blocks, water not existing in the same block as them (due to both being blocks) was taken into consideration at the time water was added. In 0.0.12a Classic, water not existing in the same spot as other blocks was just fine visually.

Fences are also blocks, but did not come into play until well after water. By the time of 1.0.17 Alpha, water's properties had been in play for a while. Fences and other such non-full blocks look strange with it, but it worked as intended. Water's properties WERE thought out when it comes to some things like redstone, buttons, and torches (where they are destroyed or removed upon contact), but that's generally non-solid items (they don't have a collision box that bars entities from moving across them), while fences and other "solid" blocks are meant to be a barrier.

Water works as it was programmed and intended to, so this is not a bug with the game code.

Now whether this is best with the way the game is now and what sort of ways this could be improved, I don't know.

Comment by James Wright [ 06/Feb/13 ]

That seems unlikely, since the physics for water was programed before fences and such were implemented.

Comment by George Gates [ 05/Feb/13 ]

That depends on your definition of "intention".

A - An idea (formed before/during development) of how the game world should be.

B - How the game was actually programmed due to space/memory/engine/computational limitations.

This is the latter, since the engine is working as it was originally designed to.

Comment by James Wright [ 05/Feb/13 ]

And that's why the "Realistic" argument always fails. But simply, there are limits to how far realism can be stretched. If minecraft had shovels for gravel and dirt but only pickaxes and hoes worked on sand it would be unrealistic. Yeah, it's a game. But some amounts of unrealism are jarring enough to seem like a bug. Clearly water not flowing through fences is one of those things for some people. I doubt its working as intended, they are simply bowing to limitations Notch created for them when he coded the game. We are challenging them to find a way past those limitations, and I think that's okay.

If there are contraptions that would break then perhaps they should make a block intended to do these things(like the comparator did for bud switches) rather than exploit was is clearly a bug. As you can see the top doesn't say "not a bug" it says "won't fix"

Comment by George Gates [ 05/Feb/13 ]

And in real-life you need to drink regularly and take bathroom breaks. Videogames often break from reality to allow for game mechanics, and holding water back with transparent objects (like signs) is a game mechanic used in tons of builds.

Comment by Thomas Rohloff [ 04/Feb/13 ]

@George Gates:
1) Then the water would flow through it like it would flow through air.
2) If it has holes water flows through it.
3) Designs which use signs/ladders/... to keep water away would break, yes, but to quote myself: "do you try to hold water back with signs and ladders in real-life?"

Look also here: http://www.minecraftforum.net/topic/1583885-blocks-like-ladders-and-water/

Comment by George Gates [ 02/Feb/13 ]

And Thomas, what if a block only has water on one side of it and not on the other side? Should it only show water on one half, and if so, which half? What if it's something like the brewing station or fence that has obviously holes and/or missing areas, if there's no water on the other side should the water pretend that the block isn't there and flow past it? If so, what about designs where people use floating signs and such to hold water in place?

etc.

Comment by Thomas Rohloff [ 30/Nov/12 ]

I also think this should get fixed. As James Wright told a easy solution would be to add/extend data values of affected blocks. Of course this requires work, but every fix/feature does that, so that isn't a excuse (nobody says fix it RIGHT NOW. We say: Take your time to fix...).

@Dinnerbone telling that this is a "design choice" sounds very lazy and I don't believe it, but even if so it was a bad choice. Technical limitation: Yes, that's what I believe, but that can be changed.

//EDIT: Also I don't even think all blocks would need this, you could just destroy some (telling they where washed away) if they are placed in water. For lava I think most blocks won't need it, just destroy them.

Comment by James Wright [ 04/Nov/12 ]

Couldn't there simply be a damage value to indicate whether or not the item is submerged? Though I suppose there's an issue with varying water levels (as you get further from the source block). But still, making blocks entirely underwater contain water like that dock in the picture would go miles for making the game look really nice.

Comment by [Mojang] Nathan Adams [ 02/Nov/12 ]

Design choice and technical limitation.

Comment by Sid Ben [ 01/Nov/12 ]

This is a design choice. Every block in the game have an ID, and water, lava, etc are blocks too.

You can't have a block with 2 IDs, to "fix" this would require to create an ID for every water/block combination possible.

EDIT: Paitings works like item frames, and they are not blocks, like Ezekiel said.

Comment by Ville Lahdenvuo [ 01/Nov/12 ]

I think this is a feature, but I also think something could be done to improve this.

Comment by [Mod] Ezekiel (ezfe) [ 01/Nov/12 ]

This is not a bug. The only reason painting's and item frames are not affected by water is because they are not blocks

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