Pocketmine-mp: Various health-related bugs

Created on 14 Oct 2016  路  13Comments  路  Source: pmmp/PocketMine-MP

Issue description

  • [x] Double hit-animation when taking fall damage (not reproducible as of 1.0.0.16)
  • [x] Players taking fall-damage enough to kill them frequently do not have the "You died!" screen displayed, instead staying alive at zero hearts and recovering up to 1 heart.
  • [x] Hit-animation when players regain health (health should be set using attributes, not SetHealthPacket) (old client bug)
  • [x] Cancelling health regeneration doesn't seem to work (#157)
  • [x] No death animation when dying from fall damage (to other players you literally just vanish when you hit the ground)
  • [x] Changing a player's max health doesn't update client attributes (client bug?)

OS and versions

Client Gameplay Fixed

Most helpful comment

most bugs are related to the setHealthPacket now only used for killing players/(decreasing health).

All 13 comments

most bugs are related to the setHealthPacket now only used for killing players/(decreasing health).

Can anyone reproduce the double hit animation issue? I can't anymore.

3 is not reproducible as of 1.0.0.16.

Small bug. I don't think it's worth a separate issue. Anyways, I'm not off topic.
Player::setMaxHealth($amount) does not update until the player's health has changed (when Player::setHealth() is called)

Attributes issue, you can resend them manually if it's important to you.

Exactly what I'm doing right now.
Thanks, anyways!

@Muqsit I believe that is a client bug, the server-side code is perfect as far as I can tell. Similar issues can be seen on Realms with the XP bar not updating, so I think that's a client issue.

4 is due to client-sided health regeneration effects. This would require attribute resending when the regeneration is cancelled by a plugin.

4 has been reported to Mojang as https://bugs.mojang.com/browse/MCPE-20507 .

Just tested on 1.2 beta and 4 is still reproducible on it.

Read the comments. 4 is a client-sided bug, so there's nothing for us to do about it.

I know it was a client bug, I voted on it. Just got a bit confused sorry

6th was fixed in 1.2, tested.
A workaround for 1.1 clients is to Player::setHealth(Player::getHealth()) after changing the player's max health.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

MisteFr picture MisteFr  路  3Comments

JoshuaACasey picture JoshuaACasey  路  3Comments

nmo0ory picture nmo0ory  路  3Comments

dktapps picture dktapps  路  3Comments

Muqsit picture Muqsit  路  3Comments