-
Notifications
You must be signed in to change notification settings - Fork 48
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
Error while loading #95
Comments
Never mind, with ProtocolLib it should be possible. |
And what do i do with this information ? |
Nothing, that's for @lucko. |
Okay. |
When will it be fixed ? |
When someone looks at it. Look at the open issues before this one. 😉 |
You can try an older version. This was bug was introduced in the latest commit. |
Ur right. Thank you. |
same issue on spigot 1.19.3 |
Try PaperSpigot instead of Spigot. |
Spigot 1.8.8
[ERROR] Error occurred while enabling BungeeGuard v1.3-SNAPSHOT (Is it up to date?)
java.lang.NoSuchMethodError: org.bukkit.Server$Spigot.getSpigotConfig()Lorg/bukkit/configuration/file/YamlConfiguration;
at me.lucko.bungeeguard.spigot.BungeeGuardBackendPlugin.onEnable(BungeeGuardBackendPlugin.java:57) ~[?:?]
at org.bukkit.plugin.java.JavaPlugin.setEnabled(JavaPlugin.java:321) ~[server.jar:git-Spigot-21fe707-741a1bd]
at org.bukkit.plugin.java.JavaPluginLoader.enablePlugin(JavaPluginLoader.java:340) [server.jar:git-Spigot-21fe707-741a1bd]
at org.bukkit.plugin.SimplePluginManager.enablePlugin(SimplePluginManager.java:405) [server.jar:git-Spigot-21fe707-741a1bd]
at org.bukkit.craftbukkit.v1_8_R3.CraftServer.loadPlugin(CraftServer.java:357) [server.jar:git-Spigot-21fe707-741a1bd]
at org.bukkit.craftbukkit.v1_8_R3.CraftServer.enablePlugins(CraftServer.java:317) [server.jar:git-Spigot-21fe707-741a1bd]
at net.minecraft.server.v1_8_R3.DedicatedServer.init(DedicatedServer.java:199) [server.jar:git-Spigot-21fe707-741a1bd]
at net.minecraft.server.v1_8_R3.MinecraftServer.run(MinecraftServer.java:525) [server.jar:git-Spigot-21fe707-741a1bd]
at java.lang.Thread.run(Thread.java:748) [?:1.8.0_312]
The text was updated successfully, but these errors were encountered: