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] Editing other player's inventories causes NPE #132

Closed
Draycia opened this issue Mar 15, 2020 · 2 comments · Fixed by #143
Closed

[Bug] Editing other player's inventories causes NPE #132

Draycia opened this issue Mar 15, 2020 · 2 comments · Fixed by #143

Comments

@Draycia
Copy link

Draycia commented Mar 15, 2020

Issue:
Using essentialsx's /invsee or openinv's /openinv to edit another player's inventory results in one of two different NPEs being thrown.

Errors:
https://pastebin.com/nk20jkaQ
https://pastebin.com/9uS4GxRu

Plugins:
Plugins (2): Essentials, Prism

Server:

[00:35:53 INFO]: This server is running Paper version git-Paper-135 (MC: 1.15.2) (Implementing API version 1.15.2-R0.1-SNAPSHOT)
[00:35:53 INFO]: Checking version, please wait...
[00:35:54 INFO]: Previous version: git-Purpur-489 (MC: 1.15.2)
[00:35:54 INFO]: You are running the latest version

Tested on java-13 and java-14.

Config is completely unchanged except for necessary MySQL settings.

@Draycia
Copy link
Author

Draycia commented Mar 15, 2020

Also, this primarily happens when placing items into the target's inventory, though I believe I have seen an NPE when picking up items.

Nothing is thrown when editing my own inventory whilst in /invsee however.

@Bobcat00
Copy link
Contributor

Bobcat00 commented Mar 30, 2020

Me too. This wasn't from /invsee, this was apparently a player accessing his enderchest.

https://pastebin.com/FNWpzrPu

addstar added a commit that referenced this issue Apr 27, 2020
Fix error when using /invsee (or similiar) - Fixes #132
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.

2 participants