Satoru Nakajima
- magnet2000
- JIRAUSER709485
- Europe/Stockholm
- Yes
- No
MCPE-149622
When a piston pushes a block on which a player is standing, the player is left behind by about 0.5 blocks.
At least 1.17.11, playerfollowedthe standing block accurately.Affected entity:
Player, Boat (that player is riding), Horse (that player is riding and saddle is equipped)Platform:
I confirmed this bug occurs in Win10 and Android at least.Versions since:
This bug started to occur between release versions 1.17.11 and 1.17.30.When a piston pushes a block on which a player is standing, the player is left behind by about 0.5 blocks.
Other entities follows the standing block accurately.
At least 1.17.11, player followed the standing block accurately.Affected entity:
Player, Boat (that player is riding), Horse (that player is riding and saddle is equipped)Platform:
I confirmed this bug occurs in Win10 and Android at least.Versions since:
This bug started to occur between release versions 1.17.11 and 1.17.30.
Playerdoesn't follow the standing block pushed by pistonPlayers aren't dragged by moving block that they are standing
Players aren't accurately dragged by moving block that they are standing
Players aren't accurately dragged by moving block that they are standingPlayers are not accurately dragged by moving block that they are standing
When a piston pushes a block on which a player is standing, the player is left behind by about 0.5 blocks.
Other entities follows the standing block accurately.
At least 1.17.11, player followed the standing block accurately.
Affected entity:
Player, Boat (that player is riding), Horse (that player is riding and saddle is equipped)Platform:
I confirmed this bug occurs in Win10 and Android at least.Versions since:
This bug started to occur between release versions 1.17.11 and 1.17.30.Summary:
When a piston pushes a block on which a player is standing, the player is left behind by about 0.5 blocks.
Step to reproduce:
- Place piston or sticky-piston horizontally.
- Place any blocks horizontally so that it can be pushed by the piston.
- Get on top of the blocks.
- Activate the piston.
Observed result:
Player moves about 0.5 block toward pushed direction.
Expected result:
Player moves 1.0 block toward pushed direction.
Note:
Other entities follows the standing block accurately.
At least 1.17.11, player followed the standing block accurately.Affected entities:
Player, Boat (that player is riding), Horse (that player is riding and saddle is equipped)
Platform:
I confirmed this bug occurs in Win10 and Android at least.
Versions:
This bug started to occur between release versions 1.17.11 and 1.17.30.
Summary:
When a piston pushes a block on which a player is standing, the player is left behind by about 0.5 blocks.
Step to reproduce:
- Place piston or sticky-piston horizontally.
- Place any blocks horizontally so that it can be pushed by the piston.
- Get on top of the blocks.
- Activate the piston.
Observed result:
Player moves about 0.5 block toward pushed direction.
Expected result:
Player moves 1.0 block toward pushed direction.
Notes:
Other entities follows the standing block accurately.
At least 1.17.11, player followed the standing block accurately.Affected entities:
Player, Boat (that player is riding), Horse (that player is riding and saddle is equipped)
Platforms:
I confirmed this bug occurs in Win10 and Android at least.
Versions:
This bug started to occur between release versions 1.17.11 and 1.17.30.
Summary:
When a piston pushes a block on which a player is standing, the player is left behind by
about0.5 blocks.Step to reproduce:
- Place piston or sticky-piston horizontally.
- Place any blocks horizontally so that it can be pushed by the piston.
- Get on top of the blocks.
- Activate the piston.
Observed result:
Player moves
about0.5 block toward pushed direction.Expected result:
Player moves 1.0 block toward pushed direction.
Notes:
Other entities follows the standing block accurately.
At least 1.17.11, player followed the standing block accurately.Affected entities:
Player, Boat (that player is riding), Horse (that player is riding and saddle is equipped)
Platforms:
I confirmed this bug occurs in Win10 and Android at least.
Versions:
This bug started to occur between release versions 1.17.11 and 1.17.30.
Summary:
When a piston pushes a block on which a player is standing, the player is left behind by 0.5 blocks.
Step to reproduce:
- Place piston or sticky-piston horizontally.
- Place any blocks horizontally so that it can be pushed by the piston. (except honey block)
- Get on top of the blocks.
- Activate the piston.
Observed result:
Player moves 0.5 block toward pushed direction.
Expected result:
Player moves 1.0 block toward pushed direction.
Notes:
Other entities follows the standing block accurately.
At least 1.17.11, player followed the standing block accurately.Affected entities:
Player, Boat (that player is riding), Horse (that player is riding and saddle is equipped)
Platforms:
I confirmed this bug occurs in Win10 and Android at least.
Versions:
This bug started to occur between release versions 1.17.11 and 1.17.30.
Summary:
When a piston pushes a block on which a player is standing, the player is left behind by 0.5 blocks.
Step to reproduce:
- Place piston or sticky-piston horizontally.
- Place any blocks horizontally so that it can be pushed by the piston.
(except honey block)- Get on top of the blocks.
- Activate the piston.
Observed result:
Player moves 0.5 block toward pushed direction.
Expected result:
Player moves 1.0 block toward pushed direction.
Notes:
Other entities follows the standing block accurately.
At least 1.17.11, player followed the standing block accurately.Affected entities:
Player, Boat (that player is riding), Horse (that player is riding and saddle is equipped)
Platforms:
I confirmed this bug occurs in Win10 and Android at least.
Versions:
This bug started to occur between release versions 1.17.11 and 1.17.30.
Summary:
When a piston pushes a block on which a player is standing, the player is left behind by 0.5 blocks.
Step to reproduce:
- Place piston or sticky-piston horizontally.
- Place any blocks horizontally so that it can be pushed by the piston.
- Get on top of the blocks. (except honey block)
- Activate the piston.
Observed result:
Player moves 0.5 block toward pushed direction.
Expected result:
Player moves 1.0 block toward pushed direction.
Notes:
Other entities follows the standing block accurately.
At least 1.17.11, player followed the standing block accurately.Affected entities:
Player, Boat (that player is riding), Horse (that player is riding and saddle is equipped)
Platforms:
I confirmed this bug occurs in Win10 and Android at least.
Versions:
This bug started to occur between release versions 1.17.11 and 1.17.30.
Players arenot accurately dragged bymovingblockthat they are standingPlayers are left behind by Moving-blocks whose standing on
Summary:
When a piston pushes a block on which a player is standing on, the player is left behind by 0.5 blocks.
Step to reproduce:
- Place piston or sticky-piston horizontally.
- Place any blocks horizontally so that it can be pushed by the piston.
- Get on top of the blocks. (except honey block)
- Activate the piston.
Observed result:
Player moves 0.5 block toward pushed direction.
Expected result:
Player moves 1.0 block toward pushed direction.
Notes:
Other entities follows the standing block accurately.
At least 1.17.11, player followed the standing block accurately.Affected entities:
Player, Boat (that player is riding), Horse (that player is riding and saddle is equipped)
Platforms:
I confirmed this bug occurs in Win10 and Android at least.
Versions:
This bug started to occur between release versions 1.17.11 and 1.17.30.
Summary:
When a piston pushes a block
onwhich a player is standing on, the player is left behind by 0.5 blocks.Step to reproduce:
- Place piston or sticky-piston horizontally.
- Place any blocks horizontally so that it can be pushed by the piston.
- Get on top of the blocks. (except honey block)
- Activate the piston.
Observed result:
Player moves 0.5 block toward pushed direction.
Expected result:
Player moves 1.0 block toward pushed direction.
Notes:
Other entities follows the standing block accurately.
At least 1.17.11, player followed the standing block accurately.Affected entities:
Player, Boat (that player is riding), Horse (that player is riding and saddle is equipped)
Platforms:
I confirmed this bug occurs in Win10 and Android at least.
Versions:
This bug started to occur between release versions 1.17.11 and 1.17.30.
Summary:
When a piston pushes a block which a player is standing on, the player is left behind by 0.5 block lengths.
Step to reproduce:
- Place piston or sticky-piston horizontally.
- Place any blocks horizontally so that it can be pushed by the piston.
- Get on top of the blocks. (except honey block)
- Activate the piston.
Observed result:
Player moves 0.5 block toward pushed direction.
Expected result:
Player moves 1.0 block toward pushed direction.
Notes:
Other entities follows the standing block accurately.
At least 1.17.11, player followed the standing block accurately.Affected entities:
Player, Boat (that player is riding), Horse (that player is riding and saddle is equipped)
Platforms:
I confirmed this bug occurs in Win10 and Android at least.
Versions:
This bug started to occur between release versions 1.17.11 and 1.17.30.
Drowned spawns in blocklightDrowned spawns in block-light
Summary:
In 1.18.0 and after, Drowned seems to spawn in condition [sky-light<=7 && block-light<=7].
Since 1.18.0, I understand as that Hostile mobs spawn in [sky-light<=7 && block-light=0].
- Hostile mobs spawn only in areas where the light level is equal to 0. (This change affects only block-light and not sky-light.)
Surface mobs spawn only in areas where non block-light, as expected.
And in Java Edition, Drowned spawns in non block-light, too.Step to reproduce:
- Set time to daytime. (sky-light = 15)
- Prepare water 4 blocks in depth. (sky-light level of bottom of water = 15-2-2-2-2 = 7)
- Fill bottom of water with glow-lichen. (block-light level = 7)
Observed results:
Drowned spawns on bottom of water.
Expected results:
Drowned doesn't spawn. (because there are no blocks to fulfill the condition)
The conditions tested in this video were midnight, clear weather, River biome.
I also tested in other condition such as thunder, day, noon, Ocean biome, all with the same results.
Drowned_spawns_in_block-light.mp4
Affect 1.18.2
I confirmed that the extra "half a heart" is False health.
When player take damage after this issue, "True health value" is displayed until next natural regeneration.
("True health value" is affected by
MCPE-36131Taking damage is sometimes negated by natural regeneration.)For example, in situation of water drowning:
True health:
10 -> 9 -> 8 -> 7 -> 6 -> 6.5 (
MCPE-36131and 0.5 natural regenerated) -> 5.5 (1 damaged)Displayed health:
10 -> 9 -> 8 -> 7 -> 6 -> 7 (
MCPE-36131and 1 regenerated by this issue) -> 5.5 (True health is displayed by damaging)And I think "Players health naturally regenerates 1 heart every 4 second" is not exactly.
After this issue is started, stop taking damage. (As example, getting out of water)
Then, subsequent natural regenerations are half a heart every 4 second.
For example, in situation of water drowning:
True health:
10 -> 9 -> 8 -> 7 -> 6 -> 6.5 (
MCPE-36131and 0.5 natural regenerated) -> (stop drowning) -> 7 (0.5 natural regenerated)Displayed health:
10 -> 9 -> 8 -> 7 -> 6 -> 7 (
MCPE-36131and 1 regenerated by this issue) -> (stop drowning) -> 7.5 (0.5 natural regenerated)However, the first natural regeneration after "True health value" is displayed by taking damage, then "Players health naturally regenerates 1 heart" again.
This state finishes when natural regeneration is ended by low saturation.
True health:
6.5 (not under issue) -> 6 (0.5 damaged by something) -> 6.5 (0.5 natural regenerated)
Displayed health:
7 (under this issue) -> 6 (True health is displayed by damaging) -> 7 (1 regenerated by this issue again)
Additionally, I confirmed that this issue is not caused by "regeneration" status effect. It only causes
MCPE-36131.Affected 1.18.10
in beta (preview) v1.18.30.21, this issue is no longer reproduced.
beta (preview) v1.18.30.21
It seems this issue is no longer reproduced.
It seems to be fixed. Thank you!