-
Notifications
You must be signed in to change notification settings - Fork 43
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
TradePlus not working after updating to 1.16.5 #81
Comments
Hey, I literally paid $7.50 for this plugin, because it wasn't working. A reply would be nice. |
I will do some testing with latest releases of 1.16 and fix the issue soon.
Sorry for the inconvenience.
…On Mon, Aug 9, 2021, 11:20 AM Miles B Huff ***@***.***> wrote:
Hey, I literally just paid $7.50 for this plugin. A reply would be nice.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#81 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACW2LWTGCZ7W73ODCLR757TT3753DANCNFSM5BKTZ6GQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email>
.
|
Thank you! Worth noting: I'm on Java 16. I have a suspicion that that is why; but I'm unable to downgrade because some plugins require it now. |
Just updated to the latest version on the Spigot website. Plugin is still broken in exactly the same way. I paid you $7.50 to fix this half a year ago. What is going on, lol. Players are upset and there's nothing I can do. |
I paid for the plugin, and am running TradePlus v3.81.0. It does not work on my 1.16.5 Paper server. Players run
/trade
, and no trade window appears. Worse: players become frozen in-place, unable to move until they relog.The issue also occurred in version 3.79.2, which is the latest version available on GitHub; but players weren't frozen in-place.
The text was updated successfully, but these errors were encountered: