Unfair Advantage in Mining Speeds between Bedrock & Java

[DarkChromaMC]

Describe the bug

Bedrock Edition players can mine at a faster rate than Java Edition players using the same tools. This provides an unfair advantage.

To Reproduce

See video below to reproduce bug (Use a enchanted pickaxe with efficiency)

1. Mine with a pickaxe enchanted with efficiency >5
2. Optional: Use haste effect
3. Observe the differences between Java & Bedrock
   https://youtu.be/W-ByI4oEyvY

Expected behaviour

Bedrock mining speeds is consistent with Java Edition, so there are no differences.

Screenshots / Videos

https://youtu.be/W-ByI4oEyvY

Server Version and Plugins

No response

Geyser Dump

No response

Geyser Version

Geyser version 2.1.2-SNAPSHOT (git-master-c1d8009) (Java: 1.20, Bedrock: 1.19.80/1.19.81 - 1.20.10)

Minecraft: Bedrock Edition Device/Version

No response

Additional Context

No response

[onebeastchris]

I'm wondering if #3348 boils down to the issue described here; the fix for it might come once this commit (Kas-tle@0d110ca) is merged; it is included in the PR #3505 .
Essentially, this also includes #1621, or #3473, or a few others.
Bedrock 1.20.20 looks promising as it seems that Mojang is working on parity in terms of block breaking durations; see the changelog for the 1.20.20 beta for reference. There's even a neat table included for the blocks that were changed.

tldr: marking as confirmed bug (e.g. endstone bricks, or logs with haste2, or efficiency enchantments); but also as a possible duplicate.

[JerryHan3]

Since the PR #3505 has been merged, maybe we can close this issue as resolved.

[onebeastchris]

This issue isn't resolved for mining speeds with haste; it's e.g. possible to insta-mine deepslate on Bedrock which isnt possible on Java.

[Serial1990]

This issue isn't resolved for mining speeds with haste; it's e.g. possible to insta-mine deepslate on Bedrock which isnt possible on Java.

Both Videos with Efficiency 5 and Haste 3 Beacon:

Java Version: https://youtu.be/kwgFgkPBALQ
Bedrock Vesion: https://youtu.be/r7SzQHB6OTQ

I use the following Versions of Plugins:

GeyserMC: #407 Bungee-version
Waterfall: #556 1.20.4
Paper: #170 1.20.1

[seergh]

This issue isn't resolved for mining speeds with haste; it's e.g. possible to insta-mine deepslate on Bedrock which isnt possible on Java.

Both Videos with Efficiency 5 and Haste 3 Beacon:

Java Version: https://youtu.be/kwgFgkPBALQ Bedrock Vesion: https://youtu.be/r7SzQHB6OTQ

I use the following Versions of Plugins:

GeyserMC: #407 Bungee-version Waterfall: #556 1.20.4 Paper: #170 1.20.1

i just confirm same issue on my server, Bedrock Players are way faster than Java with the same tools

[Serial1990]

Push

Are there any updates from the developers here?

[Kas-tle]

We've done what we can with regards to custom tools and blocks but at this time we don't have the ability to change the mining speed for vanilla tools on vanilla blocks. The bedrock client calculates the break speed on its end and for whatever reason Java is perfectly fine with the client deciding when the block breaks. So nothing will change unless Mojang introduces full parity for client calculated break speeds.

[Budderman18]

I've developed a fix for this issue myself, since geyser is way too quick to call things "impossible" and not research a bit more. I won't be updating this at all, but if someone wants to copy the project and either take it over or merge it, just ensure i'm credited in the plugin.yml and in the javadocs (its already like that atm).
BedrockDIgSpeedFix.zip

[Kas-tle]

Unfortunately since this proposed fix modifies server behavior, it's not suitable for Geyser.

[JerryHan3]

I got an alternative solution for 1.20.5 and above: since mojang added the attribute player.block_break_speed that control the overall boost on mining speed since then, we can make a new plugin that completely cancel the vanilla behavior of the Haste effect, and apply a +0.2 modifier to this attribute for each effect level. This follows the Java Edition's mechanic of Haste effect.

This solution breaks vanilla behavior, so it shouldn't be implement to Geyser, but I'm really looking forward for someone make a plugin or addon with this idea.