-
Notifications
You must be signed in to change notification settings - Fork 19
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
Deadbolt requires a "players" directory #94
Comments
Can confirm this is so. Unfortunately, my players have already felt the negative effects of this issue. |
My users have also been affected by this issue. When any of them log off from the server their protections expire immediately instead of after 90 days resulting in widespread looting of their containers. A workaround until this issue is fixed is to disable the expiry date of protections by setting it to 0 in the configuration file. Hopefully a fix will be provided soon. |
Sounds like a bukkit bug with looking up players.also deadbolt won't work across name changes. |
By the way I should have mentioned I am using right now Spigot build #1453 and in-front of that I am using BungeeCord build #905. |
@md-5 I don't know about RenMX's issue, but my original report is not a bukkit bug, deadbolt looks for a "players" directory here: and the "players" directory has been renamed in 1.7.9, so this causes deadbolt to fail to start. |
@roastnewt The reason I replied in this thread is because I figured the bug you reported was applicable to my situation as I assumed that the reason it's not able to determine expiry dates for users is because it's looking in the wrong folder for the user files. |
Actually I've just experienced @RENMX 's issue too - but I guess that should be in a separate issue ticket :) |
As of 1.7.8, there is no "players" directory in the minecraft world folder (it's now playerdata or something). Deadbolt seems to depend on the players directory existing in order to work. This bug can be worked-around by making an empty directory titled "players."
The text was updated successfully, but these errors were encountered: