-
-
Notifications
You must be signed in to change notification settings - Fork 2
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
update dependencies #12
base: master
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for your PR updating it. The actual changes to the OpenInv loading logic seems solid as far as I can tell, will have to test it when I find the time (especially around the edge cases that the player retaining was supposed to help with in the past)
However you seem to have done a lot of changes that don't seem related to the functionality and are really only cosmetic. That makes reviewing it pretty hard as well as messes up the git history, I would advice using a minimal diff policy. Please revert those changes, if you want style changes/fixes then please do those in a separate PR.
56dff2a
to
79dce15
Compare
79dce15
to
8f7eee3
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good now. Thanks again! I will do some testing myself before merging though just to be sure it works in the different cases (don't want to risk people blindly updating to an untested version of such an essential plugin)
Updated the dependencies to the newest (1.20.6) version.
Most importantly is OpenInv with a change in its public API, where "retainPlayer" is now marked for removal.
I know the way I aggressively pushed everything to the newest versions probably means loading this version on older Spigot/Paper versions doesn't work, but since there is version indifferent reflection, loading it in the api defined 1.13 could have been broken anyway.