Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Various health-related bugs #23

Closed
6 tasks done
dktapps opened this issue Oct 14, 2016 · 13 comments
Closed
6 tasks done

Various health-related bugs #23

dktapps opened this issue Oct 14, 2016 · 13 comments
Labels
Category: Client Related to Mojang client (usually client-caused bugs) Category: Gameplay Related to Minecraft gameplay experience Resolution: Fixed

Comments

@dktapps
Copy link
Member

dktapps commented Oct 14, 2016

Issue description

  • Double hit-animation when taking fall damage (not reproducible as of 1.0.0.16)
  • 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.
  • Hit-animation when players regain health (health should be set using attributes, not SetHealthPacket) (old client bug)
  • Cancelling health regeneration doesn't seem to work (Health regeneration still appears to occur when cancelled by plugins #157)
  • No death animation when dying from fall damage (to other players you literally just vanish when you hit the ground)
  • Changing a player's max health doesn't update client attributes (client bug?)

OS and versions

  • PocketMine-MP: 2fba107
  • PHP: doesn't matter
  • OS: doesn't matter
@dktapps dktapps added Category: Bug Category: Gameplay Related to Minecraft gameplay experience labels Oct 14, 2016
@robske110
Copy link
Contributor

robske110 commented Oct 14, 2016

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

@dktapps
Copy link
Member Author

dktapps commented Jan 9, 2017

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

@dktapps
Copy link
Member Author

dktapps commented Jan 9, 2017

3 is not reproducible as of 1.0.0.16.

@Muqsit
Copy link
Member

Muqsit commented Jan 9, 2017

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)

@dktapps
Copy link
Member Author

dktapps commented Jan 9, 2017

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

@Muqsit
Copy link
Member

Muqsit commented Jan 9, 2017

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

@dktapps
Copy link
Member Author

dktapps commented Jan 9, 2017

@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.

@dktapps
Copy link
Member Author

dktapps commented Mar 18, 2017

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

@dktapps
Copy link
Member Author

dktapps commented Mar 20, 2017

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

@dktapps dktapps added the Category: Client Related to Mojang client (usually client-caused bugs) label Mar 23, 2017
@buchwasa
Copy link
Contributor

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

@dktapps
Copy link
Member Author

dktapps commented Aug 11, 2017

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

@buchwasa
Copy link
Contributor

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

@Muqsit
Copy link
Member

Muqsit commented Sep 6, 2017

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.

@dktapps dktapps closed this as completed Jan 3, 2018
@dktapps dktapps added Resolution: Fixed and removed Status: Reproduced Bug has been reproduced, but cause has not yet been identified labels Jan 3, 2018
This was referenced Jul 13, 2019
@ghost ghost mentioned this issue Apr 11, 2020
@supercrafter333 supercrafter333 mentioned this issue Jun 7, 2020
@Lycol50 Lycol50 mentioned this issue Jun 8, 2020
@ghost ghost mentioned this issue Jul 19, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Category: Client Related to Mojang client (usually client-caused bugs) Category: Gameplay Related to Minecraft gameplay experience Resolution: Fixed
Projects
None yet
Development

No branches or pull requests

5 participants