MC-141817The drop rate of moving block is reduced in the explosion
In versions prior to 1.13.2, there was a feature that moving blocks created by piston or block 36, had 100% drop rate when they were exploded. But in the 18w50a snapshot, their drop rate became about 30%. I think that it must be a bug!
This bug affects many tnt-based blast chambers. They can't break blocks efficiently now.
Linked Issues
Created Issue:
The drop rate of moving block is reduced in the explosion
In versions prior to 1.13.2, there was a feature that moving blocks created by piston or block 36, had 100% drop rate when they were exploded. But in the 18w50a snapshot, their drop rate became about 30%. I think that it must be a bug!
This bug affects many tnt-based blast chambers. They can't break blocks efficiently now.
![[Mod] Neko](../../../data/avatars/users/92901.png){kind=small}
relates to
![[Mod] violine1101](../../../data/avatars/users/92858.png){kind=small}
is duplicated by
user-f2760: Can you provide a setup to reproduce this? I cannot reproduce in 18w50a, nor can the reporter of MC-141817 it seems.
Before doing anything, it is important to know what is the intended behaviour. MC-123025 and MC-141817 can't both be a bug.
First, I want to precise that this feature (a moved block having a blast resistance of 0, implying a 100% drop rate) is extremely usefull in case you want to do a farm that produce a huge amount of blocks which need to be mine using tnt instead of hand (first, it makes it an afk farm ; second, mining is longer than using tnt on a lot of block at once). You can move the blocks that need to be destroyed, and at the same time they are moved by pistons you destroy them using tnt (with a dispenser, using precise timings)
Second, this feature doesn't impact negatively anyone. It is only beneficial. So, it might be intended.
Third, ALL blocks, when moved, is technically changed into block 36, which has a blast resistance of 0 (which implies a 100% drop rate). That means that if MC-123025 is a bug, then the way blocks get moved in minecraft need to be changed. That could creates a lot of new issues, when the system we have now is perfectly fine.
That said, I very much hope that MC-123025 get fixed, and MC-123025 get resolve as WAI.
Duplicate of MC-141817
Could be WAI - idk
[Mod] Neko
Before doing anything, it is important to know what is the intended behaviour.
MC-123025andMC-141817can't both be a bug.First, I want to precise that this feature (a moved block having a blast resistance of 0, implying a 100% drop rate) is extremely usefull in case you want to do a farm that produce a huge amount of blocks which need to be mine using tnt instead of hand (first, it makes it an afk farm ; second, mining is longer than using tnt on a lot of block at once). You can move the blocks that need to be destroyed, and at the same time they are moved by pistons you destroy them using tnt (with a dispenser, using precise timings)
Second, this feature doesn't impact negatively anyone. It is only beneficial. So, it might be intended.
Third, ALL blocks, when moved, is technically changed into block 36, which has a blast resistance of 0 (which implies a 100% drop rate). That means that if
MC-123025is a bug, then the way blocks get moved in minecraft need to be changed. That could creates a lot of new issues, when the system we have now is perfectly fine.That said, I very much hope that
MC-123025get fixed, andMC-123025get resolve as WAI.Useful or not, an exploit is an exploit. I think we both know (even if we do not want to admit it) that moving a block to make sure that it drops 100% of the time is exploitative.
Sure, but there is no correlation between something being beneficial and something being intended. Are item duplicators beneficial? Of course. That does not mean they are intended.
That is also a bug, MC-123217.
Yes, but unlike items duplicators, this isn't overpowered. This bug just increases you're production to a finite amount, that required effort to obtain. The effort required are proportionnal to obtained rates of your farm (if you want a 100% drop rate, you need to calculate delays, distance beetween tnt explosion and pistons so they don't get blown up too...)
It would require a lot of time for Mojang to fix the pushing system in minecraft, when some aspects of it are better now than it could be. This is why there is a chance that Mojang considers that a feature (or at least as "Won't Fix")
I know that arguing the usefulness of a bug isn't productive by any kind, because today people and Mojang want to fix every possible bug they can if they are called bugs. By the past, a lot of bugs became features, because people and Mojang liked the feature. They were weighting pros and cons ; now unfortunately this isn't considered anymore. Bug == Threat
You can mark this ad confirmed/community consenses (because neko couldn't reproduce
MC-123025anymore too).To mods/helpers, you might want to ask mojang what the intended behavior is (but I still stand by my point the current snapshot behavior is what it should be, as it was more than likely an oversight).
From technical point of view, this special block now copies moved block drop behavior. We generally don't add explicit code to restore technical glitches (maintenance impact!), so for now I think it's WAI.
My two cents are that this is an unnecessary behavioral regression. If we see Minecraft as an application platform (which it most certainly is), and we see blast chambers as an application, then this change is an undesirable break in backward compatibility for a pre-existing application. This is something that the Windows development team takes VERY seriously. If you consider this to be a maintenance issue for Mojang developers, what about the maintenance impact for all the players who use this mechanic?
That's all I have to say. If anyone wants to debate the self-evident fact that Minecraft is an application platform, we can take this to /r/mojira.
[Mojang] Bartosz Bok, if you say it’s intended, why not resolve it as such?
While yes, it is a bug, it is a bug that just about no player has experienced unless they intended to experience it. Do I think it should have been fixed? More or less. I do understand fixing bugs but leaving them in a game for so long as unintended features and then removing them without adding anything to take their place is irresponsible and disrespectful to those that use it.
Maybe the real bug is that TNT explosions don't drop an item for every block that they destroy. Before the days of item grouping, I could understand this. But maybe it's time to improve features as you improve performance.
Why not make TNT drop blocks at 100%? TNT is basically pointless after that change and totally useless.
I'd agree with Sandro if this bug is not resolved then TNT's use case is almost eliminated in this game - (which the dev's do not intend and therefore by the definition of 'software bug' which is 'unintended behavior of software' a feature becoming useless is itself a bug)
Insinuating that TNT was useless before this mechanic was found.
Well, TNT dropping moving blocks almost all the time has made it useful in a very "deconstructive" (as opposed to plain destructive) kind-of way, by being able to automate block breaking, if you make a machine that feeds the blocks into a dedicated blast chamber at exactly the right time.
After this fix, TNT's main (non-duping) use will be griefing and making irregular holes in the ground. Can the community request a change to TNT block breaking in general that would increase the drop rates to make blast chambers worthwhile again? Technical Minecraft is a very interesting part of the game after all, but it seems 1.14 is introducing many changes that break previous achievements in that field, most of them seemingly without replacement.
WAI, but TNT now has no drop loss.
[Mojang] Bartosz Bok
Thank you so much!!!