The bug
stat.fallOneCm doesn't increase in a linear fashion. This causes the fall damage to be incorrect. For example, the player should die when jumping from 23 blocks, but doesn't. while he does at 24 blocks.
How to reproduce
Load a new creative world, with cheats enabled.
Create a scoreboard with the statistic
minecraft.custom:minecraft.fall_one_cmwith:/scoreboard objectives add fallen minecraft.custom:minecraft.fall_one_cm /scoreboard objectives setdisplay sidebar fallenFall from distance 3, 4, 5, 6 while taking note of the
minecraft.custom:minecraft.fall_one_cm. Reset it after every fall.At distances 11-12, 16-17, 19-20 etc. The
minecraft.custom:minecraft.fall_one_cmhas the same value.
Fall damage is also the same at those levels, creating inaccurate fall damage.
After some testing, it turns out the score jumps at 0.609552546740036 from 0 to 1 (MC-99958), and at 1.194561548248788 from 1 to 2 (meaning that decreasing one of numbers' digit by one would give the lower score).
Attached files
A screenshot of my debug screen data.
A few screenshots of the process of getting the date from the
minecraft.custom:minecraft.fall_one_cmAn Excel file containing the values with a graph (x=height fallen from according the y value of f3 and y= data from
minecraft.custom:minecraft.fall_one_cm
Linked issues
relates to 2
Attachments
Comments 8
It does not. MC-99958 Describes that it only updates when you hit the ground in survival mode, while this reports that the values of falling from different heights does sometimes not result in a different value for the stat.fallOneCm, while it should.
Confirmed with unmodded 1.12.1 with teleporting to be able to measure more precisely.
It also looks like the values are somewhat rounded as there are some "steps" in the graph. If I had measured with a higher resolution (I took a measurement every 0.5 blocks), I think the "steps" would maybe all have the same length.
I attached a graph of my measurements for everyone who does not have excel.
[media]
This seems to also be the case for other movement stats, or at least stat.flyOneCm MC-111286
Although I haven't done much in-depth testing
MC-111286 is not a bug. The reason that short 'flights' do not count is due to jumping. If it would count any time the player is in the air, it would count jumping too.
By the same logic, this report would not be a bug either.
Leaving both open until a developer says it's not a bug.
Does MC-99958 describe your issue?