NOTE, this was tested on realms. Player knockback is broken after the latest update (not 100% sure if this bug is in mc preview). Basically when another player hits you u normally take abit of knockback but now you go absolutely flying (not literally). The bug is amplified when the player punching the other player is moving. NOTE, this was tested with multiple items in the players hand including just the fist and the results were still the same
Linked issues
is duplicated by 10
MCPE-191426
"Problem 1 Knockback increase(it has excelled to a greater amount so it's harder to do things such as combo)
Resolved
MCPE-191452
"Problem 1 Knockback increase
Resolved
MCPE-218270
Hitting mobs/players
Resolved
MCPE-218114
Mobs deal excessive knockback compared to normal in Bedrock Preview 1.21.90.21 (PS5)
Resolved
MCPE-219465
When hitting you deal more knockback than on previous versions
Resolved
relates to 3
Attachments
Comments 10
Can still reproduce the issue in 1.21.101. Video attached. The first time that Flashdriveman hits me is a single click. The second time is a spam click.
@AgentMindStormThat happens because players can knockback any mobs with sprint knockback or knockback enchantment regardless of applying damage.
the knockback has been more extreme for a while and it has not been fixed still, cant believe this game has forgotten about all these bugs and focusing on silly updates.
This is the same issue as (MCPE-170242). It started to apply to players because of server-authoritative-movement in 1.21.60.
When will mojang fix the server-authoritative movement because it has been a whole year now and nothing has got resolved in regards of this issue. A lot of players are STILL complaining about this bug, and it appears that the developers aren't doing anything in regards to solve this issue. Mojang developers fixed the useless and minor bugs that has way less votes than this votes, yet they couldn't fix a whole gameplay bug that has been going on for a year with a lot of votes. Cmon mojang, at LEAST do better than that….
This is related to the server authoritative movement changes from 1.21.60. Reverting the pointless server auth movement change (that also causes many other issues) will fix this bug.