MC-57906Sponges don't cause block updates
When a Sponge soaks up water, it doesn't cause a block update.
Reproduce: build a BUD, place a (dry) Sponge next to the block that detects the update, place water next to the Sponge. The Sponge will get wet, but an update does not occur.
Environment
Windows 7 Professional, Service Pack 1, 64-Bit System
Java Version 7 Update 55
Linked Issues
Low
Created Issue:
Sponges don't cause block updates
When a Sponge soaks up water, it doesn't cause a block update.
Reproduce: build a BUD, place a (dry) Sponge next to the block that detects the update, place water next to the Sponge. The Sponge will get wet, but an update does not occur.
Environment
Windows 7 Professional, Service Pack 1, 64-Bit System
Java Version 7 Update 55
Added Affects Versions: 14w26c
Added Attachments:
Added Affects Versions: 1.8.2-pre1
Added Linked Issues:
duplicates
Confirmed for 14w26c
This happens because even though the sponge has changed to a different block, it only has changed it's data value, so technically, its still the same block. It can be fixed by allowing data values/BlockStates into block updates.
@kazblox
That is incorrect, place a grass block next to a BUD and place another block on top of it. The BUD gets triggered as soon as the grass block turns into a dirt block, even though it's just a change of data value.
Dirt and grass blocks actually have seperate IDs. BUDs can detect changes of Block IDs but not data values.
MC-5898Works as Intended... I guess?
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.
@kazblox
You are correct, my mistake.
@Galaxy_2Alex
Just checked for 1.8.2-pre1, yes, it still occurs, altough it could be argued it is not a bug and it's intented that a block changing data value doesn't cause an update.