mojira.dev
MCPE-178858

The 1.20.60 update changed player sprint-jump behavior.

Bugs you want to report once? A spec change? We don't know which, but we would like to see one or the other reverted. That's our guess,

[Moving on the ground]
Until 1.20.51, when dashing on the ground, the first tick was running speed.
After 1.20.60, when dashing on the ground, the first tick is walking speed.
[Movement in the air]
Until 1.20.51, 1st tick when dashing in the air is walking speed
After 1.20.60, 1st tick when dashing in the air is running speed

This means that you can no longer do various moves, and you can no longer use the same coordinates that you could use until 1.20.51.

(Coordinates means that if you do this move from this position, you can ride that gimmick.)

If this is a bug due to a fix or a spec change, either way it doesn't concern us.
If this is a spec change we are very sad and retiring from MCBE.
If we have been running 1.20.51 up until now, I don't see the point in changing it now.

Please go back to 1.20.51.
We love Minecraft and are life, parents.
Please let this voice be heard and please take immediate action.

↓Reference video.

https://1drv.ms/v/s!Att4Lmnvv_WSg0BZiBn9_8GamFUk

Linked issues

Attachments

Comments 12

I'm sure no such change were made. Are there any add-ons applied? If so, please attach them here.

Your report does not contain enough information to understand or reproduce the problem.
Please add the following information to the Description, as shown here:

Steps to Reproduce:
1. (list every step carefully, so someone else can reproduce the issue)
2.
3.
Observed Results:
(briefly describe what you see happen, including any message(s) shown)
Expected Results:
(briefly describe what should happen)

Try following your steps to make sure you include everything and can still reproduce the issue yourself.

In the steps/results, please clearly explain how exactly you are testing this timing, and also how it impacts gameplay.

Use screenshots or video to help explain (but not replace) the above information

This report has been temporarily resolved as Awaiting Response. It will automatically reopen when you add information. Please follow the format shown and include all sections (steps, observed, expected). Reports that do not contain all of the requested information and complete steps to reproduce the issue may be closed as Incomplete. For more information please read the Bug Tracker Guidelines.

Many players find this Bug Report Creation Form useful for filling in all helpful information.

Your report does not contain enough information to understand or reproduce the problem.
Please add the following information to the Description, as shown here:

Steps to Reproduce:
1. (list every step carefully, so someone else can reproduce the issue)
2.
3.
Observed Results:
(briefly describe what you see happen, including any message(s) shown)
Expected Results:
(briefly describe what should happen)

Try following your steps to make sure you include everything and can still reproduce the issue yourself.

In the steps/results, please clearly explain how exactly you are testing this timing, and also how it impacts gameplay.

Use screenshots or video to help explain (but not replace) the above information

This report has been temporarily resolved as Awaiting Response. It will automatically reopen when you add information. Please follow the format shown and include all sections (steps, observed, expected). Reports that do not contain all of the requested information and complete steps to reproduce the issue may be closed as Incomplete. For more information please read the Bug Tracker Guidelines.

Many players find this Bug Report Creation Form useful for filling in all helpful information.

1.20.51,X.39.06365 Y.0 Z83.61819 F19.9
1.20.60,X.39.06365 Y.0 Z83.61819 F19.9
Same movement under these same conditions.

Both are the same move with the same coordinates, but with 1.20.51 it is possible, but with 1.20.60 it gets stuck on the wall.
The specific reason is that the first move is run 1t W→W+D JUMP
In 1.20.60, the initial speed of run became the same as the initial speed of walk ← This makes it impossible to reach the place where you can originally avoid the wall, and you get stuck.

https://1drv.ms/v/s!Att4Lmnvv_WSg0FYsnc6KcsVnKq-

2 more comments

The jump from planks at 0, Y, 0 to 0, Y+1, Z+4, shown in the reference video in the description is actually possible in 1.20.62. Maybe just difficult?

[media]

Dear GoldenHelmet.

The video I sent is to prove that 1.20.51 from the very front that can be done with sneak can be done with no problem, but 1.20.60 can not be done due to the reduced initial speed of the run. 3+1 can be done by helping from the back, that's a given.

If you want any help, BE and JE can do 4+1 or 5 block jumps
https://youtu.be/r6B9VftocmE?si=t_x7GPAUzudvW1zf

What I want to tell you this time is what I said at the beginning.
[ground].
Until 1.20.51, the first tick when dashing on the ground is running speed
After 1.20.60, when dashing on the ground, the first tick is walking speed.
[Aerial]
Until 1.20.51, 1st tick when dashing in the air is walking speed
After 1.20.60, 1st tick when dashing in the air is running speed
About.

Dear GoldenHelmet.

The video I sent is to prove that 1.20.51 from the very front that can be done with sneak can be done with no problem, but 1.20.60 can not be done due to the reduced initial speed of the run. 3+1 can be done by helping from the back, that's a given.

If you want any help, BE and JE can do 4+1 or 5 block jumps
https://youtu.be/r6B9VftocmE?si=t_x7GPAUzudvW1zf

What I want to tell you this time is what I said at the beginning.
[ground].
Until 1.20.51, the first tick when dashing on the ground is running speed
After 1.20.60, when dashing on the ground, the first tick is walking speed.
[Aerial]
Until 1.20.51, 1st tick when dashing in the air is walking speed
After 1.20.60, 1st tick when dashing in the air is running speed
About.

Here is set of steps to reproduce that are more straightforward, from MCPE-179189.

Steps to reproduce:
1. Put 2 blocks together on ground.
2. Jump onto it and sneak to the back edge of it.
3. Face forward, hold sprint, then press W and space at the same time.

Expected behaviour:
You will jump off the 2 blocks (tested in 1.20.51).

Observed behaviour:
You can jump again from the front edge of the 2 blocks (tested in 1.20.60 and 1.20.62).

See the video attached.
https://bugs.mojang.com/secure/attachment/562542/1.20.60.mp4

Here is set of steps to reproduce that are more straightforward, from MCPE-179189.

Steps to reproduce:
1. Put 2 blocks together on ground.
2. Jump onto it and sneak to the back edge of it.
3. Face forward, hold sprint, then press W and space at the same time.

Expected behaviour:
You will jump off the 2 blocks (tested in 1.20.51).

Observed behaviour:
You can jump again from the front edge of the 2 blocks (tested in 1.20.60 and 1.20.62).

See the video attached.
https://bugs.mojang.com/secure/attachment/562542/1.20.60.mp4

popai

(Unassigned)

1190743

Confirmed

Multiple

All terminals

1.20.60, 1.20.62 Hotfix

1.21.0.20 Preview, 1.21.0

Retrieved