Paper: Potion of Harming Dupe

Created on 10 Jul 2020  路  14Comments  路  Source: PaperMC/Paper

What behaviour is expected:

Upon drinking a potion of harming that would cause lethal damage, the player drops an empty bottle.
(In regular Minecraft this is glitched as well, but differently. The bottle stays in the inventory on death and disappears completely on respawn. This isn't much better but at least it doesn't create a dupe.)

What behaviour is observed:

If the players dies from drinking a potion of harming, they drop a duped potion of harming and keep the empty bottle in their inventory on death. When they respawn, they still have the bottle in their inventory.

Steps/models to reproduce:

Bring your health down low enough and drink a potion of harming that would cause lethal damage.

Plugin list:

EssentialsX
Multiverse/Multiverse-Inventories
Towny
Vault
WorldEdit
WorldGuard

Paper build number:

git-Paper-79 (MC: 1.16.1) (API version 1.16.1-R0.1-SNAPSHOT)

Anything else:

No additional information.

accepted

Most helpful comment

I'm leaving a comment to un-stale this issue as it still occurs, and the pull request that solves it has been marked at "ready for core".

All 14 comments

Multiverse/Multiverse-Inventories

No, it isn't. It occurs with MVInv disabled and I'm not teleporting between worlds when I respawn, which is the only time MVInv takes effect.

Reproduce on latest without plugins.

Still occurs.

Cannot reproduce on Paper-79

What did you do? 'Cause I've been able to consistently reproduce this glitch accross multiple versions.

Low health & drinking a Potion of Harming.

Did drinking the potion of harming kill you?

Yes

I was able to reproduce on latest. I found the problem in the code and will make a pull request later.

produced locally

Newer and better pull request has been made.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

I'm leaving a comment to un-stale this issue as it still occurs, and the pull request that solves it has been marked at "ready for core".

Was this page helpful?
0 / 5 - 0 ratings