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

[BUG] Lingering potions does not log properly #44

Open
TNTUP opened this issue Jul 3, 2022 · 0 comments · May be fixed by #46
Open

[BUG] Lingering potions does not log properly #44

TNTUP opened this issue Jul 3, 2022 · 0 comments · May be fixed by #46

Comments

@TNTUP
Copy link

TNTUP commented Jul 3, 2022

Describe the bug
Lingering potions when thrown and if the mob gets killed, it only logs who killed it but the name shown is "area effect cloud" which infact is normal but doesn't tell who thrown it to cause the entity to be killed. So it means we can't know who did that.

To Reproduce
Steps to reproduce the behavior:

  • Have Prism installed on the server and spawn a random mob enclosed in a room.
  • Give you a lingering potion (Instant Damage) then throw at the floor where the mob is.
  • Wait until it dies
  • Inspect it with /pr i or /pr lookup, you'll notice it will only say "area effect cloud killed (entity)" but nothing else will tell who thrown it for this cause.

Expected behavior
A clear and concise description of what you expected to happen.

Prism should tell us who thrown it and who killed it (infact its area effect cloud), logging both actions just in case.

Screenshots

  • If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem** via IMG

I used an alt to attempt killing the said entity (Pig), even checking at my alt's position nothing tells me who thrown it.
Server (please complete the following information):

  • Prism Version: 3.3.0
  • Server Type: [Paper]
  • Server Version: 1.18.2

Additional context
Add any other context about the problem here.

@Rothes Rothes linked a pull request Jul 6, 2022 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant