-
Notifications
You must be signed in to change notification settings - Fork 14
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
Every player login throws a Namecolor error #10
Comments
i had this error while testing the plugin originally, but updating the TAB version was what fixed it for me. Perhaps TAB updated? |
We're on the latest TAB 2.8.10. I assume you probably tested on Paper? Maybe it's an issue with Tuinity being slightly different |
well I find it quite odd it worked fine for ~4 days, and now it no longer works. indicates a potential plugin conflict or a modification or something |
It's been throwing errors since I put it on, just didn't get around to making an issue since it still works |
That's extremely odd, this wasn't present on testing. I'll look into this more sometime this week. |
There was an issue with the dependency scope, I've updated that and will check back tomorrow to see if the errors are still there |
The above pastebin was an error with Namecolor having TAB has a dependency but the scope wasn't explicitly provided in the pom, so I added that and it fixed that issue. However we are still getting the original issue, which is any player with no namecolor is throwing an error on login. This is because if you don't have a namecolor, your value is null, and the plugin cannot handle that and throws the error. |
thats a quick fix, i'll do it momentarily |
should be fixed if #11 is merged. |
https://pastebin.com/jTUDL6kT
@KaloHG could you take a look at this please ?
The text was updated successfully, but these errors were encountered: